MODS Record Origin Statements
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 name | form field type | required | MODS element | Collections Portal display | notes |
---|---|---|---|---|---|
(MODS Origin Statement) | text area | no, but strongly recommmended | recordOrigin | N/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:
| recordOrigin[@lang="eng"] |
Subelements
No subelements for <recordOrigin>.
XML Examples
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
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 element | Mapping condition | Solr DAMS | Solr Collections Portal | Notes |
---|---|---|---|---|
recordInfo/recordOrigin | mods_recordInfo_recordOrigin | N/A |
Welcome to the University Wiki Service! Please use your IID (yourEID@eid.utexas.edu) when prompted for your email address during login or click here to enter your EID. If you are experiencing any issues loading content on pages, please try these steps to clear your browser cache.