AEM Assets lets you import asset metadata in bulk using a CSV file for newly uploaded assets. In addition, you can also update the metadata for assets in bulk for existing assets by importing a CSV file. You can also ingest asset metadata in bulk from third-party system in CSV format.
In other words, you can use a single CSV file to simultaneously update the metadata for multiple assets simultaneously. The operation is asynchronous. and, therefore, does not impede your system performance. Importing a large amount of metadata can result in resource-intensive XMP writeback activity if run workflows flag is checked. Plan such an import during lean server usage so that performance for other users is not impacted.
To be able to import metadata on custom namespaces, first register them.
Specify the following configuration parameters:
Number of assets in a batch for which metadata is to be imported. Default value is 50. Maximum value is 100.
Default value is Comma. You can specify any other character.
Multi value Delimiter
Separator for metadata values. Default value is |.
False by default. When set to true and default Launcher settings are in effect for the DAM Metadata WriteBack Workflow (that writes metadata to the binary XMP data). Enabling launch workflows slows the system down.
Asset Path Column Name
Defines the column name for the CSV file with assets.
AEM Assets lets you export metada for multiple assets in CSV format and reimport the metadata in a third-party system. You can also share asset metadata within project team.
The metadata is exported asynchronously and, therefore, does not impact the performance of your system. When you export metadata, AEM traverses through properties of the asset node jcr:content/metadata and its child nodes and exports metadata properties in a CSV file.