Abstract
REQUIRED MULTILINGUAL MODS Element name: <location><physicalLocation> Short definition: The institution or repository that holds the original resource or where it is available. Input guidelines: Contains the name of the repository owning the physical original of a digitized resource. Controlled terminology, only the following values are currently permitted for this field/element: If you need additional values for this field, please consult with the DAMS management team.
Definition
The institution or repository that holds the original resource or where it is available.
DAMS input form fields
Repository
DAMS form field name | form field type | required | MODS element | Collections Portal display | notes |
---|---|---|---|---|---|
Repository Name | dropdown selection
| yes | location/physicalLocation | Owning Repository | Controlled terminology, only the values available in the dropdown selection are currently permitted for this field. If you need additional values for this field, please consult with the DAMS management team. |
Language of Repository Name | text field | yes | location/physicalLocation[@lang] (attribute of physicalLocation) | N/A | Currently, the only permitted value is "eng". Enter ISO-639-2 language code (3 letters). Default is "eng". |
Authority | dropdown selection
| no | location/physicalLocation[@authority] (attribute of physicalLocation) | N/A | Leave this selection empty until further notice.
|
Authority URI | text field | no | location/physicalLocation[@authorityURI] (attribute of physicalLocation) | N/A | Leave this field empty until further notice.
|
MODS Element description
Element <blub>
http://www.loc.gov/standards/mods/userguide/name.html
Guidelines for use
Attributes
Attribute name | Details | XPath syntax examples |
---|---|---|
Subelements
The following subelements of name are used in the DAMS:
- blubblub
Subelement blub/blubblub
Guidelines for use
Attributes
Attribute name | Details | XPath syntax examples |
---|---|---|
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 |
---|---|---|---|---|