Difference between revisions of "WormBase-Caltech Weekly Calls"

From WormBaseWiki
Jump to navigationJump to search
 
(435 intermediate revisions by 9 users not shown)
Line 21: Line 21:
 
[[WormBase-Caltech_Weekly_Calls_2019|2019 Meetings]]
 
[[WormBase-Caltech_Weekly_Calls_2019|2019 Meetings]]
  
 +
[[WormBase-Caltech_Weekly_Calls_2020|2020 Meetings]]
  
 +
= 2021 Meetings =
  
 +
[[WormBase-Caltech_Weekly_Calls_January_2021|January]]
  
= 2020 Meetings =
+
[[WormBase-Caltech_Weekly_Calls_February_2021|February]]
  
[[WormBase-Caltech_Weekly_Calls_January_2020|January]]
+
[[WormBase-Caltech_Weekly_Calls_March_2021|March]]
  
[[WormBase-Caltech_Weekly_Calls_February_2020|February]]
+
[[WormBase-Caltech_Weekly_Calls_April_2021|April]]
  
[[WormBase-Caltech_Weekly_Calls_March_2020|March]]
+
[[WormBase-Caltech_Weekly_Calls_May_2021|May]]
  
[[WormBase-Caltech_Weekly_Calls_April_2020|April]]
+
[[WormBase-Caltech_Weekly_Calls_June_2021|June]]
  
[[WormBase-Caltech_Weekly_Calls_May_2020|May]]
 
  
[[WormBase-Caltech_Weekly_Calls_June_2020|June]]
+
== July 1, 2021 ==
  
[[WormBase-Caltech_Weekly_Calls_July_2020|July]]
+
=== Importing genes for tm alleles from GeneACE ===
 +
* https://github.com/WormBase/website/issues/8262
 +
* Nightly dump currently excludes tm allele genes
 +
* Most tm (Mitani) alleles are not being manually connected to specific genes in GeneACE
 +
* Should pull the data from WS release (into Postgres) after the build has mapped the alleles to genes
 +
* ~100,000 alleles in Postgres; ~70,000 don't have a gene connection
 +
* Would Hinxton be willing to take WS-mapped allele-to-gene associations and populate GeneACE with associations not already in there?
  
 +
=== Citace upload ===
 +
* Curators upload files to Spica for citace upload on Tuesday (July 6)
  
==July 9th, 2020==
+
=== Chen B1 kitchen Usage Considerations ===
===Gene names issue in SimpleMine and other mining tools===
+
* Clean up after oneself.
*Wen: Last week, Jonathan Ewbank raised the issue of gene names that may refer to multiple objects.  
+
* Mark food storage with name and date.
*this can be an issue for multiple data mining tools including WormMine, BioMart, and Gene Set Enrichment.  
+
* Mark storage drawers
*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).
+
* Consumables
*Jae: The public name issue has heterogeneous natures. That means there may be no single solution to solve all those problems.
 
*Gene list curation from high-throughput studies, confusing usage of public names probably less than 2% (still cannot be ignored). See examples below--
 
**single public name is assigned to multiple WBgene ID, Wen has a list of these genes
 
**overlapped or dicistronic genes, ex. mrpl-44 and F02A9.10
 
**overlapped or dicistronic, but has a single sequence name, examples:
 
    exos-4.1 and tin-9.2 (B0564.1)
 
    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===
+
== July 8, 2021 ==
*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===
+
=== Alliance work ===
*Caltech summer student will try using Noctua initially for dauer (neuronal signaling) pathways
+
* Orange team presenting initial plans at Alliance PI meeting tomorrow
 +
* What working groups are still meeting? What are their responsibilities?
 +
** Expression
 +
** Variants
 +
** Disease & Phenotype
 +
** Technical working groups
 +
*** Technical call
 +
*** Data quartermasters
 +
*** DevOps
 +
* Expression working group working on LinkML model with Gil (FB)
 +
** Includes work on antibody class, image class, movie class
 +
** Are species-specific anatomy ontologies being utilized for expression annotations or still just Uberon?
 +
* Creating a curation interface/tool:
 +
** Will require loading auxiliary data types in addition to primary data types (e.g. if we are focused on disease annotation curation, we will need to load genes, alleles, strains, etc. in addition to the disease annotations themselves) to be available to make connections to
 +
** One requirement already expressed by curators is the need to generate new entities, like alleles, and have them quickly (immediately?) available for use in curation
 +
** Maybe this could be handled by an Alliance central name server that mints new IDs (Alliance IDs and maybe also MOD IDs?) for the objects to make them available (also with a mechanism for these new objects/IDs to make their way back to the MODs as well)
 +
** Micropublication curation forms have tackled a lot of issues of collecting lexica and entity names and IDs; should consider work already done with Micropubs
  
===Nightly names service updates to postgres===
+
== July 15, 2021 ==
*Nightly using Matt's wb-names-export.jar to get full output of genes from datomic/names service, and updating postgres based on that.
 
  
 +
