Reference Glossary
Tag vs category
Tags are free-form, often user-added keywords with no hierarchy; categories are a controlled classification an asset is deliberately assigned to, usually from a fixed, governed list.
Why it matters in a DAM
Uncontrolled tags cause duplicate and near-duplicate terms — "dog," "dogs," "canine" — that fragment search results and make faceted filtering unreliable, while categories from a controlled vocabulary guarantee everyone searching "Apparel" retrieves the same governed set. Mature DAM taxonomies typically run both together deliberately: categories for the fixed browse structure, tags for supplementary, flexible description.
A worked example
Common mistake
Letting every contributor free-tag uploads without a shared vocabulary produces, within months, dozens of near-duplicate tags for the same concept and makes faceted search unreliable — the fix is a moderated tag list or auto-suggest drawn from existing tags, not disabling tagging altogether.
A tag is a free-form keyword anyone can add at upload or afterward, with no required relationship to other tags. A category is a controlled classification an asset is deliberately placed into, usually chosen from a fixed, governed list that a librarian or metadata rule maintains rather than something a contributor invents on the spot.
The practical consequence is search reliability. Tags are useful precisely because they’re flexible and cheap to add, but that same flexibility means the same concept accumulates near-duplicate spellings and synonyms over time — “dog,” “dogs,” “canine” — which fragments what should be one search result into three partial ones. Categories avoid this because everyone is choosing from the same fixed list, so filtering by “Apparel > Outerwear” returns a consistent, complete set every time.
Most working DAM taxonomies use both deliberately rather than choosing one: categories carry the load-bearing browse structure that has to stay consistent, while tags add supplementary, informal description that would be too costly to govern as strictly. The common mistake is treating tagging as unlimited and ungoverned from day one, which is fine at small scale and becomes a search-quality problem once a few hundred contributors have each added their own version of the same idea.
Frequently asked
What's the fundamental difference between a tag and a category?
A tag is a free-form keyword anyone can add with no required relationship to other tags. A category is a controlled classification chosen from a fixed, governed list that a librarian or metadata rule maintains, not something a contributor invents on the spot.
Why do uncontrolled tags cause search problems over time?
The same concept accumulates near-duplicate spellings and synonyms -- "dog," "dogs," "canine" -- which fragments what should be one search result into several partial ones, making faceted filtering unreliable.
Why do categories return more consistent search results than tags?
Because everyone chooses from the same fixed list, so filtering by something like "Apparel > Outerwear" returns a consistent, complete set every time, unlike tags where wording varies contributor to contributor.
Should a mature DAM taxonomy use tags or categories?
Both, deliberately -- categories carry the load-bearing browse structure that has to stay consistent, while tags add supplementary, informal description that would be too costly to govern as strictly.
What's the fix for a tagging system that's become unreliable?
A moderated tag list or auto-suggest drawn from existing tags -- not disabling tagging altogether, since the flexibility of tags is still valuable when a shared vocabulary keeps them from fragmenting.
Who typically assigns categories versus tags?
Categories are usually assigned by a librarian or through rules-based assignment, while tags can be added by any contributor at upload or afterward.