Difference between revisions of "WormBase-Caltech Weekly Calls"

From WormBaseWiki
Jump to navigationJump to search
 
(187 intermediate revisions by 7 users not shown)
Line 22: Line 22:
  
  
GoToMeeting link: https://www.gotomeet.me/wormbase1
+
 
  
 
= 2020 Meetings =
 
= 2020 Meetings =
Line 34: Line 34:
 
[[WormBase-Caltech_Weekly_Calls_April_2020|April]]
 
[[WormBase-Caltech_Weekly_Calls_April_2020|April]]
  
 +
[[WormBase-Caltech_Weekly_Calls_May_2020|May]]
  
 +
[[WormBase-Caltech_Weekly_Calls_June_2020|June]]
  
== May 7, 2020 ==
+
[[WormBase-Caltech_Weekly_Calls_July_2020|July]]
 
 
=== Alliance COVID Page ===
 
* Available on stage
 
* Textpresso for Coronavirus up for testing
 
 
 
=== SimpleMine at Alliance ===
 
* Still some confusion about what it is
 
* Will try to help clarify on PI meeting on Friday
 
 
 
=== Development environment for Alliance work ===
 
* Raymond and Juancarlos have been working on
 
* Existing hardware is strained; set up virtual machine
 
* Still some technical issues
 
 
 
=== Open Publishing Festival ===
 
* Later this month
 
* Micropublications involved
 
* Organized by the Collaborative Knowledge Foundation
 
* Will involve publishers of books, journals, etc.
 
* Will have a MOD-focused event, would be good to have WB curators participate/attend
 
* Open to all
 
 
 
=== Genotype class ===
 
* Ranjana finished populating the Genotype OA with genotypes needed for disease curation
 
* Will need to keep in mind that we will have a mapping pipeline to determine which genes are involved for a variation
 
* There could end up being a discrepancy between an original or published name of a genotype and the components that are inferred by WormBase
 
* Would be good to be clear/transparent about which components were automatically inferred
 
 
 
=== WS277/278 ===
 
* Pipelines are pushed back by about 14 days/2 weeks
 
 
 
 
 
==May 13, 2020==
 
  
=== SURF students ===
+
[[WormBase-Caltech_Weekly_Calls_August_2020|August]]
* Welcome Fernando!
 
* Will work on neuron function with respect to dauer formation
 
  
=== Progress Report ===
+
[[WormBase-Caltech_Weekly_Calls_September_2020|September]]
* Review Google Doc from Paul to make sure you're latest updates are there
 
* Doc here: https://docs.google.com/document/d/1f3ettnkvwoKKiaAA4TSrpSQPEF7FmVVn6u2UdflA_So/edit?usp=sharing
 
  
===Genotype class===
 
*Have 27 genotypes in the genotype OA, dumper and test .ace file ready
 
*Will test ace file in citace as soon as we get the new models file, can also send to Paul D., in advance to test
 
*Disease OA annotations now converted to the newly created genotypes where needed
 
*Need to work on disease dumper changes next
 
  
=== What genes should be linked to genotypes? ===
+
== October 1, 2020 ==
* We have a "Gene" tag in the ?Genotype model for capturing relevant genes
 
* What should we consider a "relevant gene"?
 
* We plan to populate the "Gene" tag with genes identified by the variation-to-gene mapping pipeline
 
* For transgenes, what genes should be extracted as "relevant"? Genes whose promoters are cloned? Genes that are expressed? Genes whose 3'UTR's are cloned? Wild type rescue genes used as a marker/selection tool, e.g. "unc-119(+)"?
 
* For rearrangements, consider relevant any genes "inside" the rearrangement?
 
* For now, we will omit any genes from transgenes or rearrangements from being dumped into the "Gene" tag
 
