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

Data Fields – Provenance

In addition to user-defined data, EIDR records have a number of system-defined fields. For Content records, the foremost of these is the EIDR Content ID itself. In addition, there is a resolution format option called Provenance that collects information about the history of a record. This is a read-only record structure. It cannot be registered or edited directly by a user.

The Provenance Data for is contained within ProvenanceMetadata:

Field NameTypeCardinalityExplanatory Notes
IDEIDR Content ID: e.g., 10.5240/3222-CFD8-DB21-9DA8-00B6-9   <xs:element name=”ID” type=”eidr:assetDOIType”/>1 RequiredThe EIDR Content ID of the associated record.
IssueNumberA positive integer: e.g., 7   <xs:element name=”IssueNumber” type=”xs:integer”/>1 RequiredThe version number of the record. The initial registration is 1. Each modify increments the number by one.
StatusEnumeration:  valid, in development, alias   <xs:element name=”Status” type=”eidr:statusType”/>1 RequiredThis is similar to the Status field in BaseObjectData, but it is available even when the object is deleted.[1]   For details on Provenance Status, see Registry Technical Overview.
Administrators<xs:element name=”Administrators” type=”eidr:administratorsInfoType”/>1 RequiredThe record’s Registrant and Metadata Authorities.   Administrators is a complex type where all data are recorded in child elements. See Base Object Type “
Administrators Details” above.
 /RegistrantThe EIDR Party ID of the entity that created the record: e.g., 10.5237/F012-89FD   <xs:element name=”Registrant” type=”eidr:registrantType”/>1 RequiredThe record’s original Registrant.
 /MetadataAuthorityThe EIDR Party ID of the entity that created the record: e.g.: 10.5237/F012-89FD   <xs:element maxOccurs=”4″ minOccurs=”0″ name=”MetadataAuthority” type=”eidr:metadataAuthorityType”/>0-4 OptionalThe record’s Metadata Authorities.
CreatedByThe EIDR User ID of the person or automated system that created the record: e.g., 10.5238/mklei   <xs:element minOccurs=”0″ name=”CreatedBy” type=”eidr:userDOIType”/>0-1 OptionalEIDR username that created the record.   NOTE: This field is not visible to users who are not on the record’s ACL (Access Control List).   For details on the ACL see the Registry Technical Overview.
CreationDateA full date and time in the format yyyy-mm-ddThh-mm-ssZ: e.g., 2013-10-22T22:52:17Z <xs:element name=”CreationDate” type=”xs:dateTime”/>1 RequiredRecord creation timestamp in UTC based on receipt by the Registry.
LastModifiedByThe EIDR User ID of the person or automated system that last modified the record: e.g., 10.5238/rkroon-superparty   <xs:element minOccurs=”0″ name=”LastModifiedBy” type=”eidr:userDOIType”/>0-1 OptionalEIDR username that last modified the record. When a record is first created (IssueNumber = 1), CreatedBy and LastModifiedBy are the same.   NOTE: This field is not visible to users who are not on the record’s ACL (Access Control List).   For details on the ACL see the Registry Technical Overview.
LastModificationDateA full date and time in the format yyyy-mm-ddThh-mm-ssZ: e.g., 2016-01-01T04:02:41Z <xs:element name=”LastModificationDate” type=”xs:dateTime”/>1 RequiredLast modification timestamp in UTC based on receipt by the Registry. When a record is first created (IssueNumber = 1), CreationDate and LastModificationDate are the same.
PublicationDateA full date and time in the format yyyy-mm-ddThh-mm-sssZ: e.g., 2016-01-01T04:07:50.558Z <xs:element minOccurs=”0″ name=”PublicationDate” type=”xs:dateTime”/>0 OptionalPublication timestamp with milliseconds in UTC based on when the record was finally processed and made available in the Registry (following Registry validation and De-Duplication review).   NOTE: Older records do not have a Publication Date, only Creation and Modification Dates. When it is present, this is always > the Last Modification Date.

NOTE: If the user is not on a particular record’s ACL (Access Control List), then the CreatedBy and LastModifiedBy fields will not be visible.

Here is sample XML for the Provenance Metadata for a record that has been modified seven times:

<ProvenanceMetadata xmlns="http://www.eidr.org/schema">
  <ID>10.5240/3222-CFD8-DB21-9DA8-00B6-9</ID>
  <IssueNumber>7</IssueNumber>
  <Status>valid</Status>
  <Administrators>
    <Registrant>10.5237/F012-89FD</Registrant>
    <MetadataAuthority>10.5237/F012-89FD</MetadataAuthority>
  </Administrators>
  <CreatedBy>10.5238/mklei</CreatedBy>
  <CreationDate>2013-10-22T22:52:17Z</CreationDate>
  <LastModifiedBy>10.5238/rkroon-superparty</LastModifiedBy>
  <LastModificationDate>2016-01-01T04:02:41Z</LastModificationDate>
  <PublicationDate>2016-01-01T04:07:50.558Z</PublicationDate>
</ProvenanceMetadata>

[1] Records are never deleted in EIDR. Instead, they are aliased to the Tombstone record, 10.5240/0000-0000-0000-0000-0000-X.

Updated on April 11, 2021

Was this article helpful?