Difference between revisions of "What's staying in postgres?"
From WormBaseWiki
Jump to navigationJump to search (Created page with 'For now, we will keep several types of annotations in postgres: #ncRNA #uncloned loci #IEP evidence code ##IEP evidence code annotations made to proteins will eventually be manu…') |
|||
Line 10: | Line 10: | ||
##Cre-vbh-1 annotations - will be added to uniprot manually and then deleted from postgres | ##Cre-vbh-1 annotations - will be added to uniprot manually and then deleted from postgres | ||
##gst-10 - annotations will be added to uniprot manually using a doi as reference id and then deleted from postgres | ##gst-10 - annotations will be added to uniprot manually using a doi as reference id and then deleted from postgres | ||
+ | ##MTCE.26 - annotations will be added to uniprot manually - need to update gp2protein file, but also need to check on status of uniprot identifiers in xrefs.txt file for elegans mitochondrial proteins |
Revision as of 20:57, 7 February 2013
For now, we will keep several types of annotations in postgres:
- ncRNA
- uncloned loci
- IEP evidence code
- IEP evidence code annotations made to proteins will eventually be manually deleted from postgres and entered into protein2go
- other specific annotations that have unique issues
- fox-1 annotations that have yDp13 in with/from - will need to work out with uniprot how to handle these
- jnk-1 and sir-2.1 annotations that have a WBTransgene in the with/from column - will need to work out with uniprot how to handle these
- Cre-vbh-1 annotations - will be added to uniprot manually and then deleted from postgres
- gst-10 - annotations will be added to uniprot manually using a doi as reference id and then deleted from postgres
- MTCE.26 - annotations will be added to uniprot manually - need to update gp2protein file, but also need to check on status of uniprot identifiers in xrefs.txt file for elegans mitochondrial proteins