March 2010Licenses For Europe/WG3Licenses For Europe/WG330 May 2013

• Overview/reminder of organizational structure• Overview/reminder of Data Model• Catalog registration projects

15/5/13

Organizational StructureOrganizational Structuregg

M b hi b d fit i tiMembership-based non-profit organization

• What members can do• Registrations are free for members• Members can integrate with the registry API using a variety of• Members can integrate with the registry API using a variety of

technologies (Java, .NET, XML and REST)• Members can mirror the entire Registry• Members can ask to be given write permission on records

registered by others

Wh t d• What anyone can do• Lookups are free to anyone

• Human readable -- through the EIDR UI (https://ui.eidr.org) g ( p g)• Machine readable through the EIDR registry and the DOI proxy• Linked Data-friendly format coming soon

• Anyone can ask an EIDR member to register small number of• Anyone can ask an EIDR member to register small number of records on their behalf

5/1/2012

St i htf d A l F St tStraightforward Annual Fee Structure

Annual Revenue Basic User FeePromoter Fee (includes Basic (

User Fee)

< $100M $       5,000 ,

$    35,000 $100M ‐ $500M $     10,000 $500M ‐ $1B $ 20 000$500M  $1B $     20,000 

>$1B $     25,000 

EIDR M b hiEIDR Membership

C & SP t Contributors & SupportersPromoters

EXACTUALS

Japan Cable Labs

9/27/2012

Data ModelData Model

EIDR E bli S l bl C t t S iEIDR – Enabling Scalable Content Services

EIDR

Value-

Metrics& Analytics

Ownershipand license

rights

Contributormetadata

(cast crew etc )

Offerterms

Digitalrevenuereporting

Value-added

metadataand

servicesrights (cast, crew, etc.) services

85/1/2012

5/1/2012

E l EIDR M i Hi hExample EIDR Movie Hierarchy

T i t l e s IsPromotionFor

E d i t i o n s( P e r f o r m a n c e s )

IsEditOf IsEditOf

Movie( A b s t r a c t i o n s )

Movie Trailer( e o a c e s )

Theatrical(Original Domestic)

Director’s Cut

IsEditOf

h l

IsEditOf

Home Entertainment Edition 

Theatrical(Regional Release)

E n c o d i n g s I E di Of Similar Hierarchy

Mezzanine

E n c o d i n g s( D i g i t a l ) IsEncodingOf,

IsLanguageOf

Similar HierarchyHere

Blu‐Ray Disc Mezzanine(EN, FR, SP)

IsEncodingOf, IsLanguageOf

Blu Ray Disc Image (EN, FR, SP)

Retailer SD(EN)

VOD(EN, FR, SP)

Retailer HD(EN)

5/1/2012

Fi ld f EIDR B A t R i t tiFields for EIDR Base Asset Registration

• Referent Type • Approximate LengthReferent Type• Movie, TV, Series, Season, Short, Web,

Composite, Interactive, Supplemental

• Title

Approximate Length• HH [:MM(:SS)]

• Country of Origin2 Character Country Code

• Title• Language code (RFC 5646)

• Original Language

• 2 Character Country Code

• One or more of• Principal Agent

• Language code (RFC 5646)• Manifestation (Audio, subtitle)

• Structural Type

• Company name, role (Producer, Distributor)

• Director2 A• Abstraction, Performance, Digital,

Physical

• Publication Status

• 2 Actors• Encouraged, not required

• Alternate titles• Valid, In development

• Release Date• YYYY (/MM/DD)

• Alternate IDs• Other types have extra requirements

E i d i ID b t• Mode

• Visual, Audiovisual, Audio, Other5/1/2012 11

• Episodes: series ID, number, etc• Edit: region, purpose, etc

Catalog MatchingCatalog Matchingg gg g

C t l t hi d i t tiCatalog matching and registration

• Do in non-production registry (the Sandbox) first for each new kind of recordP• Process– Align data models– Export to some useful format– Export to some useful format– Match against EIDR records– Process matched records– Register ‘gap’ records

• Quality of input data is the main determiner of time, effort, and cost

5/1/2012

Ali D t M d lAlign Data Models

M i i d fi ld EIDR fi ld• Map existing data fields to EIDR fields• Pay attention to the source’s conventions and customary practices

– Titling conventions (embedded years, trailing articles, etc)Titling conventions (embedded years, trailing articles, etc)– Normalization/non-normalization of cast and crew– Meaning of common vocabulary (‘short’, ‘series’, etc)

N b i f i di t t– Numbering of episodic content• Associated companies are often confusing

– Producer vs Distributor; which companies really matter; etc; p y ;• Fill in any missing required fields

– Follow interim best practices for missing data• Should only have to do this once for each class of records

– Episodic TV vs film; Different data sources; etc

• Aim for disambiguation, not completenessg , p

5/1/2012

E t t f l f tExport to some useful format

• Depends on the matching tool you’re going to use• People have used

– XML– Spreadsheets– Text files– Text files– Custom software (integrated with next step)

• All have advantages and disadvantagesa e ad a ages a d d sad a ages– Machine usable vs human-readable

• May be a multi-stage process, e.g.y g p g– Archive->EN 15907->EIDR XML– Archive->text file->smart spreadsheet

• Do what works best for you5/1/2012

M t h A i t EIDR dMatch Against EIDR records

• Possible paths– Standalone EIDR desktop tools

External matching systems (provided by EIDR or EIDR– External matching systems (provided by EIDR or EIDR members)

– Custom software using EIDR APIs

• Output will be– Records that are definitely in EIDR– Records that might be in EIDR– Records that are definitely not in EIDR

Errors– Errors

• ‘Best Practices for Matching’ document in preparation, based on experiences so farbased on experiences so far

5/1/2012

P M t h d d 1Process Matched records, 1

• Records that are definitely in EIDR– Spot-check, just to be sure– Take the EIDR ID and add it to your system– Optionally

• Add your ID to the EIDR record as an Alternate ID (Standardized process)

• Get yourself added to the permissions list for the matched• Get yourself added to the permissions list for the matched records

• Use the two records (Archive, EIDR) to correct and supplement each other

5/1/2012

P M t h d d 2Process Matched records, 2

• Records that might be in EIDR– These probably create most of the work for this step– Examine the kinds of ‘maybes’

• Look for systemic issuesff– E.g. episodic numbering differences

• See if any of the ‘maybe’ records are a good match– If so, see ‘Process matched records, 1’If so, see Process matched records, 1

– Further matching• Some maybe can be moved to ‘strong match’• Do a data cleanup pass to reduce the number of these, and

then try matching againOnce down to a small number can send them through to• Once down to a small number, can send them through to EIDR operations as part of the registration step

5/1/2012

P M t h d d 3Process Matched records, 3

R d h d fi i l i EIDR• Records that are definitely not in EIDR– Spot-check, just to be sure

• Use simple queries through desktop tools or registry UI

• Errors– Failed data validation rules

• E g duplicate alternate titles illegal country code etc• E.g. duplicate alternate titles, illegal country code, etc– Look for systemic issues

• Bugs in output generationC i t t i i d t b• Consistent issue in source database

• ...but there are always some random things– Ways of fixing

• Manual – modify the file you’re using• At source

– Fix source data or the output tool– Regenerate output file, run it through again

5/1/2012

R i t G R dRegister Gap Records

• Remove definite matches before submitting– Remember: first run submitted on Sandbox

W it f EIDR ti t i i• Wait for EIDR operations to process any remaining duplicates, possible matches, etc (usually not long)

• Investigate results• Investigate results• Once results are satisfactory

Take the corrected file and run the process against the– Take the corrected file and run the process against the production Registry

– Make sure results are as expected– Run subsequent sets of the same kind of records directly against

the production Registry• How and how often you do this can be fine-tuned with EIDRHow and how often you do this can be fine tuned with EIDR

operations5/1/2012

BFIBFI

D t b• Databases– Film and short-form in good shape– TV slightly less tidy

• Initial exercise is non fiction short form in support of a digitization project• Initial exercise is non-fiction short form, in support of a digitization project– 5000 records total, initial sample of 209.

• Data model alignment and output generation took 3-4 days• A day or two of iteration with EIDR staff to learn about error conditions, etc

– Plan to do 150+/month (essentially no additional cost)– Uses XML and EIDR desktop tools– Adding BFI identifier as an Alternate ID to new and existing records

Oth j t ill th th d l• Other projects will use the same methodology– Legacy fiction feature films (11,000 total; 250+/month)– UK Regional non-fiction archives (5,000 items; 150/month)

• Ongoing new UK feature filmsg g– May use desktop tools, may use UI (40-50/month)

• UK current TV– Data model alignment not yet done

St t ith t i l l ti f 400 t th– Start with curatorial selection of 400 current programmes per month

5/1/2012

SSony

• Approx 73,000 records registered– 25,000 edits coming soon

U d d h t d t l t hi t l• Used spreadsheets and external matching tool• 1 month of data model alignment and data prep

2 5 th i th i t ti• 2.5 months processing the registrations– Uncovered hidden bottleneck in EIDR process

• Improvements mean it would be about 1-1 5 months nowImprovements mean it would be about 1-1.5 months now

• Data quality was a big issue– Data is sourced from many subsidiaries, acquired catalogs, etcy , q g ,– Episodic TV was hardest– Meant that the ‘process match results’ step took longer than

t dexpected

5/1/2012

C i l t d t idCommercial metadata providers

• IVA– 30,134 records

• Baseline– 18,632 records

matched• Add IVA ID to existing

records

matched• Add Baseline ID to

existing recordsrecords

– API Integration• 1 week analysis

existing records

– API Integration• 6 Engineer-weeks total1 week analysis

• 1 week implementation

– Second set of 5000

6 Engineer weeks total

took 2 days

5/1/2012

OthOther

• Warner Bros• Fox

• Q2/Q3 13 (120,000 records)• Q3 13 (Data in preparation)

• NBCU, Paramount• Disney (ABC)

• Q3 13• Q4 13y ( )

• BBC • Exploratory talks for trialimplementation

• ITV • Alignment and format stepsunderway for one month of broadcasts (~2000 items) with ISAN data as starting point

5/1/2012

Thi ’ l dThings we’ve learned

W d diff hi diff l• Words mean different things to different people• ‘Green field’ is easier than records that have heavy overlap with

existing EIDR registrationsg g• Episodic TV is harder than film• Doing subsets is better than trying to do everything at once

– Easier to focus– Lets you spot type-dependent issues– Feels less SisypheanFeels less Sisyphean

• Quality of input data is the main determiner of effort, time, and cost• External identifiers are very, very useful

– Can provide guidance for de-duplication– Enable new kinds of applications and accessibility– Facilitate communication with othersFacilitate communication with others

5/1/2012

EIDR M b W ki T th 1EIDR Members Working Together, 1

• Very active technical users’ group– Recent session on how best to do matching

Most members are happy to share ideas and experiences– Most members are happy to share ideas and experiences

• Some EIDR members are also service providers of various sortsvarious sorts– Metadata services, technical consulting, etc.

• Member participation in standards bodiese be pa c pa o s a da ds bod es– DVB– SMPTE– ATSC

5/1/2012

EIDR M b W ki T th 2EIDR Members Working Together, 2

• Work towards common formats and tools, e.g.– Convert ISAN data to EIDR data, and vice versa (being used for

ITV project)ITV project)– Provide configurable EN 15907 to EIDR XSLT (based on work

done by BFI)– Provide configurable EBUCore to EIDR translator (starting from

work done with EBU in 2012)– RDF and linked data (using input from EBU BBC EN 15744 )RDF and linked data (using input from EBU, BBC, EN 15744,...)

• Sharing of Alternate IDs– Matching members’ IDs to existing recordsg g– Makes discovery, use, enrichment easier– Extensions to ID types and relationships

5/1/2012

W ki T th ll b ti li tiWorking Together – collaborating on applications

Th t i l ti t• Theatrical ratings management• Metadata Enhancement/Enrichment

– Use the collective data to improve individual systemsUse the collective data to improve individual systems• Reporting

– Usage and viewing data for broadcast and cableTh t i l ti– Theatrical reporting

– Cue sheets– Broadcast ad placement

• Fingerprinting and Watermarking • Multiplatform/second screen applications

C t t R d ti t• Content Recommendation systems• Retail distribution

– Cross-Studio/Electronic Retailer End-to-EndCross Studio/Electronic Retailer End to End

28EIDR Confidential

W ki t th f t d tiWorking together - features and practices

I d l if i i i d f• Improve and clarify existing practices and features• Add practices and/or features for new use cases• Recently finishedRecently finished

– Extensions/modifications to episodic TV (features and practices)– Compilations and composites (features and practices)– Language specification (clarified general practices; new features for

closed vs open captions, forced subtitles, title and end cards, etc)– Silent films (suggested practices)

• Current work on– Cross-registration to/from ISAN (practices)

Radio (practices now; minor new feature later)– Radio (practices now; minor new feature later)– Theatrical shorts and serials (practices)– Live events (practices; simplifying supporting feature later)– Provisional data (practices)

5/1/2012

Wh h ld hi ti i t ?Why should an archive participate?

ID bl l t f li ti• IDs enable lots of applications– Cross-catalog search– Rights management– Resolvable, fine-grained citations and references– More automated distribution– Multiple views into the same data

• Makes it possible to discover and share information– E.g. two archives may have the same film, but different associated metadata– Especially useful for version-related questionsp y q

• Good first step for Linked Data applications– EIDR Alternate IDs are a good way to find other information

• ...one of EIDR’s important initial design points

– Some Alternate IDs can turn into public URLs (but some don’t)• ... some work well with RDF, etc, and some won’t

5/1/2012

AppendixAppendixpppp

EIDR O ti Hi hli htEIDR Operations Highlights

Category Today 2012 2011 2010

T l dTotal records 379,201 279,900 221,146 183,915Original/title‐level content:

Movies 65,994 51,496 45,774 43,573

Series 10,998 9,613 8,719 7,541

One‐Time‐Only TV 26,976 26,112 22,199 17,952

Shorts 1,829 1,406 1,224 1,121

Web 5 4 0 0

Episodes 234,212 158,371 130,284 105,891

4/21/2013

151 034 d h Alt t ID’151,034 records have Alternate ID’s

fCategory of ID May 2013

Sony 89,539

Flixster 29,763

IMDb 26,677

IVA 25,235

Baseline 18 616Baseline 18,616

Netflix 17,609

Amazon 7,062

ISAN 4,751

5/13/2013

A hit tArchitecture

D l S tDeveloper Support

W b UI• Web UI– Register, modify, resolve, browse, query

• Simple toolsSimple tools– Register, modify, query, resolve, etc– Bulk change, manage alternate IDs

S• SDK– REST, Java, .NET– Published as source, with sample applications (see above), p pp ( )

• Other tools– Bulk registration provided by system operator

C t l t hi t l ( t l d )– Catalog matching tool (external vendor)– Ultraviolet CFF registration

• Help with Proof of Concept implementationsHelp with Proof of Concept implementations

D t tiDocumentation

• Registrant documentation– Data fields guide

Best practices (Film Episodic and many corner cases)– Best practices (Film, Episodic, and many corner cases)

• Technical documentation– Registry Users Guide API documentation a tutorial or two– Registry Users Guide, API documentation, a tutorial or two

• ID format guidelines– Standard, binary, URN, URI, compressed, etcStandard, binary, URN, URI, compressed, etc

• Mapping guidelines for other metadata standards– ISAN, EN 15907, EBUCore– Base records only; taking input on versions and episodic

IP d D t O hiIP and Data Ownership

• Functional opaque ID has no implication of ownership• Functional, opaque ID has no implication of ownership• IP rights remain with data and asset owners

Registry has non-exclusive license to data• Registry has non-exclusive license to data

• Low IP risk due to narrow EIDR focus• Commodity namespace data with low IP valuey p• Minimal descriptive metadata• No intent to compete with metadata owners or suppliers

Built on open source IP from mid 1990s• Built on open-source IP from mid-1990s

• EIDR specification is published freelyMembers provide reciprocal patent non assert• Members provide reciprocal patent non-assert• Protects use and operation of the EIDR Registry• Applies to the actual as-built Registry run by EIDR

5/1/2012

• Standard defensive suspension clause

37

EIDR t tEIDR ecosystem support

C tProgrammers & Di t ib tP d & hi Creators

gaggregators DistributorsProducers & archives

L b

MetadataInfrastructure and CPEReporting, tracking,business intelligence

Labs

P t d t d d i tiPromoters and standards organizations