Coming soon!
Metadata fields are attributes used to describe an asset for further categorization, grouping and retrieval
Filerobot distinguishes two types on metadata fields:
Embedded metadata: EXIF/IPTC metadata embedded by the camera or the graphical editor software
Custom metadata: metadata fields created in Filerobot to enrich assets
Filerobot allows the creation of simple or complex metadata structures, aka taxonomies, with each metadata field capable of supporting multiple dimensions, such as translations, currencies, distribution channels or any other variant required by your use case.
Metadata can be viewed and edited during the upload process, in bulk post-upload or individually for each asset in the asset management modal, see Manage assets.
Assets can then be searched by metadata field values and dynamic Collections created based on metadata field values.
Let's get started!
Embedded metadata may contain for example the GPS coordinates of where the picture was taken, the author, the camera, the lens, ... Filerobot can extract these metadata, including ones from custom namespaces (for example model name, product category) and map it to custom metadata.
To enable the extraction of embedded metadata, navigate to Settings > Development > Automations and enable the Extract embedded metadata post process.
Once enabled, Filerobot will extract embedded metadata from asset upon upload and display them in the Details tab of the asset management modal:
To leverage search and collections grouping based on embedded metadata, contact our support team to enable the mapping between embedded metadata and custom metadata.
The users have the option to define metadata structures, create new fields and group them into different categories. This kind of metadata is defined per Filerobot project (token) and applies to all assets in it. You can have different metadata taxonomies if you have multiple Filerobot tokens.
See Managing metadata.
Metadata, as well a Tags can be translated in multiple languages. You can manage languages from the Metadata variants section under Settings > Project > Metadata > (tab) Configuration. Edit the Language variant to enable or disable languages.
Please note the special case for the Language variants:
The topmost 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 (and not free text entries) - the API keys are the ISO code of the language selected, e.g. en for English
the API key cannot be edited
You can also create additional custom metadata variants to declinate a metadata field in different dimension, such as currencies, file format, etc, ...
Incorporating metadata enriches your assets with valuable insights, transforming them into more than just files – they become organized, searchable, and informative resources
Asset metadata can be viewed and managed from the asset management modal.
Users with level Contributor or higher, can edit metadata fields during or after file upload.
You can also edit metadata fields of multiple assets in bulk. For that purpose, select the assets you want to edit metadata of and select the Edit multiple assets option from the contextual menu or navigation bar:
You have 2 ways to retrieve assets by metadata fields:
You can search by a specific metadata field in the search bar, pointing to this field with the special symbol @:
If can combine metadata-based search with free text search.
Alternatively, you can use the Metadata filter to select a field and a search value. Entering multiple metadata fields in the metadata filter will perform an "OR" search.
Clicking on the button allows to edit languages:
Create a new variant via the button:
To link a variant to a metadata field, navigate to to Settings > Project > Metadata > tab Assets and either create a new metadata field or edit an existing field suing the button.
Metadata variants can be toggled using the toggle.
You can edit the metadata information of an asset through the icon in the top right corner of the screen:
If any metadata field is in the metadata structure, no metadata changes can be saved if the field value stays empty.
