What Metadata Standards Should DAM Systems Support?

Metadata standards matter because they determine whether the information attached to a file survives when that file moves. When a JPEG is converted to WebP for web delivery, or a TIFF is sent to a print vendor, or an asset is migrated from one DAM platform to another, the metadata travels with the file only if both the source system and the destination system speak the same standard.

Without standards, metadata is proprietary: it lives in the DAM's database and is stripped or lost the moment the file leaves the system. With standards, metadata is embedded in the file itself (IPTC, XMP) or expressed in a portable schema (Dublin Core) that any compliant system can read.

What Happens When a DAM Does Not Support Metadata Standards?

• Rights data is lost on conversion: A licensed image converted to a new format without IPTC/XMP write support loses its copyright notice and usage terms. The next person to use the file has no way to know it is licensed.
• Migration is expensive: Moving from one DAM to another requires manual re-entry of metadata that was never embedded in files, because it only existed in the old system's proprietary database.
• Interoperability breaks: Connecting the DAM to a CMS, PIM, or archival system requires custom mapping of proprietary fields, adding integration cost and fragility.
• Compliance gaps appear: In regulated industries, records that lack standardized metadata cannot be reliably retained, retrieved, or disposed of according to policy.

The four standards below address these risks. Each covers a different layer of the metadata problem.

The IPTC Photo Metadata Standard (published and maintained by the International Press Telecommunications Council at iptc.org) defines the fields embedded directly in image files for descriptive, administrative, and rights metadata. It is the dominant standard for image metadata and is supported by virtually every professional image editing tool and camera system.

What Fields Does IPTC Define?

The IPTC Core schema defines fields including:

• Creator: The photographer or originating organization.
• Copyright Notice: The rights holder and copyright statement.
• Rights Usage Terms: Plain-language description of permitted uses.
• Caption/Description: Descriptive text about the image content.
• Keywords: Controlled vocabulary terms for search and retrieval.
• Date Created: The date the image was captured or created.
• City, Country: Location metadata for news and editorial images.

The IPTC Extension schema adds fields for model releases, property releases, artwork rights, and more detailed licensing information relevant to commercial photography and stock image management.

What to Verify in a DAM Evaluation

Ask the vendor to demonstrate that the DAM reads IPTC Core and Extension fields on ingest, writes them back on export, and preserves them through format conversion (JPEG to TIFF, JPEG to WebP). A DAM that reads IPTC on ingest but strips it on export creates a rights gap every time a file is delivered to a downstream channel.

XMP (Extensible Metadata Platform) is Adobe's open standard for embedding metadata in a wide range of file formats using an RDF/XML structure. It is documented at adobe.com/products/xmp and maintained as an open specification. XMP and IPTC are complementary: IPTC defines the fields; XMP defines how those fields are embedded in file formats that IPTC alone does not cover, including PDF, INDD, AI, PSD, and video formats.

The xmpRights Namespace

The XMP Specification Part 1, section 8.5, defines the xmpRights namespace, which carries four fields critical for DAM rights management:

• xmpRights:Marked (boolean): Indicates whether the asset is rights-managed.
• xmpRights:WebStatement (URL): Points to a web page describing the rights statement.
• xmpRights:UsageTerms (language alternative): Plain-language usage terms in one or more languages.
• xmpRights:Owner (bag of proper names): The rights holder(s).

A DAM that writes xmpRights fields on export ensures that rights information travels with every file, regardless of format, to every downstream system that reads XMP, including Adobe Creative Cloud applications, CMS platforms, and print production systems.

XMP in Practice

XMP is embedded in the file header, not in a sidecar file (though sidecar XMP files are used for formats that do not support embedded metadata, such as camera RAW files). This means XMP metadata survives email attachment, FTP transfer, and cloud storage, as long as the receiving application does not strip it. A DAM should be configured to warn or block exports that would strip XMP from files.

IPTC and XMP address file-level metadata for images and creative files. Dublin Core and ISO 16175-1 address a different layer: interoperability between systems and compliance in regulated environments.

Dublin Core: Interoperability Between Systems

The Dublin Core Metadata Initiative (DCMI) publishes the DCMI Metadata Terms specification at dublincore.org. Dublin Core defines 15 core elements (title, creator, subject, description, publisher, contributor, date, type, format, identifier, source, language, relation, coverage, rights) that provide a minimal common vocabulary for exchanging records between systems.

In a DAM context, Dublin Core matters when the DAM must export asset records to:

• A CMS that uses Dublin Core as its metadata interchange format.
• A library or archival system (many use Dublin Core as their base schema).
• A federated search system that aggregates records from multiple repositories.
• A regulatory submission system that requires standardized record metadata.

A DAM does not need to use Dublin Core as its primary schema, but it should be able to map its fields to Dublin Core for export. Verify this capability during integration testing, not after go-live.

ISO 16175-1: Records Management in Regulated Environments

