The Identifiers.org 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.

Prefix

mir

Links

Homepage

Pattern for Local Unique Identifiers

Local identifiers in Identifiers.org Registry should match this regular expression:
^\d{8}$

Example Local Unique Identifier

00100037   Resolve

Pattern for CURIES

Compact URIs (CURIEs) constructed from Identifiers.org Registry should match this regular expression:
^mir:\d{8}$

Example CURIE

mir:00100037

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 , 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 mir:MIR:00100037 (instead of the canonical form mir:00100037). The Bioregistry will automatically strip off the banana when standardizing local unique identifiers and CURIEs.

Contact

Missing Contact

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

In Collection (1)

Synapse.org external links

Mappings from records in Bioregistry to external registries comprises the metaregistry. This resource has 3 mappings to external registries with 1 unique external prefixes.

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 00100037 is used to demonstrate the providers available for Identifiers.org Registry. Some providers may use a different example, which is displayed in the table below. A guide for curating additional providers can be found here.