A taxonomy is a hierarchical classification scheme: a tree of categories, from broad to narrow, used to organize assets consistently. "Products → Furniture → Chairs → Office chairs" is a taxonomy path; every asset filed under "Office chairs" is automatically part of "Furniture" too.

Taxonomies matter in a DAM because they give browsing a predictable shape. Search answers "find me this specific thing"; a taxonomy answers "show me what exists in this area." When a new team member opens the library, the taxonomy is the map — it tells them how the organization thinks about its own content. It also powers rollups: a filter on a parent category includes everything beneath it, so "all Furniture imagery" works without tagging each asset at every level.

The common failure mode is building the tree too deep, too early, around how one department is structured today. Good taxonomies stay shallow, reflect how people actually look for things rather than the org chart, and evolve as the content does. A useful test: if most branches hold fewer than a handful of assets, the tree is more elaborate than the library needs. Taxonomies also work best alongside flat tags — the hierarchy carries the stable, structural dimensions (product family, region, asset type), while tags carry the ad-hoc ones.

In freedam, taxonomies are built as tree-structured controlled vocabularies, so hierarchical terms are managed centrally and applied consistently across the library.

Related terms: Controlled Vocabulary, Metadata