Reference Glossary
Controlled vocabulary
A predefined, managed list of approved terms that catalogers select from when tagging assets, instead of typing free-text keywords, so the same concept is always recorded the same way.
Why it matters in a DAM
Free-text keyword fields fragment over time — the same product photographed by three different people ends up tagged "sofa," "couch," and "settee," and a search for any one of them misses the other two-thirds of relevant assets. A controlled vocabulary fixes the label a search index actually queries, which is what makes faceted filtering and saved smart collections behave predictably instead of degrading as more people tag more assets.
A worked example
Common mistake
Teams build a controlled vocabulary once at DAM launch and never assign anyone to govern additions — when a cataloger needs a term that isn't on the list, they type a close variant into a free-text field instead, and within a couple of years the "controlled" vocabulary is running alongside an uncontrolled shadow one nobody planned for.
The formal guidance for building controlled vocabularies in English-language information systems is ANSI/NISO Z39.19, first issued in 1974 and most recently revised in 2005. The 2005 revision broadened its scope beyond library thesauri to cover simple term lists, synonym rings, taxonomies, and full thesauri alike, and it’s the standard most enterprise cataloging and DAM implementations reference — even informally — when deciding how to structure preferred terms, synonyms, and hierarchical relationships.
Controlled vocabularies range in complexity from a flat picklist (a fixed dropdown of department names) to a full thesaurus with preferred terms, non-preferred synonyms that redirect to them, and explicit broader/narrower/related-term relationships. Most DAM platforms implement the simple end of that range natively — a managed keyword or category field backed by an editable term list — and require a separate taxonomy management module or third-party thesaurus tool for the fuller relationship structure.
The distinction from a taxonomy is worth keeping straight: a controlled vocabulary constrains which words are valid for a field, while a taxonomy organizes those (or other) terms into a browsable parent-child hierarchy. The two are often built together but solve different problems — one is about consistency, the other about navigation.
Frequently asked
What is a controlled vocabulary in a DAM?
A predefined, managed list of approved terms that catalogers select from when tagging assets, instead of typing free-text keywords, so the same concept is always recorded the same way.
Why does free-text tagging cause problems over time?
Free-text keyword fields fragment — the same product photographed by three different people ends up tagged 'sofa,' 'couch,' and 'settee,' and a search for any one of them misses the other two-thirds of relevant assets.
What DAM features actually depend on a controlled vocabulary working correctly?
Faceted filtering and saved smart collections depend on it — a controlled vocabulary fixes the label a search index actually queries, which is what makes those features behave predictably instead of degrading as more people tag more assets.
What's the most common way a controlled vocabulary breaks down?
Teams build it once at DAM launch and never assign anyone to govern additions. When a cataloger needs a term that isn't on the list, they type a close variant into a free-text field, and within a couple of years the 'controlled' vocabulary is running alongside an uncontrolled shadow one nobody planned for.
Does a controlled vocabulary need ongoing management to stay useful?
Yes — without a governance owner responsible for reviewing and adding terms, catalogers route around the list whenever it doesn't cover their need, which is exactly what erodes its value over time.
How does a controlled vocabulary differ from a taxonomy?
A controlled vocabulary is a flat, approved list of terms for tagging; a taxonomy adds hierarchical parent-child structure on top of categories, letting users browse broader-to-narrower rather than just selecting a fixed label.
Sources
- ANSI/NISO Z39.19, first presented in 1974, was most recently revised in 2005 to cover term lists, synonym rings, taxonomies, and thesauri checked 2026-08-07 — NISO, ANSI/NISO Z39.19-2005 (R2010)