Page tree

Versions Compared


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


  • Mint persistent handle identifiers for use as keys: Guaranteed persistent unique keys can be created by minting persistent handle identifiers (using either the ANDS Handle Service for handles or an equivalent). This approach implies a commitment to maintaining the currency of the location component of the key into the future.
  • Create local keys: If minting persistent handle identifiers to use as metadata record keys is not a suitable solution for a contributor, local primary keys or identifiers may be used, although these cannot be guaranteed to be globally unique. These keys should not be changed in the local system once created. Local keys can be programmatically enhanced by adding a server or domain name from your own institution, or some other unambiguous and unique identifier, to an existing object identifier.
    • Party keys can use a local unique identifier for the person or group that is maintained internally by the institution or agency, such as a staff number or username, prepended with the contributor's domain name and a trailing slash to make it globally unique. Example:
  • Generate random keys: Those contributors using the RDA Registry to manually create records may choose to use the 'Generate Random Key' function which generates keys that are unique within the Registry. The keys produced are random strings of characters.

Do not use the NLA party identifier as the RIF-CS record key by any contributor other than the National Library of Australia (NLA). Use of NLA party identifiers as keys in ANDS systems is reserved for the NLA, to enable record exchange between the RDA Registry and the NLA.


Do not use grant identifiers as keys for activity records: keys of the form are reserved for records from funders.

Contact if you have technical questions about what keys can be accepted by the RDA Registry.