News: NCBI is going to eliminate GI identifiers
NCBI gets rid of the old GI identifiers for sequence records by September 2016, see here.
ncbi
gi
• 3,735 views
•
link
updated
by
Ram
•
written
by
Anima Mundi
0 answers
No answers yet.
Log in to answer this question.
More posts like this
-
GI numbers in NCBI
written by Christoph •In 2016 NCBI announced that it will phase out GI numbers. https://ncbiinsights.ncbi.nlm.nih.gov/2016/09/12/the-future-of-existing-gi-numbers-at-ncbi/ And the documentation says: "Special note for sequence databases. NCBI is no longer …
-
GenBank entry with apparently unmarked changes
written by Anima MundiDears, I have an mRNA sequence stored as a local file. I retrieved it from GenBank in late 2016 (ID: XM_014915109.1). I just found out …
-
What does BLAST command line - gilist option refer to?
written by yarmda •https://www.ncbi.nlm.nih.gov/books/NBK431010/#news_03-02-2016-phase-out-of-GI-numbers describes the phasing out of GI numbers two years ago. Has BLAST caught up with that, but they haven't renamed the flag in blastn/t …
-
GI identifiers lost
written by albert.rafels •I have a set of proteins from diverse Bacteria. I'm trying to analyze them using DAVID but it cannot recognize more than 80% of my …
-
Understanding NCBI identifiers
written by tlorinThis is kind of a general question regarding NCBI accesion numbers. Suppose I have this sequence >myseq MGQ-----NSPNLLR------LSQ --TLVGSSLLSSPSSPTTLKVKMPHAFPFLTPDQ-KKELSDIAHKIVAKGKGILAADES- --TGSVAKRFQSINTENTEENRRLYRQLLFTA-DERAGPCIGGVIFFHETLYQKTDAGKT FPEHVKSRGWVVGIKVDKGVVPLAGTN-GETTTQ---GLDGL--------YERCAQYKKD GCDFAKWRCVLKITSTTPSRLAIMENCNVLARYASICQM--HGIVPIVEPEILPDGDHDL KRTQYVTEKV-LAAMYKALSDHHVYLEGTLLKPNMVTAGHSCSHKYTHQDIAMATITALR RTVPPAVPG--ITFLSGGQSEEEASINLNVMNQCPLHRPWAITFSYGRALQASALKAWGG KPGNGKAAQEEFIKRAL------ANSLACQGKYVSSGN-S-A-AAGDSLFVANHAY …
-
NCBI Blast locally: filter by accession number and NOT by GI number
written by tlorinI have downloaded the NCBI nt database using the `blastdb_update.pl` perl script, but I want to blast some query file not on the whole nt …
-
Can I Use blastdb_aliastool and Accessions List Make a Bacteria Subset Nr Database
written by felix.kuo.1211 •I have know that NCBI has (or is about to) [stopped supporting gi numbers.][1] It change to use Accessions. I have use ["Question: Vertebrate Subset …
-
Question: How to Extract Bacteria From Ncbi Nt.
written by felix.kuo.1211 •I want to extract bacteria from ncbi nt to make a bacteria subset nt database. And use bowtie2 mapping reads with this bacteria subset nt …
-
News: Ncbi Releases Entrez Direct, The Entrez Utilities On The Unix Command Line
written by Pierre Lindenbaumhttp://www.ncbi.nlm.nih.gov/news/02-06-2014-entrez-direct-released/ > NCBI has just released Entrez Direct, a new software suite that enables users to use the UNIX command line to directly access NCBI …
-
Retrieving Fasta Sequences From Ncbi Using Biopython
written by Ankur •<p>I have a file with GI numbers and would like to get <code>FASTA</code> sequences from ncbi.</p> <pre><code>from Bio import Entrez import time Entrez.email ="eigtw59tyjrt403@gmail.com" f …
would all existing entries change or only the new submissions?
Appears to be all entries. GI's may still be used internally at NCBI but they will not be visible/included in GenBank, GenPept, and FASTA records.
Indeed, as far as I understood is going to be eliminated from all entries.
Although they now provide accession2taxid map files, these do not work with makeblastdb -taxid_map option even if you parse columns 2 and 3 (accession.version & taxid) into their own file. It's relatively painless to join the taxids to tabular blast output, but it gets less convenient if you also want to see e.g. "sscinames" ;-( There should really be taxid2alltaxinfo map files..
I suggest that you send that request in to BLAST help email address. Perhaps NCBI will start making that file available by the time GI gets phased out in September 2016.
I did that yesterday. At least right now there is no solution and you have to do post processing yourself.
This. It's crazy how many slow API alls are required to extract meaningful taxonomic information from BLAST results. It's hilariously user unfriendly. Thanks for making the request.
So it looks like we'll soon have to do this to get any meangful info from BLAST results:
Someone please tell me there's a better solution