A RAiD's contributors, organisations, and related objects are each identified using a specific persistent identifier scheme, enforced by the RAiD API. This page summarises which schemes are accepted for each relationship, and links to detailed instructions where the scheme needs one.
Contributors
|
Scheme |
Format |
Example |
|---|---|---|
|
ORCID |
|
|
|
ISNI |
|
|
The RAiD demo environment accepts only ORCID sandbox IDs (https://sandbox.orcid.org/...) for testing.
Organisations
|
Scheme |
Format |
Example |
|---|---|---|
|
ROR |
|
|
ROR is currently the only identifier scheme accepted for organisations.
Related objects
|
Scheme |
Format |
Example |
Notes |
|---|---|---|---|
|
DOI |
|
|
Preferred scheme when the object has a DOI. |
|
Handle |
|
|
For Handle System identifiers that are not DOIs. A DOI pasted under this scheme is validated as a Handle, not rerouted to DOI validation — use the DOI scheme instead when the object has a DOI. |
|
RRID |
|
|
For research resources registered with SciCrunch — antibodies, model organisms, cell lines, software tools, etc. |
|
|
|
For objects with no persistent identifier at all. See Use a web.archive.org identifier for a related object for the full snapshot-creation workflow. |
When you paste an identifier into the Identifier field of the Add Related Object form, the RAiD User Interface automatically detects DOI, Handle, RRID, and web.archive.org URLs and sets the correct scheme for you.