Glossary

Digital Asset Management Glossary

The DAM vocabulary, defined in plain language

Digital asset management runs on a vocabulary that gets used loosely, and the same word often means two different things in two different rooms. This glossary defines the terms the way we use them on client projects: plain language, no vendor spin, with a link to deeper reading where we have written more about it.

Stacks is a digital asset management consultancy in Nashville. We help teams build DAM programs that hold up after launch. If a term you need is missing here, email info@stacksteam.com and we will add it.

All terms

Adoption · AI (Artificial Intelligence) · Asset Approval · Brand Portal · Buy-In · Cloud-Based DAM · Content Management System (CMS) · Controlled Vocabulary · DAM Health Score · DAM Maturity · DAM Platform · DAM Program · Digital Asset · Digital Asset Management (DAM) · Digital Rights Management (DRM) · Embedded Metadata · Enrichment · Folderless DAM · Governance · Integration · Keywords · Licensing · Metadata · Migration · On-Premise Software · Permissions · Product Information Management (PIM) System · Rendition · Single Source of Truth · Taxonomy · Upload · Upstream and Downstream Workflows · Version Control · Workflow

Adoption

The share of intended users who actually use the DAM as part of their normal work, and how deeply they use it. Adoption is the number most DAM programs live or die on, because a well built library nobody opens returns nothing.

AI (Artificial Intelligence)

In a DAM context, AI usually means automated tagging, visual search, transcription, and generated descriptions applied to assets at scale. It is a force multiplier on good metadata practice, not a replacement for it. AI pointed at a library with no taxonomy produces tags nobody trusts.

Asset Approval

The review step that moves an asset from draft to cleared for use, with a named approver and a recorded decision. Approval is what makes "is this the right file" answerable without asking anyone.

Brand Portal

A curated view into a DAM that shows one audience only the assets and guidelines they are cleared to use. Agencies, retail partners, franchisees, and press are the usual audiences.

Buy-In

Documented agreement from the leaders and teams whose work the DAM will change, secured before the platform is bought. Buy-in is a prerequisite, not a launch activity. Programs that skip it end up with a system one department uses.

Cloud-Based DAM

A DAM hosted and maintained by the vendor and reached through a browser, billed as a subscription. The buyer gives up server level control and gets continuous updates, vendor managed uptime, and no hardware to replace.

Content Management System (CMS)

The system that builds and publishes web pages. A CMS manages content in the context of a page. A DAM manages the source files those pages use, independent of where they get published. Most organizations need both, connected.

Controlled Vocabulary

A fixed, approved list of the exact terms allowed as metadata values, so one concept has one spelling. Without it, the same product photo gets tagged sneaker, shoe, trainer, and footwear by four people, and none of them can find each other's work.

DAM Health Score

A periodic, scored assessment of how a DAM program is performing across dimensions like metadata quality, adoption, governance, and workflow, used to decide where the next cycle of effort should go.

DAM Maturity

A staged model describing how far a DAM program has developed, from ad hoc file storage through to a governed, measured, business critical system. Maturity models are most useful for locating your actual starting point honestly.

DAM Platform

The software product itself. The platform is the smaller half of the decision. The program around it, meaning the people, standards, and workflows, is what determines whether the platform pays off.

DAM Program

The whole operation around a DAM: the people who own it, the standards they enforce, the workflows that feed it, and the measurement that proves it works. A platform is bought. A program is built.

Digital Asset

A file with rights, context, and business value attached. A photo sitting on a laptop is a file. The same photo with a known owner, a usage license, a shoot date, and product metadata is a digital asset.

Digital Asset Management (DAM)

The practice, and the software, of storing, describing, finding, controlling, and distributing an organization's digital files from one governed source.

Digital Rights Management (DRM)

The controls that track and enforce what an organization is legally allowed to do with an asset: who owns it, where it can run, and when the permission expires.

Embedded Metadata

