Metadata Configuration
in Settings > Library > Metadata > Configuration (tab) you can find general metadata settings for assets upload, constraints, metadata variants, field mapping and embedded metadata options.
Last updated
in Settings > Library > Metadata > Configuration (tab) you can find general metadata settings for assets upload, constraints, metadata variants, field mapping and embedded metadata options.
Last updated
This tab contains general settings for metadata variants and upload constraints.
Enabling this option will prevent users from uploading assets without specifying the required metadata.
Variants enable alternative displays for the same asset attributes, e.g. language, currency, location, etc. System variants (language, regional groups...) are required for the system to run.
Custom variants can be created by users by clicking on the Add variant button:
Name
The name of the variant. The Language variants are mandatory and they can not be removed.
API Key
The key used to store the variant's information in the databse / to retrieve the variant from the back-end
Label
the "user-friendly" name for the particular variant
Please note the special case for Language system variants
The top option will be the default language for metadata and tags
All language options are to be selected from a drop-down list of supported languages (Languages that are supported by AI are indicated with an AI tag)
The language API key is the ISO code of the language and it can't be modified
This section allows the user to specify which metadata fields should be used for special system attributes and functionalities, such as licence expiration period. To add a mapping, click on the Add mapping button:
Choose the system attribute to which you want to map a metadata field, select a compliant metadata field from the drop-down menu, and press Save.
license expiry
The mapped field should be of type Date
No regional Variant enabled
If there are no suitable metadata fields, you can click on the Create new metadata field button, which will trigger the Add metadata field modal (restricting the options of what metadata Type to create to the applicable ones).
Embedded metadata may contain, for example, the GPS coordinates of where the picture was taken, the author, the camera, and the lens. DAM can extract these metadata values, including ones from custom namespaces (for example, model name and product category), and map them to custom metadata. To extract embedded metadata, navigate to Settings > DAM> Automations and enable the Extract embedded metadata post process. Once enabled, DAM will extract embedded metadata from the assets upon upload and display them in the Metadata > Embeded tab of the asset management modal:
Users can define metadata structures, create new fields, and group them into categories. This metadata is defined per DAM project (token) and applies to all assets. If you have multiple DAM tokens, you can have various metadata taxonomies.
In this section, you can define non-standard XMP metadata fields in custom namespaces. This data is then extracted upon upload and can be mapped to DAM custom metadata
This functionality allows you to map common XMP metadata fields from your files (their embedded metadata) to a custom metadata field in the DAM structure. The mapped field value (if existing) is being copied to the respective DAM custom metadata field upon file upload.
If you check option "Write on download", this will copy the field value from the DAM custom metadata to the respective XMP field upon file download.
Thereafter, all assets with that field filled will be searchable and, most importantly, can be alerted on that (expiry) date. See for how to configure them.
To leverage search and collections grouping based on embedded metadata, to enable the mapping between embedded metadata and custom metadata.
