Functional Debate: Categories vs. Tags

Several days ago (or more, seeing how long it actually took me to get this finished, whoopsie), Twitter user @stomer brought up a question to the Twitterverse regarding a common tool we use any time we work in social media these days:  “This a fair description?: categories are like table of contents items, tags are more granular like items that would be in index?“  I happened to be on right when this hit the feed, and replied: “Categories are for organizing, tags are for identifying.“  It was a simple exchange which prompted a third comment from @jdwcornell asking for some expansion on this idea, to which I am happy to oblige.

categories v tags Functional Debate: Categories vs. TagsCategories and tags are two functional elements that many of us who use things like blogs, Flickr, YouTube, or many content management systems are familiar with using on a day to day basis.  It’s easy for us to see how they work and what they are for because we have such a high level of exposure to them.  But that’s us.  I know that I’ve found myself on more than one occasion explaining the tag cloud on our university’s home page.  These systems are very smart, and apply these things in cool ways, but users can tend to be, well, not so savvy.  To some people, functionally, they seem very similar, which is exactly why I came up with my simple description that categories are an organizational tool while tags are for item identification.  Generally this helps people get over the hump of understanding them.  YouTube does a pretty good job of exemplifying this, where they have just over a dozen categories (like “Pets & Animals”) that you choose from, and then a blank field where you could freely tag a video (like “dog, boxer, barking, trick”).  The first tells you where it goes, the second tells you what’s in it.  Flickr lets you tag photos as well, and you categorize them through the use of sets.  In that case, you get to name the sets (as opposed to YouTube where they are predefined by them), but they are basically serving as a category the same as anywhere else.

In our case, we use both categories and tags in the university CMS (we use dotCMS).  When a user creates content for the university in the content management system, we ask them to do both of these things.  The first question that usually follows is: “What?”  This is quickly followed by the second question: “Huh?”  In all fairness, I can’t blame them on this.  Both of these fields can be used on the front end of the web site (or not, depending on what it is), but we also use them in the CMS to enhance internal searching for content.  Under this setup, categories form the basic structure of the college: office names, departments, organizations.  Tags then allow specificity in identification.  The result of this is searching for content categorized as the “Admission Office,” and then tagged with “checklist,” or “forms.”  Or if you needed more generic information, you could search for content tagged as “contact information” and pull it from all the areas, or categories.  This exposes the idea that the tags are simply identifying what is in the content.  We use a similar mechanism for the calendar, categorizing by area, and tagging by topics.  Then, any department or office can get a customized event feed of their category, or more general areas can pull from them all by tags.  Seeing this type of stuff in action usually really helps people understand the difference when they didn’t before.

To make further comparisons, categories are kind of like folders.  They are designed to help users located related content based on the implied relationship of the category name, usually based on a theme or topic.  Generally, categories are predefined by some kind of administrator ahead of time, and aren’t added willy-nilly.  For instance, there’s the “Admission Office” category in our CMS.  It’s there in a list for the contributor to select from when they make content, and so they couldn’t make a new category called “Admissions Office” or “Undergrad Admission Office.”  They are bound to what we have set up.  This makes them useful for building things off of because they are predictable and structured.

Tags are almost never preset like that.  Instead of folders, these would be like contextual post-it notes you stick on papers in the folder.  You might agree on a policy to use some kind of convention (like always pluralize words, never capitalize, don’t include spaces, etc…), but generally there are no restrictions on their use, and authors can create and assign them during authorship of content without any extra help.  In many ways, tags are a type of visible meta information, and you will hopefully break out a thesaurus if using them well.  Not to confuse the matter, but it is possible to also create tags that can serve the purpose of categories, a kind of “super tag,” if you will (but it would rely on use of a convention to function properly).  That kind of functionality will normally depend on your infrastructure, but the idea is that a tag, in a way, is basically a type or subset of categories.  But they tend to be much more fluid and less predictable than categories.  I could pull information based on the tag “student,” for example, but at the risk of missing stuff tagged “students,” or if you have the ability you could use the tag “student” to match things like “student employment,” “student events,” “student groups,” etc…  In this way they are less useful functionally, but far more useful in identifying, connecting, and relating items.  And looking at the big picture, properly implemented tags get picked up by sites like Technorati to help identify and group similar information from thousands of web sites on a macro level (for more information on this, take a look at the rel=”tag” microformat).

So there you go - categories organize, tags identify.  Ultimately, their basic function and usage might change depending on what you’re using them in (a blog, Flickr, a CMS, etc…), but that basic principle will generally always stay the same no matter where you are.  When users question their function, try to give them a simple example to go off of.  If they don’t get it in our CMS at first, I tend to find refering to Flickr and YouTube to be nice examples that everyone seems to get.  For more information on the discussion, I recommend the Categories vs. Tags articles at Haacked, or Usability Post.

8 Responses to “Functional Debate: Categories vs. Tags”

  1. Says:

    I think this is mostly sound, but let me suggest that at the core, this distinction is largely arbitrary and bound to a specific platform or product. I think the original question was directed at WordPress. Other CMSes may not frame it the same way. Me? I think they are ontologically the same and the distinction arises from our functional choices. That said, blog ‘tags’ and ‘categories’ seem to be a universally accepted paradigm; and as you suggest, use categories to put things in big buckets, use tags to freely identify items.

  2. Says:

    I think what you are proposing is the ideal way it should work, but Ernest hit the nail on the head regarding platforms. That may be where some of the confusion lies.

    For instance our Movable Type system has options for categories and tags but they all end up in pretty much the same place. When posting an entry I can put something in either the category or the tag field and it will create a new category. (These all then get listed as tags as the bottom of my posts.)

    Despite this there is still a way to impose the structure you suggest. On our Community Outreach site I configured these to be primary and secondary categories. When you look at the Categories index you will see that the secondary ones (tags) are indented. In this way we can even include our 5 core categories in our menu, like the TOC you describe. The trick in our system is just to go to the categories control panel and make sure and secondary tags are assigned to a parent category.

    So while systems and nomenclature may vary, I think from a structural standpoint your framework recommendation can be a great navigational aid for users.

  3. Says:

    In my experience, the question of categories vs. tags or vice-versa doesn’t really arise unless there is some major re-org of the blog, such as a blog migration from one platform to another. In the end, its good practice to review both categories and tags and see if they are truly relevant to the site.

  4. Says:

    I agree, good practice is to review both categories and tags to effectively sort your data (whether it be a blog, a picture database or video database). I also think this is common sense because it can categorized something and then to sort within the category you can use tags… Regards!

  5. Says:

    Tags for a blog site is also good for automated content such as “related articles.” This way, you don’t have to manually type it up. It can be done with categories too, however not as accurate since two articles on the same topic may have totally different word choice in the title.

  6. Says:

    I like the “folders” and “postit notes” analogy. So it follows that an article would generally only have one category (a physical page can only be in one folder) but you can stick lots of notes (tags) to it.

  7. Says:

    One of the interesting things I’ve noted so far as tags go is that Google seems to love them. I have a number of niche marketing blogs and often the tag page will rank higher than the actual post(s).


  1. Categories vs tags - katagorier kontra nøgleord « --> says:

    [...] Dot eduGuru: [...]