* In the future, we may want to consider genes that have been specifically annotated as having some functional consequence and informs that the gene is of functional relevance to the genotype
 
  
=== Volunteer Community Curators ===
+
=== Gene association file formats on FTP ===
* Have had an additional 13 people volunteer
+
* For example, current production release ONTOLOGY directory: ftp://ftp.wormbase.org/pub/wormbase/releases/current-production-release/ONTOLOGY/
* Single one-on-one tutorial for someone in Hong Kong this past Monday
+
* Our association files have format "*.wb"; is this useful or necessary?
* Chris will hold a tutorial today and tomorrow for everyone else
+
* Other than referring to GAF in the header, it isn't clear to users what the columns refer to or what the column headers should be
* Have received many new community annotations from volunteers (and authors), validation still pending
+
* We could add a README file and/or convert to the new [https://github.com/geneontology/geneontology.github.io/blob/issue-go-annotation-2917-gaf-2_2-doc/_docs/go-annotation-file-gaf-format-22.md GAF 2.2 format] which would have a more expressive file header and possibly column headers(?)
 +
** File headers could possibly link to the format specification page
  
=== Open Publishing Festival ===
+
=== Phenotype association file idiosyncrasy ===
* Ranjana will join as a panelist
+
* As we've discussed previously, there is an oddity to how the phenotype association file we provide lists, or doesn't, references
* Other MOD curators will also join
+
* According to the GAF spec, column 6 is for reference and is required, whereas column 8 is "With (or) From" and is optional
* Festival calendar: https://openpublishingfest.org/calendar.html
+
* When we have a reference, the WBPaper ID is provided in column 6 and the WBVar ID or RNAi ID is provided in column 8
 +
* However, when we have no reference (personal communication, e.g. from NBP allele submissions), the WBVar ID is instead put in column 6 (because we need something there), and column 8 is blank.
 +
** This results in (1) column 6 having a mix of paper/reference IDs (good) and WBVar IDs (not good) and (2) WBVar IDs split between column 6 and 8; thus making it tedious to parse this file
 +
* Proposed solution: Can we come up with some type of reference object ID to associate to the personal communications (or any annotations currently lacking a formal reference)?
 +
* With the proposed solution, we can always have a reference ID in column 6 (the intended purpose of the column) and WBVar IDs for alleles can always remain consistently in column 8
 +
* Proposal is to put WBPerson IDs in column 6 for personal communications. Chris & Karen will check if this will work.
  
=== Move to Chen building ===
+
=== Server space in Chen Building ===
* Scheduled for late January 2021
+
* It looks like that we will not have a specific space for server computers.
  
=== First completely virtual GO meeting ===
 
* Kimberly: went really well
 
* Only met 4 hours per day, due to time zone differences
 
* Had breakout sessions for focus groups
 
  
=== Alliance Literature Acquisition working group ===
+
== October 8, 2020 ==
* Plan to come up with use cases for OntoMate and Textpresso
 
**Ontomate link https://rgd.mcw.edu/QueryBuilder/
 
  
* Kimberly plans to draw up most common use cases for Textpresso
+
=== Webinar Announcement ===
* Google doc for test cases: https://rgd.mcw.edu/QueryBuilder/getResult/?qFieldConditions%5B0%5D.fieldName=ontology&qFieldConditions%5B0%5D.fieldValue=Coronavirus%20infectious%20disease
+
* Here is the live registration site: http://tazendra.caltech.edu/~azurebrd/cgi-bin/forms/webinar.cgi
 +
* Caltech zoom allows 300 attendees.
  
 +
=== Descriptions from GO-CAM models ===
 +
* One suggestion for the Alliance is to create a description based on a GO-CAM model
 +
* Could also micropublish some descriptions (semi-automated?)
 +
* Can make curators authors of micropublications for GO-CAM models/pathways
  
== May 21, 2020 ==
+
=== Transcription Factors in WormBase ===
 +
* WormBase has a ?Transcription_factor class that is currently underutilized
 +
* Chris spoke with Gary Williams about the status as he has done much of the work on the class
 +
* Because transcription factors can often be complexes, it was decided to create the ?Transcription_factor class rather than simply an extension of tags to the existing ?Gene class
 +
* The class seems reasonably complete; it's important to note that some TFs are general transcription factors, not necessarily gene-specific or sequence-specific DNA-binding TFs; it will be good to make that distinction clear to users
 +
* Chris has compiled a [https://docs.google.com/spreadsheets/d/1KdmvybWDWHXdlJwZgfleL4xHDoyPoYR13WAUcERF82g/edit?usp=sharing Google sheet] to assess the class before Gary W. leaves WB in the next couple of weeks
 +
* The Google sheet has several tabs/worksheets, including one for the ACEDB data model (and notes about usage of tags), a summary table of associated genes, bound sequence features, existence of other protein-DNA binding data, etc.
 +
* It would be good to make TF binding info (per gene and globally) more accessibly to our users, maybe via a new widget on gene pages (e.g. list incoming, regulating TFs and, for TF genes themselves, list potential target genes)
  
=== Volunteer curators ===
+
== October 15, 2020 ==
* Received surge of annotations earlier this week
 
* All tutorials done for now; all but 3 recorded
 
* Each tutorial is ~1 hour in length
 
  
=== AFP tutorial ===
+
=== BioGRID data sharing ===
* AFP group working on tutorial/webinar
+
* Rose from BioGRID proposed that BioGRID curate high-throughput C. elegans interaction datasets, capturing confidence scores when available, and making those annotations available to WormBase for regular ingest
* Had someone on phenotype curation tutorial specifically asking about it (Kimberly responded)
+
* Will need to consider a few points:
 +
** BioGRID doesn't curate protein-DNA interactions
 +
** We don't yet know the turn-around timeline for BioGRID curation of worm datasets; WB may be able to curate them much sooner
 +
* Chris and Jae will work with Rose et al. to coordinate HTP curation
  
=== Open Publishing Festival ===
+
=== Enriched genes ===
* Had micropublication session yesterday, went well
+
* Some genes are considered "enriched" for an expression cluster data set even if the enrichment was in comparison to another cell or tissue (not whole animal)
* Had ~50 participants
+
* We should reconsider the ?Expression_cluster model to make sure we can appropriately model and communicate enrichment or subtypes thereof
* Saved Zoom chats? Can get public ones, maybe not private ones
 
  
  
== May 28, 2020 ==
+
== October 22, 2020 ==
  
=== Wormicloud ===
+
=== CHEBI ===
* Introducing a new tool for a graphical summary of queried papers, Please take a look and leave any comments on it. (http://textpressocentral.org:5010/)
+
* Karen spoke to CHEBI personnel on Tuesday
 +
* CHEBI only has ~2 curators to create new entities
 +
* CHEBI had submitted a proposal to establish pipelines to process requests from MODs
 +
* Chemical Translation Service (CTS)
 +
* OxO = https://www.ebi.ac.uk/spot/oxo/search
  
=== Genes to Physical Map ===
+
=== Training Webinar ===
* https://colab.research.google.com/drive/1e83jv94-eO_VQ7kKdJ36TgDDb4WRkFhM?usp=sharing
+
* Scheduled for tomorrow at 1pm Pacific/4pm Eastern
To run: Runtime->Run All. Change the list of gene names and run again.
 

Latest revision as of 18:40, 22 October 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

September


October 1, 2020

Gene association file formats on FTP

  • For example, current production release ONTOLOGY directory: ftp://ftp.wormbase.org/pub/wormbase/releases/current-production-release/ONTOLOGY/
  • Our association files have format "*.wb"; is this useful or necessary?
  • Other than referring to GAF in the header, it isn't clear to users what the columns refer to or what the column headers should be
  • We could add a README file and/or convert to the new GAF 2.2 format which would have a more expressive file header and possibly column headers(?)
    • File headers could possibly link to the format specification page

Phenotype association file idiosyncrasy

  • As we've discussed previously, there is an oddity to how the phenotype association file we provide lists, or doesn't, references
  • According to the GAF spec, column 6 is for reference and is required, whereas column 8 is "With (or) From" and is optional
  • When we have a reference, the WBPaper ID is provided in column 6 and the WBVar ID or RNAi ID is provided in column 8
  • However, when we have no reference (personal communication, e.g. from NBP allele submissions), the WBVar ID is instead put in column 6 (because we need something there), and column 8 is blank.
    • This results in (1) column 6 having a mix of paper/reference IDs (good) and WBVar IDs (not good) and (2) WBVar IDs split between column 6 and 8; thus making it tedious to parse this file
  • Proposed solution: Can we come up with some type of reference object ID to associate to the personal communications (or any annotations currently lacking a formal reference)?
  • With the proposed solution, we can always have a reference ID in column 6 (the intended purpose of the column) and WBVar IDs for alleles can always remain consistently in column 8
  • Proposal is to put WBPerson IDs in column 6 for personal communications. Chris & Karen will check if this will work.

Server space in Chen Building

  • It looks like that we will not have a specific space for server computers.


October 8, 2020

Webinar Announcement

Descriptions from GO-CAM models

  • One suggestion for the Alliance is to create a description based on a GO-CAM model
  • Could also micropublish some descriptions (semi-automated?)
  • Can make curators authors of micropublications for GO-CAM models/pathways

Transcription Factors in WormBase

  • WormBase has a ?Transcription_factor class that is currently underutilized
  • Chris spoke with Gary Williams about the status as he has done much of the work on the class
  • Because transcription factors can often be complexes, it was decided to create the ?Transcription_factor class rather than simply an extension of tags to the existing ?Gene class
  • The class seems reasonably complete; it's important to note that some TFs are general transcription factors, not necessarily gene-specific or sequence-specific DNA-binding TFs; it will be good to make that distinction clear to users
  • Chris has compiled a Google sheet to assess the class before Gary W. leaves WB in the next couple of weeks
  • The Google sheet has several tabs/worksheets, including one for the ACEDB data model (and notes about usage of tags), a summary table of associated genes, bound sequence features, existence of other protein-DNA binding data, etc.
  • It would be good to make TF binding info (per gene and globally) more accessibly to our users, maybe via a new widget on gene pages (e.g. list incoming, regulating TFs and, for TF genes themselves, list potential target genes)

October 15, 2020

BioGRID data sharing

  • Rose from BioGRID proposed that BioGRID curate high-throughput C. elegans interaction datasets, capturing confidence scores when available, and making those annotations available to WormBase for regular ingest
  • Will need to consider a few points:
    • BioGRID doesn't curate protein-DNA interactions
    • We don't yet know the turn-around timeline for BioGRID curation of worm datasets; WB may be able to curate them much sooner
  • Chris and Jae will work with Rose et al. to coordinate HTP curation

Enriched genes

  • Some genes are considered "enriched" for an expression cluster data set even if the enrichment was in comparison to another cell or tissue (not whole animal)
  • We should reconsider the ?Expression_cluster model to make sure we can appropriately model and communicate enrichment or subtypes thereof


October 22, 2020

CHEBI

  • Karen spoke to CHEBI personnel on Tuesday
  • CHEBI only has ~2 curators to create new entities
  • CHEBI had submitted a proposal to establish pipelines to process requests from MODs
  • Chemical Translation Service (CTS)
  • OxO = https://www.ebi.ac.uk/spot/oxo/search

Training Webinar

  • Scheduled for tomorrow at 1pm Pacific/4pm Eastern