Dynamically Map House Metadata to Platform Metadata

One of the key workflow challenges in the modern, fragmented media ecology lies with metadata; specifically ensuring that the metadata associated with a project remains intact as it progresses through the various stages of production. As metadata becomes more important at all stages in delivering video, this an increasingly critical task which is made complex by the fact that each and every platform has its own specific metadata rules and requirements.

 

This is leading to the creation of additional pain points above and beyond accommodating variances in video and audio delivery specifications when it comes to delivering versions to different platforms. In the current landscape a media company is therefore tasked with ensuring metadata is normalised where possible when it enters their jurisdiction and matched to a variety of different platforms on delivery. This can be a laborious process.

 

To facilitate and greatly accelerate the later part of this workflow, Metadata Service can be used. This is a module contained within OWNZONES Connect, our content servicing & supply chain platform in the cloud. It dynamically maps a superset of asset metadata onto the specific requirements for an endless number of different platform endpoints, allowing companies to deliver more titles to more platforms without incurring the time and resource penalties that current metadata compliance efforts can result in. 

 

Metadata Service is extremely flexible and provides a range of options to ensure that users can configure their own metadata hierarchy and sets. For example, the user can set a hierarchy for a series, season, and episode wherein each tier has different metadata requirements that are completely customizable. 

 

One master file is completed for each tier, rather than countless variations for different assets and endpoints. This means that a single file is completed for the series, one for the season, and one for the episode, echoing the usual OWNZONES ethos of avoiding duplication and multiple versions of the same asset that we have pioneered with our use of IMF.

 

The workflow is simple. The user fills out a CSV template that is provided by their OWNZONES solutions engineer and this CSV is then simply uploaded to Connect via the Assets page via the following path: Import > Import Assets and Metadata > Drag & Drop the CSV file > Click Import. The metadata is then automatically attached to the corresponding asset, ready for delivery.

 

With users having both flexibility and control when it comes to configuring their own supersets, the result is a significant saving of time on meeting metadata requirements from multiple suppliers, as well as a streamlining and refining of the internal process that can help mitigate against the propagation of human error and subsequent further time and resource penalties.

Tags:
NEXT

RELATED ARTICLES

RELATED ARTICLES