Metadata in Digital Asset Management

Metadata is the structured information attached to a digital asset: what it shows, who owns it, where it may be used and when it expires. In a digital asset management system, metadata is what turns a shared folder of files into a library people can actually search. This article covers why metadata matters, the field types available and what each is good for, and how tags, languages and visibility classification fit alongside them.

Why Metadata Matters

Without metadata, finding an asset depends on someone remembering where it was filed and what the file was called. That works for a few hundred files and breaks down completely at scale, which is the point most organisations start looking for a DAM in the first place.

Good metadata delivers five things:

• Findability: people search for what an asset is rather than guessing filenames, and narrow large result sets with filters instead of scrolling.
• Consistency: a controlled list of values stops the same campaign being recorded as "Q4 Campaign", "q4-campaign" and "Autumn push" by three different people.
• Reuse: assets that can be found get used again, instead of being recommissioned because nobody knew they existed.
• Rights and compliance: ownership, usage rights and expiry dates travel with the asset, so the people using it can see the terms without asking.
• Automation: filters, smart folders and lifecycle rules all act on metadata values, so well-described assets can be routed, expired and reported on without manual work.

What Is Captured Automatically

Every uploaded file arrives carrying technical metadata, and this is read on upload without anyone configuring anything:

• File properties: dimensions, file type, upload date and the user who uploaded it.
• Capture data: EXIF information from photographs, including the date the image was taken and camera settings.
• Location: GPS coordinates embedded by the camera or phone, which place the asset on the map view.
• Embedded keywords: keywords written by photographers and editors in IPTC and XMP fields are read out of the file and added as tags.
• Copyright: copyright and rights statements embedded in the file are applied when the asset does not already have a copyright record.

This is free organisation, but it only ever describes the file. It cannot tell you which campaign an image belongs to, whether it has been approved, or which markets it may be used in. That business context is what custom fields are for.

Custom Metadata Fields and the Types Available

Custom fields, called metafields, capture the information specific to your organisation. The type you choose decides how a value is entered and, more importantly, whether it can be used as a filter.

Types you can filter on

• Dropdown: a single selection from a controlled list. Best for categories, status and asset type.
• Dropdown (Multiselect): multiple selections from a controlled list. Best for values that legitimately overlap, such as target markets or product lines.
• Tags: behaves like a multiselect but is built for large vocabularies. Options are searched as you type, and the field can optionally let users add new values while editing an asset.
• Checkbox: a yes or no value. Best for binary states such as approved or featured.
• Date: a calendar date picker, for shoot dates, campaign dates or review dates.
• Autocomplete: free text that suggests values already in use as the user types. Useful when you want tidy, consistent text without maintaining a fixed list.

Types for context and search

These are searchable but are not offered as filters, so use them for detail people read rather than for narrowing a result set:

• Textfield: short text, for reference codes and brief labels.
• Textarea: long text, for descriptions, notes and usage instructions.
• URL: a link to an external resource such as a source page or brief.

Special purpose

• GPS: geographic coordinates, usually extracted from the image itself, which enable the map view.

Options on every field

Beyond the type, each field carries a few settings worth knowing about:

• Required: force a value before an asset can be saved, either everywhere or only within particular metadata profiles.
• Order: control the sequence fields and their options appear in, so the form matches how people think rather than the order things were created.
• Hide when disabled: remove a field from view entirely when it cannot be filled in, instead of showing it greyed out.
• Conditional values: show an option only once something else has been selected, which keeps long lists manageable. Requirements from the same field combine with OR, requirements from different fields combine with AND.

Metadata Profiles

A metadata profile is a template that decides which fields appear on an asset. Rather than showing every field the platform has to every user, a profile presents only the ones relevant to that kind of content: a product photograph and a sales presentation need very different information recorded against them.

Profiles also decide which of those fields are required, so the rules can be strict for the content that matters and relaxed elsewhere. A profile is applied when an asset is uploaded and can be changed afterwards by editing the asset, and metadata set on a folder is applied to assets uploaded into it. This is the mechanism that keeps metadata consistent without asking people to remember conventions.

System Metadata

Beyond custom metafields, the platform provides its own metadata. This comes in two forms.

Automatic Attributes

These are captured by the platform and always present on an asset:

• Folder structure: The folder path is always visible on the asset and offers organizational context
• Audit data: Created and modified dates, and by whom
• File information: Extension, size, and format

System Metafields

System metafields are built-in fields that behave like custom metafields but are provided by the platform rather than created by your organisation. They include:

• Name and Photo taken
• Tags
• Ownership: The assignment of an owner or responsible team
• Copyright: Licensing and rights management information
• Language: The language associated with an asset, shown with a country flag
• Alert note: A message shown to users before they download the asset
• 360 image: Marks an image for display in the 360-degree viewer