ISO 16175-1:2020 (available at iso.org) sets principles and functional requirements for software that manages records in electronic office environments. The 2020 revision replaced the 2010 edition and aligns with ISO 15489-1 (records management) and ISO 30300 (management systems for records).

ISO 16175-1 applies to DAM deployments where digital assets are also official records: financial services firms managing regulatory filings, healthcare organizations managing clinical images, government agencies managing public records, and media organizations with archival obligations.

The standard's functional requirements relevant to DAM include: unique and persistent identifiers for records (section 5.2), capture of contextual metadata at creation (section 5.3), retention scheduling and disposition (section 5.5), and audit trail of all actions on a record (section 5.6). During a DAM evaluation in a regulated environment, map these requirements to the vendor's feature set before shortlisting.

What This Article Does Not Cover

This article covers the four primary metadata standards relevant to DAM evaluation. It does not cover video-specific metadata standards (such as EBUCore or SMPTE Metadata Dictionary), PIM-specific schemas (such as GS1), or the design of a custom metadata schema for a specific organization. Those topics are addressed in separate guides on this site.

Disclosure: The DAM Republic earns revenue through vendor profile listings and clearly labeled sponsored content. No vendor pays to influence editorial scores or rankings.

Vendor claims about metadata standards support are easy to make and difficult to verify without a structured test. The following checklist gives practitioners a practical way to confirm support before signing a contract.

Metadata Standards Evaluation Checklist

1. IPTC round-trip test: Ingest a JPEG with IPTC Core fields populated (creator, copyright, caption, keywords). Export the file as TIFF and WebP. Open both exports in a tool that reads IPTC (Adobe Bridge, ExifTool) and verify all fields are present and correct.
2. XMP round-trip test: Ingest a PDF with xmpRights fields populated (Marked, UsageTerms, WebStatement). Export the PDF. Open it in Adobe Acrobat and verify the XMP fields are intact under File Properties.
3. Dublin Core export test: Export a batch of asset records as Dublin Core XML or as a CSV with Dublin Core field names. Verify that all 15 core elements are present and correctly mapped from the DAM's native fields.
4. Metadata on format conversion: Use the DAM's built-in transcoding or conversion feature to convert a JPEG to WebP. Verify that IPTC and XMP fields survive the conversion, not just the original file.
5. Metadata on download: Download an asset via the DAM's public share link. Verify that IPTC and XMP fields are present in the downloaded file, not stripped by the delivery pipeline.
6. Audit trail verification (ISO 16175-1 section 5.6): Perform a sequence of actions on an asset (view, download, edit metadata, new version). Verify that the DAM's audit log records each action with a timestamp and user identity that cannot be edited or deleted.

Run these tests in the vendor's sandbox environment before shortlisting. A vendor that cannot support a sandbox test for metadata round-trip is a vendor that cannot support the requirement in production.

For the full DAM evaluation framework, see How to Evaluate and Select a DAM Vendor. The DAM Republic's 17-criterion rubric includes metadata standards support as a scored criterion in all vendor profiles.

What metadata standards should a DAM system support?

A DAM system should support at minimum: IPTC Photo Metadata Standard (for image descriptive and rights fields), XMP Specification Part 1 (for cross-format metadata embedding, including the xmpRights namespace), Dublin Core (for interoperability with other systems), and ISO 16175-1 where records management compliance is required. These standards ensure metadata survives format conversion and distribution across channels.

Why does IPTC metadata matter for DAM?

IPTC Photo Metadata Standard defines the fields embedded directly in image files for creator, copyright notice, caption, and usage rights. A DAM that reads and writes IPTC fields preserves rights data through every format conversion and delivery step. Without IPTC support, rights metadata is stripped when files are converted or downloaded, creating legal exposure from untracked licensed images.

What is XMP and why is it relevant to DAM metadata?

XMP (Extensible Metadata Platform) is Adobe's open standard for embedding metadata in a wide range of file formats using an RDF/XML structure. Its xmpRights namespace, defined in XMP Specification Part 1 section 8.5, carries usage terms, marked status, and web statement fields. XMP and IPTC are complementary: IPTC defines the fields, XMP defines how they are embedded in formats including PDF, INDD, and AI files.

What is Dublin Core and when does a DAM need it?

Dublin Core is a 15-element metadata schema published by the Dublin Core Metadata Initiative (DCMI). It provides a minimal common vocabulary for exchanging asset records between systems: DAM, CMS, PIM, library catalogues, and archival repositories. A DAM needs Dublin Core support when it must export or import asset records to systems that do not share the same proprietary schema.

How does ISO 16175-1 apply to DAM?

ISO 16175-1 (2020 revision) sets principles and functional requirements for software that manages records in electronic environments. It applies to DAM deployments in regulated industries such as financial services, healthcare, and government, where digital assets are also official records. During a DAM evaluation in these sectors, verify that the platform's retention, disposition, and audit trail capabilities meet ISO 16175-1 section 5 requirements.