Note
Work in Progress

Expand

title	Click here to show Table of Contents...

Table of Contents

Abstract

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

Upon ingest, the DAMS automatically creates identifier metadata elements type with the following values:

utldamsURI: the URI of an asset in the DAMS
utldamsPID: the PID (unique identifier string) for an asset in the DAMS
fileName: the name of the data file ingested as the main data object for an asset in the DAMS (the OBJ datastream)

Excerpt

Status

colour	Red
title	Autogenerated

MODS Element name: <identifier>

Short definition: Contains a unique standard number or code that distinctively identifies a resourceSystem-generated identifiers for assets in the DAMS.

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

Do not remove, alter or overwrite these identifiersidentifier elements with types utldamsURI, utldamsPID or fileName. Do not use the reserved these identifier type values when preparing your own metadata outside of the DAMS.

Removing, altering or overwriting these identifier elements will cause the DAMS to malfunction.

Definition

Identifiers are strings of text that help to universally and specifically identify a particular resourceSystem-generated identifiers for assets in the DAMS.

DAMS input form fields

Identifier(s)

...

Depending on the identifier Type selected for the identifier, identifier value will display as:

PID
URI
Local

...

dropdown selection

(none/empty)
pid
uri
oclcSource
oclcSurrogate
local

...

identifier[@type]

(attribute of identifier)

...

Depending on the identifier Type selected for the identifier, identifier value will display as:

PID
URI
Local

System-generated metadata element. These elements cannot be edited in the DAMS metadata web form.

MODS Element description

Element <identifier>

http://www.loc.gov/standards/mods/userguide/identifier.html

Guidelines for use

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

...

Upon ingest, the DAMS automatically creates identifier metadata elements type with the following values:

utldamsURI: the URI of an asset in the DAMS
utldamsPID: the PID (unique identifier string) for an asset in the DAMS
fileName: the name of the data file ingested as the main data object for an asset in the DAMS (the OBJ datastream)

Warning

Do not remove, alter or overwrite identifier elements with types utldamsURI, utldamsPID or fileName. Do not use these identifier type values when preparing your own metadata outside of the DAMS.

Removing, altering or overwriting these identifier elements will cause the DAMS to malfunction.

Attributes

Element Parts

Details

XPath syntax examples

type

values:

pid
uri
oclcSource
oclcSurrogate
local
utldamsPID
utldamsURI
fileName

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

Warning

utldamsURI
utldamsPID
fileName

Do not remove, alter or overwrite these identifiersidentifier elements with types utldamsURI, utldamsPID or fileName. Do not use the reserved these identifier type values when preparing your own metadata outside of the DAMS.

Removing, altering or overwriting these identifier elements will cause the DAMS to malfunction.

identifier[@type="oclcSource"]

Subelements

No subelements for <identifier>.

XML Examples

Code Block

language	xml
collapse	true

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

<identifier type=”pid”>isla-1234567-89<"utldamsURI">dams-p01-rh7.lib.utexas.edu/islandora/object/utlgs:42c659c8-e331-41d3-a661-1171a46407c6</identifier>

<identifier type=”oclcSource”>181516677<"utldamsPID">utlgs:42c659c8-e331-41d3-a661-1171a46407c6</identifier>

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

<identifier type=”local”>batch no.12456523</identifier>"fileName">txu-oclc-945199055.tif</identifier

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
dc:identifier	MODS to DC	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"	System-generated identifier are mapped to dc:identifier elements.
dc:identifier	DC to MODS	identifier	Do not map DC element values into MODS identifier elements with types utldamsURI, utldamsPID or fileName.

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

*

MARC to MODS

identifier[@type]

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

pid
uri
oclcSource
oclcSurrogate

001

OCLC control/accession number of the bibliographic record refers to the analog/physical original.="utldamsURI"]

Do not map MARC data into MODS identifier elements with types utldamsURI, utldamsPID or fileName.

*

MARC to MODS

identifier[@type="oclcSourceutldamsPID"]

001

OCLC control/accession number of the bibliographic record refers to a derivative/surrogate representation.

Do not map MARC data into MODS identifier elements with types utldamsURI, utldamsPID or fileName.

*

MARC to MODS

identifier[@type="oclcSurrogatefileName"]

856$u

identifier[@type="URI"]Do not map MARC data into MODS identifier elements with types utldamsURI, utldamsPID or fileName.

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	Solr DAMS	Solr Collections Portal	Notes
identifier[@type="utldamsPID"]	mods_identifier_utldamsPID	mods_identifier_utldamsPID	Autogenerated value.
identifier[@type="PIDutldamsURI"]	mods_identifier_pidmods_identifier_pidutldamsURI	N/A
identifier[@type="URIfileName"]	mods_identifier_uri	mods_identifier_uri	identifier[@type="local"]	mods_identifier_local	mods_identifier_localfileName	N/A

Versions Compared

Old Version 1

New Version Current

Key

Abstract

Definition

DAMS input form fields

Identifier(s)

MODS Element description

Element <identifier>

Guidelines for use

Attributes

Subelements

XML Examples

Mappings

Dublin Core

MARC 21

Solr

Page Comparison

Versions Compared

Old Version 1

New Version Current

Key

Abstract

Definition

DAMS input form fields

Identifier(s)

MODS Element description

Element <identifier>

Guidelines for use

Attributes

Subelements

XML Examples

Mappings

Dublin Core

MARC 21

Solr