Metadata is central to how iconik stores information about your assets, your collections of assets and parts of your asset. Once you have metadata on your entities in iconik you can then use the search to find matches from your metadata to your assets and collections.

iconik metadata for user

Structure of Metadata in iconik

iconik has a unique structure of metadata that allows for flexible viewing and representations of metadata to your end users.

Metadata Fields.

At the lowest level we have Metadata Fields. Each field has an associated type and attributes that an Administrator can set. A typical field could be a Description field - which could be a text field that is required to be entered.

All Metadata in iconik is stored in Metadata Fields, and Fields can then be applied to Assets, parts of Assets (segments) or collections.

Metadata Views

Metadata Views organizes Metadata Fields into Forms and viewable structures. You can have multiple Metadata Views in iconik, each contains different or the same fields but use them for different purposes - and restrict who can view or edit them with Access Control.

It is the view that users typically interact with when adding and updating Metadata.

Metadata Categories.

Metadata Categories define where a view is allowed to be used in iconik. This means that you can use one view for Search, another for Collections and yet another for Assets.

By creating Sub-Categories of Metadata means that your users can go to edit metadata and be shown the right Categories of Metadata Views to edit their Metadata.

Defining Metadata Structures

Admins can define the Fields, Views and Categories for users to use. They can also set who is allowed to see what views or fields.

More on Metadata and administrating it

Using Metadata

Metadata is typically used in the following places:

Metadata can also be used to set up warnings and blocking sharing and downloads of an asset:

Learn more