What is XMP

How XMP works in a DAM

XMP stores metadata as a packet of named properties inside the file, grouped in namespaces. Adobe created XMP and publishes the specification in three parts: the data model, the standard schemas and storage in files.

A DAM uses XMP in two directions:

• Read on ingest: the DAM extracts XMP properties and maps them to fields in its metadata schema.
• Write on export: the DAM writes approved values back into the file, so the metadata travels with every download.

Common namespaces include Dublin Core for title, creator and rights, XMP Rights Management for usage terms, and the IPTC Core and Extension schemas. Camera raw files usually carry XMP in a separate sidecar file with the same name. Organisations can also define a custom namespace for their own fields, such as a product SKU or a campaign code.

Example of XMP

Worked example: a photographer delivers 400 JPEG files with creator, copyright notice and keywords stored in XMP. The DAM maps the Dublin Core creator to its Creator field and the rights statement to its Copyright notice field.

Embedded keywords go to a review queue before they enter the controlled vocabulary. When an agency downloads an approved image, the DAM writes the licence terms into the XMP usage terms property. The agency then sees the terms in any editing tool that reads XMP.

XMP in a DAM selection

XMP belongs at checkpoint 2, Define, where the buyer maps embedded fields to the metadata model. The metadata mapping guide and the metadata model builder list the fields to map.

Test these four behaviours at checkpoint 5, Test:

1. Ingest a buyer file with XMP in a standard and a custom namespace, and show the mapped fields.
2. Edit a field in the DAM, download the file and inspect it in an independent metadata reader.
3. Ingest a camera raw file with an XMP sidecar and show that the DAM pairs the two.
4. Show which value wins when the embedded XMP and the DAM record disagree.

DAMSelection assessment: write-back on export is the test most DAM demos skip. Add it to the demo script as a pass or fail criterion.

Common mistakes with XMP

XMP projects fail through four common mapping mistakes.

• Mapping XMP on ingest only, so files leave the DAM without the rights data the library holds.
• Assuming every format stores XMP the same way. Raw files, PDFs and video containers differ.
• Creating a custom namespace without documenting it in the data dictionary.
• Letting embedded keywords bypass the controlled vocabulary and pollute search filters.

Related terms

XMP connects to five other glossary terms.

• IPTC: the photo metadata fields most often carried inside XMP.
• EXIF: the technical camera metadata stored alongside XMP.
• Metadata schema: the DAM field model that XMP maps into.
• Content credentials: signed provenance that complements embedded descriptive metadata.
• Rendition: each derived file needs XMP written again.

The metadata schema guide explains field design, and the DAM glossary lists every term.