A basic EIDR record consists of a single BaseObjectData block. This is the starting point for all Content record types – and the ending point for non-episodic Abstraction records, since Movies and non-episodic TV, Web, and Shorts do not only require any ExtraObjectMetadata.
Every record in the EIDR Content ID Registry begins with this same set of BaseObjectData. In some cases, ExtraObjectMetadata is added to provide data unique to that record type: i.e., Compilation, Episode, or Edit. ExtraObjectMetadata is also added when a record has Lightweight Relationships to other EIDR records.
Records that are not at the root of a registration tree (Seasons, Episodes, Edits, Clips, and Manifestations) can inherit much of their BaseObjectData from their immediate parent record, which may have inherited BaseObjectData from its immediate parent, and so on up to the root record (which has no parent to inherit data from). When a particular inheritable data value in a child record is the same as its parent, do not repeat the value in the child. Instead, allow it to inherit from the parent. This makes the records more compact, easier to construct, and allows data updates to flow down the registration tree. See Data Fields Reference for a list of those data elements and attributes that can be inherited for each EIDR record type.
Only move on to the more complex record types once you have mastered the basic types.
There are more than forty different data points in BaseObjectData, but relatively few of them are required for any given record. For a list of the required, conditionally required, and optional but recommended EIDR data elements and attributes for Abstraction records, please see EIDR Required Data Fields for Abstractions, Episodics, and Edits. For a full list of all possible data points and their individual requirements and restrictions, please see Data Fields Reference.
The following BaseObjectData elements have standard values for an Abstraction record:
- ID: The EIDR ID – assigned by the Registry at the time of creation
- StructuralType: “Abstraction”
- Mode: Usually “AudioVisual” (Silent films are “Visual” and Radio are “Audio”)
- ReferentType: One of “Movie”, “TV”, “Short”, “Web”, “Supplemental”
- Status: “valid” (in most cases)
- Registrant: Your EIDR Party ID as the creator of the record.
The remaining BaseObjectData elements uniquely describe the audiovisual asset referenced by the assigned EIDR ID. In the case of an Abstraction record, that is often a Movie or non-episodic TV, Short, Web, or Supplemental program. Include as much descriptive metadata as is known or can be determined. This extra effort at the time of registration will help ensure proper de-duplication and will facilitate later discovery and subsequent de-duplication when someone else attempts to match or register the same underlying asset.
When matching third party data to the EIDR Registry, the proper data sources must be selected and certain elements will have to be transformed to comply with EIDR requirements. See the “Selected Data Best Practices” section of Best Practices and Use Cases for Creating Abstraction Records for common data formatting rules and Data Fields Reference for other requirements and limitations.
There are a number of common issues that may be encountered during data model alignment or when preparing a catalog for EIDR matching or registration:
- Title Selection Overview
- Associated Org Overview
- Credits Overview
- Provisional Data
- Controlled Vocabularies
 Optional ExtraObjectMetadata may still be added for Lightweight Relationships or Composite work types.