Post-Release-Checklist: Difference between revisions

From Genecats
Jump to navigationJump to search
(→‎UniProtKB: updated email for uniprot and added link for hg38)
Line 26: Line 26:




Send an email to the following people at UniProt, notifying them of the new UCSC Genes release:
Send an email to UniProt (uniprot-prod@ebi.ac.uk), notifying them of the new UCSC Genes release:
*Benoit Bely: bbely@ebi.ac.uk
 
*Francesco Fazzini: ffazzini@ebi.ac.uk
*Severine Duvaud: severine.duvaud@isb-sib.ch




The current download URLs are:
The current download URLs are:


ftp://hgdownload.cse.ucsc.edu/goldenPath/hg38/UCSCGenes/uniProtToUcscGenes.txt
ftp://hgdownload.cse.ucsc.edu/goldenPath/hg19/UCSCGenes/uniProtToUcscGenes.txt
ftp://hgdownload.cse.ucsc.edu/goldenPath/hg19/UCSCGenes/uniProtToUcscGenes.txt
ftp://hgdownload.cse.ucsc.edu/goldenPath/mm9/UCSCGenes/uniProtToUcscGenes.txt
ftp://hgdownload.cse.ucsc.edu/goldenPath/mm9/UCSCGenes/uniProtToUcscGenes.txt

Revision as of 23:13, 10 June 2014

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
  • Add a news item to the Genome Browser front page
  • Tweet the news (Bob or Pauline usually do this)

Contact various collaborators

Exon Primer Links

For human and mouse, send an email to Tim Strom (http://ihg2.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.cse.ucsc.edu/goldenPath/hg38/UCSCGenes/uniProtToUcscGenes.txt ftp://hgdownload.cse.ucsc.edu/goldenPath/hg19/UCSCGenes/uniProtToUcscGenes.txt ftp://hgdownload.cse.ucsc.edu/goldenPath/mm9/UCSCGenes/uniProtToUcscGenes.txt ftp://hgdownload.cse.ucsc.edu/goldenPath/rn4/UCSCGenes/uniProtToUcscGenes.txt ftp://hgdownload.cse.ucsc.edu/goldenPath/ce6/UCSCGenes/uniProtToUcscGenes.txt ftp://hgdownload.cse.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.