Abstract

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.

Definition

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

DAMS input form fields

System-generated metadata element. These elements cannot be edited in the DAMS metadata web form.

MODS Element description

Element <originInfo>

http://www.loc.gov/standards/mods/userguide/origininfo.html

Guidelines for use

<originInfo> is a container element that contains all subelements related to publication and origination information. It includes all dates associated with the creation, issuance, and/or publication of the resource. Dates associated with the temporal content of the resource go under <subject>, and dates associated with the metadata go in <recordInfo>. Data is input only within each subelement.

Attributes

Currently no attributes for originInfo are implemented in the DAMS.

Subelements

The following subelements of <originInfo> are used in the DAMS:

• dateCreated
• dateIssued
• (copyrightDate)
• (place)
• (publisher)

Subelement <originInfo><dateCreated>

Guidelines for use

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.

Attributes

Subelements

No subelements for dateCreated.

Subelement <originInfo><dateIssued>

Guidelines for use

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.

Attributes

Subelements

No subelements for dateIssued.

XML Examples

<originInfo>
	<dateCreated keyDate="yes" encoding="w3cdtf" point="start">2001-01-01</dateCreated>
</originInfo>

Mappings

Dublin Core

Depending on the direction of mapping necessary, check

• DC to MODS: https://www.loc.gov/standards/mods/dcsimple-mods.html
• MODS to DC: http://www.loc.gov/standards/mods/mods-dcsimple.html

The following specific guidelines apply for the DAMS:

MARC 21

see http://www.loc.gov/standards/mods/mods-mapping.html#publication. The following specific guidelines apply for the DAMS:

Solr

In general, all MODS metadata is imported into the DAMS Solr server upon ingest. The ingest process generates Solr fields typically named according to the following schema:

mods_value*_suffix

where

• value* can be one or multiple element, subelement or attribute names that allow to distinguish Solr fields
• suffix is s, t, ss, ms or mt, which refers to the type of data stored in a Solr field and how it is indexed. The Solr index usually contains multiple copies of each field with the same content, distinguished by their suffix.

The following table shows mappings between MODS elements and Solr fields for those fields that are currently used for display in the Collections Portal, or where additional processing happens in Islandora or during the publishing process. Suffixes are ignored, unless relevant for the mapping.