1. Home
  2. EIDR Data Fields
  3. Composite
  4. Data Fields – Composite

Data Fields – Composite

Composites are single works that contain elements of one or more other works, such as a clip show, a work that incorporates stock footage, a program that includes a flashback from an earlier program, etc. The Composite information is added to an Abstraction record, so you can have a Movie that’s a Composite, an Episode that’s a Composite, etc.[1]

Composite data fields can be included at the time an EIDR record is created or added later. See the Registry Technical Overview for details on adding Relationships to existing records.

The previously existing Elements that are included in a Composite can be identified by an EIDR Content ID or an Alternate ID if the Element does not have an EIDR ID.

The Extra Object Metadata for a Composite is contained within CompositeInfo:

Field NameTypeCardinalityExplanatory Notes
CompositeClassEnumeration: Mashup, Omnibus, Excerpt, Inclusion, Other   <xs:element name=”CompositeClass” type=”eidr:compositeClassType”/>1 RequiredDescribes the general type of Composite.   See “CompositeClass Details” below.  
Element<xs:element maxOccurs=”unbounded” minOccurs=”0″ name=”Element” type=”eidr:compositeElementType”/>0-∞ OptionalThe components of the Composite, creating an inventory list of the included Elements.   Element is a complex type where all data are recorded in child elements.   NOTE: A Composite should, but does not have to include Elements.
 /IDEIDR Content ID: e.g., 10.5240/4DDF-A111-8543-E67B-58F6-2 <xs:element name=”ID” type=”eidr:assetDOIType”/>0-1 Conditionally RequiredThe EIDR Content ID of the Element.   Required if OtherID is not present.
 /OtherIDA text string with no whitespace characters, constrained according to the idType (free text for “Proprietary”): e.g., tt0058548 <xs:element name=”OtherID” type=”eidr:alternateIDType”/>0-1 Conditionally RequiredAn Alternate ID of the Element .   Required if ID is not present.   This is the same type of field as BaseObjectData/AlternateID. See “
Alternate ID Details” above.
  @relationEnumeration:   IsSameAs, IsEntirelyContainedBy, ContainsAllOf, IsPartiallyContainedBy, ContainsPartOf, IsDerivedFrom, IsSourceOf, HasCueSheet, HasSoundRecording, DepictsEvent, Duplicate, Other <xs:attribute name=”relation” type=”eidr:alternateIDRelationType”/>0-1 OptionalThe relationship between the included Element and the work identified by the Alternate ID. In most cases, this is isSameAs (when not provided, isSameAs is assumed), but if the included Element was derived from the Alternate ID source material, then the Relation would be IsDerivedFrom.
  @xsi:typeEnumeration:   Ad-ID, AFI, AMG, Baseline, BFI, cIDF, CRID, DOI, EAN, GRid, GTIN, IMDB, ISAN, ISRC, ISTC, IVA, Lumiere, MUZE, Proprietary, SMPTE-UMID, TRIB, TVG, UPC, URI, UUID, URN1 RequiredThe Alternate ID type. Generally, the organization that issues the IDs. NOTE: “Proprietary” is a term of art from the Standards Community. It does not mean that the ID is not freely available or publicly resolvable. All that it means is that the ID is not defined in a published standard.
  @domainA text string with no whitespace characters, following the general pattern of a dot-separated list of sub-domains ending in a top-level domain followed by an optional slash-separated list of ID types: e.g.: spe.sony.com/MPM <xs:attribute name=”domain” type=”eidr:constrainedURIType” use=”required”/>0-1 Conditionally RequiredIdentifies the organization that issued the ID with the option to specify a type of ID if the organization maintains more than one. Required if Type is Proprietary. Not valid otherwise.
 /SourceStartAn amount of time (xs:duration): e.g., PT4M24S   <xs:element minOccurs=”0″ name=”SourceStart” type=”eidr:startingPointType”/>0-1 OptionalThe starting point of the extracted Element included in the Composite as measured from the start of the source material referred to by ID or OtherID. It is presented using the same xs:duration data type as the time components discussed in “Time and Date Details” above.
 /SourceDurationAn amount of time (xs:duration): e.g., PT4M24S   <xs:element minOccurs=”0″ name=”SourceDuration” type=”xs:duration”/>0-1 OptionalThe total length of the Element extracted from the source program referred to by ID or OtherID. It is presented using the same xs:duration data type as the time components discussed in “Time and Date Details” above.
 /ComponentsModeEnumeration: Audio, Visual, AudioVisual, Other, All   <xs:element minOccurs=”0″ name=”ComponentsMode” type=”eidr:componentsModeType”/>0-1 OptionalThe Element’s Mode, which need not be the same as the source material’s Mode. For example, a Visual Element could be extracted from an AudioVisual source.
 /DestStartAn amount of time (xs:duration): e.g., PT4M24S   <xs:element minOccurs=”0″ name=”DestStart” type=”eidr:startingPointType”/>  0-1 OptionalThe starting point of the included Element  measured from the start of the Composite program. It is presented using the same xs:duration data type as the time components discussed in “Time and Date Details” above.
 /DestDurationAn amount of time (xs:duration): e.g., PT4M24S   <xs:element minOccurs=”0″ name=”DestDuration” type=”xs:duration”/>  0-1 OptionalThe total length of the Element within the Composite program, including any adjustments or alterations to the Element. It is presented using the same xs:duration data type as the time components discussed in “Time and Date Details” above.
 /DescriptionUnicode 128 character string: e.g., Interview stock footage   <xs:element minOccurs=”0″ name=”Description” type=”eidr:string128Type”/>0-1 OptionalA free text description of how the Element is used within the Composite.

Here is sample XML for the Extra Object Metadata for a Composite (the preceding Base Object Data is not shown):

<ExtraObjectMetadata>
  <CompositeInfo>
    <CompositeClass>Mashup</CompositeClass>
    <Element>
      <ID>10.5240/2046-2046-2046-2046-02BC-V</ID>
      <SourceStart>PT0S</Start>
      <SourceDuration>PT30M</SourceDuration>
    </Element>
    <Element>
      <ID>10.5240/2046-2046-2046-2046-0283-Q</ID>
      <SourceDuration>PT6M</SourceDuration>
    </Element>
  </CompositeInfo>
</ExtraObjectMetadata>

NOTE: Composite data are always added to an Abstraction record. See “Composite Details” under “Base Object Type”, above, for an example of a Composite Movie. See “Composite Details” under “Episode”, above, for an example of a Composite Episode. In the former case, the CompositeInfo may be the only entry in the ExtraObjectMetadata section. In the latter case, CompositeInfo follows EpisodeInfo in the ExtraObjectMetadata section.

CompositeClass Details

ValueExplanatory Notes
MashupThe resulting work is primarily a sequence of clips, edited together, with little other material, such as a clip show. This is the most common Composite Class.
OmnibusThe Composite work is a condensed summary of a group of other programs, such as the weekly run of a serial.
ExcerptA substantial portion of the Composite is made up of clips from other works along with significant new material, such as That’s Entertainment (1974), which mixed existing clips with new interviews. This differs from a Mashup, where the included clips comprise nearly the entire program.
InclusionThe included clips represent a relatively small portion of the Composite and are not its primary focus.
OtherThe Composite is in a form not otherwise defined.

[1] You cannot add Composite information to a Series, Season, or Compilation because, while these are Level 1 records, they are container or grouping records, not Title records.

Updated on April 11, 2021

Was this article helpful?