Difference between revisions of "WormBase-Caltech Weekly Calls"

From WormBaseWiki
Jump to navigationJump to search
 
(200 intermediate revisions by 11 users not shown)
Line 23: Line 23:
 
[[WormBase-Caltech_Weekly_Calls_2020|2020 Meetings]]
 
[[WormBase-Caltech_Weekly_Calls_2020|2020 Meetings]]
  
= 2021 Meetings =
+
[[WormBase-Caltech_Weekly_Calls_2021|2021 Meetings]]
  
[[WormBase-Caltech_Weekly_Calls_January_2021|January]]
+
= 2022 Meetings =
  
[[WormBase-Caltech_Weekly_Calls_February_2021|February]]
+
[[WormBase-Caltech_Weekly_Calls_January_2022|January]]
  
[[WormBase-Caltech_Weekly_Calls_March_2021|March]]
+
[[WormBase-Caltech_Weekly_Calls_February_2022|February]]
  
[[WormBase-Caltech_Weekly_Calls_April_2021|April]]
+
[[WormBase-Caltech_Weekly_Calls_March_2022|March]]
  
 +
[[WormBase-Caltech_Weekly_Calls_April_2022|April]]
  
== May 13, 2021 ==
+
[[WormBase-Caltech_Weekly_Calls_May_2022|May]]
  
=== Textpresso supplement ===
 
* Due Monday
 
* Michael working with Paul S
 
  
=== AWS credits ===
+
= Aug 25th, 2022=  
* Michael and Valerio were awarded AWS credits, more than they can use
+
* Phosphoproteomic dataset
* Maybe they can be repurposed
+
* WB grant - the new and radically different format for a “Biomedical Knowledgebase (U24 - Clinical Trials Not Allowed)” application
* Valerio will play around with AWS to determine the best/cheapest configuration before migrating to the Alliance
+
*
 +
*
  
=== Automated gene descriptions ===
 
* Will the Alliance ever accommodate non-elegans worm species? Can we port over the computed/derived descriptions for non-elegans species to the Alliance?
 
* Maybe have clade-specific descriptions based on the popular model (worms based on C. elegans); may be provided in MOD portal page(s)
 
* May be the focus of an Alliance supplement
 
* We want a flexible pipeline that can be configured depending on availability of data (e.g. protein domains)
 
  
=== IWM 2021 WB Workshop ===
 
* Scheduled for June 22, 2021
 
* Session begins at 8:30am Pacific / 11:30am Eastern / 4:30pm UK
 
* Workshop runs for 90 minutes: 4 15-minute talks followed by 30 minute Q&A session
 
* Here is the submitted workshop schedule:
 
11:30 am (EDT) Magdalena Zarowiecki, EMBL-EBI, A whistle-stop tour of all the types of data you can find in WormBase
 
  
11:45 am (EDT) Chris Grove, California Institute of Technology, Researching transcriptional regulation using WormBase transcription factors, TF binding sites and the modENCODE data
 
  
12:00 pm (EDT) Ranjana Kishore, California Institute of Technology, Comparative genomics and disease research using Alliance of Genome Resources
 
  
12:15 pm (EDT) Daniela Raciti, California Institute of Technology, How can you contribute? Community curation and tools, and the author-first-pass (AFP) pipeline
+
= Aug 18th, 2022=
 +
* Raymond reporting on meeting with Scott Emmons and neural connectivity data
  
  12:30 pm (EDT) Chris Grove, California Institute of Technology, Open Discussion / Q & A
+
= Aug 11th, 2022 =
 +
 
 +
Secondary species information content.
 +
* Gone through and counted number of objects in different data classes for all species
 +
* https://docs.google.com/spreadsheets/d/1Q1FE7Miz0IJxultBtEq-VFoAcdz1UpxM3wfER4-qQGg/edit?usp=sharing
 +
* Pristionchus: Talk to Ralf Sommer and see if wee can take some of the pristionchus.org data into WB -> Ranjana; Decision: after more discussion, decided to hold off on this as the plan is to focus on C. elegans for the grant. Perhaps in the future, we can seek finding and collaboration with the Pritionchus community (such as Sommer lab, etc).
 +
 
 +
