Abstract
REQUIRED REPEATABLE MODS Element name: <recordContentSource> Short definition: Name of the organization, unit or entity that either created or modified the original metadata record. Input guidelines: Default is University of Texas Libraries. Replace as needed. The name or code should be pulled from an authoritative list and indicated in the authority and authorityURI attribute. This field/element should be repeated for each code or name recorded.
Definition
Name of the organization, unit or entity that either created or modified the original metadata record.
DAMS input form fields
Record Info: MODS (Record Content) Source(s)
| DAMS form field name | form field type | required | MODS element | Collections Portal display | notes |
|---|---|---|---|---|---|
| Source Name | text field | yes | recordContentSource | N/A | |
| Authority | dropdown selection
| recordContentSource[@authority] (attribute of recordContentSource) | N/A | Authority control for names is strongly recommended. Consult one of the following if applicable:
| |
| Authority URI | text field | recordContentSource[@authorityURI] | N/A | When using a local authority file, provide a URI that identifies the file. The URI should identify the authority file as a whole, not to a specific entry. If you selected "naf" or "viaf" in the Authority form field, leave the field blank. The DAMS will automatically add URIs for LoCNAF and VIAF respectively. |
MODS Element description
Element <blub>
http://www.loc.gov/standards/mods/userguide/name.html
Guidelines for use
Attributes
Element Parts | Details | XPath syntax examples |
|---|---|---|
Subelements
The following subelements of name are used in the DAMS:
- blubblub
Subelement blub/blubblub
Guidelines for use
Attributes
Subelements
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
The following specific guidelines apply for the DAMS:
| Dublin Core field | Mapping condition | MODS element | Notes |
|---|---|---|---|
MARC 21
see http://www.loc.gov/standards/mods/mods-mapping.html. The following specific guidelines apply for the DAMS:
| MARC 21 field | Mapping condition | MODS element | Notes |
|---|---|---|---|
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 |
|---|---|---|---|---|