Short answer
A taxonomy is a hierarchical classification that groups assets into categories and subcategories. DAM taxonomies work best as several independent facets. DAMSelection rule of thumb: keep each facet to three or four levels, because every extra level adds a click before a user reaches assets and another node someone must maintain.
How a taxonomy works in a DAM
A taxonomy works in a DAM as a tree of parent and child values attached to one metadata field. Users tag an asset with the most specific value, and the DAM infers its parent values.
DAM taxonomies serve three jobs:
- Browse: users open a branch and see every asset in it and its sub-branches.
- Filter: the taxonomy feeds a facet in faceted search.
- Govern: permissions and workflows follow a branch, such as one brand.
A DAM usually runs several small taxonomies side by side. Brand, asset type, channel, region and campaign each form their own facet. The table shows why that structure beats one large tree.
| Design | Asset in two categories | Change one dimension | Search experience |
|---|---|---|---|
| One large tree | Duplicate or pick one branch | Rebuild many branches | Deep clicking |
| Several facets | Multi-select within each facet | Edit one facet | Combine filters freely |
Example of a taxonomy
Worked example: a homeware brand uses Brand > Product line > Product as one facet among others. Asset type, channel and season sit in separate facets.
A lifestyle photo shows two products from different product lines. The editor selects both products in the product facet, and the DAM places the photo under both lines. In a single folder tree, the same photo needs two copies or one arbitrary location.
Taxonomy in a DAM selection
A taxonomy is designed at Checkpoint 2: Define, as part of the metadata model. DAMSelection assessment: the metadata model decides DAM success, so send your taxonomy to vendors before the first demo.
Ask each vendor to show these points at Checkpoint 5: Test:
- Import your taxonomy with three levels from a CSV file.
- Tag one asset with two values in the same facet.
- Move a node to a new parent and confirm tagged assets follow.
- Sync the product hierarchy from your PIM through the API.
- Show labels in Dutch, German and English for the same node.
The DAM taxonomy guide covers facet design. The metadata model builder captures each facet with its owner.
Common taxonomy mistakes
The most common taxonomy mistake is mirroring the organisation chart, which changes at every reorganisation. Other recurring errors:
- One deep tree that mixes brand, asset type and season.
- A product hierarchy typed by hand in the DAM while the PIM already holds it.
- Catch-all branches such as 'Other' or 'Misc' that grow faster than real branches.
- No owner or change process, so nodes multiply after go-live.
Related terms: Ontology, Faceted search, Controlled vocabulary.
Frequently asked
What is the difference between a DAM taxonomy and folders?
A DAM taxonomy is metadata, so one asset can sit in several categories at once. A folder holds one physical location per file. Taxonomies also feed filters, permissions and integrations, while folders only group files for browsing.
Should the DAM taxonomy match the PIM product hierarchy?
The DAM product facet should reuse the PIM product hierarchy through an integration. DAMSelection assessment: DAM and PIM form one product content supply chain, so one shared data model avoids two hierarchies that disagree. Brand, channel and asset type facets stay owned by the DAM.