Cantemo Portal™ includes a dedicated metadata management tool, specifically designed for helping to manage your metadata structure and schemas.
It gives the flexibility to add your own unique metadata fields, helping make that management bespoke. It contains a rich list of field types, including checkboxes, drop-boxes, lookup fields, work-step fields, and more. Each field also has a long list of attributes to enable you to fully customize them. For example, you can choose to make certain fields required, forcing users to complete them, others could be read only.
Cantemo Portal enables you to establish access rules on each field, defining which users or groups can view or edit the field. This can be particularly important in the cases where specific workflows can be triggered by different metadata values. For instance, if you have setup a rule to export the asset if it has been approved, it is important that only those who can approve an asset are able to set the approved value. Certain users should be able to see the value but not edit, and others should not even see this field.
Lookup fields could for instance contain a list of different languages. Values for each lookup field can be imported using our APIs.
Workstep fields enable you to set the right route for the workflow depending on values or status. For example, if an item is marked as approved, it may then be automatically distributed or archived.
Hierarchical fields are a relation-based way of managing metadata, enabling filtering based on the previous value. Using the Metadata Manager, users can browse and manage all of the different fields and relations within their hierarchy and add items at any given time.
Portal gives users the flexibility to add their own metadata fields, helping make that management bespoke. For each piece of information you want to manage, you’ll add a metadata field. Portal provides a rich list of field types and users can enter any kind of data in these fields.
If your organisation spans multiple territories, then the ability to translate metadata into other languages will be very helpful. Based on your settings, you can make your English tagged content ready for Spanish, French, German or other languages you work with.
Including metadata is important, but just as important is being able to extract that metadata embedded in a media file and make it searchable. Portal handles EXIF, XMP, and IPTC metadata automatically upon ingest. This could for instance be the camera exposure time or color space that is stored in the file EXIF metadata.
You might want to use different metadata schemas for different type of assets, or in a multi-tenant system use different schemas for different end customers. Because of this, Portal supports hosting multiple metadata schemas in the same repository.
Portal supports metadata transformation mapping to and from other XML formats. This allows administrators to create an XML mapping to any XML format, and register the mapping in the system. These mappings can then be associated with a certain export location, ensuring that the metadata exported to that location is in the right format that is expected by the receiving party.
The same works for importing metadata. Create a metadata transformation mapping from your internal CMS system, and every time and XML is imported from a certain location, Portal will automatically translate that to our internal metadata format.
Hierarchical metadata enables you to filter based on a previous value. A schema can have sub-groups, which are in turn other metadata schemas. Each sub group can be either a reference sub-group, i.e. instances of metadata groups that are stored outside of the parent metadata group but referenced from it; or non-referenced, i.e. group values are stored within the parent metadata group. Users can apply different default metadata groups for different purposes. For example, separate default metadata can be set for items, subclips, and collections.
An example of a hierarchical metadata group is below:
Parent group: Film
Portal enables certain metadata fields to be inherited from a parent asset to all children assets. First, use the related pane on the asset page to establish relationships between assets. Using the inherit metadata fields, a “child” item will automatically inherit the metadata value from the “parent” item. This also works within collections and sub collections, , as well as from collections to items and between different Metadata groups. All items within those groups will inherit the metadata attributes. For example, you can apply inherit metadata to an entire season of a specific series, which will then apply that metadata to every episode within that.
If you are updating metadata for a batch of items in one go, Portal indicates if the metadata in a given field differs between items within that batch. This means that users cannot accidentally overwrite a metadata field in batch updates. If there is no difference in a metadata field, the value will be displayed.