DATA MANAGEMENT

CONTENT ORGANIZATION AND MEDIA IDENTIFICATION

John DoeExecutive Vice President

Digital Division

Objectives• Setting the Stage (Handout)

– Numbering (Smart / dumb)– Master Data / Data– Basic Definitions for Title, Program, Version, Alpha, Metadata,

• Identification between systems design principles– Inter system– Across the Enterprise– Across multiple Enterprises

• Ccontent organization approaches (What’s working, what are the opportunities) – GOAL: Get on the same page

– Review current approaches (Page 1 – screenshots and words, page 2 hierarchy picture Spain Budapest UK Digital Backbone / SPE Distribution LATAM EIDR

– What definitions need to be worked out? What of that needs to be sorted out before the project starts– What do we want our practices to be:

What are the strengths and weaknesses of each approach? What questions were raised on Wednesday data movement that we need to address? What are the design constraints related to these (ie broadcast system requires a smart number ? What design principles would we want to leverage from what we are doing? What IDs (Data) should be referenced across the enterprise or between enterprises? For enterprise or inter enterprise,

how should re register or issue ide? Will this approach work for our digital distribution models (VOD/OTT)? If not, what needs to be considered What needs more discussion and needs to be sorted out before GL

– What are the gaps from where we want to be to where we are today?• Master Data Opportunities• Metadata and VOD/OTT – What additional metadata requirements do we need to plan for with VOD

and OTT? (Leverage Spencer and Jocson and previous day comments)• What Systems and Dataflows are in plan and what additional analysis do we need to complete to lock

down scope?• Decide what content

Outputs

• Homework or Decisions on– Content organization approach– Identifiers used (Internal / External)– Masterdata in Scope– Source Systems

• Design Principles

Identify Areas of Content Organization

• Titles (Programs)• Versions• Alphas• Inventory

– Core Media – Source – from distributor– Supporting Materials (Eagle)– Promotions– Physical Sources– Deliverables – Transmission Copy

• Other?

Defining Version

• What is the current definition of version?• How does it relate to what we define as an

alpha?• Review examples

Content Organization: Definitions

Title/Program Title is the master data describing the intellectual property, which is maintained as the highest level of organization for its content.

Alpha Alpha is a unique picture/audio/content cut of a Title (See 'Title') created for business, territory, S&P, etc. It can loosely be thought of as a "version".

In regards to fulfillment, it is the secondary level of organizational data used with a Title (See 'Title') in order to drive what end Product needs to be manufactured. (Title > Alpha > Component)

Version

Master Data

Metadata Metadata is the data that describes other data.

Metadata Specifications

The Metadata Specification defines the information required to generate a Metadata File for a specific customer or client

Technical Metadata

Technical Metadata represents the data values that are captured for specific ingested or deliverable assets (i.e. frame rate, bitrate, aspect ratio, codec, audio configuration, file format)

Component A Component is the building block for the creation of a 'Product', e.g. video, audio, subtitle, chapters, etc. A Component is the discrete audio, video, text and/or combined Assets (See 'Asset') that are associated with a Component Type, stored as raw materials for Automated Content Processing. Components are Title (See 'Title') and Alpha (See 'Alpha') specific. A Component can be used in one or many deliverables (applies to both digital and physical media).

Content Organization: Definitions

Asset Asset is meant to convey the broad scope of physical or digital elements maintained and tracked as a unit within any asset management system. Asset metadata uniquely describes the characteristics of the asset and must be permanently connected to the essence whether in a physical or digital asset management system. Whether an asset contains multiple parts, e.g. 5.1 Audio, or whether each part is maintained as an asset is subject to the specific protocol of the managing system. With regard to the more formal term, Component (See Components); an asset, once verified and matched to Component Type specification, becomes a component. All Components are assets, not all assets are components.

Content Org Approaches: :LATAMProgram record created representing a season. No series level record seems to exist

Season Identified by ‘ID’ field

Contains full list of episodes which exist season

Materials for Transmission

Associated directly to the TX id/Barcode on the alpha

Content reference id from episode is referenced for each segment

Program record created representing an episode.

Episode record Identified by ‘Content Reference’ ID

Contains full list of alphas for episode. Each alpha contains distinct ‘Transmission ID’ which is the same as the barcode

Content Org Approach: LATAM

Program: Beveriy Hills

90210 – Season 3

ID: 1111046

Episode: Mystery Loves

CompanyContent Ref ID:

24633

Version A: LAT Barcode: X194636

Materials – Segment 1

Barcode X194636

Content Ref ID: 24633

Materials – Segment 2

Barcode X194636Content Ref ID:

24633

Materials – Segment 3

Barcode X194636Content Ref ID:

24633

Version B: BRA

Episode: Home and Away

Version A: LAT Version B: BRA

Vision - London

1. No Series / Season Only2. Barcode Matches TXID3. House ID’s are

generated by Vision and sometime manually overidden depending on channel and delivery method.

4. House ID’s are generated by channel specific templates in Vision for Promos.

5. House ID’s for commercials are imported from Ad Sales systems via a spot import.

6. Versions are created for SD/HD,(assigned TX ID)

London Cont

1. House ID not turned on for London users.

Vision - Budapest

1. No Series / Season Only2. Barcode Matches TXID3. TX ID’s and Barcode ID’s

match. These would appear to be the Channel code, Abbreviated programme title, Episode number and version combined….

4. House ID’s for commercials are imported from Ad Sales systems via a spot import.

Broadcast Master- Spain

1. From the screenshot provideed by Eva it would appear an ‘EventNumber’ and ‘Media ID’ is used. Eva would need to clarify how this is generated and which other numbers it relates to.

Title : Alpha : Component Structure

• Title is the highest organizing level of SPE’s intellectual property

• Alpha can be thought of as a version or a unique cut of a title

• Component is an asset approved to fulfill a specific title alpha

Spider-Man(Program)

Director’s Cut (Program)

Virgin Air Cut (Program)

Domestic Teaser 1(Teaser)

Domestic Trailer 1(Trailer)

Director’s Commentary

(VAM)

Original Theatrical (Program)

Alpha

Title

Alpha-to-Alpha association

The Making of Spider-Man

(VAM)Alpha Type:

Alpha attribute: “Original Market” HOME ENTERTAINMENT

Component

Spanish (Lat Am) Subtitle

(Program)

Spanish (Lat Am) 5.1 (Discrete)

Audio (Program)

Standard Stereo Audio

(Teaser)

NTSC 4x3 FF(Teaser)

THEATRICALAIRLINE

5.1 (Discrete) Audio

(Program)

NTSC 16x9 FF(Program)

Program

Teaser TrailerVAM

Title TypesColor Key

Alpha TypesColor Key

Program

Component Types

Color KeyProgram Teaser

FEATURES

Title/Alpha/Component Structure

Client Specification

Transformers

Unrated

169FFHDOM

43FFNTSCOM

5.1 LAS

5.1 Eng

CC Eng

Transformers/ Unrated

4x3LBNTSCOM

Transformers/ Unrated

16x9FFHDOM

Transformers/ Unrated

AUD 5.1LAS

Transformers/ Unrated

AUD 5.1Eng

Transformers/ Unrated

CCEng

Content Organization: High Level

Program

Version

Inventory (Assets)

Inventory (Assets)

Version

Inventory (Assets)

Inventory (Assets)

Content Organization: Example - 1

Breaking Bad

Version: HD

HD Source Subs

Version: SD

SD SourceSubs

Content Organization: Example - 2

Breaking Bad

Version: Dom

Source Subs

Version: Compliance Edit

Source Subs

Content Organization: Example - 3

Breaking Bad

Version: Localized -

Spanish

Source Spanish Subs

Version: Localized -

French

Source French Subs

Content Organization: Example - 4

Breaking Bad

Version: Base

HD Source

SD Source Subs

Version: Int

HD Source

French Subs

Spanish Subs

German Subs

What Level of Content Organization exists in Business Systems

• Harris Systems (Broadcast Master, Harris, Landmark)

• GPMS• Eagle• Cineshare• Media Center (CWM)

Internal and External Identifiers

Area Identifiers

Program Transmission ID, SPTN House Number, GPMS ID

Version Version ID

Alpha

Inventory (Assets) Barcode

Content Registration

• Internal Product Identification– What internal identifiers are used within the

existing business systems – Which identifiers are hardwired into existing

business processes and automation

• External Product Identification – Registration to external organization (i.e. EIDR,

ISAN)

Master Data Opportunities

• Where can we nourish existing content

Metadata surrounding hierarchy

Area Type

Program General Title Attributes, Program Identifiers, Localized Metadata (i.e. Synopsis, Titles, Genres, Copyrights, Ratings), Client Specific Identifiers, Rights, Transmission information?

Version General Version Attributes, Alpha Identifiers, Localized, Rights, Transmission information?

Inventory (Assets)

Asset Identifiers, Technical Metadata (i.e. Aspect ratio, format, framerate), QC, Ingest related (encode facility, ingest date, source id),

Deliverables Technical Metadata, Title and Version metadata, Client Specific, Rights Detail, Package Details, content status?

Metadata related to Linear, Non Linear, OTT

Non-linear metadata

Program

Assets

Version/Alpha

Rights

Metadata for VOT/OTT

Data Movement –Originated vs. Interfaced

Open Questions

• What will be the source system for setting up in the initial program?

• What level of content organization do we need within each business system in order to complete end-to-end process from program set up, delivery to play-out?

• Do we need standardized rules for defining versions for consistent inventory?

• How do we deal with promotions and supporting materials in the content hierarchy?

• What are the areas of data that will need to be interchanges across systems and at what point in the cycle are they needed?

• Metadata for content exports out of CWM – do we need to source this information from GPMS? Or are we storing and editing internally at the MC

• Where does schedule fit in the content oganization?

Data Migration

• What data can be migrated immediately?• Implications of data migration• Long term data migration goals

Homework

• Check connections to the RFP• Kelly to connect to RFP via YouSendIt• Kelly to see Vision

Wrap-up and Review

Questions

• What needs to be identified?• Versions• How do we want to organize our content? What

does a reference architecture look like?• What issues or opportunities• What are our master data opportunities?• Design Principles• What should be centrally registered versus locally

registered?• What is the implication on Data Migration

• OTT / VOD needs versus Broadcast Needs