Vendors and consultants use the same words to mean different things. Taxonomy to one is schema to another. Metadata to one means tags, to another means rights, to a third means the whole structure. Operators who use precise terms get clearer answers and produce documentation their successors can actually use.
These are the 20 terms every working DAM practitioner needs. Plain definitions, what they actually mean in operation, and what to watch for.
Foundations
Asset
A file plus the rights and metadata that describe it. A JPEG on a drive is a file. A JPEG in your DAM with title, description, rights, and usage history is an asset. The distinction matters because vendors price by asset count.
Metadata
Structured information about an asset. Falls into four buckets: descriptive (title, keywords), administrative (creator, date), rights (license, expiration), and technical (file format, dimensions). Good metadata is the foundation everything else rests on.
Taxonomy
The controlled vocabulary your team uses to describe assets. Not the same as folder structure. A taxonomy might say campaign: spring-2026 or product: model-x. When vendors say taxonomy they usually mean the structure, when they say vocabulary they mean the allowed values.
Schema
The shape of your metadata. Which fields exist, which are required, what type of data goes in each. A schema can change without changing the taxonomy values, and vice versa.
Controlled vocabulary
The list of allowed values for a metadata field. Free-text fields drift; controlled vocabularies stay clean. A Region field with a controlled vocabulary will have exactly the regions you defined, not EMEA, Emea, and Europe, Middle East, and Africa all coexisting.
Operations
Ingestion
The process of getting an asset into the DAM. Bulk ingestion is one-time imports; ongoing ingestion is the daily flow from creators and partners. The ingestion workflow is where most metadata quality is won or lost.
Workflow
The steps an asset moves through from creation to publication to expiration. Vendors will show you visual workflow builders; the question to ask is what your real-world workflow looks like, not what is theoretically possible.
Approval
A workflow step where a person or process gates an asset before it can be used. Approval chains are where bottlenecks live. The teams that solve approval problems do not add reviewers, they remove the decisions that did not need a person looking at them.
Lifecycle
The full arc of an asset from ingestion to archive or deletion. Programs that manage lifecycle deliberately end up with cleaner libraries; programs that do not end up with files that should have expired five years ago.
Governance
The rules and processes that keep the library consistent over time. Governance is what separates a DAM that works after two years from one that has drifted into chaos.
Rights and usage
Rights metadata
Information about what you can do with an asset, where, and for how long. Includes licenses, model releases, talent contracts, and usage restrictions. Required for any asset used externally; useful for any asset at all.
Usage rights
The actual permissions for an asset: which channels, which geographies, which dates. Often confused with rights metadata, which is the storage; usage rights are what the storage describes.
Embargo
A date before which an asset cannot be published. Common with product launches and PR.
Expiration
A date after which an asset can no longer be used. Common with licensed photography and talent contracts.
Distribution
Rendition
A version of an asset at a specific size, format, or crop. The master is the original; renditions are the derivatives produced for different use cases. Modern DAMs generate renditions on-demand instead of pre-rendering all variants.
CDN (content delivery network)
Edge servers that cache and serve assets globally. Most DAMs ship with built-in CDN delivery for public-facing assets.
Embed
Pulling an asset into another system (CMS, email, slide deck) by reference instead of by copy. Embedded assets stay in sync with the DAM; copied assets do not.
Platforms and integrations
Headless DAM
A DAM accessed primarily through APIs, designed to feed multiple front-end channels rather than be a destination itself. Common for teams building custom content delivery infrastructure.
Brand portal
A public-facing view onto a subset of the DAM, usually for partners or distributors. Brand portals show curated assets without giving outsiders access to the full library.
iPaaS (integration platform as a service)
Middleware that connects the DAM to other systems. Examples: Workato, Zapier, Tray. iPaaS lets you wire DAM events to other tools without custom code, but it adds another vendor relationship to maintain.