.png)
Motivation
It may be that within your current metadata schema, you may want to define that certain fields (1) become available/unavailable based on another field’s (2) choice. This form of relationship can be seen as dependency and greatly simplify an end user’s approach when it comes to metadata value input.
Example
When choosing a specific value from a dropdown (enum metdata type field) such as a country’s state (1), another metadata field (2) may restrict which values are made available in another field such as the cities available within that state.
The following example is taken from MediaPortal’s UI, specifically an asset’s metadata tab:
Resources
Via API
The necessary resources can be found here:
Metadata datasets — Vidispine REST API documentation
How to
Via API
The necessary steps for accomplishing the use case can be found in this article. Check the documentation for “Metadata datasets“ here:
Metadata datasets — Vidispine REST API documentation
Via ConfigPortal
System administrators with access to ConfigPortal can set existing metadata in a dependency relationship.
-20220113-140311.png?cb=0644a1cabcfdebc5f4aba4e336247d83)
A detailed explanation on how to configure data sets in ConfigPortal can be found here: