in Settings > DAM > Metadata > Assets (tab) you can find detailed specification of the metadata structure of the project.
This tab allows users to manage metadata through System fields and Custom fields.
System fields appear in the System metadata category, marked by a padlock icon and cannot be deleted. Custom metadata, however, is fully customizable and can be added, reordered, edited, or removed by users.
Users can perform the following actions:
Search fields by Name or API Key.
Organize groups: Reorder custom metadata groups.
Manage fields: Add, edit, or delete custom fields and groups.
You can search for fields by either Name or API Key. This filter applies to both System and Custom fields.
Each asset includes two essential metadata fields:
Title
Description
Both fields are of the "Short text" type and support regional language variants.
To create a new group:
Click the + Add new group button.
The group will be added to the bottom of the custom groups list, and the screen will auto-scroll to the new group.
Use the ...
button to rename or delete the group as needed.
To add fields to the group, click + Add new field.
After adding fields, use the ...
button to edit or delete each field.
When adding a new field:
Click + Add new field.
A modal appears with options to configure the new field, including:
Visibility: Toggle ON/OFF whether to show the field in the public API response header.
Name: The display name of the metadata field.
API Key: Used to store/retrieve metadata information from the backend. It auto-fills based on the Name but can be manually edited (avoid special characters).
Type: Defines the data type (e.g., Text, Number). Select this only when creating the field, as it cannot be changed later. For details on supported types, see the Metadata Field Types section.
Placeholder: Example text that guides users on what to enter in the field.
Info Tooltip: Optional, providing extra details on expected field values.
Metadata Variant: Select from available metadata variants. Note that if the field Type is "List" (single or multiple values), Metadata Variant will be disabled.
Required: Toggle ON/OFF if this field must be filled in for each asset. Required fields must be populated during asset upload, or DAM will explicitly prompt for completion.
After setting up the field, click Add to finalize it. Repeat this process for additional fields as needed, and ensure you click Save to apply all changes. Unsaved changes will be lost.
When the user chooses List (single value) or List (multiple values) type for the metadata field, they have to provide one or more list options with the following details per each:
API key
Option’s value
The API key is automatically created on the basis of the Value.
Editing a custom field follows the same steps as adding, with the following exceptions:
Type and Metadata Variant cannot be modified after the field is created.
To reorder groups, click the Organize button, then drag and drop groups using the reorder icon
Name | Type | Description | Examples (used for) |
---|---|---|---|
Short text
TEXT
Free text is shown on 1 line. Does not accept line breaks.
Title
Long text
TEXTAREA
Similar to "Short text" but you can place inside longer content and paragraphs.
Description
Boolean
BOOLEAN
True/False indicator. Note: In the DAM UI it is visualised as a check-box.
"Approved"
or
"Published"
Date
DATE
Calendar date format.
Created at
Number (integer)
INTEGER
Positive and round number.
Note: takes only digits.
Order number
List (single value)
SELECT
List with pre-defined options, where only one can be selected.
Note: should not be used for more than 100 options to chose from.
Country of origin
List (multiple values)
MULTI-SELECT
List with predefined options, where multiple values can be selected. Note: should not be used for more than 100 options to chose from.
Markets
Supertags
TAGS
Custom-defined list of tags, optimised for faster search in the system
Customers
URI-type attachment
URI
Link to an external (WWW) asset or resource. Officially supported URI schemes are: - url (http://xx, https://xx, www.xx) - phone (tel:+xx) -email (mailto:xx) Other URI schemes will also function but are not documented
Privacy policy
Asset-type attachment
ATTACHMENT
Attach an internal hub asset Can add up to 5 attachments per metadata -- all hub assets types (video, image, pdf..) are supported
Asset