Metadata
File
Standard fields
The following fields from the photo file are always present when adding or editing metadata.
The label shown in the user interface, the height of the edit field (in rows) and whether the field should be required or not can be configured. The fields can be sorted and if a field is hidden, it won't be visible for the user.
Only changes within the standard metadata fields is part of the downloaded photo.
Extra file metadata
Configures which additional metadata fields from a photo file that can be added or edited in the user interface.
Consists of an array of objects. Each object corresponds to a single metadata field from the file.
If both xmp and iptc are specified, xmp will be used if a value exists in the file, otherwise it will fall back to using the iptc value.
If neither xmp or iptc is specified, an empty field will be rendered. This is useful for adding custom metadata that is not present in the file.
The following example configuration contains a custom field (Alt text), and a field from iptc (City).
If you are not using "Extra file metadata", the configuration needs to contain a pair of empty square brackets: [ ]
Select and checkbox
When adding custom metadata, a select or a checkbox can be rendered instead of a text field. Additional keys used for this are:
A select or checkbox can not use values from xmp or iptc.
A checkbox can not be required.
Example configurations of checkbox and select:
Concepts
Configures which concept types that can be added or edited in the user interface.
Consists of an array of objects.
Example:
The usage of rel is that is saved as a part of the link that gets written to the document. Later it's used to extract the different configured types to be displayed accordingly. This makes it so that you should NOT use the same rel in two different objects.
Wrong example ⚠️
Correct example ✅
Units
"Share with organization" checked by default - controls whether "Share with organization" initially should be checked or not when uploading images.
Last updated