Assembly Release QA Steps
Welcome to the Assembly Release: QA Guide 😀
Page created Fall. 2016 by Cath, Jairo, and ChrisV.
This page is currently a draft in progress.
For now, use Releasing_an_assembly instead.
Introduction
When a developer is ready for a new assembly to be released, the QA team (usually an individual of) will QA and release the assembly. This wiki section exists as a guide for the assembly QA and release process.
There are two types of assemblies that the QA team will process:
- New species
- New version for existing species
Change happens
Collaboration rocks. Keep me updated!
Editing this wiki will bring gaggles of glittery giggling unicorn-riding leprechauns to you, and they will improvise a dope rap about you that would make Snoop Dog jelly.
Assembly notes
Assemblies/sequences, from various organizations, are submitted to the mother ship GenBank.
Those assemblies might be included in RefSeq if criteria are met.
NOTE - maybe we should move this section to a QA step!
- RefSeq assemblies:
- use accession ID: GCF_000002315.4 (e.g., galGal5)
- are delivered with chrMt (if they exisit)
- are delivered with NCBI gene predictions
- Genbank assemblies:
- use accession ID: GCA_000001305.2
- delivered without a chrMt.
- do not have gene predictions.
For the UCSC Genome Browser, it is preferable to use RefSeq assemblies (in part due to 'more data').
This is a "learn as we go" direction; historically GeneBank was preferred.
Helpful article: Nature, 2012 A beginner's guide to eukaryotic genome annotation
Assembly QA Google Spreadsheet Checklist Template This Gspreadsheet corresponds to this Assembly Release Guide.
🔵 Ready to get started? Let's go to Assembly QA Part 1: DEV Steps