* Brainstorm on how wee can utilize other species data -> may be a separate grant
 +
* remanei (4 genome versions) and briggsae (3 genome versions) problem -> several versions of the genome. Same problem in parasite. Will need to address in the future. Want to have multiple sequence alignments so researchers can compare different versions.
 +
* Address c elegans version assemblies in the grant. LoS from authors?
 +
* Parasite has a new RNAseq analysis pipeline (not single cells yet)
 +
 
 +
= July 28th, 2022 =
 +
 
 +
Global Core Biodata Resource application
 +
https://docs.google.com/document/d/1juJ4mm1evay32lNt3OOsbKL36RY4_3cW/edit?usp=sharing&ouid=106019143058337411488&rtpof=true&sd=true
 +
 
 +
 
 +
 
 +
= July 14th, 2022 =
 +
== Reference and Person Evidence ==
 +
* We need to know how best to move forward with ?Reference and ?Person evidence in the context of data exchange between WB and the Alliance
 +
* Does A-team need to connect those WB Persons to be able to populate data in the Alliance curation db ? 
 +
** If so, can it wait until we have proper persons ?  
 +
** If not, when we have persons later will the data be reconnected to Person objects ?
 +
* Where does data come from, which we call Person_evidence ?  Some forms ?  Direct emails ?  Other sources ? 
 +
* For author curation/verification, what evidence do we want to use?
 +
* Can we create Paper objects for the actual emails or other forms of communication (figure out details of when and what requirements), but keep Person_evidence for form submissions ?
 +
* How much will it muddy things to create Paper objects for emails, e.g. how will it affect NLP downstream, do we need PDFs ?
 +
* If we create personal communication References at Alliance only do we also want them as WBPapers, or will we just keep ?Person evidence at WB?
 +
* Are we okay with conflating Person data and Paper data in Reference at the Alliance.  That is, duplicating the same data as a Person and as a Reference.
 +
 
 +
== How to look up balancers (Df / Dp) in WB (PWS/Ryan Baugh) ==
 +
 
 +
= June 30, 2022 =
 +
 
 +
= June 23, 2022 =
 +
 
 +
Helpdesk tickets
 +
 
 +
SOba in Alliance
 +
 
 +
GCBR application due 8th Aug
 +
 
 +
Prepare for grant; nice pics for metrics eg https://pharos.nih.gov
 +
 
 +
Should Alliance gene & allele model have Clone/Sequence name as an attribute?
 +
 
 +
 
 +
= May 26, 2022 =
 +
 
 +
WormBase user survey
 +
 
 +
 
 +
 
 +
 
 +
= May 12, 2022 =
 +
 
 +
==Subcellular localization field==
 +
* WB has 2 separate free text fields to capture anatomical and subcellular localization statements but obviously the boundaries are fuzzy, see the example below where the statement belongs to both- there are many examples.
 +
“miR-228 is expressed in the germline and preferentially localizes to the nuclear periphery.”
 +
 
 +
* Other MODs do not make such distinction.
 +
* Daniela is asking the group advice to see if there is any objection in merging the 2 fields and slot the paragraph descriptions in the  ExpressionExperimentStatement in LinkML.
 +
 
 +
* Decision: Keep just one field that will take care of both anatomical expression and subcellular localization
 +
 
 +
<pre>
 +
ExpressionExperimentStatement:
 +
 
 +
    is_a: EntityStatement
 +
 
 +
    description: >-
 +
 
 +
      Free-text describing some aspect(s) of a gene's expression, particularly
 +
 
 +
      nuanced information that is not readily captured in annotations.
 +
 
 +
      This statement's scope is limited to the associated ExpressionExperiment.
 +
 
 +
    notes: >-
 +
 
 +
      Inherits: statement_subject, statement_type, statement_text, references.
 +
 
 +
    slot_usage:
 +
 
 +
      statement_subject:
 +
 
 +
        range: ExpressionExperiment
 +
</pre>

