Going to the ASCB | EMBO meeting? Stop by the NCBI booth (#327) to learn about all that NCBI has to offer, ask questions, and provide feedback on how we can better meet your needs for research and teaching.
Booth #327, Exhibit Hall:
- Sunday, December 9, 9:30 AM – 4:00 PM
- Monday, December 10, 9:30 AM – 4:00 PM
- Tuesday, December 11, 9:30 AM – 4:00 PM
Visit the booth anytime during exhibit hours to discuss any topic or just to say hello. We’re also offering specific times at the booth for focused conversations about using specific sets of NCBI resources in your research and teaching.
- 12:30 PM NCBI BLAST in research and teaching
- 12:30 PM Jupyter notebooks to teach scripting and NCBI resources
- 12:30 PM EDirect for command-line access to NCBI databases
- 2:00 PM Jupyter notebooks to teach scripting and NCBI resources
To stay up-to-date about NCBI at ASCB or in general, follow us on Twitter at @NCBI .
As previously announced, GenBank and other INSDC members will expand the accession formats used for sequencing projects by the end of this year. We’re introducing these new formats to accommodate the growth of Whole Genome Shotgun (WGS), Transcriptome Shotgun Assembly (TSA), and Targeted Locus Study (TLS) sequencing sequences. More details about those changes are available on NCBI Insights.
You may have to adjust your code and databases to accommodate the new formats’ longer length. In particular, the first line of the flatfile format, referred to as the LOCUS line, includes the “Locus Name” (usually identical to the accession number), which may now grow to as long as 20 characters. See section 3.4.4 of the GenBank release notes for examples of how the LOCUS line might change.
Since 2003, the GenBank release notes have recommended that flatfile parsers use a whitespace-separated tokens approach to accommodate changes like the one described in section 3.4.4. If your flatfile parsers rely solely on position, you may have to make modifications. From our internal testing, it appears BioPython and BioPerl properly handle most of the examples shown in section 3.4.4, and only have issues with the last theoretical examples where the sequence length no longer ends at position 40. We do recommend adjusting code to accommodate those theoretical examples for future-proofing.
Please write to the helpdesk with any questions about the new formats.