Post-Release-Checklist: Difference between revisions
(→Galaxy: adding anton's email) |
(Updating Tim storm's email address) |
||
| (22 intermediate revisions by 9 users not shown) | |||
| Line 1: | Line 1: | ||
This page capture the things to remember after the release of UCSC Genes for the new assembly. | This page capture the things to remember after the release of UCSC Genes for the new assembly. | ||
== | ==wiki pages about known genes== | ||
[[QAing UCSC Genes]]<br> | |||
[[UCSC Genes tables]]<br> | |||
[[UCSC Genes Staging Process]]<br> | |||
[[Post-Release-Checklist]] | |||
== | == Announce the release == | ||
* | * Make an announcement on the genome-announce mailing list | ||
**It's a longer format like [https://groups.google.com/a/soe.ucsc.edu/forum/#!forum/genome-announce this]. | |||
* | * Add a news item to the Genome Browser front page | ||
* Tweet the news (Anyone in QA can do this see [http://genomewiki.ucsc.edu/genecats/index.php/Facebook_update Facebook/Twitter Update ] page). | |||
= Contact various collaborators = | == Contact various collaborators == | ||
=== Exon Primer Links === | === Exon Primer Links === | ||
For human and mouse, send an email to Tim Strom ( | For human and mouse, send an email to Tim Strom (TimStrom@helmholtz-muenchen.de) so that he knows we are releasing a new UCSC Gene set. He will need to prepare his website for the new UCSC IDs. *Note: without an existing dbSNP track, Tim will not be able to install the ExonPrimer feature. | ||
=== HGNC Links to us=== | === HGNC Links to us=== | ||
For human, contact HGNC: hgnc at genenames dot org to let them know about the update. They will need to rebuild their ucsc2hgnc mappings table. | For human, contact HGNC: hgnc at genenames dot org to let them know about the update. They will need to rebuild their ucsc2hgnc mappings table. | ||
=== UniProtKB === | === UniProtKB === | ||
For all but sacCer and danRer, create a special file for the folks at UniProt to create their cross-references to us. Run makeUniProtFile.csh on hgwdev. This will create a file an the appropriate downloads directory, e.g.: | |||
Run makeUniProtFile.csh | |||
hgwdev:/usr/local/apache/htdocs-hgdownload/goldenPath/hg19/UCSCGenes/ | hgwdev:/usr/local/apache/htdocs-hgdownload/goldenPath/hg19/UCSCGenes/ | ||
and then ask for a push of the file to hgdownload. | and then ask for a push of the file to hgdownload. | ||
Send an email to | |||
Send an email to UniProt (uniprot-prod@ebi.ac.uk), notifying them of the new UCSC Genes release. | |||
The current download URLs are: | |||
ftp://hgdownload.soe.ucsc.edu/goldenPath/hg38/UCSCGenes/uniProtToUcscGenes.txt | |||
ftp://hgdownload.soe.ucsc.edu/goldenPath/hg19/UCSCGenes/uniProtToUcscGenes.txt | |||
ftp://hgdownload.soe.ucsc.edu/goldenPath/mm10/UCSCGenes/uniProtToUcscGenes.txt | |||
ftp://hgdownload.soe.ucsc.edu/goldenPath/mm9/UCSCGenes/uniProtToUcscGenes.txt | |||
ftp://hgdownload.soe.ucsc.edu/goldenPath/rn4/UCSCGenes/uniProtToUcscGenes.txt | |||
ftp://hgdownload.soe.ucsc.edu/goldenPath/ce6/UCSCGenes/uniProtToUcscGenes.txt | |||
ftp://hgdownload.soe.ucsc.edu/goldenPath/dm3/UCSCGenes/uniProtToUcscGenes.txt | |||
=== Alert Ensembl === | === Alert Ensembl === | ||
Notify Ensembl that there is a new UCSC Genes set: e-mail to Andy Yates <ayates@ebi.ac.uk> and cc Paul Flicek <flicek@ebi.ac.uk>, Fiona Cunningham <fiona | Notify Ensembl that there is a new UCSC Genes set: e-mail to Andy Yates <ayates@ebi.ac.uk> and cc Paul Flicek <flicek@ebi.ac.uk>, and Fiona Cunningham <fiona@ebi.ac.uk>. They use the UCSC Gene IDs in their external reference (xref) tables. Note they also do want to be notified for rn4 even though it is not Known Genes, and they may want to be notified for assemblies with Known-Gene-like gene tracks. | ||
[[Category:Browser_QA]] | [[Category:Browser_QA]] | ||
[[Category:Browser QA UCSC Genes]] | [[Category:Browser QA UCSC Genes]] | ||
Latest revision as of 19:44, 28 January 2019
This page capture the things to remember after the release of UCSC Genes for the new assembly.
wiki pages about known genes
QAing UCSC Genes
UCSC Genes tables
UCSC Genes Staging Process
Post-Release-Checklist
Announce the release
- Make an announcement on the genome-announce mailing list
- It's a longer format like this.
- Add a news item to the Genome Browser front page
- Tweet the news (Anyone in QA can do this see Facebook/Twitter Update page).
Contact various collaborators
Exon Primer Links
For human and mouse, send an email to Tim Strom (TimStrom@helmholtz-muenchen.de) so that he knows we are releasing a new UCSC Gene set. He will need to prepare his website for the new UCSC IDs. *Note: without an existing dbSNP track, Tim will not be able to install the ExonPrimer feature.
HGNC Links to us
For human, contact HGNC: hgnc at genenames dot org to let them know about the update. They will need to rebuild their ucsc2hgnc mappings table.
UniProtKB
For all but sacCer and danRer, create a special file for the folks at UniProt to create their cross-references to us. Run makeUniProtFile.csh on hgwdev. This will create a file an the appropriate downloads directory, e.g.: hgwdev:/usr/local/apache/htdocs-hgdownload/goldenPath/hg19/UCSCGenes/ and then ask for a push of the file to hgdownload.
Send an email to UniProt (uniprot-prod@ebi.ac.uk), notifying them of the new UCSC Genes release.
The current download URLs are:
ftp://hgdownload.soe.ucsc.edu/goldenPath/hg38/UCSCGenes/uniProtToUcscGenes.txt ftp://hgdownload.soe.ucsc.edu/goldenPath/hg19/UCSCGenes/uniProtToUcscGenes.txt ftp://hgdownload.soe.ucsc.edu/goldenPath/mm10/UCSCGenes/uniProtToUcscGenes.txt ftp://hgdownload.soe.ucsc.edu/goldenPath/mm9/UCSCGenes/uniProtToUcscGenes.txt ftp://hgdownload.soe.ucsc.edu/goldenPath/rn4/UCSCGenes/uniProtToUcscGenes.txt ftp://hgdownload.soe.ucsc.edu/goldenPath/ce6/UCSCGenes/uniProtToUcscGenes.txt ftp://hgdownload.soe.ucsc.edu/goldenPath/dm3/UCSCGenes/uniProtToUcscGenes.txt
Alert Ensembl
Notify Ensembl that there is a new UCSC Genes set: e-mail to Andy Yates <ayates@ebi.ac.uk> and cc Paul Flicek <flicek@ebi.ac.uk>, and Fiona Cunningham <fiona@ebi.ac.uk>. They use the UCSC Gene IDs in their external reference (xref) tables. Note they also do want to be notified for rn4 even though it is not Known Genes, and they may want to be notified for assemblies with Known-Gene-like gene tracks.
