Determines if Fotoware Alto writes XMP values from a file to a metadata field in Fotoware Alto, from Fotoware Alto to an XMP field, or in both directions. 

XMP to Metadata will only write to Fotoware Alto on upload. Updates in Fotoware Alto will not be written back to the XMP field. This may be useful for technical information about the file (EXIF), its usage, and information managed and administered in the file. 

Metadata to XMP will only write to the file on download. Updates to the XMP values in the file, followed by a file update in Fotoware Alto, will not be updated in Fotoware Alto. This may be useful for automatic AI tagging, product keywords, and other metadata values that are much better managed and administered in Fotoware Alto. 

Both will write from the file to Fotoware Alto on upload and from Fotoware Alto to the file on download. This is the most common approach to metadata management, as all XMP values from the file are available in Fotoware Alto, where they are managed and updated. 

The supported XMP or EXIF field of the standard, available in the file that holds the value. 

We are using exiftool.org which supports the following file types. The supported namespaces include schemas like Dublin Core (dc), Photoshop Camera Raw Schema (crs), PDF (pdf), XMP Dynamic Media (xmpDM), xmp Media Managementment (xmpMM), Plus (plus), Exif (EXIF) and various others. Please consult with Fotoware to validate your requirements. 

Example: 

• XmpMetadata.dc.subject is the property "Subject" from Dublin Core within XMP. 
• XmpMetadata.xmpMM.derivedFrom.manager is the property "Manager" as part of the section "derivedFrom" from XMP Media Management within XMP. 

A Metadata field in Fotoware Alto is a field added to Schemas or available on File Types (Content Schemas) which contain metadata values. The fields are displayed as fieldpath which has the syntax layerId.fieldId. For File Types, the syntax is fileType.fieldId. 

* If you select a tagbox additional tagbox lookup settings are required, listed below.

Tagbox lookup configuration*

_{(tagbox only)}

The tagbox lookup configuration allows selecting the connected List field of the tagbox that Fotoware Alto will check. If the XMP value is found in the List the tag will be assigned on import. The matching is done based on the key field. 

Example: 

• Fotoware Alto will consider tagbox mappings with some additional logic.
• For mappings to tagboxes, Fotoware Alto splits the XMP values "Metadata, XMP Mapping" by comma and space into single terms.
• Fotoware Alto will then search those terms in the set of tags available for the tagbox (filters will be respected). 
• If the terms are found in the key field, the tags will be assigned. 

On export, the Display Pattern Name of the List is written into the XMP field (for direction Both). 

When several tags are written from Fotoware Alto into an XMP field in the file, the tags are concatenated with a comma and a space. 

Key fields*

_{(tagbox only)}

The field of the List that is connected to the selected tagbox. Fotoware Alto will generate a cache from the values of this field and compare XMP values to it. 

You can concatenate lookup fields by adding multiple fields as key fields. When you configure two key fields, e.g., "product code" and "product name," the XMP value must contain both values, e.g., CODE456-PRODUCT. 

When you want to look up different translations, each translation is one field, so for a lookup in German and English, you must create two mappings. If you try to add name.de and name.en both as key fields you will get the concatenated value e.g. name.en:Apple and name.de:Apfel will become “AppleApfel” which you will probably not find in your List.

Case sensitive*

_{(tagbox only)}

Checkbox determines if the terms of XMP value and tagbox values that are matched should be considered as case sensitive. 

Example: 

• Case sensitive true: summer in XMP will not match Summer in Tagbox
• Case sensitive false: summer in XMP will match Summer in Tagbox

Include all child schemas*

_{(tagbox only)}

If you have more than one mapping defined for a field, the Priority determines the order in which the values are written. 

You can map two values to the same field without setting a priority. Then the order of mappings is not defined, and any value could come first.