Metadata written inside the file itself, in standards like IPTC, EXIF, and XMP, so it travels with the file when it leaves the DAM. Custom metadata, by contrast, lives in the DAM database and does not survive a download unless the platform writes it in on export.

Enrichment

Adding metadata, keywords, rights information, and context to assets that arrived without them. Enrichment is the work that turns an archive you can browse into a library you can search.

Folderless DAM

A DAM organized entirely by metadata and saved searches rather than a nested folder tree. Every asset can appear in every relevant view at once, which removes the "which folder does this go in" problem and replaces it with a taxonomy problem.

Governance

The written rules for who can do what in the DAM, who decides when the rules change, and how the rules get enforced. Governance is what keeps a library from drifting back into chaos six months after launch.

Integration

A connection between the DAM and another system, such as a CMS, PIM, e-commerce platform, or creative tool, so assets and metadata move between them without anyone downloading and re-uploading files.

Keywords

The searchable terms attached to an asset. Keywords work when they come from a controlled vocabulary and fail when every user invents their own.

Licensing

The terms defining how, where, and for how long an asset may be used, and by whom. Licensing data belongs on the DAM record, not in a contract folder somewhere else, because the person about to use the asset is the person who needs to see it.

Metadata

The information about an asset that makes it findable and usable: what it shows, who made it, when, for what, and under what rights. Metadata is the product in digital asset management. The files are the payload.

Migration

Moving assets and their metadata out of an old system, shared drive, or archive and into a new DAM. The files are the easy part. Mapping old metadata to a new taxonomy, and deciding what not to bring, is the actual project.

On-Premise Software

Software installed and run on servers the organization owns and maintains, rather than hosted by the vendor. On-premise DAM gives full control over data residency and security posture, and puts upgrades, uptime, and hardware back on the buyer.

Permissions

The rules controlling which users and groups can view, download, edit, or publish which assets. Permissions are where governance stops being a document and becomes something the software enforces.

Product Information Management (PIM) System

The system of record for product data: SKUs, specs, descriptions, pricing, and category assignments. A PIM holds what a product is. A DAM holds what it looks like. Connected, the two populate a product page without anyone copying and pasting.

Rendition

A derivative version generated automatically from an original, such as a web sized JPEG from a print resolution TIFF, or a cropped social format. Renditions let one approved master serve every channel.

Single Source of Truth

One system holding the current, approved version of an asset, so nobody has to choose between four copies with similar filenames. It is the point of a DAM, and it only holds if governance keeps competing copies out.

Taxonomy

The structured system of categories and terms that organizes a DAM so people can find assets by browsing and filtering instead of guessing keywords. Taxonomy is the shape of the library. It is not the same thing as a folder structure, and on modern platforms it usually replaces one.

Upload

Adding a file to the DAM. In a governed program, upload is not a drag and drop. It is an ingest step with required metadata, a rights check, and a destination set by the taxonomy, which is why bulk uploads are usually run as a migration.

Upstream and Downstream Workflows

Upstream is everything that happens before an asset lands in the DAM: briefing, creation, review, approval. Downstream is everything after: distribution, publishing, reuse, and reporting. Plenty of DAM programs are bought to fix downstream and stall because upstream was never addressed.

Version Control

Keeping every revision of an asset attached to one record, with a clear current version, so old files stop circulating. Version control is a lot of the difference between a DAM and a very tidy shared drive.

Workflow

A defined sequence of steps an asset moves through, with an owner and a handoff at each step. Workflows are what make a DAM operational rather than archival.

Need help applying any of this?

Knowing the vocabulary is the easy part. Building a taxonomy your team will actually use, writing governance people follow, and migrating an archive without losing its metadata is the work. That is what we do. Get in touch or start with our Digital Asset Management Guide.

Successfully Take the Next Step in DAM

If you're ready to develop an effective DAM program, work with Stacks to ensure you cover all the details. We approach the process with a personalized focus to establish workflows suiting your operation. These systems develop consistency while offering simple operations, so your teams can implement them seamlessly into their work. Get in touch with our DAM experts today.