first annual meeting of participantseidr.org/documents/eidr_annual_meeting_1-18-2012_v5.5.pdf ·...

March 2010 First Annual Meeting Of Participants January 18, 2012

Agenda

•  Welcome & Introductions •  Annual Meeting Business - Announcement of 2012 EIDR Board •  Year in Review - 2011 •  Looking Forward to 2012 •  Working Discussion – 2012 POC Opportunities •  Working Discussion – Onboarding & Matching

–  Onboarding overview – what we’ve learned –  Matching framework - key challenge –  Matching service providers

•  Working Discussion - Data Model for Digital Encodings •  Close – Transition to DEG/HITS Steering Committee Meeting

1/18/2012 EIDR Confidential 2

Introductions

Please Welcome our Newest EIDR Members •  V2 Solutions •  Argo Systems •  BUFVC (British University Film & Video

Council •  Prime Focus Technologies •  Exactuals •  MediaMorph


Annual Meeting Business - Board Election

•  2011 –  7 directors/9 authorized –  4 founding promoters + 3 elected industry

promoters •  2012

–  9 directors/11 authorized –  Increase to 5 elected industry promoters –  2 expansion seats remaining

•  5 promoter nominations for the 5 seats


2012 EIDR Board of Directors

•  CableLabs – Jud Cary •  Comcast – Steve Heeb •  Deluxe – Greg Gewickey •  Disney – Arnaud Robert •  MovieLabs – Kip Welch •  Neustar – Tim Dodd •  Rovi – John Moakley •  Sony – Eric Iverson •  Warner Bros – Darcy Antonellis


Year in Review – 2011


Membership – Strong & Growing


Promoters Contributors

CableLabs Argo Systems Comcast Avail‐TVN Cox Baseline

Deluxe BUFVC Disney Charter Communica@ons

MovieLabs Civolu@on NBCU Digimarc Neustar Exactuals Rovi Corp iNDEMAND

Shaw Communica@ons Internet Video Archive Sony Pictures Prime Focus Technologies

Verance Corpora@on Rentrak Warner Bros (Time Warner) V2 Solu@ons

Vobile

Seeded Records – Steady Expansion


Titles: 2,010,335 (Year Range: 1888 - 2016)

Record type Sept Net Oct Adds Net Nov Adds Net Dec Adds Current

Movies 50967 1724 108 467 53266

Series 7617 1113 41 27 8798

Seasons 7844 1339 106 208 9497

Episodes 105961 17940 1927 4547 130375

One‐Time TV 11059 3986 266 138 15449

Shorts 776 44 2 12 834

Movie Edits & Encodings 1403 343 87 1928 3761

Totals 185627 26489 2537 7327 221980

2011 POC/Deployment Projects


Descrip9on Par9cipants Status

Digital distribu9on infrastructure with EIDR API; ini9al registra9on of ~1.5K records Disney Done

Online retail workflow integra@on with EIDR API WB/MSFT Ongoing

Title management workflow integra@on with EIDR API NBCU Ongoing

Ini9al registra9on of ~1.5K records Sony Done

UltraViolet workflow integra@on WB, NBCU, Sony, Neustar Ongoing

VOD workflow integra@on NBCU, Comcast,

iNDEMAND, Avail‐TVN, Rentrak

Ongoing

Linking VOD & linear metadata Comcast, Rovi Ongoing

Matching internal records to EIDR IDs Disney, WB, NBCU, Sony, Rovi, Baseline Research Ongoing

Monthly seeding process for new movie/TV records Rovi Done

Supplemental seeding of movie records; adding alternate ID’s

WB/Flixster, Baseline Research Ongoing

2011 Development Overview

•  Q1 Release - 1.01 –  Maintenance release

•  Q2 Release - 1.02 –  Maintenance release –  Features – party DOIs,

user-provided tokens


Q1: Maintenance Release Q2: Feature Release Q3 Q4: Two Releases

•  Q4 Release - 1.0.3 –  Maintenance release

•  Q4 Release - 1.0.4 –  Maintenance release –  Feature – Video Services ID

beta

2011 Expenses


Category of Expense 2011 Totals

Research & Development Opera@ons $329,300 New development $137,375 Total R&D Services $466,675 Hardware $37,500 Marke9ng & Bus Dev $86,812 G&A $148,644 Total 2011 Expenditure $739,631

Looking Forward – 2012


2012 Development Roadmap

•  Q1 Release - 1.1 –  Maintenance release –  Features - Video Services ID;

versions/edits & ancillary functionality

–  March 2012 (Alpha Jan)

•  Q2 Release - 1.1.x –  Maintenance release


Q1: Feature Release Q2: Maintenance Release Q3: Feature Release Q4: Maintenance

Release

•  Q3 Release -1.2 –  Maintenance release –  Features - digital asset data

model improvements; metadata harmonization

•  Q4 Release - 1.2.x –  Maintenance release

Video Service ID

•  EIDR 1.1 Alpha now up and running on a new instance of Sandbox (Sandbox 2)

•  Independent of the Sandbox running the production EIDR instance

•  Sandbox 2 will allow initial seeding and testing of the Video Services ID functionality

•  David Agranoff of CableLabs is leading feature testing and seeding


2012 Projected Expenses


Category of Expense 2012 Totals Research & Development Opera@ons $638,000 New development $342,798 Total R&D Services $980,798 Hardware $37,500 Marke9ng & Bus Dev $120,000 G&A $298,495 Total 2012 Projected Expenditure $1,436,793

Higher 2012 spending driven by planned hiring, full ops cost, member consulting services, 2 major releases, SDK & documentation updates.

Membership – Need to Double in 2012


Adobe Fox Neblix Amazon FreeWheel SAG Apple Google/YT Samsung AT&T Harris Summit BBC Hulu Technicolor BSkyB ITV TF1 BestBuy Jinni Time Warner Cable

Black Arrow Lionsgate Tivo Brighthouse Liberty Global/UPC Tribune Media Services

Canoe Microsoh Verizon CBS Neblix Viacom/Paramount/MTV

DigitalSmiths Nielsen Virgin Dish/Blockbuster NTT Labs Vivendi/Canal Plus/UMG

DirecTV Orange/France Telecom Walmart/Vudu DGA RedBee West10

Ericsson RTL Group WGA

Discussion of 2012 POC Opportunities


Type of POC Possible Par9cipants

Trailers Internet Video Archive

Repor@ng Rentrak, MediaMorph, Exactuals, Argo Systems

Content Recogni@on Verance, Vobile, Civolu@on, Digimarc

Video Service ID Comcast, Cox, Shaw, Charter, CL

Broadcast TV NBC, ABC, ESPN

Adver@sing Broadcasters, MSO’s, Ad‐ID, Avail‐TVN, Black Arrow, FreeWheel

Produc@on /Distribu@on Services

Deluxe, V2 Solu@ons, Technicolor

Satellite TV & IPTV DIRECTV, DISH, AT&T, Verizon

Live – Sports & News Broadcasters, MSO’s, Prime Focus, NBA, MLB, NFL, NHL

Archives BUFVC, BFI, AFI, INA

Working Discussion - Onboarding & Matching


Onboarding Overview – Cycle for New Registrants

Choose category of records Support &

Documenta@on

Sohware Tools

Preliminaries

Match

Register gap records

Update matched records

Register edits and children


Repeat for each new type of record – movie, episodic, etc.

EDIR Support & Documentation

•  EIDR web page – general business & technical documentation •  API guide, schema, field guide, best practices, technical notes, etc. •  http://eidr.org/resources

•  Zendesk – all members will have user accounts •  Help desk tickets, outage and other notifications, etc. •  SDK & other software tools •  Member forum coming soon

•  Basecamp – project management site for POCs •  Central and secure location to share files, project information and status •  All members working on a POCs will have access to Basecamp

•  Training – Support staff available for Q&A sessions •  EIDR support number/e-mail

•  877-620-EIDR •  [email protected]


Software - SDK Libraries

•  SDK libraries –  Calls for all the basic EIDR functions

•  Support both XML and Object based models –  Available for both Java and .NET

•  Updates planned for each new rev of registry •  Currently posted on Zendesk:

–  1.0.4 Java SDK - Beta (Windows installers) •  With Java Docs

–  1.0.4 .NET SDK – Alpha (Windows installers) –  Coming soon (Q1)

•  Mac installers •  1.1 will have Video Service ID support


Software – Tools

•  Command line tools –  Simple search, lookup, register, modify, etc. –  Easy to hook together in scripts or batch files

•  Automate jobs that would be tedious or error prone through UI –  Bundled with SDK –  Provide source code examples of each library function

•  Party matching tool –  Helps generate lists of possible matching parties

•  Catalog matching tool –  Helps automate catalog matching –  In development by PDG


Prelims – Preparation for Matching & Registration

•  Most work for any new member •  Necessary steps before matching can

begin: – Hierarchy & data model alignment – Field mapping – Data quality assessment – Party mapping (for EIDR Principal Agent field)

• Match lists of production and distribution companies


Core Matching & Registration Framework

Hierarchy & field mapping

Data quality

evalua@on Party

mapping Matching Register gap

records



While not specifically stated, consider data quality checks as the mortar between each block above

Hierarchy & Field Mapping

•  Evaluate compatibility of record hierarchy and granularity –  Title vs. Edit and original vs. derivative items

•  Map registrant fields to EIDR fields •  Determine availability of required fields

–  Create or extrapolate missing fields if possible •  Determine compatibility of data practices

–  Release date, title strings, country of origin, etc.



Data quality evalua@on Party mapping Matching Register gap

records Update matched

records

Data Quality Evaluation

•  Quality and consistency of each data field –  Identify ways to improve and normalize where needed

•  Ability to identify original title items vs. derivative –  Confirm country of origin & original titles for title-level records

•  Availability of optional fields for improved matching –  Alternate IDs, alternate titles, director, two cast

•  Decide whether sufficient to ensure accurate matching





records

Party Mapping

•  Match registrant list of production & distribution companies to EIDR’s list –  Retrieve party IDs for matched parties

•  Identify missing (gap) parties & create new party IDs •  Fix incorrect parties (incorrect spelling, punctuation,

duplicates, etc.) •  Every registration needs one or more valid party IDs





records

Matching

•  Focus on getting title-level matches right •  Be prepared for some level of manual review •  Hire matching vendor if necessary •  Matching tool approach: score possible matches

–  High scoring matches – use the matched EIDR IDs –  No (or low scoring) matches – gap items, queue for registration –  Middle scoring matches – review manually –  Metadata differences – flag for quality review and correction

•  Ingest the matched EIDR IDs 1/18/2012 EIDR Confidential 28




records

Register Gap Records

•  Register confirmed gap records •  Registration paths:

–  Use matching tool or other API integration –  Generate XML for bulk registration –  Register manually through UI

•  Ingest new EIDR IDs





records

Update Matched Records

•  Fix incorrect parties (incorrect spelling, punctuation, duplicates, etc.)

•  Add alternate IDs •  Correct mistakes or fill in missing fields

–  Improves uniqueness & subsequent matching

•  Add registrant to Access Control List





records

Onboarding Overview – Cycle for New Registrants

Choose category of records Support &

Documenta@on

Sohware Tools

Preliminaries

Match

Register Gap Records


Register edits and children


Repeat for each new type of record – movie, episodic, etc.

Matching Service Providers – Rovi & Deluxe

•  Rovi – Todd Dietz •  Deluxe – Josh Kline


EIDR Automated Matching Tool

•  Purpose: Aid match and ingest of catalog registrations •  Use Model:

–  Ingest catalog metadata –  Automate “easy” match and gap determination

•  Flag data differences on matches for review and later correction –  Facilitate manual determination of matches and gaps for the rest –  Register gap records –  Update matched records

•  Implementation: –  Relational database (MySQL) w/procedures for data transformation –  Java components for API integration and converting to EIDR XML –  A pluggable component framework for added matching modules

•  Software available to matching service providers


EIDR Automated Matching Tool Workflow

•  Ingests catalog from registrant database, XML or Excel –  Translates into EIDR data model

•  Scores matches using EIDR’s dedupe engine in a sandbox –  High scoring single matches -> confirmed match –  No (or low) scoring matches -> confirmed gap –  Mid scoring records reviewed manually or sent to EIDR for

registration w/review •  Ingests mappings of Alt IDs to EIDR IDs (if available)

–  Low scores used to flag possible Alt ID errors •  Flags data discrepancies for review and record update •  Registers gap records •  Updates records (alternate IDs, ACL additions)


Working Discussion – Data Model Updates for Digital Encodings


Digital Encodings

•  Design Point: Represent actual digital files –  Technical metadata (tracks, codecs, bitrates, etc.) –  File size and/or hash –  Individual audio or video tracks can have their own EIDRs

•  Problems: –  Files often disposable, e.g. Mezzanine file –  Often file is not what is to be identified

•  UV – container may be updated with metadata, not a new APID •  UV – distributor may rev APID w/o file change •  Mezzanine – identifying the “version” or profile given a vendor

–  Lacking some cable metadata, e.g. SCTE-35 signalling –  No longer fully aligned with MovieLabs Common Metadata

•  Proposing to update in 1.2


Digital Encoding – Designing for 1.2

•  Use cases –  UV APIDs –  Mezzanine files –  Cable encodings

•  Other possible use cases –  Individual audio and video tracks –  DVD/BD images –  Others?

•  Discussion –  Use cases –  IDing encoding “profiles” vs. actual files


first annual meeting of participantseidr.org/documents/eidr_annual_meeting_1-18-2012_v5.5.pdf ·...

Documents