This document describes the best practices for creating individual Abstraction records (often called “title” records) in the EIDR Registry. In general, there are two ways to approach EIDR record registration:
- Catalog Registrations: Large numbers of records processed in multi-record batches.
- Transactional Registrations: Small numbers of records processed one at a time.
Whether catalog or transactional, manual, or automated, there are a few common registration steps:
- Data Preparation: Collecting and formatting the registration data in a form compatible with EIDR Registry technical specifications and best practices.
- Match: Using the EIDR Match API (calling the standard EIDR fuzzy match de-duplication system); a third party matching system; and/or custom queries against the EIDR Registry to check if the intended record has already been registered with EIDR. See Catalog Matching & Registration.
- Refine Data: Depending on the Match results, it may be necessary to correct or augment the registration data prior to re-submitting for Match.
- Registration: Submit the registration data for suspected gap records to the EIDR Registry for registration.
- Manual Review: Depending on the Registration mode, it may be necessary to review the results, correct or augment the registration data, and re-submit for Registration.
As discussed in Introduction to the EIDR Data Model, the EIDR Content ID Registry implements a simple registration tree structure with four basic record types:
- Collection – a grouping record such as a Series, Season, or Compilation.
- Abstraction – an abstract work in its most general form, including movies, episodes, and TV specials.
- Edit – creative changes to a work, including both complete versions and clips.
- Manifestation – technical representations and encodings, including language versions (“subs and dubs”).
There are also dependence relationships such as isCompilationOf and lightweight relationships such as isPackagingOf and isSupplementalTo. EIDR Content IDs identify audiovisual works and their derived versions, representations, and collections independent of distribution channel, ownership, or subsequent re-use for another purpose.
Finally, there are two principal versions of the EIDR Registry available for use by EIDR Members:
- Production Registry
- Sandbox registry
As the name implies, the Production Registry should only be used for live record registration. The Sandbox is for training and for test registrations. While everyone is always free to read records from either Registry, users are only given write access to the Production Registry after they have demonstrated their competency in the Sandbox system.
The exact method employed to add records in the EIDR Registry will depend on a client’s own environment. Options include:
- The EIDR Web UI for low volume and ad hoc registrations and modifications.
- The bulk registration tools (the BMR tool with a flat file data source or the bulk data mode of the command line tools with an XML data source) for high volume/catalog registrations.
- The EIDR command line tools for those with lower record volumes and shell script-based automations or who are comfortable working directly with XML data structures.
- A client’s own title management system, directly integrated with the EIDR Registry via the .NET / Java SDKs or REST API.
- Use of a third-party service provider to perform the actual registrations. In this case, the client still needs to understand the data requirements and fundamental nature of these records.
Additional information useful in EIDR record registration can be found in other EIDR publications.
A general overview of the EIDR Content ID registry and the different types of records and relationships that it can contain can be found in:
A quick reference to the required (and strongly recommended) fields for Abstraction records can be found in:
Specific guidelines for registering episodic records (Series, Seasons, and Episodes) can be found in:
More detailed information regarding the different EIDR record types and their respective data fields is available in:
- Selected Data Best Practices
- Creating Root Abstraction Records
- Special Abstraction Registration Cases
 This step may be skipped in certain circumstances.