utilizing pbcore as a foundation for archiving and workflow...
TRANSCRIPT
Utilizing PBCore as a Foundation for Archiving and Workflow Management
Presenters • John Tooraen
IT/Web Manager Louisiana Public Broadcasting
• Don Dulchinos Executive Director Entertainment Identifier Registry
OCLC OCLC: • Member-owned and member-governed • “a worldwide library cooperative, owned, governed and
sustained by members since 1967. Our public purpose is a statement of commitment to each other—that we will work together to improve access to the information held in libraries around the globe, and find ways to reduce costs for libraries through collaboration.”
• Founded in 1967 as the Ohio College Library Center, OCLC and its member libraries cooperatively produce and maintain WorldCat, the largest online public access catalog (OPAC) in the world. http://www.oclc.org/en-US/about.html
Dublin Core Media Initiative (1995) The Dublin Core Metadata Initiative (DCMI): • Supporting shared innovation in metadata design and best practices • Managing long term curation and development of
DCMI specifications and metadata terms namespaces; • Managing ongoing discussion of current DCMI-wide work themes; • Setting up and managing international and regional events; • Curation and open availability of meeting assets
including proceedings, project reports and meeting minutes; • Creation and delivery of training resources in metadata best
practices including tutorials, webinars and workshops; and • Coordinating the global community of DCMI volunteers.
http://dublincore.org/about-us/
PBCore A metadata standard for audiovisual media which provides a rich set of descriptors for radio and television programs, both analog and digital A standard for cataloging and describing media objects in 3 general ways:
– Intellectual Content provides descriptive metadata including Title, Subject, Description, and Genre. The Intellectual Content contains no metadata concerning the physical or digital representation of the asset.
– Intellectual Property provides metadata concerning the creator, distributor, and publisher of the AV asset, along with rights information about its use.
– Instantiation contains all technical metadata about the physical or digital representation of the AV asset:
• format, media type, duration, file size, data rate, aspect ratio, frame rate, and many other aspects of the media object
• location of the physical or digital media object, which in the case of a streaming media file can be its full URL; can be many Instantiations for the same AV asset, all of which share the same Intellectual Content metadata.
• PBCore provides an XSD allowing validation of PBCore XML records. PBCore XML can be used to exchange detailed metadata about media assets, and optionally the media assets themselves, among systems configured for the PBCore standard.
http://www.pbcore.org/about/
EBUCore EBU Tech 3293 (EBUCore) is the flagship of EBU's metadata specifications. Combined with the EBU Class Conceptual Data Model (CCDM) of simple business objects, EBUCore provides the appropriate framework for descriptive and technical metadata for use in Service Oriented Architectures and also in audiovisual ontologies for semantic web and linked data developments . EBUCore has been adopted by several broadcasters around the world. It is referenced by the UK DPP(Digital Production Partnership). It has been selected as the best 'core' and integrated in MediaCorp' metadata framework. It is also the metadata scheme of reference in the project EUScreen (European portal on audiovisual public archives counting 12 EBU members and national archives), which delivers linked data to Europeana . EBUCore has been published as AES60 by the Audio Engineering Society ( AES ).
(https://tech.ebu.ch/MetadataSpecifications)
AT RISK Physical media (3/4”, 1”, U-MATIC, Beta, et. al.) Institutional memory – Producers, Directors – Photographers
Subject matter – People, places, things
2-Prong Approach Save What You Can – Digitize at-risk physical media – Digitize scripts, notes – Gather institutional knowledge and digitize
Stop the Bleeding – Create a workflow that collects all pertinent metadata for
current productions. – Digital media – Collect, digitize, index, and store all ancillary data – Include rights management
PBCore is a good start, but… Very few required elements – people only do what they are required to do, so… PBCore does not include some broadcasting fields and ancillary data resources Not enough fields to support a user-friendly environment (graphics, external resources, etc.)
Enhance PBCore Added a set of rich metadata fields to support end-user systems. Designed review capability in the Catalog Built the production process as part of the system Add in other key departments (Underwriting, Promotions, Web, etc.)
The Catalog
Basic Information Gather the required information, restricting to vocabulary where necessary Asset Type Media ID Titles (multiple) Subjects Descriptions
Format Information • Technical Information • Essence Track
Information • Tape Bar Codes • Encoding • Duration/Start/Stop
Program Profile • Producer, Contributor, Cost
Center Tracking
• Coverage Information • Supplemental Attachments
• Producer Checklist
Other Sections Program Format – Funding
Product, Information
Source Material – Track it all!
Related Contracts
Promotions / Marketing
What is EIDR? Global B2B Registry for unique identification of entertainment content and video services – Identifier solution to span the global video industry supply
chain – Built on ISO-approved Digital Object Identifier (DOI) standard
API-Based Enterprise Solution for real time registry access, with resulting efficiencies in the supply chain
Opaque Unique Identifier
• Format – Prefix identifies the EIDR registry within the DOI and handle systems – Suffix is 20 hexadecimal digits and a Base 36 check digit
• Opaque numbers are assigned directly by the registry • Purely functional without any implication of ownership • Remain the same regardless of asset or registrant ownership • Consistent with focus on functional metadata for uniqueness • Central database contains all required data • No need to predict key data to reference in number structure • Supports persistent nature of the ID
10.5240/ XXXX-XXXX-XXXX-XXXX-XXXX-C
Standard prefix for EIDR registry
Unique suffix for each asset
Check digit
Content recognition
& anti-piracy data
Ownership and license
rights
Contributor metadata
(cast, crew, etc.)
Offer terms
Digital revenue
reporting
EIDR
Value-added
metadata and
services
EIDR Scope
5/1/2012
Input from other systems • Published mappings from other standards
– In Use: • ISAN (projects with ISAN-IA and ITV) • EN 15907 (EU film archives, e.g. British Film Institute)
– Published: • EBUCore (EU Broadcasters) • EN 15744 (work-level records in EU film archives
– In progress: • PBCore
EIDR Membership Producers &
Programmers* Aggregators Distributors
Metadata Infrastructure and media services Reporting, tracking, business intelligence
Archives
*Including wholly-owned affiliates, e.g. ESPN, et al
WELCOME PBS ! Newest Member of
EIDR
EIDR and PBCore • Prototyping a PBCore to EIDR mapping
– Currently based on specs and theory – Looking for partners to provide sample data
• There are usually local practices and use cases to take into account after the basic field mapping – How pre- and post-show additions are handled, variable practices for
episodic and miniseries, etc. – Local database quirks
• Already several thousand productions by PBS member stations in EIDR – Registered as part of another catalog, as needed for EPG feeds, etc – The standard match/register process finds these, allows addition and
correction of data in existing records.
Alternate IDs • EIDR supports a wide variety of ‘standard’ Alternate IDs
– Formal standards (ISAN, ISRC, CRID, ...) – Common industry IDs (IVA, Baseline, Flixster,...) – Commercial identifiers (Amazon, Netflix,...) – De facto standards (BFI, IMDb,...) – ...as well as proprietary internal IDs (studios, broadcasters,...)
• About 55% of records have at least one Alternate ID – Some are resolvable (they can turn into links to collect extra
information) – Some are just identifiers (used to translate between systems)
• Adding alternate IDs is an important part of the registration and matching process
Standards • SCTE
– Carriage in SCTE-35 2013 segmentation descriptor – Used in dynamic ad insertion via SCTE 130 – Proposed for MPEG transport on cable via SCTE 54.
• EBU – Mapping from EBUCore to EIDR registration data available in draft – Joint participation in SMPTE Core metadata project
• Linked Content Coalition – EIDR is compliant with the LCC recommendations on interoperable and
linked identifiers. – LCC identifier principles endorsed by UK Digital Copyright Hub.
• European Union – EIDR is endorsed by the ‘Licenses for Europe’ project of the
European Commission
Documentation • Registrant documentation
– Data fields guide – Best practices (Film, Episodic, and many corner cases)
• Technical documentation – Registry Users Guide, API documentation, schemas, a
tutorial or two • ID format guidelines
– Standard, binary, URN, URI, compressed, etc • Mapping guidelines for other metadata
standards – ISAN, EN 15907, EN 15744, EBUCore
http://eidr.org/technology
Don Dulchinos Executive Director [email protected]
