Identifier

This page describes the Identifier element for RegistryObject and not one of the Identifier child elements found in CitationMetadata or RelatedInfo, however the Identifier Type vocabulary is the same and may be used for all three elements.

Meaning & purpose

An identifier is a sequence of characters or words that uniquely identify an object within a particular context or the domain of a specified authority. It may be globally unique if the specified authority has a global domain.
Identifiers that are useful for discovery, linking of metadata records, reuse, or to support the functions of the metadata provider, can be recorded, even if they are not unique or persistent.

For more information on persistent identifiers, see Citation and Identifiers.

Identifier attributes

Identifier Type

An Identifier Type is required. Preferably, specify a type from the Identifier Type vocabulary below. For types not in the vocabulary, use the Namespace in Identifiers.org Central Registry as the Identifier Type.

Use in Research Data Australia

Identifiers are displayed within Research Data Australia as provided by the contributor, as clickable links (when possible), and prefixed with the identifier type.

Where a resolvable URL can be generated for a provided identifier, the displayed identifier will become a clickable link to the generated URL. For example, a DOI provided as a:

• string, will display as - ‘DOI : 10.1109/5.771073' 
• URL, will display as - 'DOI : https://doi.org/10.1109/5.771073'

The provision of full URLs is preferable where available, both to facilitate navigation by users and to support linked data developments. 

Where two or more records (from the same or different data sources) share a common identifier, the records will be treated as describing the same thing. In Research Data Australia, these records are merged into a single search result and links to each of the merged records are displayed on the view page of each record. 

Best practice

For all records

• Identifiers for collections, parties, activities or services being described, including non-unique and local identifiers, should be recorded in the Identifier element. The Identifier element can be repeated if multiple identifiers need to be described.
• Contributors are strongly encouraged to provide a persistent, globally unique identifier such as a DOI , ORCID, ROR or RAID in the Identifier element. 

For collections

• It is strongly recommended that all identifiers be persistent, e.g. a DOI, but any URI is acceptable.
• If a global identifier is not available as a resolvable URL, provide it using a type that reflects the authority for the identifier. This will display as text only (not a resolvable link) in Research Data Australia.

For activities

• Where a project is connected to a funding grant from the ARC or NHMRC, the project or program record should record the related grant identifier in the Identifier element using the Identifier Type "arc" or "nhmrc" (rather than "purl"). This enables linking of project records to grant records supplied by funders. Where project descriptions from a research institution or agency use a local project identifier, these can also be provided.
• As more funders supply grant information to Research Data Australia, persistent grant identifiers will be available for their grants as well. The list of funders contributing grant information can be viewed on the Explore Grants and Projects page in Research Data Australia.
• Where a RAID has been minted for a project or program, it is recommended that the RAID be provided in the Identifier element for the activity using the Identifier Type "raid".

For parties

• If there is a globally unique identifier for a party, preferably an ORCID or a ROR, it is strongly recommended that it be provided in the Identifier element with the corresponding Identifier Type. System lookup facilities for ORCIDs and RORs are available.
• For funders, FundRef identifiers are being transitioned to ROR, however either identifier can be used and there is no need to provide both in separate Identifier elements.
• Include all relevant identifiers, as this helps in the disambiguation of similar names, discovery and record linking.

XML encoding examples

<identifier type="doi">https://doi.org/10.4225/35/569434cfba16e</identifier>
<identifier type="handle">http://hdl.handle.net/102.100.100/15</identifier>
<identifier type="local">experiment/view/17</identifier>

Persistent identifier examples:
<identifier type="orcid">https://orcid.org/0000-0002-1825-0097</identifier>
<identifier type="AU-ANL:PEAU">http://nla.gov.au/nla.party-1472115</identifier>
<identifier type="ror">https://ror.org/038sjwq14</identifier>
 
Other resolvable identifier example:
<identifier type="uri">http://viaf.org/viaf/29541064</identifier>
 
Local identifier examples:
<identifier type="local">researcher:3950184</identifier>
<identifier type="uri">http://www.myuni.edu.au/staffprofiles/s3799332</identifier>

RAID example:
<identifier type="raid">https://raid.org/10.26259/1cac5eb1</identifier>

Australian Research Council identifier example:
<identifier type="arc">http://purl.org/au-research/grants/arc/DP0559024</identifier>

National Health and Medical Research Council identifier example:
<identifier type="nhmrc">http://purl.org/au-research/grants/nhmrc/100009</identifier>

Change history