Autogenerated MODS elements

Owned by MM Hanke
Last updated: Nov 14, 2022

List of metadata elements that are automatically generated during ingest of an asset into the DAMS. Click on the title of a form field to access more detailed documentation, for instance about the underlying MODS XML elements.

Please refer to the UT Libraries Metadata Documentation for guidelines and templates: UT Libraries Metadata Documentation

Digital Asset Level

  • Page:
    Identifier (autogenerated) — AUTOGENERATED

    MODS Element name: <identifier>

    Short definition: System-generated identifiers for assets in the DAMS.

    Input guidelines: Upon ingest, the DAMS automatically creates identifier metadata elements type with the following values:

    • utldamsURI: the URI of an asset in the DAMS
    • utldamsPID: the PID (unique identifier string) for an asset in the DAMS
    • fileName: the name of the data file ingested as the main data object for an asset in the DAMS (the OBJ datastream)

    Do not remove, alter or overwrite identifier elements with types utldamsURI, utldamsPID or fileName. Do not use these identifier type values when preparing your own metadata outside of the DAMS.

    Removing, altering or overwriting these identifier elements will cause the DAMS to malfunction.
  • Page:
    Key Date (autogenerated) — AUTOGENERATED

    MODS Element name: <originInfo><dateCreated keyDate="yes"> (Creation date) or <originInfo><dateIssued keyDate="yes"> (Issuance date)

    Short definition: System-generated, machine-readable date value derived from either Creation Date or Issuance Date.

    Input guidelines: The system will create a machine-readable date element with a keyDate attribute based on the user-provided information for Date created or Date issued. If a date range is specified, only the start date will be used as key date. If textual date information is provided, the key date will be a numerical date approximating the textual date information. The machine-readable date is for instance used for sorting of search results.

    The ingest process currently ignores a keyDate attribute set by users when preparing metadata as MODS XML. Instead, the system will create a new machine-readable date element with a keyDate attribute based on dateIssued or dateCreated (in this order and depending on which of the two is available). Any user-provided keyDate attribute will be stripped from the metadata upon ingest.

    If you want to designate a specific date element as the key date in metadata prepared for batch ingest, add the following attribute-value pair to the respective element: keyGen="yes".
  • Page:
    MODS Record Creation Date (autogenerated) — AUTOGENERATED

    MODS Element name: <recordInfo><recordCreationDate>

    Short definition: The date on which the MODS record was first created in or ingested into the DAMS.

    Input guidelines: This MODS element is automatically created upon first ingest of a metadata record in the DAMS. Do not add a recordCreationDate element to externally created MODS metadata, as it will be overwritten at the time of ingest.
  • Page:
    UTLDAMS Digital Collection (autogenerated) — AUTOGENERATED

    MODS Element name: <relatedItem type="host" displayLabel="UTLDAMS Digital Collection">

    Short definition: Parent collection in the DAMS to which the asset belongs. Distinct from Source Collection and Digital Collection.

    Input guidelines: System-generated value created upon ingest.

    Do not remove, alter or overwrite a relatedItem element with displayLabel UTLDAMS Digital Collection or any of its subelements. Do not use the combination of type="host" and displayLabel="UTLDAMS Digital Collection"  for relateItem elements when preparing your own metadata outside of the DAMS.

    Removing, altering or overwriting the relatedItem element with displayLabel UTLDAMS Digital Collection or any of its subelements will cause the DAMS to malfunction.

Collection Level

🙋 Click here to create a DAMS service request