Difference between revisions of "WormBase-Caltech Weekly Calls"

From WormBaseWiki
Jump to navigationJump to search
(26 intermediate revisions by 3 users not shown)
Line 41: Line 41:
  
  
==July 9th, 2020==
+
==August 6th, 2020==
===Gene names issue in SimpleMine and other mining tools===
+
===Experimental conditions data flow into Alliance===
*Wen: Last week, Jonathan Ewbank raised the issue of gene names that may refer to multiple objects.
+
*Experimental conditions in disease annotations: WB has inducers (used to recapitulate the disease condition) and modifiers (a modifier can ameliorate, exacerbate, or have no effect, on the disease condition)
*this can be an issue for multiple data mining tools including WormMine, BioMart, and Gene Set Enrichment.
+
*We use the WB Molecule CV for Inducers and Modifiers in disease annotation
*Perhaps have a standalone approach to check if any gene name among a list may refer to multiple objects (users check their name lists before submitting them to any data mining tool).
+
*Experimental conditions in phenotype annotations: are free text (captured in remarks); will probably need to formalize later on
*Jae: The public name issue has heterogeneous natures. That means there may be no single solution to solve all those problems.
+
*So for data flow into Alliance:
*Gene list curation from high-throughput studies, confusing usage of public names probably less than 2% (still cannot be ignored). See examples below--
+
**In the short term we will load the Molecule CV into the Alliance (Ranjana and Michael P. will work on this)
**single public name is assigned to multiple WBgene ID, Wen has a list of these genes
+
**Groups will switch to using common data model that works for all and common ontology/ontologies in the near future.
**overlapped or dicistronic genes, ex. mrpl-44 and F02A9.10
+
* How do we handle genetic sex? Part of condition?
**overlapped or dicistronic, but has a single sequence name, examples:  
+
** Condition has been intended for external/environmental conditions, whereas genetic sex is inherent to the organism of study
    exos-4.1 and tin-9.2 (B0564.1)
+
** Expression pattern curation needs genetic sex; needs a model at the Alliance for capturing sex
    eat-18 and lev-10 (Y105E8A.7)
 
    cha-1 and unc-17 (ZC416.8)
 
 
 
**simple confusion from authors, ex. mdh-1 and mdh-2
 
*One of the most significant problems is a propagation to other DB and papers of  these gene name issues.
 
*We can make a special note for each gene page, but the people using batch analysis could not catch that easily.
 
*Conclusion: Jae and Wen will work on a tool that lets Users "sanitize" their gene lists before submission to data mining tools.  They will also write a microPub explaining this issue to the community.
 
 
 
===Wormicloud===
 
*Please test and leave any feedback on the word cloud tool (Wormicloud), https://wormicloud.textpressolab.com/
 
*Valerio and Jae have worked on a tool that uses data in Textpresso; given a keyword, eg. "transposon", the tool generates a word cloud and word trend.
 
*Any keyword can generate a graph that plots trends of occurence across the years in publication abstracts.
 
 
 
===Noctua 2.0 form ready to use===
 
*Caltech summer student will try using Noctua initially for dauer (neuronal signaling) pathways
 
 
 
===Nightly names service updates to postgres===
 
*Nightly using Matt's wb-names-export.jar to get full output of genes from datomic/names service, and updating postgres based on that.
 
 
 
 
 
==July 16th, 2020==
 
===Citing ontologies and their versions===
 
*Came up in the context of the Alliance: It would be best practice to provide users with the list of ontologies used and their versions/date.
 
*If WB ontology developers could make sure their ontology file headers (WB anatomy ontology, WB life stage, etc.) conformed to obo file header specifications, then it would be easy to pull in version and date information into the Alliance.
 
*Some useful links
 
**http://www.obofoundry.org/principles/fp-004-versioning.html
 
**http://obo-dashboard-test.ontodev.com/ (you can see that wbbt, wbls version metadata attribute is generating a warning).
 
**Note: OBO-foundry may not have been updated, but good practice to check your headers, anyway.
 
* Chris worked with Nico yesterday to update the ODK version for WBbt and WBls; versioning should be fine now (once the OBO dashboard runs again (hasn't run since February))
 
* Important point: the GitHub release version date tag (e.g. "v2020-06-30") needs to match the ODK release date (as stored in the OBO and OWL file headers)
 
** There are some existing mismatches, Chris is cataloging them now
 
 
 
=== Gene Name Sanitizer ===
 
* Would be good to always (when possible) make users aware of name ambiguities
 
* Wen will keep the "Multiple Output" section at the bottom of SimpleMine output
 
* The gene name sanitizer will be built as a stand alone tool
 
* Important to include history of gene names
 
 
 
=== Tools linking to SimpleMine ===
 
* Vennter and other tools link to SimpleMine with hard coded field/column names; we should have more dynamic/robust linking without relying on hard coded field names
 
 
 
 
 
== July 23rd, 2020 ==
 
 
 
=== Disk failures ===
 
*
 

Revision as of 16:36, 6 August 2020

Previous Years

2009 Meetings

2011 Meetings

2012 Meetings

2013 Meetings

2014 Meetings

2015 Meetings

2016 Meetings

2017 Meetings

2018 Meetings

2019 Meetings



2020 Meetings

January

February

March

April

May

June

July


August 6th, 2020

Experimental conditions data flow into Alliance

  • Experimental conditions in disease annotations: WB has inducers (used to recapitulate the disease condition) and modifiers (a modifier can ameliorate, exacerbate, or have no effect, on the disease condition)
  • We use the WB Molecule CV for Inducers and Modifiers in disease annotation
  • Experimental conditions in phenotype annotations: are free text (captured in remarks); will probably need to formalize later on
  • So for data flow into Alliance:
    • In the short term we will load the Molecule CV into the Alliance (Ranjana and Michael P. will work on this)
    • Groups will switch to using common data model that works for all and common ontology/ontologies in the near future.
  • How do we handle genetic sex? Part of condition?
    • Condition has been intended for external/environmental conditions, whereas genetic sex is inherent to the organism of study
    • Expression pattern curation needs genetic sex; needs a model at the Alliance for capturing sex