Important: A system metafield must be added to a Metadata Profile before it appears on an asset. This is the most common reason a field seems to be missing: if your team cannot set a language, add an alert note, or record copyright on an asset, check that the field is included in the profile that asset uses.

Managing Languages

Languages are the one system metafield with their own configuration. Administrators create and manage the available languages in Asset Settings > Languages, where each language is defined and given its flag. As above, Language must then be added to a Metadata Profile before users can assign it.

Folder Metadata and Inheritance

Metadata can be assigned at folder level as well as on individual assets. When a folder has metadata assigned, assets uploaded into that folder inherit those values automatically, which removes a large amount of repetitive entry for teams that organise content by campaign, product, or project.

Two behaviours are worth understanding:

• When you save folder metadata, you are prompted to apply the updated values to assets already in the folder and its sub-folders.
• Clearing folder values stops future inheritance but does not remove metadata already written to existing assets.

Folder metadata is an optional feature enabled by an administrator, and is not available on the root of the Library. Assets cannot currently be searched or filtered by folder-assigned values specifically, and folder metadata cannot be bulk-edited across multiple folders.

Tags

Tags are a shared, free-form vocabulary across the whole library. Unlike a dropdown, there is no predefined list: anyone editing an asset can add a tag, and tags extracted from a file's embedded keywords land here too. That openness is the strength and the weakness. Tags capture the things nobody thought to build a field for, but they drift quickly if left ungoverned.

Choosing between tags and a field comes down to how controlled the vocabulary needs to be:

• Use a dropdown or multiselect when the list is short, known in advance, and used for filtering or reporting. Controlled values are what make filters trustworthy.
• Use tags when the vocabulary is open-ended and grows with the content, and when being approximately right is more useful than being complete.
• Use a Tags field when you want a controlled vocabulary that is simply too large for a dropdown, scoped to a single field rather than shared across the library.

Whichever you use, agree the basics early: singular or plural, one term per concept rather than a set of synonyms, and a periodic review to merge the duplicates that inevitably appear.

Languages

Languages are maintained as a list for the workspace and then assigned to assets, which lets a library hold the same brochure in six markets without six competing naming conventions. Captions and transcriptions carry their own language, and users can filter by language to see only the versions relevant to them. User groups can also be restricted to particular languages, so a regional team sees the versions it is responsible for rather than everything.

Language here describes the content of the asset, not the interface, and no translation is performed on the asset or its metadata.

Visibility Classification

Visibility levels add asset-level access control on top of folder permissions. Each level is a named tier, users are granted a tier through their user group, and they see assets at or below that tier. Both checks apply: a user needs folder access and a sufficient tier before an asset appears, and assets with no level assigned sit at the lowest tier so they stay visible to everyone with access to the folder.

This solves a specific problem: content with different access requirements that has to live in the same place. Typical uses include:

• Keeping work in progress visible to the design team while finished assets are visible to everyone.
• Holding confidential material alongside general content without a separate folder structure.
• Giving an external agency access to a folder while internal-only assets inside it stay hidden.
• Staging a campaign so upcoming assets stay restricted until release.

If your content can simply be separated into different folders, folder permissions are the simpler tool. Reach for visibility classification when your folder structure is organised around something other than access, such as project or asset type.

Finding the Metadata View

The Metadata item in the Library navigation offers an alternative to folder browsing. It is hidden when a workspace has no metafields and no tags configured, and access to it is controlled by a permission, so not every user will see it. If you expect the Metadata view and cannot find it, contact your administrator.

Date, Time and Number Formats

How dates, times and numbers are displayed is controlled in Site Settings for the workspace and in My Profile for an individual user, under Date & Time. Only supported formats are accepted:

• Time:H:i, H:i:s, h:i a, h:i:s a
• Date:d/m/Y, m/d/Y, Y/m/d, d-m-Y, m-d-Y, Y-m-d
• Number and currency:en-US, de-DE, no-NO

Combined date and time display can also be configured. Entering a format outside these lists is rejected.

Choosing the Right Approach

As a rule of thumb:

• If people need to filter on it, use a controlled field: dropdown, multiselect or a Tags field.
• If people need to read it, use a textfield or textarea.
• If the vocabulary is open and growing, use tags and govern them.
• If different content needs different fields, use metadata profiles rather than one long form.
• If some assets must be hidden inside a folder others can see, use visibility classification.

Start with the smallest set of fields that answers the questions people actually ask when they are looking for something, and add more only when a real search fails. A short, well-maintained schema beats a comprehensive one nobody fills in.