1. Home
  2. EIDR Data Fields
  3. Data Fields – Derived Types

Data Fields – Derived Types

Contents

Summary

All data described in Base Object Type above applies to the derived types, and is similarly either required or optional. Derived types provide extra metadata, some of which is required.

All derived types except Series and Compilation have a parent:

  • Season: Parent Series
  • Episode: Parent Series or Season
  • Edit: Parent Abstraction Record, Edit, or Clip (Collection records – Series, Season, and Compilation – cannot be the parent of an Edit)
  • Clip: Parent Edit or Clip
  • Manifestation: Parent Edit, Clip, or Manifestation.

Derived types with a parent can generally inherit Base Object Data from the parent as follows:

InheritanceRequired FieldsOptional Fields
Can be Inherited ApproximateLength CountryOfOrigin Mode OriginalLanguage ReferentType ReleaseDate ResourceName StructuralTypeAssociatedOrg Credits/Actor Credits/Director VersionLanguage
Cannot be InheritedAdministrators/Registrant ID Status  Administrators/MetadataAuthority AlternateID AlternateResourceName Description RegistrantExtra

An object can have only one parent, but any number of children. Inheritance is from the nearest ancestor. If a field is provided directly with the object, then it is considered Self-Defined. (Extra Object Metadata is always Self-Defined.) Some fields that are optional in a base object are required for certain derived types while some fields that are usually inherited must be specified for certain derived types. This is all described in the sections below.

Creating objects with an identified parent also creates an implicit relationship between the child and parent object. The relationship is summarized in the Relationship field of the SimpleInfo view of an object with details in extra relationship-specific metadata. Here is the example of the Relationship field for an Edit:

<Relationship type="isEditOf">10.5240/32D7-A9D7-9BC1-F5A4-ACB4-Q</Relationship>

For details on object views available when retrieving metadata from the Registry, see the Registry Technical Overview and the EIDR 2.6 REST API Reference.

The sections that follow provide a list of Extra Object Metadata fields for each derived type that is relevant to creating and modifying these types.

Updated on April 10, 2021

Was this article helpful?

Related Articles