Difference between revisions of "WormBase-Caltech Weekly Calls"

From WormBaseWiki
Jump to navigationJump to search
m
(440 intermediate revisions by 9 users not shown)
Line 16: Line 16:
  
 
[[WormBase-Caltech_Weekly_Calls_2017|2017 Meetings]]
 
[[WormBase-Caltech_Weekly_Calls_2017|2017 Meetings]]
 +
 +
[[WormBase-Caltech_Weekly_Calls_2018|2018 Meetings]]
  
  
Line 21: Line 23:
  
  
= 2018 Meetings =
+
= 2019 Meetings =
 
 
[[WormBase-Caltech_Weekly_Calls_January_2018|January]]
 
 
 
[[WormBase-Caltech_Weekly_Calls_February_2018|February]]
 
 
 
[[WormBase-Caltech_Weekly_Calls_March_2018|March]]
 
 
 
[[WormBase-Caltech_Weekly_Calls_April_2018|April]]
 
 
 
[[WormBase-Caltech_Weekly_Calls_May_2018|May]]
 
 
 
[[WormBase-Caltech_Weekly_Calls_June_2018|June]]
 
 
 
[[WormBase-Caltech_Weekly_Calls_July_2018|July]]
 
 
 
 
 
== August 2, 2018 ==
 
 
 
=== AFP ===
 
 
 
* The AFP pipeline is currently emailing authors from karen's e-mail address
 
* Use same e-mail account Chris is using for phenotype community curation requests or create a new account for AFP (gmail)
 
* Can use outreach@wormbase.org for consistency
 
* May use the PMID in the subject line so e-mails will not be all in the same thread
 
* Todd and Chris have email credentials
 
** Chris will send to Valerio, Juancarlos, Daniela, and Kimberly
 
* Let Valerio and Juancarlos know what pipelines use AFP before they modify
 
* Do curators still want to receive emails when authors flag their data type?
 
** We will leave the alert emails as is for now
 
 
 
 
 
== August 9, 2018 ==
 
  
=== AFP ===
+
[[WormBase-Caltech_Weekly_Calls_January_2019|January]]
* Mei Zhen, SAB member suggested that we include disease models in the AFP form.
 
* The AFP group will work with Ranjana to incorporate it. Ranjana will prepare a mock by next week.
 
* We will then decide about using the existing afp_humdis tables or creating new ones.
 
  
=== Tazendra ===
+
[[WormBase-Caltech_Weekly_Calls_February_2019|February]]
  
* Shall we move tazendra.caltech.edu to the cloud? Either WormBase cloud or Caltech cloud?
+
[[WormBase-Caltech_Weekly_Calls_March_2019|March]]
  
 +
[[WormBase-Caltech_Weekly_Calls_April_2019|April]]
  
 +
[[WormBase-Caltech_Weekly_Calls_May_2019|May]]
  
== August 16, 2018 ==
+
[[WormBase-Caltech_Weekly_Calls_June_2019|June]]
  
=== Tazendra ===
+
[[WormBase-Caltech_Weekly_Calls_July_2019|July]]
* Moving to cloud? To avoid local hardware issues?
 
* Need to discuss with Juancarlos and Paul S.
 
* Need to consider logistics; put all of Tazendra functionality on cloud? Keep some things local?
 
** Postgres in cloud; forms local? Paper pipeline?
 
** Will consult with Textpresso
 
  
=== ICBO 2018 recap ===
+
[[WormBase-Caltech_Weekly_Calls_August_2019|August]]
* POTATO workshop (Phenotype Ontologies Traversing All The Organisms)
 
** Will work towards generating standardized logical definitions using Dead Simple OWL Design Patterns (DOSDP)
 
*** <Quality> and inheres_in some <Entity> (and has_modifier some <Mod>)
 
*** Exercise: Reconciling logical definitions for apparently equivalent phenotype terms across ontologies (e.g. MP vs. HP)
 
** Can use Protege to edit the OWL ontology and ROBOT for automating generation of many terms and logical definitions in parallel
 
** Will try to align WPO to UPheno as best as we can; will depend (at least in part) heavily on alignment with Uberon for anatomy
 
