Metadata as the user will see it:
iconik provides comprehensive abilities for managing your metadata for Assets and Collections. You can set up how the metadata will work, specify available fields, and define user interaction. The administration of metadata is broken down into three parts:
- Metadata Views
- Metadata Fields
- Metadata Categories.
These are explained below.
Metadata Fields
Metadata Fields are defined in iconik and can be used to add metadata to an asset. These are defined by someone with administrative capabilities, and then they are composed into views. Metadata Fields can live in multiple Metadata Views.
Metadata Fields also have attributes that can be defined, such as the type of field, whether it’s Read-Only, or which options are available in a selected view. All the attributes are listed in the overview of Metadata Field Entities.
Any metadata field that you define can then be used for any asset or collection. But you will need to place it in a view to be able to see it in the web interface.
Metadata Views
Metadata views are like forms, which are composed of metadata fields. The fields can also be split up with dividers into logical groups.
You can define which Metadata Views are shown by using Metadata Categories.
Metadata Views can also have ACLs on them to define who can Read and Write using them. By using ACLs and multiple views, you can allow different users to see different fields for the same asset or collection.
In addition to adding Metadata Fields, you can also override the properties of a field in the view.
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.
Each Metadata Category has a "Default" sub-category, and you can create additional sub-categories to organize your Metadata Views. For example, you may have Metadata categories for Sport, News, and Entertainment, each with one or more views for capturing metadata.