Difference between revisions of "WormBase-Caltech Weekly Calls"

From WormBaseWiki
Jump to navigationJump to search
 
(102 intermediate revisions by 5 users not shown)
Line 40: Line 40:
 
[[WormBase-Caltech_Weekly_Calls_July_2020|July]]
 
[[WormBase-Caltech_Weekly_Calls_July_2020|July]]
  
 +
[[WormBase-Caltech_Weekly_Calls_August_2020|August]]
  
==July 9th, 2020==
+
[[WormBase-Caltech_Weekly_Calls_September_2020|September]]
===Gene names issue in SimpleMine and other mining tools===
 
*Wen: Last week, Jonathan Ewbank raised the issue of gene names that may refer to multiple objects.
 
*this can be an issue for multiple data mining tools including WormMine, BioMart, and Gene Set Enrichment.
 
*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).
 
*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===
+
== October 1, 2020 ==
*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===
+
=== Gene association file formats on FTP ===
*Caltech summer student will try using Noctua initially for dauer (neuronal signaling) pathways
+
* 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 [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
  
===Nightly names service updates to postgres===
+
=== Phenotype association file idiosyncrasy ===
*Nightly using Matt's wb-names-export.jar to get full output of genes from datomic/names service, and updating postgres based on that.
+
* 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.
  
==July 16th, 2020==
 
===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.
 
* Chris worked with Nico yesterday to update the ODK version for WBbt and WBls; versioning should be fine now (once the OBO dashboard runs again (hasn't run since February))
 
* Important point: the GitHub release version date tag (e.g. "v2020-06-30") needs to match the ODK release date (as stored in the OBO and OWL file headers)
 
** There are some existing mismatches, Chris is cataloging them now
 
  
=== Gene Name Sanitizer ===
+
== October 8, 2020 ==
* Would be good to always (when possible) make users aware of name ambiguities
 
* Wen will keep the "Multiple Output" section at the bottom of SimpleMine output
 
* The gene name sanitizer will be built as a stand alone tool
 
* Important to include history of gene names
 
  
=== Tools linking to SimpleMine ===
+
=== Webinar Announcement ===
* 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
+
* 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
  
== July 23rd, 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)
  
=== Alliance pathway working group ===
+
== October 15, 2020 ==
* Integrating pathways from GO-CAM, Reactome, Meta-cyc
 
* Raymond, Chris interested
 
* Laurent-Philippe wants to work on user-friendly displays of GO-CAM models
 
  
=== Working on Alliance paralogs ===
+
=== BioGRID data sharing ===
* In the works
+
* 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
  
=== Summer project ===
+
=== Enriched genes ===
* Neuronal regulation of dauer formation
+
* 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)
* Fernando has been collecting literature
+
* We should reconsider the ?Expression_cluster model to make sure we can appropriately model and communicate enrichment or subtypes thereof
* Will work on GO-CAMs and build a relevant model(s)
 
  
=== Disk failures ===
 
* Brought down wobr1, wobr2, spica
 
* Raymond has upgraded OS from 8-year old OS, beefed up hardware
 
* wobr1 and wobr2 are back to full function
 
* Having trouble bringing back spica on the network
 
  
=== WormMine updates ===
+
== October 22, 2020 ==
* Paulo working on importing new classes: SO_term, disease_model_annotation, transgene, construct, molecule, wbprocess, interaction
 
* Chris is working with Paulo to move them in; talk to Paulo and/or Chris if interested in discussing
 
* Spreadsheet to map ACEDB/XML attributes to ACEDB attributes: https://docs.google.com/spreadsheets/d/1-fpzVU3rblN3Rp38wQjd3121z3rVkxmR9_i5T0EIPNo/edit?usp=sharing
 
* Still have some loader headaches
 
* Do we know the usage stats of WormMine?
 
* BlueGenes
 
** New interface coming; in the works, not sure when it will be fully functional
 
** Lacks some useful features in the current Intermine (Intermine devs are aware and working on it)
 
** Does BlueGenes have better loading? Don't know
 
  
=== WB move to Chen building ===
+
=== CHEBI ===
* Need to sort out what will get moved over; will be more limited space
+
* Karen spoke to CHEBI personnel on Tuesday
* How late can move happen? If all is OK, move will happen 2nd week of January 2021
+
* 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
  
=== Caltech BBE retreat ===
+
=== Training Webinar ===
* Will be online; may be more accessible
+
* Scheduled for tomorrow at 1pm Pacific/4pm Eastern
* Wen will submit a request to present on the Alliance
 
 
 
=== WormBase Webinars ===
 
* Could run a WormMine webinar in September
 
** 30-45 minute webinar with 15 minutes of questions and discussion
 
** Would be good have people register
 
* Chris has slot at Worcester Area Worm Meeting and Boston Area Worm Meeting coming up (late in 2020); these will likely be virtual
 
 
 
=== Gene Name Sanitizer ===
 
* Juancarlos and Wen are working on tool prototype
 
* Prototype recognizes ambiguous gene names/IDs and returns them to the user
 
* Will return HTML or single download file with a status/classification column
 
* Four types:
 
** good/valid (unambiguous match to a live gene)
 
** ambiguous (matches multiple genes)
 
** invalid (unambiguous match to dead or suppressed gene)
 
** not found (no match)
 
 
 
 
 
== July 30, 2020 ==
 
 
 
=== Gene Name Sanitizer ===
 
 
 
=== Help Desk ===
 
 
 
* https://github.com/WormBase/website/issues/7803
 
* Hi, I was wondering if there is a way to search for maternally versus zygotically enriched splice variants of a gene. I was looking through the RNAseq data and am not sure how to pull that out. I'm specifically looking at afd-1, but any help on that would be great!
 
* Ask Gary Williams
 
 
 
=== Summer project ===
 
* Fernando has made curation progress on neural control of dauer development (couple papers)
 
* Acquiring list of papers is important: Bargmann, Horvitz ablation paper; start at beginning
 
* Ablation, mosaic analysis
 

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