** Some Uberon alignment challenges: e.g. Fruit fly "tibia" and human "tibia"; human "tibia" parent is "bone" but fly "tibia" is not a bone
 
** Will participate in Phenotype Ontology Developer's call, every 2 weeks on Tuesdays (9am Pacific, 12pm East coast, 5pm UK)
 
*** Next meeting September 4, 2018
 
** Crash course in Protege, ROBOT, Ontology Development Kit, using GitHub to help develop OWL ontologies
 
** PATO needs work
 
** Questions that arose:
 
*** What should the scope of an ontology term be? Context? Life stage? Conditions? Treatment?
 
*** Being weary of ontology term count explosion; what's the right balance?
 
*** When defining phenotype terms, should the cause be included or only the observation? Maybe causes as a subclass (and assuming the observation includes assessment of cause)
 
** Some distinction between human phenotype terms and model organism terms: phenotype of individual vs. population
 
* Xenbase is trying to develop a phenotype ontology (spoke with Troy Pell, developer)
 
** Asked about WPO and how we curate
 
* Lots of plant talks
 
* Many talks on performing quality checks on ontology development and ontology re-use
 
* Domain Informational Vocabulary Extraction (DIVE) tool
 
** Entity recognition/extraction
 
** Working with two plant journals
 
** Tries to identify co-occurrence patterns of words
 
** Web interface and curation tool
 
* Semantic similarity tools and evaluation of them
 
  
=== WormBase Phenotype Ontology working group ===
+
[[WormBase-Caltech_Weekly_Calls_September_2019|September]]
* Chris will send around Doodle poll
 
* Goal is to discuss creation of logical definitions and alignment of phenotypes for Alliance
 
  
  
== August 23, 2018 ==
+
== October 3, 2019 ==
  
