Abstract

REPEATABLE 

MODS Element name: <recordInfo><recordOrigin>

Short definition: Information about the origin or provenance of the MODS record.

Input guidelines: Use to record information about the origin, or provenance of the MODS record including what methods were used to prepare the MODS record (machine generated or human prepared) and what transformations have been applied (e.g., the result of converting an existing MARC 21 record to MARCXML and to MODS). Follow your unit/collection guidelines per Supervisor/Collection Owner.

Definition

Information about the origin or provenance of the MODS record.

DAMS input form fields

Record Info: MODS Origin Statement(s)

DAMS form field nameform field typerequiredMODS elementCollections Portal displaynotes
(MODS Origin Statement)text areano, but strongly recommmendedrecordOriginN/A

MODS Element description

Element <recordInfo>

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

Guidelines for use

<recordInfo> is a container element that includes subelements relating to information necessary for managing metadata.

Attributes

No attributes for <recordInfo> are currently implemented in the DAMS.

Subelements

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

  • recordOrigin
  • (languageOfCataloging)
  • (recordContentSource)
  • (recordCreationDate)


Subelement <recordInfo><recordOrigin>

Guidelines for use

Use to record information about the origin, or provenance of the MODS record including what methods were used to prepare the MODS record (machine generated or human prepared) and what transformations have been applied (e.g., the result of converting an existing MARC 21 record to MARCXML and to MODS). Follow your unit/collection guidelines per Supervisor/Collection Owner.

Attributes

Element Parts

Details

XPath syntax examples

lang

value:

  • eng
recordOrigin[@lang="eng"]

Subelements

No subelements for <recordOrigin>.

XML Examples

<recordInfo>
	<recordOrigin lang="eng">Record has been transformed into MODS from a qualified Dublin Core record using a stylesheet available at http://www.sample.edu/. Metadata originally created in a locally modified version of qualified Dublin Core (data dictionary available: http://www.sample.edu/.)</recordOrigin><recordContentSource authority="naf" authorityURI="http://id.loc.gov/authorities/names">University of Texas Libraries</recordContentSource><recordCreationDate encoding="w3cdtf">2018-07-31</recordCreationDate>
</recordInfo>

<recordInfo>
	<recordOrigin lang="eng">human prepared</recordOrigin>
</recordInfo>

Mappings

Dublin Core

Depending on the direction of mapping necessary, check

MARC 21

See http://www.loc.gov/standards/mods/mods-mapping.html.

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.

MODS elementMapping conditionSolr DAMSSolr Collections PortalNotes
recordInfo/recordOrigin

mods_recordInfo_recordOrigin

N/A