Content Comparison

Create XMP Mapping on Translated Fields

Prerequisites

• Files with DC Subject keywords in English, in German.

• Picturepark list items with translated text fields as names, all translated.

Our Goal

• The XMP mapping should map all subject keywords from the files into the tagbox if either the German or English translation is used.

Add XMP Mapping

The German translation and the English translation count as different fields. If you want to lookup on two different fields, you'll need to configure two mappings (and you are also then able to specify a priority between them; e.g. name.en with priority 10, stop = true, and then name.de with priority 9. This will lookup in English names first, if found the lookup stops, otherwise it will check the German name.

1. Open Settings

2. Open XMP Mappings

3. Add a new mapping

4. Select the mapping direction "XMP to Metadata"

   1. as we want to write to Picturepark

   2. and we do not want to write back to XMP 

5. Select the XMP Field "dc:subject".

6. Select the Picturepark tagbox field "basicInformation.keywords"

   1. Select the name field in the first language: name.en

   2. Select case insensitive

   3. Select all child schemas

7. Select Priority 10

8. Select Stop

9. Save

Image Added

1. Add another new mapping

2. Select the mapping direction "XMP to Metadata"

   1. as we want to write to Picturepark

   2. and we do not want to write back to XMP 

3. Select the XMP Field "dc:subject".

4. Select the Picturepark tagbox field "basicInformation.keywords"

   1. Select the name field in the second language: name.de

   2. Select case insensitive

   3. Select all child schemas

5. Select Priority 10

6. Save

Limitations

• You must select the mapping direction first. 

• Data is always written to XMP even when writeback is disabled. The moment you To enable XMP mapping for the original file the XMP values will always be written from Picturepark writeback for the original you must create a copy of the original using “copyFormat” and apply the XMP mappings. Picturepark will then write XMP to the file on download. Original files XMP values can not, once overwritten, be restored. 

• Changes to the mapping direction of an existing XMP mapping will remove the mapped fields, so you have to cancel to keep your mapping settings. 

• Mappings that try to map different value formats are invalid. So if you try to map a text to a number field the value is not mapped. There will be no errors.

• You cannot map to a Layer with required fields. You can only map to a Layer with no required fields configured. 

• You cannot make a field required on a layer that has mappings. 

• You cannot remove File Types or Layers that have mappings. 

• You cannot remove a Layer from being available for File Types when the Layer has mappings. 

• You cannot remove a field that has mappings. 

• You cannot map to a field of a Layer that is not available for any file type e.g. Layers only for Virtual Types are not supported. 

• XMP values are written as a background task periodically. You might see the values not directly after import. 

• Supported data types: Strings, Translated strings (language needs to be specified), Tagboxes, Dates, Numbers, and Geopoints.