Top-level Element: <recordInfo>
| Element | <recordInfo> |
|---|---|
| Definition | Information about the metadata record. |
| Attributes | displayLabel; altRepGroup; lang; xml:lang; script; transliteration |
| Subelements | <recordContentSource> <recordCreationDate> <recordChangeDate> <recordIdentifier> <recordOrigin> <languageOfCataloging> <descriptionStandard> |
GUIDELINES | EXAMPLES | MAPPINGS
GUIDELINES FOR USE
<recordInfo> is a container element that includes subelements relating to information necessary for managing metadata.
This type of administrative information can help establish the provenance of a metadata record and may enable better interpretation of the content of the record. <recordInfo> may also include information that is relevant only to the creating or managing institution.
<recordInfo> is not repeatable.
Specific DLF/Aquifer Guidelines
The DLF/Aquifer Implementation Guidelines for Shareable MODS Records require the use of one <recordInfo> element with the subelement <languageOfCataloging> to record the language of the text in the MODS record. See the recommendations for each of the subelements below for specific mention of the types of information useful to service providers.
Within the OAI context, information about the metadata record may also be recorded in an optional <about> container outside of the <metadata> container. The information contained in the MODS <recordInfo> may be repeated in the <about> container for the MODS record, but is not required.
See the <recordInfo> entry in the DLF/Aquifer Summary of MODS Requirements and Recommendations Table for further information on requirements of this element, its attributes, and subelements.
Aggregator information: The <recordInfo> field contains information that will be of use to aggregators in determining how best to understand and process a record for use in the aggregation. None of the fields are likely to be displayed to end users of the aggregation interface, or be indexed for end user search.
The DLF/NSDL Best Practices for Shareable Metadata 
discusses issues related to <recordInfo> in the "Providing Supplemental Documentation to OAI Service Providers" section.
Element Description
Attributes
altRepGroup; lang; xml:lang; script; transliteration; displayLabel
Subelements
The following subelements are described below:
- <recordContentSource>
- <recordCreationDate>
- <recordChangeDate>
- <recordIdentifier>
- <recordOrigin>
- <languageOfCataloging>
- <descriptionStandard>
Subelement: <recordContentSource>
| Definition | The code or name of the organization that either created or modified the original record. |
|---|---|
| Attributes | authority; authorityURI; valueURI |
| Subelements | None |
Guidelines for Use
This information can be useful to trace the provenance of a particular metadata record.
The name or code should be pulled from an authoritative list and indicated in the authority attribute.
<recordContentSource> should be repeated for each code or name recorded.
Specific DLF/Aquifer Guidelines
The DLF/Aquifer Implementation Guidelines for Shareable MODS Records recommend the use of <recordContentSource> to indicate the code or name of the organization that either created or modified the original record. The use of the authority attribute is also recommended.
Element Description
Attributes
authority
The Library of Congress maintains a list of Organization Code Source Codes.
If "marcorg" is used, the value in <recordContentSource> is from the MARC Code List for Organizations.
If the authority attribute is not included, the value is presumed to be textual (i.e. a name of an institution).
authorityURI
valueURI
Subelements
There are no subelements for <recordContentSource>.
Subelement: <recordCreationDate>
| Definition | The date or date and time on which the original MODS record was first created. |
|---|---|
| Attributes | encoding; point; keyDate; qualifier; lang; xml:lang; script; transliteration |
| Subelements | None |
Guidelines for Use
If a structured date is used, indicate the formatting source using the encoding attribute.
Specific DLF/Aquifer Guidelines
The DLF/Aquifer Implementation Guidelines for Shareable MODS Records make no specific recommendation for the use of <recordCreationDate>.
Within the OAI context, service providers are more likely to rely on the <datestamp> within the OAI header for information about when the record was created than this date.
If this subelement is used, follow the DLF/Aquifer guidelines outlined in the date section of the <originInfo> element with the exception that this subelement should not be identified as the keyDate.
The use of the encoding attribute is optional. If used, the RDF/Aquifer guidelines recommend using the following value for the encoding attribute: w3cdtf (see Attributes used throughout the schema for description).
The use of the keyDate is not appropriate. keyDate is used to specify a single date which should be used by OAI service providers for date indexing, sorting, and display. Only one date element should be specified as a key date. The DLF/Aquifer guidelines recommend that the keyDate appear in the <originInfo> element.
The use of the qualifier attribute within date information in <recordInfo> is not recommended. If the creation date is not known or must be inferred, it is probably not useful to include.
Element Description
Attributes
encoding; point; keyDate; qualifier; lang; xml:lang; script; transliteration
Subelements
There are no subelements for <recordCreationDate>.
Subelement: <recordChangeDate>
| Definition | The date or date and time the original MODS record was last modified. |
|---|---|
| Attributes | encoding; point; keyDate; qualifier; lang; xml:lang; script; transliteration |
| Subelements | None |
Guidelines for Use
<recordChangeDate> may serve as a version identifier for the record.
If a structured date is used, indicate the formatting source using the encoding attribute.
Specific DLF/Aquifer Guidelines
The DLF/Aquifer Implementation Guidelines for Shareable MODS Records make no specific recommendation on the use of <recordChangeDate>.
Within the OAI context, service providers are more likely to rely on the <datestamp> within the OAI header for information about when the record was last modified than this date.
If this subelement is used, follow the DLF/Aquifer guidelines outlined in the date section of the <originInfo> element with the exception that this subelement should not be identified as the keyDate. Use of the encoding attribute is optional. If used, the DLF/Aquifer guidelines recommend using the following value for the encoding attribute: w3cdtf (see Attributes used throughout the schema for description).
The use of the keyDate is not appropriate. keyDate is used to specify a single date which should be used by OAI service providers for date indexing, sorting, and display. Only one date element should be specified as a key date. The DLF/Aquifer guidelines recommend that the keyDate appear in the <originInfo> element.
The use of the qualifier attribute within date information in <recordInfo> is not recommended. If the change date is not known or must be inferred, it is probably not useful to include.
Element Description
Attributes
encoding; point; keyDate; qualifier; lang; xml:lang; script; transliteration
Subelements
There are no subelements for <recordChangeDate>.
Subelement: <recordIdentifier>
| Definition | Contains the system control number assigned by the organization creating, using, or distributing the record. |
|---|---|
| Attributes | source; lang; xml:lang; script; transliteration |
| Subelements | None |
Guidelines for Use
There should be only one <recordIdentifier> in a record.
Specific DLF/Aquifer Guidelines
The DLF/Aquifer Implementation Guidelines for Shareable MODS Records make no specific recommendation on the use of <recordIdentifier>. Within the OAI context, service providers are likely to rely on the <identifier> in the OAI header, rather than the <recordIdentifier>.
If <recordIdentifier> is used, the DLF/Aquifer guidelines recommend the use of the source attribute if possible. The source name should be from a controlled list if possible (e.g., Organization Code Source Codes), although there is not a way to indicate the controlled list.
Element Description
Attributes
source
lang; xml:lang; script; transliteration
Subelements
There are no subelements for <recordIdentifier>.
Subelement: <recordOrigin>
| Definition | Shows the origin or provenance of the MODS record. |
|---|---|
| Attributes | lang; xml:lang; script; transliteration |
| Subelements | None |
Guidelines for Use
Use this subelement 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).
<recordOrigin> can be free text or an institution may establish locally-controlled values for machine processing and consistency.
Specific DLF/Aquifer Guidelines
The DLF/Aquifer Implementation Guidelines for Shareable MODS Records recommend the use of <recordOrigin>. The information here can be useful for a service provider to understand specific encoding conventions within element values or why certain types of information appear in certain places (for example, if the MODS record was transformed from a MARC record using the standard Library of Congress stylesheet).
The DLF/Aquifer guidelines recommend using free text with the stipulation that values be understandable outside of the local context of the creating institution. Institutions may include as much or as little detail as desired in this element; however, information such as whether a transformation was done by machine or by hand, and if a standard set of transformation rules was used are useful to service providers.
Element Description
Attributes
lang; xml:lang; script; transliteration
Subelements
There are no subelements for <recordOrigin>.
Subelement: <languageOfCataloging>
| Definition | The language of the text of the cataloging in the MODS record. |
|---|---|
| Attributes | objectPart; usage; displayLabel; altRepGroup |
| Subelements | <languageTerm><scriptTerm> |
Guidelines for Use
<languageOfCataloging> is a container element for the subelement <languageTerm> where the actual language is recorded.
Language may also be recorded using the lang attribute within each specific top-level element(s) to indicate the language of the metadata in a particular element.
Specific DLF/Aquifer Guidelines
The DLF/Aquifer Implementation Guidelines for Shareable MODS Records require the use of this subelement and its subelement <languageTerm> to record the primary language of the values found within MODS elements.
If additional language(s) are used this should be indicated with the lang attribute within the specific top-level element(s) in which the additional language(s) appears.
Element Description
Attributes
objectPart
usage
displayLabel
altRepGroup
Subelements
The following subelements are enumerated below:
Subelement of <languageOfCataloging>: <languageTerm>
| Definition | Contains the language(s) of the metadata record. |
|---|---|
| Attributes | type; authority; authorityURI; valueURI; lang; xml:lang; script; transliteration |
| Subelements | None |
Guidelines for Use
<languageTerm> may be expressed in textual or coded form.
If in coded form, the source of the code is contained in the value of the authority attribute. If no authority is given, it is assumed that the information is textual.
If there is more than one representation of the same language (e.g., text and code), <languageTerm> is repeated. If the record is in more than one language, <languageOfCataloging> is repeated.
Specific DLF/Aquifer Guidelines
The DLF/Aquifer Implementation Guidelines for Shareable MODS Records require one pair of <languageTerm> elements representing the primary language of the record wrapped in a single <language> element. One of these <languageTerm> elements should carry the attribute type="text" and the other should have type="code". Additional pairs of <languageTerm> elements representing secondary languages may be included in separate <language> elements.
The DLF/Aquifer guidelines require using the value "iso639-2b" for the authority attribute of the <languageTerm> element.
Element Description
Attributes
type
- text – This value is used to express language in a textual form.
- code – This value is used to express language in a coded form.
authority
- iso639-2b – A bibliographic language code from ISO 639-2 (Codes for the representation of names of languages: alpha-3 code). The bibliographic language codes are identical to both NISO Z39.53 and the MARC Code List for Languages.
- rfc3066 – A language identifier as specified by the Internet Best Current Practice specification RFC3066. This value includes an ISO 639-1 (alpha-2) or ISO 639-2 (alpha-3) language code with optional secondary subtags.
- iso639-3 – A language code from ISO 639-3 (Codes for the representation of names of languages - Part 3: Alpha-3 code for comprehensive coverage of languages).
- rfc4646 – A language identifier as specified by the Internet Best Current Practice specification RFC4646. This document gives guidance on the use of ISO 639-1, ISO 639-2, and ISO 639-3 language identifiers with optional secondary subtags and extensions.
authorityURI
valueURI
ID; lang; xml:lang; script; transliteration
Subelements
There are no subelements for <languageTerm>.
Subelement of <languageOfCataloging>: <scriptTerm>
| Definition | Contains the script(s) of the metadata record. |
|---|---|
| Attributes | type; authority; authorityURI; valueURI; lang; xml:lang; script; transliteration |
| Subelements | None |
Guidelines for Use
<scriptTerm> may be expressed in textual or coded form.
If in coded form, the source of the code is contained in the value of the authority attribute. If no authority is given, it is assumed that the content is textual.
If there is more than one representation of the same script (e.g., text and code), <scriptTerm> is repeated. If the record is in more than one script, <languageOfCataloging> is repeated.
Element Description
Attributes
type
- text – This value is used to express script in a textual form.
- code – This value is used to express script in a coded form.
authority
authorityURI
valueURI
lang; xml:lang; script; transliteration
Subelements
There are no subelements for <scriptTerm>.
Subelement: <descriptionStandard>
| Definition | Designates the rules used for the content of the description, if applicable. |
|---|---|
| Attributes | authority; authorityURI; valueURI; lang; xml:lang; script; transliteration |
| Subelements | None |
Guidelines for Use
Identify in <descriptionStandard> which national or specialized description conventions, such as AACR2-based manuals for special forms of materials, were used, if any.
Element Description
Attributes
authority
authorityURI
valueURI
lang; xml:lang; script; transliteration
Subelements
There are no subelements for <descriptionStandard>.
EXAMPLES
<recordOrigin>machine generated</recordOrigin>
<descriptionStandard authority="marcdescription">cco</descriptionStandard>
[Record was created by Getty Research Institute using rules specified in Cataloging Cultural Objects]
<recordOrigin>human prepared</recordOrigin>
<languageOfCataloging authority="iso639-2b">fre</languageOfCataloging>
<recordOrigin>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>
<languageOfCataloging>
MAPPINGS
MARC Mapping (Bibliographic)
<recordInfo><recordContentSource> ≈ MARC 21 field 040, subfield with authority="marcorg"
Note that MODS does not mandate the use of a code from the MARC Code List for Organizations.
<recordInfo><recordCreationDate> with encoding="marc" ≈ MARC 21 field 008/00-05
<recordInfo><recordChangeDate> with encoding="iso8601" ≈ MARC 21 field 005
<recordInfo><recordIdentifier> ≈ MARC 21 field 001.
<recordInfo><recordChangeDate> with the source attribute ≈ MARC 21 field 003, except that MODS does not mandate the use of a code from the MARC Code List for Organizations.
There is no MARC equivalent to <recordInfo><recordOrigin>.
<recordInfo><languageOfCataloging> with the <languageTerm> subelement and authority="iso 639-2b" = MARC 21 field 040 subfield b.
Note that MODS allows authorities other than ISO 639-2b to be used.
<recordInfo><descriptionStandard> ≈ MARC 21 field 040$e or Leader/18.
See also MARC Mapping to MODS for the <recordInfo> element .
Dublin Core Mapping
The MODS to Dublin Core Metadata Element Set Mapping makes no recommendations about mapping <recordInfo> to a simple Dublin Core element.
For the purposes of the required Dublin Core records within the OAI context, information contained within a MODS <recordInfo> element could be mapped to an OAI <about> container for each OAI Dublin Core record disseminated from a MODS item, or, alternatively, this information is documented in a publicly accessible place and referenced from the <about> container or the <setDescription>.
Last Updated: September 13, 2012