Work in Progress

Click here to show Table of Contents...

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.

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".

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.

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".

Attributes

Attribute name

Details

XPath syntax examples

point

value:

start

originInfo/dateCreated[@keyDate="yes" and @point="start"]

keyDate

value:

yes

The system will create a new 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.

originInfo/dateCreated[@keyDate="yes"]

encoding

value:

w3cdtf

originInfo/dateCreated[@keyDate="yes" and @encoding="w3cdtf"]

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.

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".

Attributes

Attribute name

Details

XPath syntax examples

point

value:

start

originInfo/dateIssued[@keyDate="yes" and @point="start"]

keyDate

value:

yes

Page lookup error: page "Key Date (WIP)" not found.

If you're experiencing issues please see our Troubleshooting Guide.

originInfo/dateIssued[@keyDate="yes"]

encoding

value:

w3cdtf

originInfo/dateCreated[@keyDate="yes" and @encoding="w3cdtf"]

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:

Dublin Core field	Mapping condition	MODS element	Notes
dc:date	MODS to DC	dateCreated[@keyDate="yes"]	The date value in the MODS element is prefixed with the text "Created: ".
dc:date	MODS to DC	dateIssued[@keyDate="yes"]	The date value in the MODS element is prefixed with the text "Issued: ".

MARC 21

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

MARC 21 field	Mapping condition	MODS element	Notes
*	MARC to MODS	dateCreated[@keyDate="yes"]	Do not map MARC data into MODS element with attribute keyDate.
*	MARC to MODS	dateIssued[@keyDate="yes"]	Do not map MARC data into MODS element with attribute keyDate.

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.

DAMS metadata element

Mapping condition

Solr DAMS

Solr Collections portal

Notes

*[@keyDate="yes"]

mods_keyDate_sort

display_date

mods_keyDate_sort is generated during ingest from the date value marked as key date in the MODS metadata.

display_date is generated during the publication process. The field contains the first 4 characters of the date value marked as key date in the MODS metadata.

display_date is used to generate the search facets for Date Created/Date Issued and Public Domain Status in the Collections portal.

*[@keyDate="yes"]

mods_keyDate_sort

mods_keyDate_sort is generated during ingest from the date value marked as key date in the MODS metadata.

mods_keyDate_sort is used for sorting the list of search results in the Collections portal.