Difference between revisions of "WBGene information and status pipeline"

From WormBaseWiki
Jump to navigationJump to search
Line 167: Line 167:
 
| Yes, but we'll need isoform data in WB
 
| Yes, but we'll need isoform data in WB
 
|
 
|
 +
|-
 +
| Species
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
|
 +
| This could perhaps be used to populate a future species tag for papers, but this is not an immediate need.  Other use cases?
 
|-
 
|-
 
|}
 
|}

Revision as of 15:58, 20 September 2013

AceDB tag Postgres table Current - Nameserver nightly dump Current - WS bimonthly release Future - Geneace nightly dump Future - WS bimonthly release Use - Paper or meeting abstract gene connection Use - OA data type curation Use - Dumping scripts Use - Protein2GO data conversion Comment
WBGene identifier gin_wbgene Yes Yes Yes Yes Yes
CGC_name gin_locus Yes Yes Yes Yes No
Other_name gin_synonyms No Yes Yes No Yes Yes No
Sequence_name gin_seqname Yes Yes Yes Yes No
Public_name gin_? Yes (but only when no CGC_name or Sequence_name) Don't need (Public_name also in Other_name - confirm this is always the case) Not if also in Other_name Not if also in Other_name Not if also in Other_name No Could remove this table, but need to confirm if any scripts look at Public_name but not Other_name (I doubt it, but we should check)
Molecular_name gin_molname No Yes No Yes Yes No Maybe
Status gin_dead Yes Yes Yes Yes Yes Yes
Merged_into gin_dead No Yes Yes No Historical_gene tag?
Acquires_merge ?
Split_into No Yes Yes N Historical_gene tag?
Corresponding_transcript No Yes No Yes
Corresponding_CDS No Yes No Yes
Corresponding_protein No Yes No Yes Yes Yes, but we'll need isoform data in WB
Species This could perhaps be used to populate a future species tag for papers, but this is not an immediate need. Other use cases?