Editorial-based data model migration guide
Overview
In the 20.51 (2020 Q4) release, OpenTV Platform introduced a new, editorial-based data model that is easier to use and understand. Its main advantage is that it allows you to directly associate editorial content with products, rather than technical content as was the case previously.
New deployments will use the new model. Existing deployments that are being upgraded can still use the older, technical-based model, but are encouraged to switch to the new model, as it has a number of advantages:
- Easier to understand
- Makes defining products easier
- Reduces duplication of information
Migration steps
This guide explains what you need to do to prepare for the migration from the old, technical-based model to the new, editorial-based one. (The transformation of the existing data in the Platform will be performed by NAGRA, but there are a number of other areas that must be addressed.)
- Metadata ingest – you can either ingest data in the existing, technical-based format or in the newer, editorial-based format.
- OpCon can only be used to create VOD content (including creating nodes and mapping them to content) if the newer, editorial-based data model is used. If you stick with the technical-based model, you can only perform these actions:
- By ingesting updated data – see Metadata ingest format – editorial-based.
- By using the appropriate CPM APIs. See:
- Client apps – the existing MDS APIs are unchanged, but MDS now has a new API for VOD content that reflects the new data model. This means that you do not need to make changes to an existing app, but you are recommended to use the new API for any new client applications. See:
- VOD metadata and Retrieve catalogue node information
- Metadata Server (MDS) API Documentation (see /metadata/delivery/v2/<provider>/vod/editorials)