Figure 5. Representative Genomic context (A) and Bibliography (B) sections of a Full Report display. Note that the GeneRIFs (C) subsection is provided in a scrolling window.
Records are added to Entrez Gene if any of the following conditions is met:
A RefSeq is created for a completely sequenced genome and that record contains annotated genes. In the case of RNA viruses with polyprotein precursors, annotated proteins may be treated as equivalent to a ”gene”.
A recognized genome-specific database provides information about genes (preferably with defining sequence) or mapped phenotypes.
The NCBI Genome Annotation Pipeline reports model genes.
A model organism is scheduled for sequencing, and representative sequences are identified to characterize known genes.
The minimum set of data necessary for a gene record, therefore, is: a unique identifier, or GeneID, assigned by NCBI; a preferred symbol; and either defining sequence information, map information, or official nomenclature from an authority list.
Gene records are not created for genomes that are incompletely represented by whole genome shotgun (WGS) assemblies, which are provided in terms of RefSeqs by accession numbers of the pattern NZ_ABCD12345678. Although not all existing records have been removed, loci defined by repetitive elements, endogenous retroviruses not named by nomenclature authorities, and loci identified by single transcripts with no other supporting data also are not in scope for Entrez Gene.
A unique GeneID is assigned to each new record. There are currently two number generators; one that is assigning values in the range of 7,000,000 – 99,999,999 and another that is assigning values > 100,000,000.
Records are updated when new information is received. For some genomes, this may occur when a genome is re-annotated and the corresponding RefSeqs are updated. For other genomes, this may occur when any information attached to a single gene record is altered. Updates are processed daily.
| Data category | Source | Species | Update frequency |
|---|---|---|---|
| Official nomenclature | HUGO Gene Nomenclature Committee (HGNC) | Human | Daily |
| Mouse Gene Nomenclature Committee (MGNC) | Mouse | Daily | |
| Rat Gene Nomenclature Committee | Rat | Bimonthly | |
| Zebrafish Nomenclature Commitee (ZNC) | Zebrafish | Weekly | |
| FlyBase | D. melanogaster | Data release | |
| MaizeGDB | Zea mays | Data release | |
| SGD | S. cerevisiae | Weekly | |
| Xenbase | X. tropicalis | Weekly | |
| GeneRIF | Index Section, NLM/public | All | Weekly/Daily |
| HuGE Navigator | Human | Bimonthly | |
| GO terms | Gene Ontology | Several | Weekly |
| Disease Names | OMIM (genemap) | Human | Daily |
| Interactions | BIND/BOND | Several | Static |
| BioGRID | Several | Monthly | |
| EcoCyc | E. coli | Data release | |
| HPRD | Human | Static | |
| KEGG pathway | KEGG | Several | Weekly |
| REACTOME | REACTOME | Several | Data release |
Figure 5. Representative Genomic context (A) and Bibliography (B) sections of a Full Report display. Note that the GeneRIFs (C) subsection is provided in a scrolling window.
When any change is made to a record, the modification date is changed. This includes changes in GeneRIFs. The modification date, therefore, is the later of any update to Gene or supplemental information.
About two days are required for an update to be reflected in all reports from Entrez Gene. In some cases, the full report may be more up-to-date than the ftp site, because the ftp files are regenerated after a re-index of the database, and this process may lag a day behind the update to the database itself.
Entrez Gene will suppress a record for several reasons:
Review by NCBI staff and/or collaborators indicates that a record is no longer supported or in scope for Entrez Gene. An explanation for the suppression is provided by RefSeq staff.
Review by NCBI staff and/or collaborators indicates that the original record defined only part of what is now understood to be the functional gene unit. In that event, one record is made secondary to another, and the URL to the current record is provided.
The molecular basis for a Gene record that was previously only a mapped phenotype is discovered, and there was already a record for the causative locus or loci. The record for the mapped phenotype is made secondary to one of the causative loci and added to the phenotype section of all.
By default, all records, i.e., current and suppressed, are retrieved by an unqualified query. There are several methods that can be used to restrict your results to current records. These include qualifying your query with the phrase “AND alive[property]“ or using the check box Current Records in the Include Only section of the Limits page. Query Tips provides additional details.
The content of an Entrez Gene record depends on availability of information and curatorial decisions. If you have suggestions about types of information that should be included in general, or for a specific record, please let us know by using our update form. More details about maintenance of certain types of information are provided in Gene’s FAQ.
short reports of gene-specific data (Summary, Brief, Gene Table, UI List)
comprehensive reports of gene-specific data (Full Report, ASN.1, Display XML)
links to records in other Entrez databases based on a set of records retrieved from Entrez Gene
links to databases outside the Entrez system, usually databases not in NCBI (LinkOut)
Short reports provide details about the subsets of gene-specific data. The display options are:
In the Summary format, each result is numbered, and a check box is provided at the left of the number. The check box enables you to select which of the records in the retrieval set that you want to review in another format, according to your selection in the Display menu. If none is checked, all are displayed in the selected format.
Official symbol
Locus tag
First symbol in the synonym list
The summary display allows you to reorder the results by several methods:
Relevance (the current default). Relevance is calculated from Gene's assessment of what fields are the most important by which to find search results. For example, Gene assigns more value to results if they match a term in the 'Gene Name' (symbol) field than to a match in free text such as the RefSeq or GeneRIF summary. Thus if your query is the single term 'cat', then records with symbols of 'cat' will be sorted ahead of records with the term cat only elsewhere in the record.
Gene Weight. Gene Weight is calculated from multiple lines of evidence geared toward evaluating how well a gene has been characterized. These lines include:
Informative Gene-PubMed links. Informativeness is inversely proportional to the number of Genes connected to a PubMed record.
Informative symbols or full names. A gene with a symbol constructed as LOC+GeneID is weighted less, for example, than a gene with the symbol 'ABCA1'. A gene with a description that starts with the word 'hypothetical' is weighted less than one with a description that starts with 'cystic fibrosis'.
Inclusion in HomoloGene or Protein Clusters. Genes (or their products) that are known to be conserved are weighted more highly.
Inclusion in OMIM or Books.
Gene symbol
Chromosome. Choosing this option causes the records to be sorted in this order:
Alphabetically by organism name
Numerically by chromosome
Numerically by the start position on the chromosome.
For example, suppose that the search results include genes for Homo sapiens (human) and Mus musculus (mouse). The human genes will all appear before those for mouse. Within the set of human genes in the results, those that are placed on chromosome 1 will appear first, followed by those placed on chromosome 2, and so on. Finally, within a chromosome, genes will be sorted according to their start positions on the chromosome. Genes that are not placed on a chromosome will appear at the end of the results. Genes that are placed on multiple chromosomes will be sorted according to the first such chromosome.
The functions allowed from the Brief display are similar to those described from the Summary display. The purpose of the Brief option is to support a more compact result set while providing enough information (the preferred symbol, 20 characters of the full name, and the GeneID) for you to select records to display a Full Report.
The Gene Table display represents the gene structure as annotated on the current genomic RefSeq representing the reference genome. This annotation is updated only with each comprehensive re-annotation cycle at NCBI (a build), usually no more than twice a year. This means that if the version of a RefSeq RNA has changed, or if the number of transcript variants has changed, the table will be out of date with respect to the Reference Sequences section of the full Gene report.
The table reports the intron/exon organization of each transcript, and, if an mRNA, the region of each exon that contains coding sequence (sample). It does this in two ways:
graphically, by repeating the display included in the Full Report
in a table, by reporting the position of any exon, intron, or coding region
| Scope | Link to use |
|---|---|
| Complete gene feature | Options from the menu opened by clicking on the genomic RefSeq accession (format NC_, NW_ NT_) at the top of the graphic display. |
| Complete RNA | Options from the menu opened by clicking on the RNA RefSeq accession (format NM_, NR_, XM_, XR_) at the left of the graphic display. Display in GenBank format from the RNA RefSeq accession at the top of the accession-specific subsection of the table. |
| Complete protein | Options from the menu opened by clicking on the Protein RefSeq accession (format NP_, XP_) at the left of the graphic display. Display in GenBank format from the protein RefSeq accession at the top of the accession-specific subsection of the table. |
| Single intron, exon, or coding sequence (CDS) | Display in FASTA format from the range shown in the corresponding table column. |
Please note that this function is not supported when the gene has not (yet) been annotated on any of NCBI's Genomic RefSeqs.
The sequence being retrieved is from the indicated genomic sequence, not the RNA. This means that the length of a poly(A) tail is not included in the report.
When viewing the sequence-specific nucleotide or protein record, use the Display options to generate the format you prefer.
Because the Gene Table reflects the annotation on the current genomic sequence, for bulk access you may prefer to use the seq_gene.md.gz file in the species-specific mapview subdirectory. These files are available for genomes that can be viewed in Map Viewer. For example:
The data in Gene Table reflect the current NCBI batch annotation, so it is possible that the RefSeq mRNAs, which are updated continuously, have changed. Check also the Reference Sequences section of the Entrez Gene record to determine whether updates have occurred (new versions and/or more variants and/or suppression resulting from review).
Navigation: In the Genomic regions, transcripts, and products section, the mRNA and Protein links in the table are hyperlinked to the Exon information table specific to that accession.
To the right of the Exon information tables are blue-shaded icons:
top of the page
table for the previous product
table for the next product
This display is essentially the same as that of the Brief format, with the addition of the unique identifiers (UIs) for a Gene record on the second line. The difference between the Brief and UI List displays is more apparent, however, when selecting the Send to Text option. For the UI List, only the Gene identifiers are reported.
All of the content that Entrez Gene provides is defined by the ASN.1 file. The Full Report display is of the HTML transformation of that ASN.1 and includes navigation tools (Table of Contents and Links), diagrams, and text. Some gene-specific information is not maintained in Entrez Gene but is maintained in more specialized databases such as GEO, HomoloGene, UniGene, and Probe. Access to the additional information maintained in other resources within NCBI or external to NCBI is provided by the Links menu at the top right and by other HTML anchors within the page.
For convenience, there is another Display bar at the bottom of the page. Some options discussed here are:
If multiple records are selected for display, the start of each record is indicated by the numbered open box at the left and by the Links menu at the right.
The second line of the title section contains the NCBI GeneID and the last date a record was changed. The date is in the format day-month-year. Change is defined as any modification to the content of the record, including ancillary changes such as the URL for a displayed link.
Figure 4. Representative Summary (A) and Genomic regions, transcripts, and products sections (B) of a Full Report display. Each accession in this display is hyperlinked to the Nucleotide or Protein databases as appropriate, where standard tools exist to facilitate downloading sequence.
Official Symbol: and Name: Nomenclature provided by the named external authority.
Identifier from the primary data provider: Identifier and link to the major resource outside of NCBI that provided information about this gene.
Locus tag for the record is in the next line. Locus tag corresponds to the systematic feature qualifier used by the international sequence collaboration (DDBJ/EMBL/GenBank) and can be assigned by sequence submitters as a unique, systematic gene descriptor. When such a value is not available from submitted sequence, the identifier from a collaborating model organism database is used. Locus tag is often used to anchor a link to a database other than Entrez Gene. Locus tag is also used as the preferred symbol if an official symbol has not been identified for a gene.
Gene type: Possible values are tRNA, rRNA, snRNA, scRNA, snoRNA, miscRNA, protein-coding, pseudo, other, and unknown. These are indexed as properties of a gene by using the terms:
genetype trna (transfer RNA, tRNA)
genetype rrna (ribosomal RNA, rRNA)
genetype snrna (small nuclear RNA, snRNA)
genetype scrna (small cytoplasmic RNA)
genetype snorna (small nucleolar RNA)
genetype miscrna (miscellaneous RNA)
genetype protein coding
genetype pseudo (pseudogene)
genetype other (when the type is known, but there is no specific enumeration for it)
genetype unknown (when the type of gene is uncertain)
RefSeq status: Any of the set of status descriptions defined by RefSeq.
Organism: The binomial, and strain when appropriate, with a link to the NCBI Taxonomy database.
Lineage: Binomial and lineage from the Taxonomy database.
Also known as: Unofficial symbols and descriptions that have been used for this gene and its products. If there is no official symbol, and no locus_tag, the symbol at the top of the display is repeated in this section. These names are integrated from several sources, including model organism databases, annotation on sequence records, and interactive curation from the published literature.
| Property name | Explanation |
|---|---|
| alive | The record is current and primary (i.e., not secondary or discontinued). The term secondary is applied to any record that has been merged into another. This occurs most often when multiple genes are defined based on incomplete data, and these are later discovered to be parts of the same gene. One gene record then becomes secondary to the other. |
| GeneRIF | A record having one or more GeneRIF annotations attached. |
| has ccds | A gene that encodes a protein sequence that is a member of a Consensus CDS (CCDS). See http://www.ncbi.nlm.nih.gov/projects/CCDS/. |
| has RefSeqGene | This Gene record has an associated gene-specific genomic RefSeq in the RefSeqGene class. |
| has summary | A record with summary text (gene.summary) |
| has transcript variants | A record having two or more associated RefSeq transcripts, i.e., splice variants. Note: This is limited to RefSeq annotation and should not be used to identify all genes exhibiting alternative splicing, promoter usage, and/or polyadenylation signals. |
| hiv1interactions | Genes with curated HIV-1:human protein interaction data. See http://www.ncbi.nlm.nih.gov/RefSeq/HIVInteractions/index.html |
| Interaction | A record with data in the Interaction section. |
| officially named | A record with official nomenclature. |
| Phenotype | A record including a named phenotype. |
| Phenotype only | A record for a mapped phenotypic trait for which the molecular basis in not known. |
view the intron/exon/coding region organization of a gene and its RNA product, or the placement of a pseudogene, on a genomic RefSeq
identify the RefSeqs that correspond to any RNA or protein product and see an overview of the exons they represent
navigate to the genomic, RNA, or protein sequence, by clicking on the RefSeq accession
navigate to Blink, from the protein accession, to review how this protein sequence compares to related proteins from other taxa
Each position of a gene product, when represented by a RefSeq RNA (accession NM_000000/NM_000000000 or XM_000000/XM_000000000 for mRNA, NR_000000 or XR_000000 for non-protein coding RNAs) and/or protein (NP_000000/NP_000000000 or XP_000000/XP_000000000), is provided relative to the genomic accession on which it is annotated. Each accession is an anchor to a menu that will display the sequence in several formats. Protein accession numbers also facilitate retrieval of specific BLink, CDD, or COG displays. See the following figure as an example, and read the detailed description in Box 1. Interactive View. Be sure to click the link in the box for the interactive view.
For some species, including human and other vertebrates, the genomic RefSeqs are updated independently of the annotated product RNAs, with the latter being updated more frequently. This means that several kinds of discrepancies between the diagram and the current RefSeq RNAs may result.
The diagram may be labeled with an mRNA accession (for a predicted transcript) of the format XM_123456, yet clicking on that accession results in an entry in Entrez Nucleotide that indicates that this accession is no longer primary. That means that a curated mRNA (accession of the format NM_123456 or NM_123456789) has been generated to replace the previous model accession. This new "NM" accession will be reported in the Reference Sequences section.
The diagram may be labeled with curated RNA accession numbers (of the format NM_123456 or NM_123456789 or NR_123456) different from those listed in the RefSeq section. This will result if curation after the submission of the annotated genome identified more transcript variants, which therefore are listed only in the Reference Sequence section but not in the diagram. It will also result if curation after submission of the annotated genome identified an error in the annotated product, and the accession for that product was suppressed. In that case, the Genomic regions, transcripts and products section will indicate a transcript not listed in the RefSeq section of the Entrez Gene report.
If the gene has been included in a genomic annotation, the section also diagrams neighboring genes and indicates their orientations. If the name of a gene is too long to use for a label, truncation is indicated by an ellipsis (...). The gene being shown on the diagram is in maroon. All other diagrams and labels anchor links to specific gene pages, supporting quick navigation to review neighboring genes by clicking in the area of the symbol/arrow.
If a gene has not been included in the current version of the annotated genome provided in NCBI RefSeqs, the Genomic context section will not include a diagram but will report the map location. If the gene is annotated on more than one genomic RefSeq, only one will be used for the graphic display, but the location information will be provided in the ASN.1 of the record and in the Reference Sequences Section.
There are two major subcategories of information reported as Interactions: HIV-1 interactions and general interactions.
The HIV-1, Human Protein Interaction Database is funded by the Division of Acquired Immunodeficiency Syndrome (DAIDS) of the National Institute of Allergy and Infectious Diseases (NIAID). As the title indicates, this project focuses on the human proteins that have been shown to interact with proteins from HIV-1. The format of this section is different for the human and HIV-1 gene reports. On human, the display consists of:
the HIV-1 protein, which anchors a link to Entrez Gene for that gene product
a concise description of the interaction
links to papers in PubMed that support the described interaction
For HIV-1, the display is subdivided by peptide name and includes:
a key word categorizing the interaction
the full name of the human gene, which anchors a link to that record
links to papers in PubMed that support the described interaction
Please note that there are separate reports from this section that are available for download, both from the HIV Interactions homepage and the GeneRIF subdirectory of the Gene FTP site.
Interactions in this general section are reported as pairs. The report will always include, in the first column, the product of the gene that is part of the interaction in the first column. Depending on the type of interaction, the rest of the display may report:
the other interactant, anchoring a link to more information
the gene name of the other interactant, anchoring a link to that record in Entrez Gene
the complex to which the interactant(s) belongs
the source of these data, anchoring a link to the record at that source
a concise description of the interaction
links to papers in PubMed that support the described interaction
This section reports the general characteristics of alleles that have been described for a gene and provides links to more detailed information. This function is being phased in gradually; the current set is for mouse and is being developed from information supplied by Mouse Genome Informatics.
This section includes several subcategories of information, including:
GeneOntology (GO): The specific GO terms are listed by source of the information, category, term, evidence information, and links to supporting publications. Each GO term supports a link to the AmiGO browser. Abbreviations in the Evidence column indicate the level of support for assigning a GO term to a gene. Explanations for these abbreviations are provided by the Gene Ontoloogy website.
Entrez Gene does not alter the associations provided by a model organism database, nor does Entrez Gene recapitulate the directed acyclic graph structure provided by GO. Thus, Entrez Gene does not support retrieval of all genes associated with a specific GO term based on that term's parent. If you identify a GO term that is inappropriate for a gene, please contact the model organism database directly. ftp://ncbi.nih.gov/gene/DATA/go_authorities.xml documents the authorities Entrez Gene uses to connect GO terms to GeneIDs.
Homology: A partial listing, with links, of orthologs in other species. Other views of homology data are available from TaxPlot and the HomoloGene link in the Links menu.
Phenotypes: A description of the effect of the gene on phenotype, especially disease. Links to more information are provided as available, as in the case of human disease and links to OMIM.
Figure 6. Representative General gene information section of a Full Report display. Note that the Markers subsection is provided in a scrolling window.
Pathways: A description of pathways that include this gene with links to more information about that pathway.
Relationships: This section reports some of the public sequences that were used support the prediction of the indicated RefSeq model. Thus this section is used only for those genomes for which NCBI calculates annotation, and only for those genes where there is not a supporting curated RefSeq. Sequence accessions reported in this section may differ from those for which alignments are displayed from Evidence Viewer for this gene.
This section applies only to genes that encode proteins. It reports the name or names that have been assigned to proteins encoded by the gene and provides other descriptive text. The names are as annotated on the RefSeq protein, when that protein is available. The sources of these names include model organism databases, annotation on public sequence databases, and curation by RefSeq staff.
This section describes the gene-specific NCBI reference sequences (RefSeqs) that have been established for this gene. In addition to enumerating the accession numbers and providing links to the appropriate Entrez sequence database, this section may also include descriptions of each transcript variant, accession numbers of the public sequences used to support any transcript, and a listing of computed domains in an encoded protein. The text provided in this section therefore supports retrieving gene records based on descriptions of conserved domains.
The Reference Sequence group uses several approaches in maintaining information. These can be broadly categorized as:
Genome Annotation. RefSeq RNA and protein sequence are provided only through the process of genome/chromosome annotation.
Suppressed Reference Sequence(s). Accession numbers listed in this section were suppressed for the cited reason(s). Suppressed RefSeqs do not appear in BLAST databases, related sequence links, or BLAST links (BLink) but may still be retrieved by from the Nucleotide or Protein databases, and by clicking on the hyperlinked accession.version.
This section has two subsections, one in which the nucleotide sequence is primary and one for protein sequences only (UniProt). It contains sequence accessions that are related to the gene and provides links to the appropriate sequence record in Entrez Nucleotide , Entrez Protein or UniProtKB. It is not intended to be a comprehensive list of all sequences related to any gene; such sequences can more explicitly be found by using BLAST to query sequence databases or by using pre-calculated reports of related sequences via Entrez Nucleotide, Entrez Protein, or BLink. The sequence accessions in this section are provided in a tab-delimited format in the gene2accession.gz file in the DATA directory of the Gene FTP site.
Depending on the genome of the gene being reported, the sequences included may or may not be restricted to the same subspecies or strain.
Gene purposely lists protein accession numbers on records being represented as not protein-coding. The intent is to make the connection between sequence annotation and Gene's current representation of the type of gene. Users with evidence indicating that the Gene record should be reviewed are encouraged to contact the RefSeq staff.
Accessions are reported as related sequences based on several criteria:
mRNAs with unique best placement on a genome coinciding with an annotated Gene
cDNA/cDNA sequence relatedness (calculated based on criteria of identity, length of overlap to known accessions, and coverage of the novel accession)
submissions from model organism databases or nomenclature authorities
identification of proteins with identical sequences
curation by RefSeq staff
annotated GeneIDs from the ORFeome Collaboration or Celera
This section provides a printable view of a subset of links to information both within and external to NCBI. Some of these links overlap those included in the Links menu. The intent of this section is to provide a printable report of, for example, MIM numbers, UniGene cluster numbers, and family-specific websites.
At the bottom of the Full Report is another Display bar. This bar is the same as the one at the top. There are many display options available. Of those provided, ASN.1 and XML are discussed below.
The ASN.1 display provides gene records structured according to the Entrezgene specification. An XML transformation of the ASN.1 is also available. Detailed information about the specification is provided in the Tips for Programmers section.
Any record or selected set of records can be displayed in XML format. The XML is generated automatically from the ASN.1 record that is used to support the display, with the names of the tags defined by the ASN.1 specification. Detailed information about the specification is provided in the Tips for Programmers section.
LinkOut provides easy access to relevant online resources outside of the Entrez system. These connections are maintained by the external database.
An increasing number of Gene records are annotated specifically in books and monographs provided in Bookshelf. One example, restricted to human genes, is the GeneReviews book provided in collaboration with the GeneTests group of the University of Washington. To retrieve all records in Entrez Gene in this category, try the query "gene books"[filter] from the Entrez Gene Search bar.
Protein sequences are routinely compared to canonical sequences for domains in the Conserved Domain Database. Domain records connected to protein associated with records associated with your Entrez Gene search results can be retrieved by using this display option. To retrieve all records in Entrez Gene in this category, try the query "gene cdd"[filter] from the Entrez Gene Search bar.
Genome maintains information about chromosomes and complete genomes. Genome records associated with your Entrez Gene search results can be retrieved by using this display option. To retrieve all records in Entrez Gene in this category, try the query "gene genome"[filter] from the Entrez Gene Search bar.
GENSAT maintains images of the expression of a subset of genes expression in the central nervous system and eye of the laboratory mouse. GENSAT records associated with your Entrez Gene search results can be retrieved by using this display option. To retrieve all records in Entrez Gene in this category, try the query "gene gensat"[filter] from the Entrez Gene Search bar
GEO maintains information from array-based experiments. Links between the databases are calculated when both GEO and Gene have computed a relationship to the same sequence record. To retrieve all records in Entrez Gene in this category, try the query "gene geo"[filter] from the Entrez Gene Search bar.
HomoloGene compares protein-coding genes in several key genomes to identify homologs. HomoloGene records associated with your Entrez Gene search results can be retrieved by using this display option. To retrieve all records in Entrez Gene in this category, try the query "gene homologene"[filter] from the Entrez Gene Search bar.
Some of the mRNAs associated with your Entrez Gene search results are available from NIH-supported cDNA repositories. Reports of clones in the Nucleotide database associated with your Entrez Gene search results can be retrieved by using this display option.
Nucleotide sequences associated with your Entrez Gene search results can be retrieved by using this display option. To retrieve all records in Entrez Gene with nucleotide sequence information, try the query "gene nucleotide"[filter] from the Entrez Gene Search bar.
Online Mendelian Inheritance in Animals (OMIA) maintains information about Mendelian disorders in animals. OMIA records associated with your Entrez Gene search results can be retrieved by using this display option. To retrieve all records in Entrez Gene in this category, try the query "gene omia"[filter] from the Entrez Gene Search bar.
OMIM records associated with your Entrez Gene search results can be retrieved by using this display option. To retrieve all records in Entrez Gene in this category, try the query "gene omim"[filter] from the Entrez Gene Search bar.
Publications available as full text from PubMedCentral may include explicit references to Gene. Publications may also be connected to Gene via a PubMed ID. PubMedCentral records associated with your Entrez Gene search results can be retrieved by using this display option. To retrieve all records in Entrez Gene in this category, try the query "gene pmc"[filter] from the Entrez Gene Search bar.
Probe records, such as those for resequencing primers or RNAi sequences, related to your Entrez Gene search results can be retrieved by using this display option. To retrieve all records in Entrez Gene in this category, try the query "gene probe"[filter] from the Entrez Gene Search bar.
Protein sequences associated with your Entrez Gene search results can be retrieved by using this display option. To retrieve all records in Entrez Gene with protein sequence information, try the query "gene protein"[filter] from the Entrez Gene Search bar.
PubMed citations associated with your Entrez Gene search results can be retrieved by using this display option. Those that were generated from GeneRIFs are indicated by the PubMed (GeneRIF) option. To retrieve all records in Entrez Gene with citations in PubMed, try the query "gene pubmed"[filter] from the Entrez Gene Search bar.
Use these display options to navigate to information about variation reported in the dbSNP database for the gene records in your search results. To retrieve all records in Entrez Gene with reported variation, try the query "gene snp"[filter] from the Entrez Gene Search bar.
Use this display option to navigate to information about the taxonomy of the genomes in which the gene records in your search results are found.
Use this display option to navigate to information about expression and EST sequences related to the gene records in your search results. These links are calculated from nucleotide accession numbers that are common to records in both databases. To retrieve all records in Entrez Gene with additional information in UniGene, try the query "gene unigene"[filter] from the Entrez Gene Search bar.
Use this display option to navigate to information about PCR primers associated with gene records in your search results. This gene-to-marker association is calculated from reports from external databases or by e-PCR-based matches to cDNAs or annotated genes. To retrieve all records in Entrez Gene with additional information in UniSTS, try the query "gene unists"[filter] from the Entrez Gene Search bar.
All functions of the Entrez indexing and query engine are used by Entrez Gene. This section will therefore summarize only how to use the tools in the context of the Gene database. Entrez Help provides information on how to use the tabs History, Clipboard, and Details. For general information about Entrez, see Entrez Help.
Figure 9. Representative Limits Page. Shown is an example of a Limits page used to find current records in Entrez Gene for Drosophila melanogaster that are associated with reviewed RefSeqs, are not pseudogenes, and have alcohol in the gene name. (A) Enter alcohol in the query box. (B) Set the filed name to Gene/Protein name. (C) See Exclude and check Pseudogenes. (D) See Include Only and check Current Records and RefSeqs. (E) See Limit by RefSeq Status and check Reviewed. (F) In Limit by Taxonomy, check Drosophila melanogaster in the Invertebrates subsection.
Limits is designed to make it easier to execute certain queries by checking boxes, rather than by writing out the text of an Entrez query. It is particularly useful if you want to retrieve genes only:
Remember that once you have set Limits, that setting remains through multiple queries, unless you remove the setting. A yellow banner appears below the Limits tab when Limits is turned on. Turn off Limits at any time by removing the check to the left of the word Limits in the query bar of the result page.
Genomic: Genes encoded by chromosomes or the major genomic macromolecule for the taxon.
Mitochondria: Genes encoded by mitochondria.
Plasmids: Genes encoded by plasmids.
Plastids: Genes encoded by plastids.
RefSeqs: Genes for which RefSeqs exist.
NEWENTRY: GeneIDs used to support submission of GeneRIFs, by species, for a gene not currently in Entrez Gene.
Additional limits are:
The additional limits are treated as Include Only and are hierarchical. For example, to limit your results to genes in invertebrate genomes, check Invertebrates. These selections are also treated as the Boolean operator OR, so if you want to retrieve genes from either Danio rerio or Xenopus sp., check both Danio rerio and Xenopus.
| Filter name | Definition |
|---|---|
| all | Total records, current or not |
| gene all | All current records |
| gene books | Gene records with explicit links to Entrez Books |
| gene gensat | Gene records with explicit links to Entrez GenSAT |
| gene geo | Gene records with explicit links to Entrez GEO |
| gene homologene | Gene records with explicit links to Entrez HomoloGene |
| gene nucleotide | Gene records with explicit links to Entrez Nucleotide, excluding RefSeq chromosome or contig accessions |
| gene nucleotide pos | Gene records with explicit links to Entrez Nucleotide, limited to those of RefSeq chromosome or contig accessions, and thus including position data |
| gene omim | Gene records with explicit links to Entrez OMIM, and thus includes links to both disease and “gene” records in OMIM |
| gene protein | Gene records with explicit links to Entrez Protein, and thus includes links to GenPept and SwissProt accessions |
| gene pubmed | Gene records with explicit links to Entrez PubMed |
| gene snp | Gene records with explicit links to Entrez dbSNP, and thus supports finding gene variation information available in dbSNP |
| gene taxonomy | Gene records with explicit links to Entrez Taxonomy |
| gene unigene | Gene records with explicit links to Entrez UniGene |
| gene unists | Gene records with explicit links to Entrez UniSTS (marker data) |
The Limits page also allows you to restrict queries by date. The options are:
A. To retrieve non-mitochondrially encoded NADH dehydrogenases from human, mouse, or rat, use the Limits form to:
Enter nadh dehydrogenase in the query box (case does not matter).
Select Gene/Protein name from the All fields drop-down menu.
Check Mitochondrion under Exclude.
Check Homo sapiens, Mus musculus, Rattus norvegicus.
Press Go in the search bar.
B. To retrieve E. coli genes related to tryptophan, use the Limits form to:
Check Escherichia coli.
Enter tryptophan in the query box.
Press Go in the search bar.
| Field name | Definition [including field abbreviations] | Examples |
|---|---|---|
| Name subcategory | ||
| Disease name or phenotype of mutants | Disease or phenotype associated with the record. [DIS] | Find the genes that contribute to SCID. SCID[dis] |
| Gene name | A symbol for the gene. Includes preferred symbols, aliases, and locus tags. [SYM][SYMB][GN][GENE NAME] | Genes with a symbol starting with smt. smt*[sym] |
| Preferred symbol | The preferred symbol for the gene, not including aliases or locus tags. [PREF] | Genes with a preferred symbol starting with smt. smt*[pref] |
| Gene full name | Only the full name of the gene. [GFN][GENEFULLNAME] | Find genes with a full gene name of tumor protein p53: tumor protein p53[gene full name] |
| Gene/protein name | The short or full name of the gene or any of its protein products (when applicable). [TITL][TITLE][TF][TI][Protein] | Find genes that have the word kinase in GO annotation but do not have the word kinase in the name. kinase[gene ontology] NOT kinase[gene/protein name] |
| Protein full name | Only the full name of the protein products. [PFN][PROTEINFULLNAME] | Find genes with a full protein name of glutathione S-transferase M1: glutathione S-transferase M1[protein full name] |
| Location subcategory | ||
| Base position | Base position, relative to the genomic accession. This is supported only for the reference assembly and only for genomes where chromosome coordinates are defined. In general, the query should define a range of at least 100 kb; the range must be specified as a pair of integers. The query results will include genes that lie either partly or completely within the range specified. A query by base position should also specify the chromosome and organism. This can be done by including the chromosome accession, or alternatively, by including the chromosome and either the Taxonomy ID or the Organism.[CHRPOS,CPOS,CPOSITION] | NC_000012[nucl_accn] AND 9100000:9200000[chrpos] 9606[taxid] AND 12[chromosome] AND 9100000:9200000[chrpos] |
| Chromosome | Chromosome location of the gene. The value used is according to the convention of the source genome. In other words, if III is used, III but not 3 will be indexed in this field. [CHRM][CHR][CHROMOSOME] | Retrieve records containing the word kinase, and the gene is located on chromosome III:kinase AND III[chr] Retrieve records containing the words zinc and finger that are of human origin but not on chromosome 19: zinc finger NOT 19[chr] AND "Homo sapiens"[orgn] |
| Default map location | A map location in the units standard for the genome. For example, for human it is the cytogenetic band, for mouse it is the MGI map (centiMorgans). This is processed as a text field, so range queries are not implemented. For range queries, use Map Viewer. [MV][MVMAP] | Rat genes mapped to 18 q: rat[orgn] AND 18q[default map location] |
| Sequence subcategory In Gene: This means searching by sequence identifier, not by the sequence itself, which is managed by BLAST. | ||
| Nucleotide accession | An accession for a nucleotide sequence.[NACC] | There are instances where the same accession is applied to both nucleotide and protein sequences. To restrict an accession to nucleotide, use this field. (Accession numbers beginning with BC are not in this category.) BC052629[NACC] |
| Nucleotide UID | The gi of a nucleotide sequence.[NUID][NUCL_UID][NUCLEOTIDE_UID] | Many integer identifiers have overlapping number spaces. To find the gene record that corresponds to a given nucleotide gi from gene, use this field. 27363473[NUID] |
| Protein accession | An accession for a protein sequence. [PACC][PROT_ACCN] | There are instances where the same accession is applied to both nucleotide and protein sequences. To restrict an accession to protein, use this field. (Accession numbers beginning with three letters are not in this category.) AAH52629[PACC] |
| Protein UID | Protein gi. [PUID][PROT_UID][PROTEIN UID] | Many integer identifiers have overlapping number spaces, So to find the gene record that corresponds to a given protein gi from gene, use this field. 27363473[PUID] |
| Nucleotide or Protein accession | A sequence accession of any type. [ACCN] | Find all the genes encoded in accession AE003828: AE003828 |
| Miscellaneous subcategory (alphabetical) | ||
| Creation date | Date the record was created. [cd][cdat][creation date] | Records containing the word xenopus created between February 5, 2004 and February 12, 2004: 2004/2/5:2004/2/12[cd] AND xenopus[orgn] |
| Date Discontinued | The date on which the record was discontinued[DIS_DATE][DDAT][DISCONTINUED][DISDATE] | Records discontinued between January 1, 2006 and December 31, 2006: 2006/1/1:2006/12/31[disdate] |
| Domain Name | Conserved domain and protein family names.[DOMAINNAME][DOM] | Retrieve records associated with the A2M family:A2M[domainname] |
| EC/RN number | Enzyme commission identifier for a product of the gene. Indexed without the EC prefix. [ECNO][EC] | Retrieve records where proteins have an E.C. number of 1.9.3.1: 1.9.3.1[ECNO] |
| Exon count | The number of distinct, non-overlapping RefSeq exons annotated for all RNA products of this gene interval, based on annotation in this priority: reference assembly first, alternate assembly second.This field can be queried by either a single integer value or a range.[XC][NUMEXONS] | Retrieve human records with one exon:human[orgn] AND 1[exoncount]Retrieve all records with a range of exons:10:20[exoncount] |
| Filter | Find records with a relationship to other data in Gene. For more examples of use of filters, see the Preview/Index section. | Retrieve records of mouse kinase genes with expression data stored in GEO: mouse[orgn] AND gene_geo[filter] AND kinase |
| Gene ID | Gene identifier. This field can be queried by either a single integer value or a range. [UID][ID][GeneID] | Many integer identifiers have overlapping number spaces. To find the gene record that corresponds to the human BRCA1 gene by GeneID, use this field: 672[GeneID] |
| Gene length | Gene length based on annotation in this priority: reference assembly first, alternate assembly second. If there are multiple placements, only on non-reference assemblies, then the longest value on non-reference assemblies is used.This field can be queried by either a single integer value or a range.[GL][GENELEN] | Retrieve all records with a gene span less than or equal to 5kb:1:5000[genelength] |
| Gene Ontology | GO terms applied to this gene AND the GO identifer as the integer. The terms include the component, function, and process categories.[GO][GENE ONTOLOGY] | Rat genes with GO terms starting with “kinase signaling” kinase signaling*[gene ontology] rat[orgn] Any gene with the GO id of GO:0004872: 4872[GO] |
| Group | Query terms to retrieve a set of genes with a specified relationship to another gene | Pseudogenes related to the same functional gene with GeneID = 11727 "related functional gene 11727"[Group] |
| MIM | Identifier assigned to human genes and phenotypes by OMIM [MIM] | Retrieve records that contain the MIM number 181510: 181510[MIM] |
| Modification date | Last date the record was modified.[MODDATE][MDAT][LMOD][DATE][UPDATED][MD] | Retrieve records for genes from eubacterial genomes last modified after March 10, 2004: eubacteria[orgn] AND 2004/3/10:2010/1/1[md] Retrieve records from sea urchins modified in the last 30 days: echinoidea[orgn]+AND+"last 30 days"[mdat] |
| Organism | Scientific and common names of organism[ORGN] | Find all records in Entrez Gene for the pig: pig[organism] |
| Property | An attribute of a Gene record based on its content.[prop][property] | Mouse records with transcript variants: mouse[orgn] AND "has transcript variants"[property] |
| PubMed UID | PubMed id. [PMID] | Many integer identifiers have overlapping number spaces. To find the gene record(s) that corresponds to a paper in PubMed from Gene, use this field: 12477932[PMID] |
| Taxonomy ID | Identifier for the species or strain in the NCBI taxonomy database. HINT: txid{value} also works, e.g., txid9606.[TAXID][TID] | Find all records in Entrez Gene for the pig: 9823[taxid] Alternatively: txid9823 |
| Text Word | Any word in the record.[TEXT][WORD][AB][TXT] | Retrieve records that contain “32” in a record that also contains threonine, serine, and kinase: serine AND threonine AND kinase AND 32[TEXT] |
| UniGene cluster number | UniGene cluster including the text prefix. [UNIGENE][UGEN] | Hs.2[UNIGENE] |
describe filters in general and how they can be used to find records of interest in gene
describe the properties assigned to gene records and provide examples of how to use them
describe text phrases and how they differ from text words
The term filter is used to describe categories of records that are grouped according to their relationship either to other Entrez databases or to external resources that have submitted LinkOut connections. If the former, the filter is named according to the pattern “gene other_Entrez_database”, such as “gene protein”. If the latter, the first two letters of the filter's name are ”lo”, for LinkOut. For a comprehensive listing of filters valid for the Gene database and the number of records in each, follow these steps:
Click on the Preview/Index tab under the query bar.
Use the pull-down menu named All Fields and select Filter.
Click on the Index button to the right of Preview to see the filter names and the number of instances of each.
Properties are assigned to gene records based on content, rather than relationship to other database records, which is the role of filters (see Filter). At present, the properties assigned to Gene records fall into these major categories:
Type of gene: Property named as genetype name_of_type.
Source of the gene: Property named as source name_of_source.
Type of RefSeq provided for the gene: Property named as srcdb refseq type_of_refseq.
Other
The genetype option should be self-explanatory, except perhaps for miscrna, other, and unknown. Names for the types of molecules encoded by genes follow the conventions of the collaborating sequence databases (DDBJ/EMBL/GenBank); thus miscrna (misc_rna, miscellaneous RNA) is assigned to any gene that encodes an RNA product not included in the other specifics. The genetype other property is applied to loci of known type, but a specific category has not yet been applied in the Entrezgene data model (i.e., named fragile sites). The genetype unknown property is applied to probable genes for which the type is still under review. This category is frequently used when the defining sequence has uncertain coding propensity. Note: At the time of this writing, the assignment of gene records to the latter two categories continues to be refined. We appreciate your suggestions for any improvements.
The source options should be self-explanatory, with source other being used where a specific category has not yet been applied in the Entrezgene data model.
The srcdb refseq categories are as enumerated by RefSeq and will not be duplicated here.
A text phrase is a special type of text search that uses two or more words to form a phrase. An ordinary text search of two or more words will find gene records that contain all of the specified words anywhere in the gene record. By contrast, a text phrase search will find gene records that contain all of the specified words together and in the specified order.
| Text phrase | Explanation |
|---|---|
| “Annotation Information” | For genomes that NCBI annotates, Entrez Gene will represent information about the annotation of each current GeneID. Text phrases will be attached to the gene data if the gene is not annotated well, or if annotation has changed in a complex way. Text phrases will also attached if there is no defining cDNA or genomic sequence for the gene, or if the GeneID was created after the most recent genome annotation. The goal is to facilitate retrieval of Gene records where the annotation on the RefSeq genomic records, if it exists, should be interpreted with caution. Thus records that are not known to have annotation issues can be retrieved by the query: NOT “Annotation Information” [Text] Specific sub-categories of annotation information are described below. |
| Sub-categories of annotation information | |
| “partial on reference assembly“ | The annotated gene, as suggested by the defining cDNA, is not complete. |
| “spans an assembly gap” | There is a gap in the assembly where the defining cDNA should align. |
| “suggests misassembly” | There are order/orientation issues suggested by the cDNA alignment. |
| “not annotated on reference assembly” | This gene is not annotated on the reference assembly. |
Please note that the double quotes are included in the text phrases shown here because they are mandatory when performing a text phrase search.
| Scope | Query | Notes |
|---|---|---|
| Find genes mapped to Arabidopsis thaliana chromosome 3 that have orthologs reported in HomoloGene | arabidopsis thaliana[orgn] AND 3[chr] AND gene_homologene[filter] | [orgn] is used to restrict “Arabidopsis thaliana” to the organism field. That restriction could also be set by checking Arabidopsis thaliana on the Limits form. [chr] is used to restrict ”3” to the chromosome field. gene homologene[filter] is used to restrict records to those processed by HomoloGene. This query is not currently able to be processed by MapViewer, because the relationship to HomoloGene is not processed for indexing at present, nor by HomoloGene, because the chromosome data are not captured in HomoloGene. |
| Find genes also being processed by OMIM but for which there is not currently a RefSeq of the type "known" | gene omim[filter] NOT srcdb refseq known[prop] | gene omim[filter] is used to find all Gene records with relationships to OMIM. srcdb refseq known[prop] is used (as the Boolean NOT) to find all such records that do not have RefSeqs of the accession format NM_000000, NG_000000, or NR_000000. |
| Find genes from genomes other than mammals that are classified by the GO consortium to have some relationship to the cytoskeleton | cytoskeleton[go] NOT mammalia[orgn] | [go] is used to restrict to the field “Genome Ontology”. [orgn] is used to restrict (as the Boolean NOT) to species not classified as mammals. Queries based on GO terms are not supported in either Map Viewer or HomoloGene. Please note that Gene does not recapitulate tree-based searching for GO annotation; this retrieval is based solely on the existence of the word in any GO category. Links are provided to the GO website to support more specific searches. |
Scope: The intent of a query.
Query: How to construct a query that meets that intent.
Notes: How usage of Gene to retrieve these data may compare to other gene-related resources, namely HomoloGene, Map Viewer, or UniGene.
The data model for Entrez Gene is documented in the Entrezgene specification. It combines several definitions used by other NCBI databases, such as seqfeat, but also establishes definitions specific to Entrez Gene. Of special note is the Gene-commentary, which is used to represent many descriptors of genes. Each Gene-commentary is defined by type and supports specific representation of such elements as sequence database accession numbers (accession, version), citations (refs), external or internal resources defining the data (source), and position information. Heading, label, and text are used for general data, with the choice influenced by display in the Entrez Gene viewers.
The DTD for Gene is available from NCBI's DTD directory and is called NCBI Gene.dtd.
The full power of Entrez Programming Utilities (e-Utils) can be used to extract information from Entrez Gene programmatically. The basic strategy is to identify the query that will return the desired records and then submit that query via ESearch. The GeneIDs identified by that search can then be submitted to another function, such as ESummary or EFetch. Examples for Gene are provided on the FAQ page. The FTP site contains a sample perl script that uses ESearch and ESummary.
The FTP site for Entrez Gene (README) has four major subdirectories: DATA, GeneRIF, and Tools.
DATA contains files that provide key attributes of genes, including:
all associated accession numbers, including RefSeqs (gene2accession.gz)
associated RefSeq accession numbers (gene2refseq.gz)
citations (gene2pubmed.gz)
nomenclature, ID, and map data (gene_info.gz)
MIM numbers (mim2gene)
UniGene clusters (gene2unigene)
GO terms (gene2go)
Details of the construction of these files are reported in the (README) file.
DATA also contains the ASN_BINARY subdirectory. This path contains both a comprehensive extraction from Gene (All_Data.gz), several subsets categorized by source (Organelles, Plasmids), and subdirectories grouped broadly by taxonomy. Records of genes from species that are requested frequently are also provided in species-specific files, for example these mammals. The format of these extractions is compressed binary ASN.1. The program gene2xml is available to convert these files to XML or ASN.1 text.
The GENE_INFO subdirectory of DATA provides subsets of the gene_info file grouped broadly by taxonomy. This directory structure mirrors that of the ASN_BINARY path. Thus if you want the type of information provided in gene_info, but do not want to have to process the complete text, you can use one of the files in the appropriate subdirectory, for example these plants.
GeneRIF contains files that provide supplemental information about gene functions, either from the GeneRIF pipeline (generifs_basic.gz) or the HIV-1, Human Protein Interaction Database (hiv_interactions.gz). The tab-delimited files are not subdivided by species of interest. All files except the file reporting GeneID/PubMedID relationships (gene2pubmed.gz) have a column with the ID from the NCBI Taxonomy database to facilitate the extraction of a subset of the data from the file by species.
Gene_tools provides or points to programs and scripts to mine data from Entrez Gene. Of particular interest is gene2xml, which can be used to convert the binary ASN.1 in the ASN_BINARY directory to XML or to ASN.1 in text format (README).
Entrez Gene can serve as a gateway to information on your website served from your local database. Users of Entrez Gene will discover your website if you participate in our LinkOut system and become a LinkOut provider. Any Entrez database will support LinkOut. Linkout Help’s Information for Other Resource Providers explains the details of this opportunity.
There are many benefits to becoming a LinkOut provider. If you want access to your database to be apparent from Entrez Gene, you can control the description of your resource, the update cycle, and the icon to anchor links to your site. In other words, you do not have to wait for NCBI staff to go to your site to obtain and process information and match to Gene records. You know your site best—you can identify which records are related to Gene records and provide the most accurate and informative URL to connect that Gene record to your site. If you already provide LinkOuts to other Entrez databases, such as Nucleotide or Protein, you do not have to re-register as a provider; you need only notify the LinkOut [mailto:linkout@ncbi.nlm.nih.gov] staff and start to submit a new resource file.
With the implementation of My NCBI, it is even more advantageous to become a LinkOut provider. One of the options registered users of My NCBI can select is to display the icons for any LinkOut provider at the top of a record. The presence of your familiar logo would invite users of Entrez Gene to go to your site.
URLs can be constructed to query Entrez Gene, or to display a specific record if you know the GeneID. For example, if your site maintains the identifiers (GeneID) used by Entrez Gene, you can construct a link from your site to Entrez Gene by combining this base
http://www.ncbi.nlm.nih.gov/gene/
with the GeneID. For example, to link to GeneID 1, use this URL:
http://www.ncbi.nlm.nih.gov/gene/1
URLs that query Entrez Gene are constructed by adding ?term=[search term]
For example, to find records in Entrez Gene containing the phrase ‘immunoglobulin domain’, use this URL
http://www.ncbi.nlm.nih.gov/gene/?term=immunoglobulin_domain
More examples of queries are provided on Gene’s Home page, and general rules for building URLs to query Entrez databases are provided in the Creating a Web Link to the Entrez Databases chapter of this book. The valid display options are also documented in that chapter.
| Letter in LocusLink | Link name | Scope |
|---|---|---|
| P | PubMed | All citations, including those established via GeneRIFs |
| O | OMIM | The OMIM records based on the gene or the phenotype (human only) |
| R | Not implemented separately; included in Nucleotide | |
| G | Nucleotide | A subset of nucleotide links. ESTs are excluded unless the gene is defined by an EST; unannotated, high-throughput genomic (HTG) sequences are also excluded unless used as a source for a RefSeq. |
| P | Protein | A subset of protein sequences encoded by the gene |
| H | HomoloGene | HomoloGene links based on a shared GeneID |
| U | UniGene | UniGene links based on shared nucleotide sequences |
| V | SNP | Links to dbSNP for all variations related to the GeneID, variant by variant |
| GeneView in dbSNP | A display of all variations related to the GeneID, by placement in the gene. This is the view directly corresponding to the V link |
Note: Gene supports many more links from the menu at the right of the Summary and Brief views than than the color-coded letter icons that LocusLink provided. For Gene, all that is required is a connection between Gene and another Entrez database. Thus, there may be links to Books, GEO, UniSTS, Taxonomy, etc.
| LocusLink | Gene | Comments |
|---|---|---|
| Table of Contents | Not retained | |
| Alphabetic lists | Not retained | |
| Gene diagram | Transcripts and Products | Gene adds the function of Genomic context to allow a quick view of nearby genes and links to their report pages. |
| Link to Evidence Viewer from Gene diagram | Evidence Viewer link in Links menu | The option to first see only the diagram of the alignment is not retained. |
| Button Links | Links menu | On the Gene Graphic/Default display, the number of links may be greater than in LocusLink. |
| Title bar with links to nomenclature source | Initial text, with link to nomenclature source via LocusTag | Links from LocusTag values may connect to an external database where official nomenclature has not been assigned. |
| Overview Section | ||
| RefSeq Summary | Summary | Not changed. |
| Locus type | Combination of Gene type and evidence type (under development) | The text values are not equivalent. LocusLink's Locus type values are being subdivided into Gene type and Evidence type categories. |
| Protein names | General protein information | Not changed. |
| Alternate symbols | Gene aliases | Not changed. |
| Relationships Sections | ||
| Homology data | Links menu; HomoloGene | What is printed in LocusLink is still printed in Gene. |
| Related models | Related | Not changed; limited to genomes being annotated by NCBI's pipeline. |
| Function Section | ||
| GeneRIFs | GeneRIFs | Not in a function section; indented under Bibliography. |
| GO annotation | General gene information: GeneOntology | Organization changed, but not content. |
| Phenotype | General gene information: Phenotypes | Organization changed, but not content. |
| Map Section | ||
| Chromosome | Genomic context | Not changed. |
| Associated markers | General gene information: Sequence Tagged Site (Markers) | Entrez Gene added display of alternate marker names. |
| Sequence Section | ||
| RefSeq Subsection | ||
| Category | RefSeq status | Not changed. |
| GenBank source | Source sequence | Not changed. |
| Domain matches | Domains | CDD link also attached to the protein accession in Transcripts and Products and in the Links menu. |
| BL (BLink) | BLink link attached to the protein accession in the Transcripts and Products section. | The function was not changed, but the placement and visibility are different. |
| Variant name | After the protein accession in the Transcripts and Products section. | Content not changed. |
| Annotation Subsection | ||
| Genomic contig | Transcripts and Products | Function retained. |
| gb: Link to gene-specific subsequence | GENBANK view from source NC, NT, or NW accession | Function retained as GENBANK option from the genomic accession-based menu. |
| sv: Link to graphic display of gene-specific subsequence | GRAPHICS view from source NC, NT, or NW accession | Function retained as GRAPHIC option from the genomic accession-based menu. |
| mv: Map Viewer | Map Viewer in Links menu | Function retained. |
| ev: Evidence viewer | Evidence Viewer in Links menu | Function retained. |
| mm: ModelMaker | ModelMaker in Links menu | Function retained. |
| Strain or haplotype | Not retained. | |
| Related Sequences Subsection | ||
| Accessions, type, and strain data | Related Sequences | Content not changed. |
| BL (BLink) from protein accessions | Not retained. | |
| Additional Links | Additional Links | |
| LL_tmpl description | Entrezgene equivalent |
|---|---|
| >>[numeric] record separator; the number equals the LocusID Note: LocusID = geneid for those records also public in LocusLink | Record set closed by bracket matching Entrezgene ::= { |
| LOCUSID [numeric] [unique] [required] the unique integer id for a locus Note: LocusID = geneid for those records also public in LocusLink | geneidEntrezgene ::= { track-info { geneid 2, |
| CURRENT_LOCUSID: [numeric] [unique] [optional] If a LocusID has been merged with another, the current LOCUSID, corresponding to the value on the previous LOCUSID line, is provided here. | current-id In this example, geneid 217346 is secondary to geneid 193217. Entrezgene ::= { track-info { geneid 217346, status secondary, current-id { { db "LocusID", tag id 193217 }, { db "GeneID", tag id 193217 } }, |
| LOCUS_CONFIRMED: [alphanumeric][yes|no] The LOCUSID has been assigned to a confirmed locus and can be treated as an identifier that will be tracked. | No direct equivalent at present |
| LOCUS_TYPE: [alphanumeric] description of the type of locus | typetype protein-coding, and evidence (under development) |
| ORGANISM: [alphanumeric] [unique] [required] source species (Homo sapiens, Rattus norvegicus, etc.), based on NCBI's Taxonomy | source→taxnamesource { genome genomic, origin natural, org { taxname "Homo sapiens", common "human", db { { db "taxon", tag id 9606 } }, syn { "man" }, orgname { name binomial { genus "Homo", species "sapiens" }, lineage "Eukaryota; Metazoa; Chordata; Craniata; Vertebrata; Euteleostomi; Mammalia; Eutheria; Primates; Catarrhini; Hominidae; Homo", gcode 1, mgcode 2, div "PRI" } }, |
| RELL: [set][optional][alphanumeric][multiple] description|id|id type|print representation[/set] brief text summarizing the relationship, the other id, the type of id, and the display for that second id. At present these id types of are 2 classes: l for locus_id, n for nucleotide accession official/default symbol for the other locus being described. The function of reporting the other GeneID is not retained. Consider HomoloGene's FTP site for these data. | Gene/Gene relationship of Homologyhomology { { type comment, heading "Mouse", label "A2m", text "6 62.00 cM", source { { src { db "HomoloGene", tag str "A2m" }, anchor "A2m", url "/Homology/view.cgi?map=ncbi_mgd&tax_id=10090&chr=6&symbol=A2m" } } } }, |
| STATUS: [alphanumeric] [optional] (only if a reference sequence exists) [REVIEWED|PROVISIONAL|PREDICTED|MODEL|INFERRED] type of reference sequence record | Gene-commentary of type comment with heading ="RefSeq Status" and label of the appropriate value { type comment, heading "RefSeq Status", label "REVIEWED" }, |
| NC: the accession for chromosome RefSeq records [alphanumeric] [optional] (only if a reference sequence exists) the RefSeq accession for a genomic record, followed by the gi and strain, if applicable. | locus→accession locus { { type genomic, label "tat", accession "NC_001802", seqs { int { from 5376, to 7969, strand plus, id gi 9629357 } }, |
| NR: The RefSeq accession for a non-messenger RNA. | May be in two places: if annotated on a genomic RefSeq, then in locus, products, type="...", accessionalways in comments, type comment, products, type ..., heading "...Sequence", accession type comment, heading "NCBI Reference Sequences (RefSeq)", products { { type mRNA, heading "mRNA Sequence", accession "NM_000014", version 3, source { { src { db "Nucleotide", tag str "6226959" }, anchor "NM_000014" } }, seqs { whole gi 6226959 }, products { { pe peptide, heading "Product", accession "NP_000005", version 3, source { { src { db "Protein", tag id 4557225 }, anchor "NP_000005", post-text "alpha 2 macroglobulin precursor" } }, seqs { whole gi 4557225 }, |
| NM: The RefSeq accession for a mRNA record [alphanumeric] [optional] (only if a mRNA reference sequence exists) the accession for the mRNA, followed by the gi and the strain, if applicable | |
| NP: The RefSeq accession for a protein record [alphanumeric] [optional] (only if a reference sequence exists) the RefSeq accession number for a protein record, followed by the PID for that protein | |
| XR: [alphanumeric][optional] (only if a model exists) the RefSeq accession of a model RNA, not associated with a protein product | |
| XM: [alphanumeric] [optional] (only if a model exists) the accession for the mRNA, followed by the gi and the strain, if applicable | |
| XP: The RefSeq accession for a model protein record [alphanumeric] [optional] (only if an XM exists) the RefSeq accession of a model protein, followed by the PID for that protein | |
| NG: The RefSeq accession for genomic region (nucleotide) records | Gene-commentary only, heading "NCBI Reference Sequences (RefSeq)" type comment, heading "NCBI Reference Sequences (RefSeq)", comment { { type genomic, heading "Reference", accession "NG_002315", version 1, source { { src { db "Nucleotide", tag id 24047158 }, anchor "NG_002315" } }, seqs { int { from 1, to 652, strand plus, id gi 24047158 } } } } }, |
| PRODUCT: [alphanumeric] [optional] (only if a reference sequence exists) the name of the product of this transcript | Provided as post-text in the Gene-commentary for the protein accession products { { type peptide, heading "Product", accession "NP_000005", version 3, source { { src { db "Protein", tag id 4557225 }, anchor "NP_000005", post-text "alpha 2 macroglobulin precursor" } }, |
| TRANSVAR: [alphanumeric] [optional] (only if a reference sequence exists) a variant-specific description | Gene-commentary, of type comment, where heading "Transcriptional Variant". Within the Reference Sequences Gene-commentary, indented under the RNA product. comment { { type comment, heading "Transcriptional Variant", comment { { type comment, text "Transcript Variant: This variant (PAX3A) includes an alternate segment in the coding region, which causes a frameshift, and lacks several segments in the 3' coding region, compared to variant PAX3. The resulting protein (isoform PAX3a) has a shorter and distinct C-terminus, compared to isoform PAX3. Isoform PAX3a lacks the paired-type homeodomain." } } }, |
| ASSEMBLY: [alphanumeric] [optional][multiple] (only if a reference sequence exists)[/SET] | Gene-commentary, of type other, where heading "Source Sequence". Within the Reference Sequences Gene-commentary, indented under the RNA product. { type other, heading "Source Sequence", source { { src { db "Nucleotide", tag str "AJ007392,S69369" }, anchor "AJ007392,S69369" } }, |
| CONTIG: [SET][alphanumeric][optional][multiple] the accession.version of the RefSeq contig, the nucleotide gi, the strain, the position of the gene (from|to|orientation), the chromosome, and an indicator of whether this is on the reference assembly or a strain|haplotype | |
| XG: [alphanumeric][optional] (only if an NG accession was used in the annotation process to define position of features on the contig) NG accession, nucleotide gi, strain [SET] | The function of indicating whether an NG accession was used in NCBI's annotation process is not currently retained. The NG accessions are, however, included in the Reference Sequence section. |
| EVID: [alphanumeric] [optional] (only if a model exists) text summary of the evidence for this model | The function reporting the evidence supporting an annotated gene or RNA feature is not currently retained. |
| CDD: [alphanumeric][multiple][optional] name|key|score|e_value|bit_score [/SET] [/SET] | Gene reports domain content; position of these domains is part of the annotation of the RefSeq protein. The domain information is included as a gene-commentatary of type other, with the heading Domains on a gene-commentary of type peptide. The e-value is not reported. comment { { type other, heading "Domains", comment { { type other, source { { src { db "CDD", tag id 5952 }, anchor "pfam00207: Alpha-2-macroglobulin family", post-text "score:2365" } } }, |
| ACCNUM: GenBank nucleotide accession used related to the RefSeq record [SET][alphanumeric] [optional] [multiple] nucleotide sequence accession number (no version), nucleotide gi, strain (if applicable), 5' end of the gene in the sequence, 3' end of the gene in the sequence one accession number per line | The data previously reported as ACCNUM, TYPE, and PROT are now reported as a set of gene-commentaries starting with one of type comment with the heading Related Sequences. The nucleotide sequence information is reported under products, as a gene-commentary of type mRNA. If that nucleotide sequence has an associated accession for one or more protein products, those data are reported under products as type peptide. Accession, version, and gi are provided. The function of reporting the position coordinates if there is no protein product is not currently retained. Example of an mRNA, its encoded protein, and strain of origin type comment, heading "Related Sequences", products { { type mRNA, heading "mRNA", accession "AY185125", version 1, source { { src { db "Nucleotide", tag id 27966960 }, anchor "AY185125" } }, seqs { whole gi 27966960 }, products { { type peptide, accession "AAO25741", version 1, source { { src { db "Protein", tag id 27966961 }, anchor "AAO25741" } }, seqs { whole gi 27966961 } } }, comment { { type other, label "Strain", text "C57BL/6" } } }, |
| TYPE: [e|m|g] refers to type of nucleotide sequence: e=EST m=mRNA g=genomic | |
| PROT: [SET][multiple][optional] A potentially repeating set of two values: accession and identifier (PID value) for the coding region or regions annotated on the associated nucleotide record, one line for each accession If no data are available, na is supplied. The delimiter is |. [/SET][/SET] | |
| [OFFICIAL|PREFERRED]_SYMBOL: [alphanumeric] [unique] [required] the symbol used for gene reports OFFICIAL: validated by the appropriate nomenclature committee PREFERRED: interim option selected for display na is used for models without evidence | The preferred symbol and preferred name are reported as gene→locus and gene→desc, respectively. Whether or not these are official is not explicitly represented. If there is a value for locus-tag, the resource associated with that locus-tag should be used to determine if the names are official or interim. If locus is not supplied, however, it indicates no official symbol has been identified. A record with an official symbol and name.gene { locus "A2m", desc "alpha-2-macroglobulin", ... A record with no identified official symbol or name. gene { desc "spongiotrophoblast specific protein", maploc "17p14", db { { db "LocusID", tag id 64509 } }, syn { "Tpbp" }, locus-tag "RGD:621454" }, |
| [OFFICIAL|PREFERRED]_GENE_NAME: [alphanumeric] [unique] [required (but may be null)] the gene description used for gene reports OFFICIAL: validated by the appropriate nomenclature committee PREFERRED: interim selected for display [Note: If the symbol is official, the gene_name will be official. No record will have both official AND interim nomenclature. | |
| PREFERRED_PRODUCT: [alphanumeric] [unique] [optional] the name of the product used in the RefSeq record | The name of any RefSeq protein product is reported as part of the protein's gene-commentary, as post-text. type peptide, heading "Product", accession "NP_057236", version 2, source { { src { db "Protein", tag id 7706625 }, anchor "NP_057236", post-text "retinoic acid receptor, beta isoform 2" } }, seqs { whole gi 7706625 }, |
| ALIAS_SYMBOL: [alphanumeric][multiple] other symbols associated with this gene | All aliases are listed as synonyms gene→syn. syn { "HAP", "RRB2", "NR1B2" }, |
| ALIAS_PROT: [alphanumeric][multiple] other protein names associated with this gene | All protein names are enumerated as prot→name. prot { name { "retinoic acid receptor, beta", "RAR-epsilon", "RAR, beta form", "HBV-activated protein", "retinoic acid receptor beta 2", "retinoic acid receptor beta 4", "hepatitis B virus activated protein", "retinoic acid receptor, beta polypeptide" } }, |
| REL2: [set][optional][alphanumeric][multiple] LocusID of the interacting protein| RefSeq accession of the interacting protein| name of the interacting protein| keyword for the type of interaction| accession of the RefSeq protein associated with this locus| name of the RefSeq protein at this locus| a description of the interaction| PubMed id(s) describing the interaction [/set] | Not yet implemented. |
| PHENOTYPE: [SET][alphanumeric][multiple] a phenotype associated with a mutation in this gene | Descriptions of phenotypes associated with a gene are reported in gene-commentaries of type comment with the heading Phenotypes. The name of any phenotype is provide as text, and the source of that name, and its identifier there, are reported as database cross-references source. type comment, heading "Phenotypes", comment { { type comment, text "Cystic fibrosis", source { { src { db "MIM", tag id 219700 }, anchor "MIM: 219700" } } }, { type comment, text "Pancreatitis, idiopathic", source { { src { db "MIM", tag id 602421 }, anchor "MIM: 602421" } } }, { type comment, text "Sweat chloride elevation without CF", source { { src { db "MIM", tag id 602421 }, anchor "MIM: 602421" } } } } }, |
| PHENOTYPE_ID: [/SET] an ID used for this phenotype. For humans, this is the MIM number | |
| SUMMARY: [alphanumeric][optional] a summary description of the gene, its products, its significance, and mutant phenotypes | This is optional text, represented in the ASN.1 as 'summary', after the 'gene' and 'prot' text and before 'location'. |
| UNIGENE: [alphanumeric][multiple] UniGene cluster id(s) associated with this gene | UniGene cluster designations are reported as a gene-commentary of type comment and text UniGene within a gene-commentary of type comment and heading Additional Links. The cluster designation is provided both as a db_xref and as an anchor. { type comment, heading "Additional Links", comment { { type comment, text "UniGene", source { { src { db "UniGene", tag str "Hs.411882" }, anchor "Hs.411882", url "/UniGene/clust.cgi?ORG=Hs&CID=411882" } } }, |
| OMIM: [numeric][optional][multiple] MIM number | MIM numbers are reported as a gene-commentary of type comment and text MIM within a gene-commentary of type comment and heading Additional Links. The MIM number is provided both as a db_xref and as an anchor. { type comment, heading "Additional Links", ... comment { type comment, text "MIM", source { { src { db "MIM", tag str "602421" }, anchor "602421" } } }, |
| CHR: [alphanumeric][optional][multiple] the chromosome assignment | Chromosome is represented according to the NCBI-BioSource standard, namely as source→subtype. source { genome genomic, origin natural, org { taxname "Homo sapiens", common "human", ... }, subtype { { subtype chromosome, name "7" ... |
| MAP: [alphanumeric][optional][multiple] One line, consisting of a repeating set of 3 data elements, each element separated by | the first element is the location; the second is the source (as a URL when appropriate), and the third element is the type of map information (G = genetic, C=cytogenetc) | Map data are stored under location, with the units of the location being reported as method map-type. An example of a cytogenetic map location. location { { display-str "7q31.2", method map-type cyto } }, |
| STS: set of STS markers [SET][alphanumeric][optional][multiple] multiline set, one marker per line marker name|chromosome|sts_id|D segment|seq_known|evidence[/SET] evidence types are <currently either epcr, or PubMed id(s) | Markers are reported as gene-commentaries of type comment under the heading Sequence Tagged Site (Markers). The UniSTS id is the value of tag id, the preferred name is anchor, and evidence is post-text. The function of reporting the chromosome to which the marker has been mapped is not retained. The function of enumerating all marker aliases has, however, been added. { type comment, heading "Sequence Tagged Site (Markers)", comment { { type comment, source { { src { db "UniSTS", tag id 12967 }, anchor "D7S2742", post-text "(e-PCR)" } }, comment { { type other, label "Alternate name", text "G00-674-897" }, { type other, label "Alternate name", text "G11318" }, { type other, label "Alternate name", text "G13271" }, ... |
| COMP: Set of comparative map links [alphanumeric][optional][multiple] c_tax_id|c_symbol|c_chromosome|c_position|c_locus_id| q_chromosome|symbol of the current gene|map_name[/SET] the tax_id of the homolog, the symbol of the homolog, the homologous chromosome, the homologous position, the locus_id of the homolog, the chromosome of the source record, the map name | This function is not likely to be retained. |
| ECNUM: [alphanumeric][optional][multiple] | Enzyme Commission numbers (EC) are reported as gene-commentaries of type property and label EC. The EC number is reported as text. comment { { type property, label "EC", text "1.2.3.1" } } |
| BUTTON: [SET][alphanumeric][optional] an web resource accessed by a button, as well as or in addition to text | If retained, then as a sequence of Gene-commentary. type comment, heading "Additional Links", comment { { type comment, text "UniGene", xtra-properties { { tag "UNIGENE", value "Hs.74561" } }, source { { src { db "UniGene", tag str "Hs.74561" }, anchor "Hs.74561", url "/UniGene/clust.cgi?ORG=Hs&CID=74561" } } }, |
| LINK: [/SET][alphanumeric the url underlying the button (note: if there are variation data for this locus at NCBI, the line "BUTTON: snp.gif" will be present) | |
| DB_DESCR: [SET][alphanumeric][optional][multiple] The name of an external website with more information about this locus | |
| DB_LINK: [/SET][alphanumeric] the URL | |
| PMID: [numeric][multiple] a subset of publications associated with this locus with the link being the PubMed unique identifier comma separated | comments, type comment, refs where the value is pmid { type comment, refs { pmid 14637088, pmid 14506912, pmid 1370808, pmid 1281457 } }, |
| GRIF: [SET][alphanumeric][optional][multiple][/SET] PubMed unique identifier|comment | Under development. |
| GO: [SET][alphanumeric][optional][/SET] category of term|the term itself|evidence code|GO identifier| source of annotation|PubMed id(s) | Gene Ontology annotation is reported as properties in gene-commentaries with the heading GeneOntology. The provider of the annotation is indicated under source. The Function, Process, and Component categories are headed by label. The term is provided as anchor, the id as a db_xref, and an evidence code as post-text. properties { { type comment, heading "GeneOntology", source { { pre-text "Provided by", anchor "RGD", url "http://rgd.mcw.edu/" } }, comment { { type comment, label "Function", comment { { type comment, source { { src { db "GO", tag id 3677 }, anchor "DNA binding", post-text "evidence: IEA" } } } } }, |