Latest revision as of 13:16, 24 August 2022

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

2022 Meetings

January

February

March

April

May


Aug 25th, 2022

  • Phosphoproteomic dataset
  • WB grant - the new and radically different format for a “Biomedical Knowledgebase (U24 - Clinical Trials Not Allowed)” application



Aug 18th, 2022

  • Raymond reporting on meeting with Scott Emmons and neural connectivity data

Aug 11th, 2022

Secondary species information content.

  • Gone through and counted number of objects in different data classes for all species
  • https://docs.google.com/spreadsheets/d/1Q1FE7Miz0IJxultBtEq-VFoAcdz1UpxM3wfER4-qQGg/edit?usp=sharing
  • Pristionchus: Talk to Ralf Sommer and see if wee can take some of the pristionchus.org data into WB -> Ranjana; Decision: after more discussion, decided to hold off on this as the plan is to focus on C. elegans for the grant. Perhaps in the future, we can seek finding and collaboration with the Pritionchus community (such as Sommer lab, etc).
  • Brainstorm on how wee can utilize other species data -> may be a separate grant
  • remanei (4 genome versions) and briggsae (3 genome versions) problem -> several versions of the genome. Same problem in parasite. Will need to address in the future. Want to have multiple sequence alignments so researchers can compare different versions.
  • Address c elegans version assemblies in the grant. LoS from authors?
  • Parasite has a new RNAseq analysis pipeline (not single cells yet)

July 28th, 2022

Global Core Biodata Resource application https://docs.google.com/document/d/1juJ4mm1evay32lNt3OOsbKL36RY4_3cW/edit?usp=sharing&ouid=106019143058337411488&rtpof=true&sd=true


July 14th, 2022

Reference and Person Evidence

  • We need to know how best to move forward with ?Reference and ?Person evidence in the context of data exchange between WB and the Alliance
  • Does A-team need to connect those WB Persons to be able to populate data in the Alliance curation db ?
    • If so, can it wait until we have proper persons ?
    • If not, when we have persons later will the data be reconnected to Person objects ?
  • Where does data come from, which we call Person_evidence ? Some forms ? Direct emails ? Other sources ?
  • For author curation/verification, what evidence do we want to use?
  • Can we create Paper objects for the actual emails or other forms of communication (figure out details of when and what requirements), but keep Person_evidence for form submissions ?
  • How much will it muddy things to create Paper objects for emails, e.g. how will it affect NLP downstream, do we need PDFs ?
  • If we create personal communication References at Alliance only do we also want them as WBPapers, or will we just keep ?Person evidence at WB?
  • Are we okay with conflating Person data and Paper data in Reference at the Alliance. That is, duplicating the same data as a Person and as a Reference.

How to look up balancers (Df / Dp) in WB (PWS/Ryan Baugh)

June 30, 2022

June 23, 2022

Helpdesk tickets

SOba in Alliance

GCBR application due 8th Aug

Prepare for grant; nice pics for metrics eg https://pharos.nih.gov

Should Alliance gene & allele model have Clone/Sequence name as an attribute?


May 26, 2022

WormBase user survey



May 12, 2022

Subcellular localization field

  • WB has 2 separate free text fields to capture anatomical and subcellular localization statements but obviously the boundaries are fuzzy, see the example below where the statement belongs to both- there are many examples.

“miR-228 is expressed in the germline and preferentially localizes to the nuclear periphery.”

  • Other MODs do not make such distinction.
  • Daniela is asking the group advice to see if there is any objection in merging the 2 fields and slot the paragraph descriptions in the ExpressionExperimentStatement in LinkML.
  • Decision: Keep just one field that will take care of both anatomical expression and subcellular localization
ExpressionExperimentStatement:

    is_a: EntityStatement

    description: >-

      Free-text describing some aspect(s) of a gene's expression, particularly

      nuanced information that is not readily captured in annotations.

      This statement's scope is limited to the associated ExpressionExperiment.

    notes: >-

      Inherits: statement_subject, statement_type, statement_text, references.

    slot_usage:

      statement_subject:

        range: ExpressionExperiment