MM5.4 Iterative metadata

Owned by Stefan Fodor (Unlicensed)
Last updated: Oct 28, 2020 by Gosia Creosteanu (Unlicensed)
2 min read

General limitations

  1. MM5 only supports read-only of iterative metadata, in the right-hand side panel of the asset preview.

  2. Language specific and conditional fields are not supported.

Configuration

Navigate to the MM5 Config Manager, and select one or more groups the following configuration:

 

 

 

 

 

 

 

 

 

 

After being configured, the iterated metadata values will be displayed in the right hand side panel in the asset preview

The metadata and fields inside are language versioned - meaning that you can custom tailor the UI to the language of your users.

“Asset related metafield groups“ also accepts non-iterative metagroups. However, this is not something we explicitly support.

The role “Editor_SystemTools_AlwaysAllowItemSecurityEdit“ gives read access to all iterative metadata in the MM. You must not apply this role to a non-admin user.

Security

For a user to gain read access to the iterative metadata in MM, two conditions have to be met:

  • The user (or a group the user is a part of) must have read access to the “Metagroup“

  • The user must have read access to the metadata fields in the subgroup.

Example: You have a subgroup named “Subgroup“

and a metadata group named “Metagroup“

You add the Subgroup to the Metagroup, and give your users read rights to the metadata fields inside the Subgroup (e.g. AI Explicit Content - in the first image) and then read rights for your user to the Metagroup.

You can choose to only allow access to a subset of the metadata fields inside the Subgroup. Meaning that, in my example, I could have chosen to only allow “AI Explicit Content“ to be shown in the iterative metadata for an asset. Thereby, not showing e.g. Faces, Landmark, and so on.