Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Attribute name

Details

XPath syntax examples

lang
Note

Currently, the only permitted value is "eng".

values:

Enter ISO-639-2 language code (3 letters).

location/physicalLocation[@lang="eng"]
authority
Note

Do not apply this attribute until further notice.

values: 

  • naf
  • viaf
  • local

Authority control for names is strongly recommended. Consult one of the following if applicable:

location/physicalLocation[@authority="viaf"]

location/physicalLocation[@authority="naf"]

authorityURI
Note

Do not apply this attribute until further notice.

values: 

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.

location/physicalLocation[@authorityURI="http://viaf.org/viaf/data"]

location/physicalLocation[@authorityURI="http://id.loc.gov/authorities/names"]

displayLabel

value:

  • Repository

Subelements

No subelements for <physicalLocation>.

XML Examples

Code Block
languagexml
collapsetrue
<!-- some XML examples --><location>
	<physicalLocation lang="eng" displayLabel="Repository">Alexander Architectural Archives, University of Texas Libraries, The University of Texas at Austin</physicalLocation>
</location>

<location>
<physicalLocation lang="eng" displayLabel="Repository">Fine Arts Library, University of Texas Libraries, The University of Texas at Austin</physicalLocation>
</location>

<location>
	<physicalLocation lang="eng" displayLabel="Repository">University of Texas Libraries, The University of Texas at Austin</physicalLocation>
</location>

Mappings

Dublin Core

...

No standardised mapping of <location><physicalLocation> to a DC element or vice versa available, cf.:

The following specific guidelines apply for the DAMS:
Dublin Core fieldMapping conditionMODS elementNotes

MARC 21

see See http://www.loc.gov/standards/mods/mods-mapping.html. The following specific guidelines apply for the DAMS:

MARC 21 fieldMapping conditionMODS elementNotes

Note

Currently, only limited values from a list of controlled names are permitted.

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
location/physicalLocation

mods_location_physicalLocation

mods_location_physicalLocation