=== Alliance tables ===
+
=== SObA comparison graphs ===
* Filtering/sorting priorities
+
* Raymond and Juancarlos have worked on a SObA-graph based comparison tool to compare two genes for ontology-based annotations
* Open question about which tables on the Alliance website should be prioritized for acquiring sorting and filtering functionality
+
* [http://wobr2.caltech.edu/~azurebrd/cgi-bin/soba_multi.cgi?action=Gene+Pair+to+SObA+Graph Prototype 1]
 +
** [http://wobr2.caltech.edu/~azurebrd/cgi-bin/soba_multi.cgi?action=annotSummaryCytoscape&filterForLcaFlag=1&filterLongestFlag=1&showControlsFlag=0&datatype=phenotype&geneOneValue=lin-3%20(Caenorhabditis%20elegans,%20WB:WBGene00002992,%20-,%20F36H1.4)&autocompleteValue=let-23%20(Caenorhabditis%20elegans,%20WB:WBGene00002299,%20-,%20ZK1067.1 Example comparison between lin-3 and let-23]
 +
* [http://wobr1.caltech.edu/~azurebrd/cgi-bin/soba_multi.cgi?action=Gene+Pair+to+SObA+Graph Prototype 2]
 +
** [http://wobr1.caltech.edu/~azurebrd/cgi-bin/soba_multi.cgi?action=annotSummaryCytoscape&filterForLcaFlag=1&filterLongestFlag=1&showControlsFlag=0&datatype=phenotype&geneOneValue=lin-3%20(Caenorhabditis%20elegans,%20WB:WBGene00002992,%20-,%20F36H1.4)&autocompleteValue=let-23%20(Caenorhabditis%20elegans,%20WB:WBGene00002299,%20-,%20ZK1067.1) Example comparison between lin-3 and let-23]
 +
* What information does a user most care about?
 +
# What terms (nodes) are annotated to gene 1 and what terms to gene 2
 +
# For a given term, what is the relative number of annotations between gene 1 and gene 2.
 +
# For a given node, what is the relative number of annotations each gene has to the total annotations of that gene.
 +
* # 3 is actually what we applied to size the nodes in the single-gene version of SObA. Thus, not surprisingly, I think it is important.
 +
* Generally people like Prototype 2 as a default view; we could possibly have a toggle to see the other view
 +
* In either case users need a good legend and/or documentation
 +
* Jae, it would be good if a user could specifically highlight nodes specific to each gene and gray-out or de-emphasize the common nodes
  
=== Worm Phenotype Ontology working group ===
+
=== Germ line discussion ===
* Gary S., Karen, Kimberly, and Chris have responded to [https://doodle.com/poll/xzkxet8sb57enver#table Doodle poll]
+
* Currently, the anatomy ontology has "germ line" as a type of "Cell" and a type of "Tissue", and "germ cell" as a type of "germ line"
* Looks like 12pm Pacific (3pm Eastern) on Thursdays is the time that works for everyone
+
* Chris would like to (1) remove "germ line" from under "Cell" and leave it under "Tissue" and (2) move "germ cell" out from under "germ line" and place directly under "Cell"
** May start late on days when WB CIT meeting goes past 12pm Pacific
+
** [https://github.com/obophenotype/c-elegans-gross-anatomy-ontology/pull/23 Made pull request]
** May want to start a bit past 12pm to allow west coasters to get lunch, etc.?
+
* Chris will update pull request to include a change to move "germline precursor cell" out from under "germ line" and place it under "Cell" (done)
* Goals:
 
** Work on logical definitions for WPO terms
 
** Consider any restructuring of WPO that would facilitate ontology alignment with other MODs and UPheno
 
** Could we eventually create a phenotype annotation tool (and term requester) that allows modular expressions of a phenotype observation to lookup existing terms or create new terms with logical definitions based on those modular elements?
 
  
=== Alliance anatomy ===
+
=== Script to remove blank entries from Postgres ===
* Data quartermasters and expression working group are looking to get updated anatomy-Uberon mappings
+
* Chris stumbled across several entries in the OA that were blank (empty strings) or consisted of only whitespace, some of which were causing errors upon upload to ACEDB
* How frequent are data updates at the Alliance? Seems to be every ~2 months
+
* Juancarlos has written a script to look for all such entries; 66 tables have them on sandbox (likely same on live OA)
* Anatomy-Uberon mappings will affect phenotype ontology alignments
+
* Does anyone object to removing these entries throughout Postgres?
 +
* Juancarlos will remove all the empty fields identified by his script
  
=== Automated Gene Descriptions ===
 
*Ranjana and Valerio working to finish the new pipeline for automated descriptions for WB, will aim to finish them for the next upload, WS268.
 
* Working on one of the last data types--tissue expression; will use the anatomy ontology to perform logical trimming for the annotation set of cell/anatomy types (for each gene) including neurons (as opposed to using a file for neuronal term groupings taken from Oliver Hobert paper in the old pipeline)
 
* Currently playing around with thresholds to see how the sentences look, will feedback any ontology related issues to Raymond
 
* Working on incorporating feedback from users for information-poor genes (defined as genes with no human orthology and no GO annotations). Will include other types of information suggested by Users such as human ortholog function and protein domains, etc.
 
* When no other data is available, will include expression cluster data.  Users have complained that they don't find this data useful as it's non-specific and from large scale studies, so will give it the lowest priority for inclusion.
 
*Suggestion to exclude the writing and storing of the thousands of automated descriptions to the Postgres database; there is really no advantage in them being in Postgres. 
 
* At the time of generation of the automated descriptions the related .ace files can also be generated; though will need to include the 6000+ manual descriptions that live in Postgres.  So will need to rethink this part a bit, though skipping Postgres will reduce the number of manual steps in the pipleline and Postgres will have less data that needs to be uploaded and downloaded from future cloud storage.
 
  
== August 30, 2018 ==
+
== October 10, 2019 ==
  
=== EPIC dataset in the Alliance import ===
+
=== Biocuration 2020 ===
 +
* Held in Bar Harbor, Maine (organized by JAX, including MGI's Sue Bello and Cindy Smith)
 +
* Dates: Sunday May 17th to Wednesday May 20th, 2020
 +
* Will have 3rd POTATO workshop
 +
* [https://www.jax.org/education-and-learning/education-calendar/2020/05-may/biocuration-2020-conference Meeting website]
 +
* Key Dates
 +
** October 31, 2019 - Paper Submission Deadline
 +
** January 24, 2020 - Abstract  and Workshop Submission Deadline
 +
** March 6, 2020 - Notification of Acceptance
 +
** April 6, 2020 - Early Bird Registration Ends
 +
** May 8, 2020 - Registration Deadline
 +
* Academic ISB Member, early bird registration fee is $250
 +
* Author First Pass form paper, submitting to Database, biocuration issue (managed by biocuration group); authors have an opportunity to present at Biocuration conference
  
* the EPIC dataset has fine-grained anatomy-life stage annotations (e.g. single cell per minute)
+
=== ICBO 2020 ===
* This generates thousands of annotations per gene (up to 30,000) for the 127 genes analyzed in the study
+
* International Conference on Biomedical Ontologies
* How to deal with this. In WB we do not display anatomy/life stage pairings but we display one list for anatomy terms and one for life stage. Also, we display the EPIC study in a separate panel on the gene page so that it does not ‘dilute’ small scale annotations (concerned raised by Oliver H at the time of the import).
+
* [https://icbo2020.inf.unibz.it/ Meeting website]
 +
* Held in Bozen-Bolzano, Italy
 +
* 16 - 19 September 2020
  
https://www.wormbase.org/species/c_elegans/gene/WBGene00015143#1--10
+
=== SObA comparison tool ===
 +
* [http://wobr2.caltech.edu/~azurebrd/cgi-bin/soba_multi.cgi?action=Gene+Pair+to+SObA+Graph Prototype #1] updated
  
*Possible solution:
+
=== Textpresso derived paper connections ===
** 1. throw away the pairing information. e.g. for WBGene00020093, there are paired 10713 annotations from expression pattern Expr10421. On WormBase, we have a panel for Expr10421 (on the page for WBGene00020093) that shows 413 life-stage associations and 112 anatomy associations, with no pairing information. 
+
* For example for strains and constructs, maybe anatomy terms?
***This approach will still give big tables (annotation in the hundreds) for the analyzed genes and the dilution problem will still be there. On the other hand, when the Alliance tables could be sorted/filtered this can be less of an issue
+
* May want to flag Textpresso predictions (as opposed to manually connected)
*** This can be implemented for 2.1 as changing the code for 2.0 is fairly involved -upload tomorrow
+
* Couple of options:
** 2. assign a high-level life stage term (embryo) to the EPIC expression patterns for the alliance import so they will be discoverable on the Alliance website and will be hyperlinked to the WormBase detailed records
+
** 1) At time of build, populate the papers (in ACEDB/Datomic) into a 'Putative_reference' tag and display in a distinct 'Putative references' widget
 +
** 2) Not part of database build, but make associations live (using RESTful API to link out to Textpresso and submit search with URL) using Textpresso with links to Textpresso and Textpresso results, giving users chance to see context of matches in sentences at the Textpresso site
 +
*** A link to Textpresso could be done regardless of other approaches; low-hanging fruit?
 +
*** Do a diff so that Textpresso pulls up only additional papers (not already associated)?
 +
** 3) Could populate WB page with connections made through a Textpresso API call (could cache results? maybe, but might as well choose 1st option?)
 +
* Transgene pipeline:
 +
** Arun wrote script, matching transgene names (using regex; Is and Si transgenes) to papers, automatically populate OA
 +
** Another script, captures Ex transgenes as well, automatically connects to construct objects
 +
** WB only displays verified papers; unverified (predicted) associations are not dumped
 +
* Could integrate author verification as part of AFP pipeline, even for older papers? Would we want to re-request AFP results for authors that have already replied in the past? Probably not
 +
* Could embed AFP predictions in WB display with link to AFP form for authors (and others?) to verify, via logged-in users? Or via a validation token sent via email?
 +
* Chris will make GitHub ticket to ask WB web team to add a link to Textpresso search from References widget on respective page; will require a Textpresso URL constructor
 +
* Can apply to: genes, transgenes, constructs, strains, alleles, AFP-vetted entities

Revision as of 15:06, 11 October 2019

Previous Years

2009 Meetings

2011 Meetings

2012 Meetings

2013 Meetings

2014 Meetings

2015 Meetings

2016 Meetings

2017 Meetings

2018 Meetings


GoToMeeting link: https://www.gotomeet.me/wormbase1


2019 Meetings

January

February

March

April

May

June

July

August

September


October 3, 2019

SObA comparison graphs

  1. What terms (nodes) are annotated to gene 1 and what terms to gene 2
  2. For a given term, what is the relative number of annotations between gene 1 and gene 2.
  3. For a given node, what is the relative number of annotations each gene has to the total annotations of that gene.
  • # 3 is actually what we applied to size the nodes in the single-gene version of SObA. Thus, not surprisingly, I think it is important.
  • Generally people like Prototype 2 as a default view; we could possibly have a toggle to see the other view
  • In either case users need a good legend and/or documentation
  • Jae, it would be good if a user could specifically highlight nodes specific to each gene and gray-out or de-emphasize the common nodes

Germ line discussion

  • Currently, the anatomy ontology has "germ line" as a type of "Cell" and a type of "Tissue", and "germ cell" as a type of "germ line"
  • Chris would like to (1) remove "germ line" from under "Cell" and leave it under "Tissue" and (2) move "germ cell" out from under "germ line" and place directly under "Cell"
  • Chris will update pull request to include a change to move "germline precursor cell" out from under "germ line" and place it under "Cell" (done)

Script to remove blank entries from Postgres

  • Chris stumbled across several entries in the OA that were blank (empty strings) or consisted of only whitespace, some of which were causing errors upon upload to ACEDB
  • Juancarlos has written a script to look for all such entries; 66 tables have them on sandbox (likely same on live OA)
  • Does anyone object to removing these entries throughout Postgres?
  • Juancarlos will remove all the empty fields identified by his script


October 10, 2019

Biocuration 2020

  • Held in Bar Harbor, Maine (organized by JAX, including MGI's Sue Bello and Cindy Smith)
  • Dates: Sunday May 17th to Wednesday May 20th, 2020
  • Will have 3rd POTATO workshop
  • Meeting website
  • Key Dates
    • October 31, 2019 - Paper Submission Deadline
    • January 24, 2020 - Abstract and Workshop Submission Deadline
    • March 6, 2020 - Notification of Acceptance
    • April 6, 2020 - Early Bird Registration Ends
    • May 8, 2020 - Registration Deadline
  • Academic ISB Member, early bird registration fee is $250
  • Author First Pass form paper, submitting to Database, biocuration issue (managed by biocuration group); authors have an opportunity to present at Biocuration conference

ICBO 2020

  • International Conference on Biomedical Ontologies
  • Meeting website
  • Held in Bozen-Bolzano, Italy
  • 16 - 19 September 2020

SObA comparison tool

Textpresso derived paper connections

  • For example for strains and constructs, maybe anatomy terms?
  • May want to flag Textpresso predictions (as opposed to manually connected)
  • Couple of options:
    • 1) At time of build, populate the papers (in ACEDB/Datomic) into a 'Putative_reference' tag and display in a distinct 'Putative references' widget
    • 2) Not part of database build, but make associations live (using RESTful API to link out to Textpresso and submit search with URL) using Textpresso with links to Textpresso and Textpresso results, giving users chance to see context of matches in sentences at the Textpresso site
      • A link to Textpresso could be done regardless of other approaches; low-hanging fruit?
      • Do a diff so that Textpresso pulls up only additional papers (not already associated)?
    • 3) Could populate WB page with connections made through a Textpresso API call (could cache results? maybe, but might as well choose 1st option?)
  • Transgene pipeline:
    • Arun wrote script, matching transgene names (using regex; Is and Si transgenes) to papers, automatically populate OA
    • Another script, captures Ex transgenes as well, automatically connects to construct objects
    • WB only displays verified papers; unverified (predicted) associations are not dumped
  • Could integrate author verification as part of AFP pipeline, even for older papers? Would we want to re-request AFP results for authors that have already replied in the past? Probably not
  • Could embed AFP predictions in WB display with link to AFP form for authors (and others?) to verify, via logged-in users? Or via a validation token sent via email?
  • Chris will make GitHub ticket to ask WB web team to add a link to Textpresso search from References widget on respective page; will require a Textpresso URL constructor
  • Can apply to: genes, transgenes, constructs, strains, alleles, AFP-vetted entities