PicaJet

Reference Glossary

Taxonomy governance

Taxonomy governance is the ongoing process of defining, maintaining, and controlling the vocabulary and category structure used to tag assets, including who may add new terms.

Why it matters in a DAM

A DAM's search and filtering only work as well as the consistency of its tags. If several people can each free-type a new tag for the same concept, search results for that concept split across all the variants, and nobody using standard search finds everything relevant. Governing the taxonomy — who can add terms, how synonyms get merged, how the hierarchy evolves — is what keeps tagging usable as the library and the team both grow.

A worked example

Controlled vocabulary Approved term list or hierarchy that tagging must draw from
Term request process How a user proposes a new tag and who approves it before it enters the vocabulary
Synonym handling A preferred term plus mapped synonyms, so alternate phrasing still resolves to one tag
Review cadence Periodic audit for duplicate, unused, or inconsistent tags

Common mistake

Teams leave tagging fully open so any user can free-type new tags, and the library ends up with near-duplicate variants of the same concept — 'trade show,' 'Trade Show,' 'tradeshow' — that fragment search results across what should be one tag.

Taxonomy and taxonomy governance are different things: the taxonomy is the vocabulary and category structure itself, while governance is the process that keeps it from drifting into inconsistency as more people add tags over time. A well-designed taxonomy on day one still degrades without governance, because usage patterns and content change faster than any fixed vocabulary anticipates.

The most visible symptom of missing governance is synonym sprawl: the same concept tagged multiple slightly different ways by different contributors, none of them technically wrong, all of them fragmenting search for anyone who does not happen to search using the exact variant a given asset was tagged with. Merging those after the fact is far more expensive than preventing them with a controlled vocabulary and a term-approval step in the first place.

Governance does not have to mean fully locking down tagging to a fixed list; many DAMs support a hybrid model where users can suggest new terms, but those terms sit in a pending state until someone responsible for the taxonomy reviews and either approves them into the controlled vocabulary or maps them to an existing term.

Frequently asked

What's the difference between a taxonomy and taxonomy governance?

A taxonomy is the vocabulary itself — the fixed set of categories, terms, and hierarchy relationships used to tag assets. Taxonomy governance is the ongoing process layered on top of it: deciding who can add new terms, how synonyms get merged, and how the hierarchy changes as the asset library grows. Without governance, even a well-built taxonomy drifts into inconsistency as more contributors tag independently over time.

What's the most visible symptom of missing taxonomy governance?

The clearest symptom is synonym sprawl: near-duplicate tags like 'trade show,' 'Trade Show,' and 'tradeshow' all describing the same concept, created independently by different contributors with no one merging them. Each variant collects its own subset of assets, so search results for that concept fragment across multiple tags instead of pooling under one. Anyone searching with the 'wrong' variant misses assets tagged with the others.

Why does open, free-type tagging tend to break DAM search over time?

Free-type tagging lets every contributor invent their own wording for the same concept — synonyms, capitalization differences, plurals, abbreviations, and outright typos all become separate tags. Search treats each variant as a distinct term, so a query only returns assets tagged with that exact string. As the library grows and more people tag independently, the variants multiply, and no single search reliably surfaces everything relevant to a concept.

Does taxonomy governance require fully locking tagging down to a fixed list?

No — many DAMs use a hybrid model where users can suggest new terms, but those terms sit pending until someone responsible reviews and approves or maps them to an existing term.

Why does a well-designed taxonomy still need ongoing governance after launch?

A taxonomy built at launch reflects the products, categories, and terminology that existed at that moment. Usage patterns and content change faster than any fixed vocabulary anticipates: new product lines, campaigns, or categories emerge over time, and contributors need new terms to describe them. Without a governance process for reviewing and approving those additions, teams either work around the taxonomy with free-type tags or let it fall out of date.

How does synonym handling work in a governed taxonomy?

In a governed taxonomy, each concept has one preferred, canonical term, and alternate phrasings — synonyms, misspellings, regional variants, or abbreviations — are mapped to it as aliases. When a contributor tags or searches using an alias, the system resolves it to the canonical term automatically, so all assets end up under one consistent tag regardless of which wording was typed. This keeps search complete without forcing every user to know the exact preferred term.