=== hlh-34 expression ===
 +
* Rebecca Mcwhirter (Miller lab) contacted WB saying that the annotations to AVJ for hlh-34 are incorrect. 4 evidences list AVJ -> the authors of the first paper that describes hlh-34 expression (Cunningham et al, 2012 : http://dx.doi.org/10.1016/j.cmet.2012.05.014) had to pick one neuron per reviewer's request. The neuron should instead be AVH.
 +
* Oliver is putting together a micropub to clarify the issue
 +
* How to deal with existing  annotations? Add a comment in the remarks that points to the microPub? remove AVJ from the anatomy association list?
 +
* Should we also add public comments to the relevant papers?
  
==July 16th, 2020==
+
== July 22, 2021 ==
===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.
 
  
=== Gene Name Sanitizer ===
+
=== Copying data from textpresso-dev to tazendra ===
* Would be good to always (when possible) make users aware of name ambiguities
+
* Michael has been asking curators to retrieve any data they might still want on textpresso-dev before the machine dies
* Wen will keep the "Multiple Output" section at the bottom of SimpleMine output
+
* Can we copy files to tazendra?
* The gene name sanitizer will be built as a stand alone tool
+
* If so, do we need to have a more general approach/strategy other than creating new folders in the individual curator directories?
* Important to include history of gene names
+
* Are there any size considerations for what we copy over?  There are 1.1T free in /home2 which is not backed up
 
 
=== 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
 

Latest revision as of 18:00, 22 July 2021

Previous Years

2009 Meetings

2011 Meetings

2012 Meetings

2013 Meetings

2014 Meetings

2015 Meetings

2016 Meetings

2017 Meetings

2018 Meetings

2019 Meetings

2020 Meetings

2021 Meetings

January

February

March

April

May

June


July 1, 2021

Importing genes for tm alleles from GeneACE

  • https://github.com/WormBase/website/issues/8262
  • Nightly dump currently excludes tm allele genes
  • Most tm (Mitani) alleles are not being manually connected to specific genes in GeneACE
  • Should pull the data from WS release (into Postgres) after the build has mapped the alleles to genes
  • ~100,000 alleles in Postgres; ~70,000 don't have a gene connection
  • Would Hinxton be willing to take WS-mapped allele-to-gene associations and populate GeneACE with associations not already in there?

Citace upload

  • Curators upload files to Spica for citace upload on Tuesday (July 6)

Chen B1 kitchen Usage Considerations

  • Clean up after oneself.
  • Mark food storage with name and date.
  • Mark storage drawers
  • Consumables


July 8, 2021

Alliance work

  • Orange team presenting initial plans at Alliance PI meeting tomorrow
  • What working groups are still meeting? What are their responsibilities?
    • Expression
    • Variants
    • Disease & Phenotype
    • Technical working groups
      • Technical call
      • Data quartermasters
      • DevOps
  • Expression working group working on LinkML model with Gil (FB)
    • Includes work on antibody class, image class, movie class
    • Are species-specific anatomy ontologies being utilized for expression annotations or still just Uberon?
  • Creating a curation interface/tool:
    • Will require loading auxiliary data types in addition to primary data types (e.g. if we are focused on disease annotation curation, we will need to load genes, alleles, strains, etc. in addition to the disease annotations themselves) to be available to make connections to
    • One requirement already expressed by curators is the need to generate new entities, like alleles, and have them quickly (immediately?) available for use in curation
    • Maybe this could be handled by an Alliance central name server that mints new IDs (Alliance IDs and maybe also MOD IDs?) for the objects to make them available (also with a mechanism for these new objects/IDs to make their way back to the MODs as well)
    • Micropublication curation forms have tackled a lot of issues of collecting lexica and entity names and IDs; should consider work already done with Micropubs

July 15, 2021

hlh-34 expression

  • Rebecca Mcwhirter (Miller lab) contacted WB saying that the annotations to AVJ for hlh-34 are incorrect. 4 evidences list AVJ -> the authors of the first paper that describes hlh-34 expression (Cunningham et al, 2012 : http://dx.doi.org/10.1016/j.cmet.2012.05.014) had to pick one neuron per reviewer's request. The neuron should instead be AVH.
  • Oliver is putting together a micropub to clarify the issue
  • How to deal with existing annotations? Add a comment in the remarks that points to the microPub? remove AVJ from the anatomy association list?
  • Should we also add public comments to the relevant papers?

July 22, 2021

Copying data from textpresso-dev to tazendra

  • Michael has been asking curators to retrieve any data they might still want on textpresso-dev before the machine dies
  • Can we copy files to tazendra?
  • If so, do we need to have a more general approach/strategy other than creating new folders in the individual curator directories?
  • Are there any size considerations for what we copy over? There are 1.1T free in /home2 which is not backed up