Assembly Release QA Steps: Difference between revisions

From Genecats
Jump to navigationJump to search
No edit summary
No edit summary
 
(61 intermediate revisions by the same user not shown)
Line 1: Line 1:
<div style="border: 2px solid #A3B1BF; padding: .5em 1em 1em 1em; border-top: none; background-color: #FFFBF1; color: #000;">
<div style="border: 2px solid #A3B1BF; padding: .5em 1em 1em 1em; border-top: none; background-color: #FFFEFB; color: #000;">
 
== Welcome to the '''Assembly Release: QA Guide''' 😀 ==


{| class=wikitable width=415 align=right
{| class=wikitable width=415 align=right
|
|
:Home: [[Assembly_Release_QA_Steps]]
<span style="color:darkorange">Navigation Menu</span>
#[[Assembly QA Part 1: DEV Steps]]
:[[Assembly_Release_QA_Steps | Home Page]]
#[[Assembly QA Part 2: BETA Steps]]
::[[Assembly QA Part 1 DEV Steps | Assembly QA Part 1: DEV Steps]]
#[[Assembly QA Part 3: RR Steps]]
::[[Assembly QA Part 2 Track Steps | Assembly QA Part 2: Track Steps]]
#[[Assembly QA Part 4: Post Release Steps]]
::[[Assembly QA Part 3 BETA Steps | Assembly QA Part 3: BETA Steps]]
::[[Assembly QA Part 4 RR Steps | Assembly QA Part 4: RR Steps]]
|}
|}


<span style="color:darkred">
Page created Fall. 2016 by Cath, Jairo, and ChrisV. <br>This page is currently a draft in progress.<br>For now, use [[Releasing_an_assembly]] instead.
</span>
===<span style="color:blue">Introduction===
</span>


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.
<span style="color:olive">See also: [[Releasing_an_assembly | Releasing an assembly (old steps)]] </span>
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




===<span style="color:blue">Change happens===
===<span style="color:dodgerblue">Introduction===
</span>
</span>
Collaboration rocks. Keep me updated!<br>
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.


===<span style="color:blue">Assembly notes===
When a developer is ready for a new assembly to be released, a member of the QA team will QA and release the assembly. This wiki section exists as a guide for the assembly QA and release process.
</span>


Assemblies/sequences, from various organizations, are submitted to the mother ship [https://www.ncbi.nlm.nih.gov/genbank/ GenBank].<br>
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!
The QA rock star can follow this guide in unison with a sync'd Google spreadsheet checklist, simply by copying the [http://genomewiki.ucsc.edu/genecats/index.php/Assembly_QA_Part_1_DEV_Steps#Setup:_Create_a_Google_spreadsheet_checklist_from_a_template super fancy-pants spreadsheet template]. These wiki steps are automatically populated in the spreadsheet as a checklist, and therefore will always be in sync with the wiki.
: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.


 
🔵  Ready to get started? Go to  [[Assembly QA Part 1 DEV Steps | Assembly QA Part 1: DEV Steps ]]
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: [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.
 
 
 
🔵  Ready to get started? Let's go to  [[Assembly QA Part 1: DEV Steps]]




Line 97: Line 60:




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

Latest revision as of 23:21, 20 March 2018

Navigation Menu

Home Page
Assembly QA Part 1: DEV Steps
Assembly QA Part 2: Track Steps
Assembly QA Part 3: BETA Steps
Assembly QA Part 4: RR Steps


See also: Releasing an assembly (old steps)


Introduction

When a developer is ready for a new assembly to be released, a member of the QA team will QA and release the assembly. This wiki section exists as a guide for the assembly QA and release process.


The QA rock star can follow this guide in unison with a sync'd Google spreadsheet checklist, simply by copying the super fancy-pants spreadsheet template. These wiki steps are automatically populated in the spreadsheet as a checklist, and therefore will always be in sync with the wiki.


🔵 Ready to get started? Go to Assembly QA Part 1: DEV Steps

Retrieved from "https://genomewiki.ucsc.edu/genecats/index.php?title=Assembly_Release_QA_Steps&oldid=4642"