The Digital Object Identifier System is for identifying content objects in the digital environment.


The DOI resolution factsheet specifies that is the preferred format:

Users may resolve DOI names that are structured to use the DOI system Proxy Server ( (preferred)). The resolution of the DOI name in this case depends on the use of URL syntax: the example DOI name doi:10.10.123/456 would be resolved from the address: "". Any standard browser encountering a DOI name in this form will be able to resolve it. The proxy service (both and the earlier but no longer preferred is accessible over IPv6, and supports DNSSEC. The proxy servers respond to HTTPS (preferred) as well as HTTP requests.

bibliography centrally registered identifier knowledge and information systems
Missing Contact
Pattern for Local Unique Identifiers

Local identifiers in Digital Object Identifier should match this regular expression:

Example Local Unique Identifiers
10.1038/s41597-022-01807-3   Resolve
10.21/FQSQT4T3   Resolve
10.1333/s00897980202a   Resolve
10.1139/z02-135   Resolve
10.1016/j.foodchem.2008.11.065   Resolve
10.1093/acprof:oso/9780195159561.001.1   Resolve
Pattern for CURIES

Compact URIs (CURIEs) constructed from Digital Object Identifier should match this regular expression:

Example CURIEs
Namespace Embedded in LUI
This resource has been annotated by the Bioregistry as having a potential namespace embedded in LUI. This means that you may see local unique identifiers that include a redundant prefix and delimiter (also known as a banana) and therefore look like a CURIE. For Digital Object Identifier, the banana looks like doi:. Therefore, you may see local unique identifiers for this resource that look like doi:10.1038/s41597-022-01807-3 (instead of the canonical form 10.1038/s41597-022-01807-3) and CURIEs for this resource that look like doi:doi:10.1038/s41597-022-01807-3 (instead of the canonical form doi:10.1038/s41597-022-01807-3). The Bioregistry will automatically strip off the banana when standardizing local unique identifiers and CURIEs.

A summary of the relations in the Bioregistry schema can be found here.

In Collection
Publication Provenance Prefixes ASKEM Epidemiology Prefixes
Metaregistry Digital Object Identifier

The metaregistry provides mappings between the Bioregistry and other registries. There are 10 mappings to external registries for this resource with 4 unique external prefixes.

Registry Name Registry Metaprefix External Prefix Curate
BioContext biocontext DOI
Biolink Biolink Model Registry logo biolink doi
Cellosaurus Cellosaurus Registry logo cellosaurus DOI
EDAM EDAM Ontology logo edam 1188
FAIRSharing FAIRSharing logo fairsharing FAIRsharing.hFLKCn
GO Gene Ontology Registry logo go DOI logo miriam doi
N2T Name-to-Thing logo n2t doi
Prefix Commons Prefix Commons logo prefixcommons doi
Wikidata Wikidata Property logo wikidata P356
RDF Information

When using this resource in RDF, the following URI format should be used:$1


A provider turns a local unique identifiers from a resource into a URI. Many providers are also resolvable as URLs (i.e., they can be used in a web browser).

The local unique identifier 10.1038/s41597-022-01807-3 is used to demonstrate the providers available for Digital Object Identifier. A guide for curating additional providers can be found here.

Name Metaprefix URI
Digital Object Identifier doi
Digital Object Identifier (RDF) rdf
Bioregistry bioregistry miriam
Name-to-Thing n2t
Extra Providers

Additional providers curated in the Bioregistry are listed here. These are typically inherited from or Prefix Commons, and need extra curation.

Code Name URL
bio2rdf Bio2RDF
doi_http Digital Object Identifier
dx_doi_http Digital Object Identifier
dx_doi_https Digital Object Identifier
miriam_legacy Legacy MIRIAM URI
scholia Scholia