Identifier
Abstract
REPEATABLE 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: Follow your unit/collection guidelines per Supervisor/Collection Owner for local identifiers. The following identifier element type values are reserved for identifiers that are automatically created by the DAMS upon ingest of an asset: 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.
DAMS input form fields
Identifier(s)
DAMS form field name | form field type | required | MODS element | Collections Portal display | notes |
---|---|---|---|---|---|
Identifier number/code | text field | no | identifier | Depending on the identifier Type selected for the identifier, identifier value will display as:
| |
Type | dropdown selection
| no | identifier[@type] (attribute of identifier) | Depending on the identifier Type selected for the identifier, identifier value will display as:
|
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:
- 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.
Attributes
Element Parts | Details | XPath syntax examples |
---|---|---|
type | values:
The following identifier element type values are reserved for identifiers that are automatically created by the DAMS upon ingest of an asset:
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
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 | 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
see http://www.loc.gov/standards/mods/mods-mapping.html#identifier. The following specific guidelines apply for the DAMS: Currently, only the following identifier types are supported by the DAMS MODS: 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.MARC 21 field Mapping condition MODS element Notes * identifier[@type] 001 OCLC control/accession number of the bibliographic record refers to the analog/physical original. identifier[@type="oclcSource"] 001 OCLC control/accession number of the bibliographic record refers to a derivative/surrogate representation. identifier[@type="oclcSurrogate"] 856$u identifier[@type="uri"]
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 |
---|---|---|---|---|
identifier[@type="pid"] | mods_identifier_pid | mods_identifier_pid | ||
identifier[@type="uri"] | mods_identifier_uri | mods_identifier_uri | ||
identifier[@type="local"] | mods_identifier_local | mods_identifier_local |
Welcome to the University Wiki Service! Please use your IID (yourEID@eid.utexas.edu) when prompted for your email address during login or click here to enter your EID. If you are experiencing any issues loading content on pages, please try these steps to clear your browser cache.