You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be an issue which appears to originate on the NCBI side, whereby genes with a read-through transcript can end up getting the NCBI gene ID of the read through assigned to one of(?) the parent Ensembl Genes.
Here's an example from Biomart (taken in Ensembl 103) which demonstrates this issue:
The text was updated successfully, but these errors were encountered:
ACastanza
changed the title
Address and Filter NCBI Gene IDs miss-assigned due to read-through transcripts
Address and Filter NCBI Gene IDs misassigned due to read-through transcripts
Oct 12, 2021
Here's an example where ENSG00000004866 (ST7) maps to both ST7 and ST7-OT3 in ncbigene:
ensembl_representative_gene_id
ensembl_gene_id
gene_symbol
xref_source
xref_accession
xref_label
xref_description
xref_info_type
xref_linkage_annotation
xref_curie
ENSG00000004866
ENSG00000004866
ST7
EntrezGene
7982
ST7
suppression of tumorigenicity 7
DEPENDENT
None
ncbigene:7982
ENSG00000004866
ENSG00000004866
ST7
EntrezGene
93655
ST7-OT3
ST7 overlapping transcript 3
DEPENDENT
None
ncbigene:93655
I don't think "ST7 overlapping transcript 3" is a read-through, although perhaps this is a similar situation where we don't want to be mapping to both ncbigenes.
What I'm thinking is that for a given representative ensembl gene, we can pick the NCBI gene mapping with the same symbol. That would address these issues as well as #10.
There seems to be an issue which appears to originate on the NCBI side, whereby genes with a read-through transcript can end up getting the NCBI gene ID of the read through assigned to one of(?) the parent Ensembl Genes.
Here's an example from Biomart (taken in Ensembl 103) which demonstrates this issue:
https://www.ncbi.nlm.nih.gov/gene/?term=1394
https://www.ncbi.nlm.nih.gov/gene/?term=104909134
From a quick look at your genes sheet:
it would seem to be affected
The text was updated successfully, but these errors were encountered: