Curator can be configured with hierarchical metadata that organises information into a nested structure, each level providing more specific details. Using location as an example, hierarchical metadata might look like this:
Hierarchical Metadata Example:
Location > Continent > Country > State/Province > City > Neighbourhood > Street > Building
Here's how this might be structured with actual data:
- Continent: North America
- Country: United States
- State/Province: California
- City: San Francisco
- Neighbourhood: Mission District
- Street: Valencia Street
- Building: 123 Valencia Street
An example of what this could look like when logging assets is shown below:
When logging, this can save time by ensuring that metadata options only display the relevant information in relation to the previous selection.
Example: In the screenshot above, when Apple is selected under Computer Companies, Curator only shows the options that belong to Apple, such as iPhone.
With hierarchical metadata applied, you can also batch edit multiple assets, applying dependent metadata to multiple assets when they are selected together with an asset that has parent metadata set.