The registry contains registered namespace and provider prefixes with associated access URIs for a large number of high quality data collections. These prefixes are used in web resolution of compact identifiers of the form “PREFIX:ACCESSION” or "PROVIDER/PREFIX:ACCESSION” commonly used to specify bioinformatics and other data resources.

Missing Contact
Pattern for Local Unique Identifiers

Local identifiers in Registry should match this regular expression:

Example Local Unique Identifier
00100037   Resolve
Pattern for CURIES

Compact URIs (CURIEs) constructed from Registry should match this regular expression:

Example CURIE
MIRIAM Namespace Embedded in LUI
The legacy MIRIAM standard for generating CURIEs with this resource annotates the namespaceEmbeddedInLUI as true. 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 Registry, the banana looks like MIR:. Therefore, you may see local unique identifiers for this resource that look like MIR:00100037 (instead of the canonical form 00100037) and CURIEs for this resource that look like None:MIR:00100037 (instead of the canonical form None:00100037). The Bioregistry will automatically strip off the banana when standardizing local unique identifiers and CURIEs.
Metaregistry Registry

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

Registry Name Registry Metaprefix External Prefix Curate
BioContext biocontext MIR logo miriam mir
N2T Name-to-Thing logo n2t mir

Providers are various services that resolve CURIEs to URLs. The example CURIE None:00100037 is used to demonstrate the provides available for this resource. Generation of OLS and BioPortal URLs requires additional programmatic logic beyond string formatting.

Name Metaprefix URI Registry mir
Bioregistry bioregistry miriam
Name-to-Thing n2t