NCBI has scheduled the next round of HTTPS tests, following up from the initial tests performed on September 15.
The schedule for these tests is as follows (all times are EDT):
You may have heard that NCBI, along with the rest of the Federal Government, is switching to HTTPS-only access. To help prepare for this, NCBI is beginning a series of tests. During these tests, all traffic to NCBI will be redirected from HTTP to HTTPS to simulate our system’s behavior once the HTTPS transition is complete.
The first test will be Thursday, September 15, from 8:00-9:00 AM EDT.
NCBI has announced that we will be changing the way we handle GI numbers for sequence records in September 2016. (Read more, in case you missed it).
In this post, we’ll address a key question:
The short answer is that nothing is happening to these GI numbers.
If a nucleotide or protein record already has a GI, it will continue to have that GI indefinitely. You will also be able to retrieve such a record using its GI either on the NCBI web site or using the E-utilities.
Moreover, GIs will remain part of the XML and ASN.1 formats of sequence records.
Accession.version identifiers. All sequence records, both new and old, will have a unique accession.version identifier.
Existing records will keep the accessions they already have; new sequences will only receive an accession.version identifier.
Stay tuned for additional posts about this topic, and please contact us if you have questions.
Following the latest biomedical literature can be a challenge, but NCBI’s new PubMed Journals will help you keep up-to-date.