Difference between revisions of "WormBase-Caltech Weekly Calls"

From WormBaseWiki
Jump to navigationJump to search
 
(394 intermediate revisions by 11 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]]
  
GoToMeeting link: https://www.gotomeet.me/wormbase1
 
  
= 2020 Meetings =
+
= 2021 Meetings =
 +
== January 14th, 2021 ==
  
[[WormBase-Caltech_Weekly_Calls_January_2020|January]]
+
===PubMed LinkOut to WormBase Paper Pages (Kimberly) ===
 +
* Other databases [https://www.ncbi.nlm.nih.gov/projects/linkout/doc/nonbiblinkout.html link out from PubMed] to their respective paper pages
 +
* For example, https://pubmed.ncbi.nlm.nih.gov/20864032/ links out to GO and MGI paper pages
 +
* Would like to set this up for WormBase and ultimately for the Alliance, but this will require some developer help
 +
* Work on this next month (after AFP and GO grant submissions)?
  
 +
===Update cycle for HGNC data in the OA (Ranjana) ===
 +
*Juancarlos had these questions for us:
 +
<pre style="white-space: pre-wrap;
 +
white-space: -moz-pre-wrap;
 +
white-space: -pre-wrap;
 +
white-space: -o-pre-wrap;
 +
word-wrap: break-word">
  
== February 6, 2020 ==
+
There's a script here that repopulates the postgres obo_*_hgnc tables
 +
based off of Chris and Wen's data
 +
/home/postgres/work/pgpopulation/obo_oa_ontologies/populate_obo_hgnc.pl
  
=== Worcester Area Worm Meeting talk ===
+
It's not on a cronjob, because I think the files are not updated that
* Confirmed for December 2020 or February 2021
+
often.  Do we want to run this every night, or run it manually when
 +
the files get re-generated ?  Or run every night, and check if the
 +
files's timestamps have changed, then repopulate postgres ?
  
=== Alaska software ===
+
</pre>
* Code developed and maintained by Joseph, but not long term solution
 
* Raymond and Eduardo talked about taking it over
 
* Why have a web application vs. a command-line application?
 
** Wanted to make it easy, but also to capture meta data for WB
 
* Should/will find out from Joseph about how hard it is to maintain the software
 
* Maybe it could be taken over by Alliance, as RNA-Seq/Microarray meta data are getting harmonized
 
* Expression working group working with Brian Oliver to have GEO take in more structured meta data
 
* Array Express tried requiring more structured meta data, but authors stopped submitting
 
* May be possible to build a form that collects meta data while simultaneously submitting to GEO in parallel
 
  
 +
===Minutes===
 +
====PubMed LinkOut to WormBase Paper Pages====
  
== February 13, 2020 ==
+
====Update cycle for HGNC data in the OA====
 +
*We will update when Alliance updates the data
 +
*Juancarlos will set it to check the timestamps and if they change will do an update for the OAs
  
=== Alliance Literature Group ===
+
====CENGEN====
* Held first meeting on Monday, February 10th
+
*Wen, Daniela, and Raymond will look at the datasets to work out how to incorporate. Start simple.
* Regular meetings will be on Tuesdays at 10am/1pm/6pm
+
*We will make links to pages on their site.
* Representatives from each group will give a brief overview of their literature pipelines before the group gets into details about deliverables
 
* Question about centralized paper repository; group needs guidance from Alliance PIs on how to proceed
 
  
=== ?Genotype class model ===
 
* [https://docs.google.com/document/d/19hP9r6BpPW3FSAeC_67FNyNq58NGp4eaXBT42Ch3gDE/edit?pli=1#bookmark=id.7r3e8pg19rd8 Proposal]
 
* Can aim to implement for WS277 but may have to wait until WS278
 
  
=== Genotype OA ===
+
== January 21, 2021 ==
* Will put documentation [[Genotype|here]]
 
  
=== WB All-Hands Meeting ===
+
=== Neural Network (NN) Paper Classification Results ===
* [https://doodle.com/poll/7f65p4ba6d88ztzt Doodle poll]
+
* Linking to Paper Display tool (as opposed to Paper Editor) from Michael's webpage for NN results (Michael will make change)
* Any thoughts at this point?  Still need to discuss with Hinxton, Toronto.
+
* NN results will be incorporated into the Curation Status Form
 +
* For AFP and VFP, there is now a table with mixed SVM and NN results ("blackbox" results); for a given paper, if NN results exist, they take priority over any SVM results
 +
* Decision: we will omit blackbox results (at least for now) from curation status form (just add the new NN results separately)
 +
* We have stopped running SVM on new papers
 +
* Interactions SVM has performed better than new NN results; would be worth attempting a retraining
  
 +
=== Community Phenotype Curation ===
 +
* On hold for a few months to commit time to updating the phenotype annotation model to accommodate, e.g. double mutant phenotypes, multiple RNAi targets (intended or otherwise), mutant transgene products causing phenotypes, expressed human genes causing phenotypes, etc.
 +
* Changes made for WB phenotypes may carry over to Alliance phenotype work
 +
* [https://www.preprints.org/manuscript/202101.0169/v1 Paper out now] on undergrad community phenotype curation project with Lina Dahlberg; we may get more requests for trying this with other undergrad classes
  
== February 20, 2020 ==
+
=== AFP Anatomy Function flagging ===
 
+
* Sometimes it is difficult to assess whether an author flag is correct (often times can be wrong/absent)
=== Genotype ===
+
* What about giving authors/users feedback on their flagging results?
* We will equate superficially similar/identical genotypes for now
+
* Would be good to provide content from paper where this data is said to exist (automatically from a Textpresso pipeline or manually from author identified data)
* What if labs sequence strains later and find out more?  
+
* We want to be careful about how we provide feedback; we should be proactive to make improvements/modifications on our end and bring those back to users for feedback to us
* Labs will have to report strains and their sequence and we back-curate accordingly
 
 
 
=== VC2010 assembly genes ===
 
* WormMine now returning double the gene count for C. elegans genes because of incorporation of newest VC2010 assembly
 
* How to best handle these "extra" genes?
 
* We could make different species entries that specify the assembly version
 
 
 
 
 
== February 27, 2020 ==
 
 
 
=== WB Project meeting ===
 
* Early May (~May 7th, 8th)
 
 
 
=== Genotype ===
 
* [[Genotype|Genotype Wiki page]] updated
 
* Will start building Genotype OA
 
 
 
=== Outreach inbox ===
 
* 65 unread messages pertaining to AFP, some dating back to June. Can we clean these up?
 
* Many are bounced emails messages
 
* Do we want a common place to track bad/bouncing email addresses? We need to distinguish addresses that bounce for policy/SPAM reasons versus those that are likely outdated or no longer in use.
 

Latest revision as of 17:52, 21 January 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 14th, 2021

PubMed LinkOut to WormBase Paper Pages (Kimberly)

  • Other databases link out from PubMed to their respective paper pages
  • For example, https://pubmed.ncbi.nlm.nih.gov/20864032/ links out to GO and MGI paper pages
  • Would like to set this up for WormBase and ultimately for the Alliance, but this will require some developer help
  • Work on this next month (after AFP and GO grant submissions)?

Update cycle for HGNC data in the OA (Ranjana)

  • Juancarlos had these questions for us:

There's a script here that repopulates the postgres obo_*_hgnc tables
based off of Chris and Wen's data
/home/postgres/work/pgpopulation/obo_oa_ontologies/populate_obo_hgnc.pl 

It's not on a cronjob, because I think the files are not updated that
often.  Do we want to run this every night, or run it manually when
the files get re-generated ?  Or run every night, and check if the
files's timestamps have changed, then repopulate postgres ?

Minutes

PubMed LinkOut to WormBase Paper Pages

Update cycle for HGNC data in the OA

  • We will update when Alliance updates the data
  • Juancarlos will set it to check the timestamps and if they change will do an update for the OAs

CENGEN

  • Wen, Daniela, and Raymond will look at the datasets to work out how to incorporate. Start simple.
  • We will make links to pages on their site.


January 21, 2021

Neural Network (NN) Paper Classification Results

  • Linking to Paper Display tool (as opposed to Paper Editor) from Michael's webpage for NN results (Michael will make change)
  • NN results will be incorporated into the Curation Status Form
  • For AFP and VFP, there is now a table with mixed SVM and NN results ("blackbox" results); for a given paper, if NN results exist, they take priority over any SVM results
  • Decision: we will omit blackbox results (at least for now) from curation status form (just add the new NN results separately)
  • We have stopped running SVM on new papers
  • Interactions SVM has performed better than new NN results; would be worth attempting a retraining

Community Phenotype Curation

  • On hold for a few months to commit time to updating the phenotype annotation model to accommodate, e.g. double mutant phenotypes, multiple RNAi targets (intended or otherwise), mutant transgene products causing phenotypes, expressed human genes causing phenotypes, etc.
  • Changes made for WB phenotypes may carry over to Alliance phenotype work
  • Paper out now on undergrad community phenotype curation project with Lina Dahlberg; we may get more requests for trying this with other undergrad classes

AFP Anatomy Function flagging

  • Sometimes it is difficult to assess whether an author flag is correct (often times can be wrong/absent)
  • What about giving authors/users feedback on their flagging results?
  • Would be good to provide content from paper where this data is said to exist (automatically from a Textpresso pipeline or manually from author identified data)
  • We want to be careful about how we provide feedback; we should be proactive to make improvements/modifications on our end and bring those back to users for feedback to us