Assembly QA Part 4 RR Steps: Difference between revisions
No edit summary |
mNo edit summary |
||
| Line 19: | Line 19: | ||
RR | ====<span style="color:dodgerblue">Tracks: Push Request==== | ||
</span> | |||
When the track is ready to be released, ask admins (push-request at soe) for a push of the tables (including trackDb_public and hgFindSpec_public, if needed) from mysqlbeta to mysqlrr. Push any associated downloads. Push any associated [[Static_Page_Protocol | static docs]], including images. Notify (cc:) the track sponsor on the push request. | |||
If the track already exists on the RR you may need to selectively push the tables/trackDb. Refer to [[Replacing_old_tables_with_new_ones|Replacing old tables with new ones]] for more information. | |||
If this is a repush of existing data that was found to be problematic, add a note to [http://genecats.cse.ucsc.edu/qa/repush.html repush.html]. The file to edit is in the genecats tree, at genecats/qa/repush.html. (This doesn't happen very often.) | |||
If the push involves pushing a '''database''' please inform admin to '''include genome-euro''' (their scripts are not expecting databases) and check on genome-euro after the final release. | |||
====<span style="color:dodgerblue">Tracks: Validate on the RR==== | |||
</span> | |||
Check your track on the RR. Check that searches work (if not, you probably need to push the hgFindSpec_public table). Also check that all default tracks still display. If you filled in the "Release Log URL" field in the push queue, check the next day to be sure that the link from the [http://genome.ucsc.edu/goldenPath/releaseLog.html release log] works as expected. | |||
Revision as of 23:42, 11 April 2017
This page is currently a draft in progress. For now, use Releasing an assembly instead.
|
Navigation Menu |
Tracks: Push Request
When the track is ready to be released, ask admins (push-request at soe) for a push of the tables (including trackDb_public and hgFindSpec_public, if needed) from mysqlbeta to mysqlrr. Push any associated downloads. Push any associated static docs, including images. Notify (cc:) the track sponsor on the push request.
If the track already exists on the RR you may need to selectively push the tables/trackDb. Refer to Replacing old tables with new ones for more information.
If this is a repush of existing data that was found to be problematic, add a note to repush.html. The file to edit is in the genecats tree, at genecats/qa/repush.html. (This doesn't happen very often.)
If the push involves pushing a database please inform admin to include genome-euro (their scripts are not expecting databases) and check on genome-euro after the final release.
Tracks: Validate on the RR
Check your track on the RR. Check that searches work (if not, you probably need to push the hgFindSpec_public table). Also check that all default tracks still display. If you filled in the "Release Log URL" field in the push queue, check the next day to be sure that the link from the release log works as expected.
🔵 Done with RR steps? Go to Assembly QA Part 5: Post Release Steps
