The Reference Sequence (RefSeq) collection aims to provide a comprehensive, integrated, non-redundant set of sequences, including genomic DNA, transcript (RNA), and protein products.

Prefix

refseq

Alternative Prefixes

REFSEQ_PROT

Links

Homepage

Contact

Missing Contact

Pattern for Local Unique Identifiers

Local identifiers in Reference Sequence Collection should match this regular expression:
^(((AC|AP|NC|NG|NM|NP|NR|NT|NW|WP|XM|XP|XR|YP|ZP)_\d+)|(NZ_[A-Z]{2,4}\d+))(\.\d+)?$

Example Local Unique Identifiers

NP_012345   Resolve
WP_029104145.1   Resolve

Pattern for CURIES

Compact URIs (CURIEs) constructed from Reference Sequence Collection should match this regular expression:
^refseq:(((AC|AP|NC|NG|NM|NP|NR|NT|NW|WP|XM|XP|XR|YP|ZP)_\d+)|(NZ_[A-Z]{2,4}\d+))(\.\d+)?$

Example CURIEs

refseq:NP_012345
refseq:WP_029104145.1

Publications

• 2015 Reference sequence (RefSeq) database at NCBI: current status, taxonomic expansion, and functional annotation.
• 2006 NCBI reference sequences (RefSeq): a curated non-redundant sequence database of genomes, transcripts and proteins.

References

GitHub Issue https://github.com/biopragmatics/bioregistry/issues/545

Contributors

• contributor Sebastian Lobentanzer   0000-0003-3399-6695   slobentanzer

Has Canonical

NCBIProtein

The metaregistry provides mappings between the Bioregistry and other registries. There are 9 mappings to external registries for refseq with 5 unique external prefixes.

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