Using Metadata Import and Export in AEM Assets

Learn how to use the import and export metadata features of Adobe Experience Manager Assets. The import and export capabilities allow content authors to bulk update metadata for existing assets.

Metadata Export

Metadata Import

NOTE

When preparing a CSV file to import, it is easier to generate a CSV with the list of assets by using the Metadata Export feature. You can then modify the generated CSV file and import it using the Import feature.

Metadata CSV File Format

First Row

The first row of the CSV file defines the metadata schema.
The First column defaults to assetPath, which holds the absolute JCR Path for an asset.
Subsequent columns in the first-row point to other metadata properties of an asset.
- For example : dc:title, dc:description, jcr:title
Single Value Property format
- <metadata property name> {{<property type}}
- If property type is not specified, it defaults to String.
- For example: dc:title {{String}}
Property Name is case-sensitive
- Correct : dc:title {{String}}
- Incorrect: Dc:Title {{String}}
Property Type is case insensitive
All valid JCR Property types are supported
Multi Value Property format - <metadata property name> {{<property type : MULTI }}

Second Row to N rows

The first column holds the absolute JCR path for an asset. For example: /content/dam/asset1.jpg
Metadata property for an asset could have missing values in the CSV file. Missing metadata properties for that particular asset are not updated.