Assembly Release QA Steps: Difference between revisions

From Genecats
Jump to navigationJump to search
No edit summary
No edit summary
Line 40: Line 40:
Those assemblies [https://www.ncbi.nlm.nih.gov/assembly/help/anomnotrefseq/ might be included in RefSeq if criteria are met].  
Those assemblies [https://www.ncbi.nlm.nih.gov/assembly/help/anomnotrefseq/ might be included in RefSeq if criteria are met].  


 
NOTE - maybe we should move this section to a QA step!
:RefSeq assemblies:
:RefSeq assemblies:
::use accession ID: '''GCF'''_000002315.4 (e.g., galGal5)
::use accession ID: '''GCF'''_000002315.4 (e.g., galGal5)
Line 56: Line 56:


Helpful article: [http://www.nature.com/nrg/journal/v13/n5/full/nrg3174.html Nature, 2012 A beginner's guide to eukaryotic genome annotation]
Helpful article: [http://www.nature.com/nrg/journal/v13/n5/full/nrg3174.html Nature, 2012 A beginner's guide to eukaryotic genome annotation]
[https://docs.google.com/a/ucsc.edu/spreadsheets/d/1DwtQRe-YXEOkcvDIpcTeU2z8hxMw9ylOyMYZum0n3_o/edit?usp=sharing Assembly QA Google Spreadsheet Checklist Template]
This Gspreadsheet corresponds to this Assembly Release Guide.




Line 94: Line 98:


[[Category:Browser QA]]
[[Category:Browser QA]]
[[Category:Browser QA New Assembly]]
[[Category:Browser QA Assembly Release Guide]]
[[Category:Browser QA Assembly Release Guide]]

Revision as of 19:00, 25 October 2016

Welcome to the Assembly Release: QA Guide 😀

Home: Assembly_Release_QA_Steps
  1. Assembly QA Part 1: DEV Steps
  2. Assembly QA Part 2: BETA Steps
  3. Assembly QA Part 3: RR Steps
  4. Assembly QA Part 4: Post Release Steps

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:

  1. New species
  2. 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