Versions Compared

Old Version 6

changes.mady.by.user MM Hanke

Saved on

compared with

New Version Current

changes.mady.by.user MM Hanke

Saved on

Key

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

...

Excerpt

Status
colourBlue
titleRepeatable

MODS Element name: <identifier>

Short definition: Contains a unique standard number or code that distinctively identifies a resource.

Input guidelines: Input one identifier per text field/element and designate the corresponding identifier type. Currently, the following identifier types are supported by the DAMS:

  • URI: Persistent identifier in the form of typically a URL (e.g. DOI/Handle, ARK, URN). A URI may or may not be resolvable.
  • PID: Persistent identifier that is not in the form of a URI
  • OCLC Source: OCLC number referring to a catalog entry describing the original work, e.g. the physical original of a digitized work
  • OCLC Surrogate: OCLC number referring to the catalog entry describing a digital copy of a work (if such a catalog entry exists)
  • Local: Any identifier string for local use, e.g. call number, file names or tape vault numbers.

Follow your unit/collection guidelines per Supervisor/Collection Owner for local identifiers.

Warning

The following identifier element type values are reserved for identifiers that are automatically created by the DAMS upon ingest of an asset:

  • utldamsURI
  • utldamsPID
  • fileName

Do not remove, alter or overwrite these identifiers. Do not use the reserved identifier type values when preparing your own metadata outside of the DAMS.

For more information see the following documentation page: Identifier (autogenerated).

Definition

Identifiers are strings of text that help to universally and specifically identify a particular resource.

...


Element Parts

Details

XPath syntax examples

type

values:

  • pid
  • uri
  • oclcSource
  • oclcSurrogate
  • local
  • utldamsPID
  • utldamsURI
  • fileName
Warning

The following identifier element type values are reserved for identifiers that are automatically created by the DAMS upon ingest of an asset:

  • utldamsURI
  • utldamsPID
  • fileName

Do not remove, alter or overwrite these identifiers. Do not use the reserved identifier type values when preparing your own metadata outside of the DAMS.

For more information see the following documentation page: Identifier (autogenerated).

identifier[@type="oclcSource"]

Subelements

No subelements for <identifier>.

XML Examples

Code Block
languagexml
collapsetrue
<identifier type=”uri”>http://hdl.loc.gov/loc.law/llst.072</identifier>

<identifier type=”pid”>isla-1234567-89</identifier>

<identifier type=”oclcSource”>181516677</identifier>

<identifier type=”oclcSurrogate">789456123</identifier>

<identifier type=”local”>batch no.12456523</identifier>

Mappings

Dublin Core

Depending on the direction of mapping necessary, check

The following specific guidelines apply for the DAMS:

Dublin Core fieldMapping conditionMODS elementNotes
dc:identifier
identifier*The MODS standard suggests to map identifiers in URL format beginning with http to a <location><url> element. The DAMS MODS does not use <url> elements outside of <relatedItem> elements. Map identifier URLs to the <identifier> element instead and assign attribute type="URI".

MARC 21

Multiexcerpt
MultiExcerptNamemarc-identifier

see http://www.loc.gov/standards/mods/mods-mapping.

html

html#identifier. The following specific guidelines apply for the DAMS:

MARC 21 fieldMapping conditionMODS elementNotes
*
identifier[@type]

Currently, only the following identifier types are supported by the DAMS MODS:

  • pid
  • uri
  • oclcSource
  • oclcSurrogate
001OCLC control/accession number of the bibliographic record refers to the analog/physical original.identifier[@type="oclcSource"]
001OCLC control/accession number of the bibliographic record refers to a derivative/surrogate representation.identifier[@type="oclcSurrogate"]
856$u
identifier[@type="
URI"]
uri"]

URIs recorded in MARC field 856 might be or might become outdated as content is migrated into the DAMS. Check if the URI recorded in field 856 is going to remain resolvable.

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.

Autogenerated value.
MODS elementMapping conditionSolr DAMSSolr Collections PortalNotesidentifier[@type="utldamsPID"]mods_identifier_utldamsPIDmods_identifier_utldamsPID
identifier[@type="pid"]
mods_identifier_pidmods_identifier_pid
identifier[@type="uri"]
mods_identifier_urimods_identifier_uri
identifier[@type="local"]
mods_identifier_localmods_identifier_local