Difference between revisions of "WormBase-Caltech Weekly Calls"

From WormBaseWiki
Jump to navigationJump to search
 
(267 intermediate revisions by 9 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]]
  
 +
= 2021 Meetings =
  
 +
[[WormBase-Caltech_Weekly_Calls_January_2021|January]]
  
= 2020 Meetings =
+
[[WormBase-Caltech_Weekly_Calls_February_2021|February]]
  
[[WormBase-Caltech_Weekly_Calls_January_2020|January]]
+
[[WormBase-Caltech_Weekly_Calls_March_2021|March]]
  
[[WormBase-Caltech_Weekly_Calls_February_2020|February]]
 
  
[[WormBase-Caltech_Weekly_Calls_March_2020|March]]
+
== April 1, 2021 ==
  
[[WormBase-Caltech_Weekly_Calls_April_2020|April]]
+
=== Antibodies ===
 +
* Alignment of the antibody class to Alliance:
 +
** Propose to move possible_pseudonym (192) and Other_animal (37) to remarks. Those tags are not currently used for curation.
 +
*** Other animal is sometimes used for older annotations, e.g. authors say that the antibodies were raised both  in rats and rabbits. Standard practice would create 2 records, one for the rat antibody and one for the rabbit.
 +
*** Possible pseudonym was used when  a curator was not able to unambiguously assign a previous antibody to a record. (we have a Other name -synonym- tag to capture unambiguous ones). When moving to remarks we can keep a controlled vocabulary for easy future parsing, e.g. “possible_pseudonym:”
 +
** Antigen field: currently separated into Protein, peptide, and other_antigen (e.g.: homogenate of early C.elegans embryos, sperm). Propose to use just one antigen field to capture antigen info.
  
[[WormBase-Caltech_Weekly_Calls_May_2020|May]]
+
All changes proposed above were approved by the group
  
[[WormBase-Caltech_Weekly_Calls_June_2020|June]]
+
=== textpress-dev clean up ===
 +
* Michael has asked curators to assess what they have on textpresso-dev as it will not be around forever :-(
 +
* is it okay to transfer data and files we want to keep to tazendra? and then to our own individual machines?
 +
* Direct access may be possible via Caltech VPN
 +
* Do we want to move content to AWS? May be complicated; it is still easy and cheap to maintain local file systems/machines
  
[[WormBase-Caltech_Weekly_Calls_July_2020|July]]
+
=== Braun servers ===
 +
* 3 servers stored in Braun server room; is there a new contact person for accessing these servers?
 +
* Mike Miranda replacement just getting settled; Paul will find out who is managing the server room and let Raymond know
  
[[WormBase-Caltech_Weekly_Calls_August_2020|August]]
+
=== Citace upload ===
 +
* Next Friday, April 9th, by end of the day
 +
* Wen will contact Paul Davis for the frozen WS280 models file
  
  
== September 3, 2020 ==
+
== April 8, 2021 ==
  
=== WS279 Citace upload ===
+
=== Braun server outage ===
* September 25
+
* Raymond fixed; now Spica, wobr and wobr2 are back up
* Local CIT upload (to Wen) Tuesday September 22 by 10am Pacific
 
  
=== New AFP datatype for curation status form (CSF)? ===
+
=== Textpresso API ===
* afp_othergenefunc (to capture gene function other than enzymatic activity)
+
* Was down yesterday affecting WormiCloud; Michael has fixed
* Can wait a bit before adding to CSF; if there will be dedicated curation for that data type we may add later
+
* Valerio will learn how to manage the API for the future
  
=== GO annotation for description ===
+
=== Grant opportunities ===
* Kimberly will look into 'male tail tip developement' terms for description
+
* Possibilities to apply for supplements
 +
* May 15th deadline
 +
* Druggable genome project
 +
** Pharos: https://pharos.nih.gov/
 +
** could we contribute?
 +
* Visualization, tools, etc.
 +
* Automated person descriptions?
 +
* Automated descriptions for proteins, ion channels, druggable targets, etc.?
  
=== Migrate wobr1 server to AWS ===
+
=== New WS280 ONTOLOGY FTP directory ===
* SOLR, WOBr, SObA, Enrichment analysis
+
* Changes requested here: https://github.com/WormBase/website/issues/7900
* Working with Sibyl on the process
+
* Here's the FTP URL: ftp://ftp.wormbase.org/pub/wormbase/releases/WS280/ONTOLOGY/
* Will try migrating wobr1 first, as a test case
+
* Known issues (Chris will report):
* May eventually move, for example, Tazendra
+
** Ontology files are provided as ".gaf" in addition to ".obo"; we need to remove the ".gaf" OBO files
** Will there be drawbacks to doing this?
+
** Some files are duplicated and/or have inappropriate file extensions
** Can we regularly ssh into Tazendra on AWS without issue? Costs for transferring large files
 
* Don't yet know the details of the costs, but we can try and keep track
 
* We should move into WB or Alliance AWS instances (or Stanford)
 
  
=== WormBase talk at Boston Area Worm Meeting ===
+
=== Odd characters in Postgres ===
* https://www.umassmed.edu/ambroslab/meetings/bawm/
+
* Daniela and Juancarlos discovered some errors with respect to special characters pasted into the OA
* Meeting will be virtual on Zoom
+
* Daniela would like to automatically pull in micropublication text (e.g. figure captions) into Postgres
* Chris will give a talk September 23rd, 6pm Eastern, 3pm Pacific (probably first speaker but not sure)
+
* We would need an automated way to convert special characters, like degree symbols ° into html unicode \&deg\;
* Send topic requests to Chris for the talk
+
* Juancarlos and Valerio will look into possibly switching from a Perl module to a Python module to handle special characters
* Current topics:
 
** Micropublications
 
** Author First Pass
 
** Automated Gene Descriptions
 
** Community Curation
 
** WB Query Tools
 
* Chris will ask organizers if others can join: post on WormBase blog? May draw too large an audience for the zoom channel;  
 
* If the organizers record the talk, we can post it on the blog and WB YouTube channel
 
  
  
== September 10, 2020 ==
+
== April 15, 2021 ==
  
=== GO GAF Files ===
+
=== Special characters in Postgres/OA ===
* WS278 GO GAF is using the new 2.2 file format  
+
* Juancarlos working on/proposing a plan to store UTF-8 characters in Postgres and the OA which would then get converted, at dumping, to HTML entities (e.g. α) for the ACE files
* [https://github.com/geneontology/geneontology.github.io/blob/issue-go-annotation-2917-gaf-2_2-doc/_docs/go-annotation-file-gaf-format-22.md Specifications]
+
* There is still a bit of cleanup needed to fix or remove special characters (not necessarily UTF-8) that apparently got munged upon copy/pasting into the OA in the past
* GO will not be emitting GAF 2.2 until the end of the year (will try to get a fixed date)
+
* Note: copy/paste from a PDF often works fine, but sometimes does not work as expected so manual intervention would be needed (e.g. entering Greek characters by hand in UTF-8 format)
* Implications for gene descriptions, but what about other tools, applications at WB?
+
* Would copy/pasting from HTML be better than PDF?
* Some errors in the current WS278 GAF, but will get fixed soon
+
* For Person curation it would be good to be able to faithfully store and display appropriate foreign characters (e.g. Chinese characters, Danish characters, etc.)
** Impacts gene descriptions for WS278, so using WS277 for now; will be OK once source GAF is fixed
+
* Mangolassi script called "get_summary_characters.pl" located here: /home/postgres/work/pgpopulation/grg_generegulation/20200618_summary_characters
 +
** Juancarlos will modify script to take a data type code as an argument on the command line and return all Postgres tables (and their respective PGIDs) that have special characters, e.g.
 +
*** $ ./get_summary_characters.pl exp
 +
*** $ ./get_summary_characters.pl int
 +
*** $ ./get_summary_characters.pl grg
 +
** or could pass just the datatype + field (postgres table). e.g.
 +
*** $ ./get_summary_characters.pl pic_description
 +
** Juancarlos will email everyone once it's ready.  It's ready, email sent.  Script is at /home/postgres/work/pgpopulation/oa_general/20210411_unicode_html/get_summary_characters.pl  Symlink this to your directory and run it from there, it will create files in the directory you are at when running it.
 +
* Action items:
 +
** Juancarlos will update the "get_summary_characters.pl" script as described above
 +
** Curators should use the "get_summary_characters.pl" to look for (potentially) bad characters in their OAs/Postgres tables
 +
** Need to perform bulk (automated) replacement of existing HTML entities into corresponding UTF-8 characters
 +
** Curators will need to work with Juancarlos for each OA to modify the dumper
 +
** Juancarlos will write (or append to existing) Postgres/OA dumping scripts to:
 +
*** 1) Convert UTF-8 characters to HTML entities in ACE files
 +
*** 2) Convert special quote and hyphen characters into simple versions that don't need special handling
  
===Disease files on FTP===
+
=== CeNGEN pictures ===
*No changes for WS278 FTP files, except an extra custom file that Hinxton is producing mostly for gene descriptions so that we don't get the wrong human diseases via poor orthology calls (see GitHub issue https://github.com/WormBase/website/issues/7839)
+
* Model change went in to accommodate images from the CeNGEN project
*Will be some consolidation of disease data possibly for WS279 FTP files, implications for downstream tools--gene descriptions, WOBR, ??
+
* Want gene page images for CeNGEN data; have the specifications for such images been worked out? Maybe not yet
 +
* Raymond and Daniela will work with data producers to acquire images when ready
  
=== WormBase talk at Worcester Area Worm Meeting ===
+
=== Supplement opportunities ===
* Chris set to give talk on December 1st, 2020, via Zoom, 4pm (or 4:30pm) EST / 1pm Pacific
+
* Money available for software development to "harden" existing software
* 30 minute slot; complementary to BAWM talk?
+
* Might be possible to make Eduardo's single cell analysis tools more sustainable
* WormBase members can attend
+
* Could make WormiCloud adapted to Alliance?
 +
* Put Noctua on more stable production footing? (GO cannot apply as they are in final year of existing grant)
  
=== WormBase talk at Boston Area Worm Meeting ===
+
=== Student project for Textpresso ===
* https://www.umassmed.edu/ambroslab/meetings/bawm/
+
* Create tool to allow user to submit text and return a list of similar papers
* Chris will give a talk September 23rd (< 2 weeks), 6pm Eastern, 3pm Pacific (probably first speaker but not sure)
+
* Use cases:
* WormBase members can attend; Zoom link will be sent next Monday
+
** curator wants an alert to find papers similar to what they've curated
 +
** look for potential reviewers of a paper based on similar text content
  
=== Worm Anatomy Ontology Fixes ===
 
* Raymond working on addressing warnings and errors (missing definitions, duplicate labels, duplicate definitions)
 
* Assessing the best way to address them
 
* Would be good to be able to automate some edits; options:
 
** Use OWL API (need someone proficient in coding with OWL API)
 
** Convert to OBO, programmatically edit, convert back to OWL?
 
** Use Cellfie plugin for Protege?
 
** Should discuss with Nico once we have a sense as to what changes need to be made
 
  
=== Dead Variations in Postgres ===
+
== April 22, 2021 ==
* Currently pulling in variations/alleles from Postgres to populate "allele" and "genetic perturbation" categories in Textpresso
 
* Noticed that many transgene names were being included, which can result in false positives for the categories
 
* Looking at Postgres table "obo_data_variation", there are ~100,000 entries, ~40,000 with status "Dead" and ~60,000 with status "Live"
 
* Trying to determine the history of the "Dead" variations, where most of the transgene names are coming from
 
* May still want to include "Dead" variations/alleles in Textpresso category for historical reasons
 
* We could use pattern matching to filter out transgene names
 
* Possible to search C. elegans corpus for all "real" allele public names in the "Dead" set to see if they should still be included in categories
 
  
=== WS279 Citace Upload ===
+
=== LinkML hackathon ===
* Local Caltech upload to Spica, Tuesday September 22, 10am Pacific
+
* Need to consider who works on what and how to coordinate
 +
* Need to practice good Git practice
 +
** Merge main branch into local branch before merging back into main branch to make sure everything works
 +
* How will we best handle AceDB hash structures? likely use something like Mark QT demonstrated
 +
** Do we have any/many hash-within-hash structures? #Molecular_change is used as a hash and tags within that model all reference the #Evidence hash
 +
* GO annotation extensions offer an interesting challenge
  
 +
=== IWM workshop ===
 +
* Need to submit a workshop schedule (who speaks about what and when) by next Thursday April 29th
 +
* An initial idea was to promote data in ACEDB that may be underutilized or many users may be unaware of
 +
** An example might be transcription factor data: the ?Transcription_factor class and the modENCODE TF data
 +
** Single cell data and tools? CeNGEN, Eduardo's single cell tools
 +
** RNA-Seq FPKM values for genes and related data; Wen will write script to pull out FPKM values from SRA data and send to Magdalena
 +
* In addition to WB data types, we will cover Alliance, AFP, and community curation
 +
* Google doc for workshop here: https://docs.google.com/document/d/1H9ARhBRMKBNuOhjyxVQ_1o6cysvpppI7uA-TJrO_UZ4/edit?usp=sharing
  
== September 17, 2020 ==
+
=== WB Progress Report ===
 +
* Due April 30th
 +
* There will be two documents: progress and plans
 +
* Place text in the appropriate places (don't write as a single integrated unit)
 +
* Paul S will put together a Google doc
 +
* We CAN include Alliance harmonization efforts
 +
* 2020 Progress report: https://docs.google.com/document/d/1f3ettnkvwoKKiaAA4TSrpSQPEF7FmVVn6u2UdflA_So/edit?usp=sharing
 +
* Last year milestone was WS276; we will compare to WS280
 +
* Google "WormBase Grants" folder: https://drive.google.com/drive/folders/1p8x9tEOfZ4DQvTcPSdNR5-JoPJu--ZAu?usp=sharing
 +
* 2021 Progress Report document here: https://docs.google.com/document/d/13E9k5JvDpUN4kWnrTm4M2iphnAJSTpk02ZiGl8O6bM4/edit?usp=sharing
  
=== Species errors in CITace ===
 
* Wen is reviewing species coming from CIT and will send individual curators lists of species that need correction
 
  
=== Webinars ===
+
== April 29, 2021 ==
* We could perform a general WormBase webinar to cover all of WormBase, maybe one hour long
 
* Allow 20-30 minutes for discussion? Can allow interruptions but plan for one hour
 
* Follow up with more specific webinars in following months: JBrowse, WormMine, Micropublication, AFP, Textpresso Central, Ontology browser & Enrichment tools, SPELL, ParaSite BioMart
 
* Chris and Wen can discuss how to setup
 
* Should we have people register? Maybe
 
* AFP probably doesn't need an hour; maybe split an hour across micropublications and AFP?
 
  
=== Transcription factors and regulatory networks ===
+
=== IWM Workshop Schedule ===
* Had another question about TFs, asking for common TFs for a list of genes
+
* Schedule format due today (April 29th)
* An issue is that the TF binding data we have is in disparate forms, trying to reconcile
+
* [https://docs.google.com/document/d/1H9ARhBRMKBNuOhjyxVQ_1o6cysvpppI7uA-TJrO_UZ4/edit#bookmark=id.jrjo4xhfnh7b Tentative schedule here]
* We have a ?Transcription_factor class; it would be good to update and integrate with other related data types
+
* Format proposal is 4, 15-minute talks followed by 30 minutes of open discussion / Q&A
 +
* Still need someone to speak (~15 minutes) about the Alliance
  
=== Alzheimer's disease portal ===
+
=== WB Progress Report ===
* Funding has been awarded for Alzheimer's research
+
* 2021 documents in [https://drive.google.com/drive/folders/1p8x9tEOfZ4DQvTcPSdNR5-JoPJu--ZAu?usp=sharing this Google Drive folder]
* Ranjana: should the disease working group consider more about an Alliance Alzheimer's disease portal?
+
* Note: there is one [https://docs.google.com/document/d/13E9k5JvDpUN4kWnrTm4M2iphnAJSTpk02ZiGl8O6bM4/edit?usp=sharing 2021 "Progress" document] and a second (separate) [https://docs.google.com/document/d/1j0HkCwuimK6DD-ui1tAkYMNpLRhxR9xb1FdSDZXFXCI/edit?usp=sharing "Future Plans" document]
* Paul S: Alliance SAB tomorrow; we'll see what the SAB says
+
* Existing future plans text has been moved to the "Future Plans" document
* Can look at other resources like RGD disease portals and Reactome disease-related pathway models
 
* Ruth Lovering is doing some work in this regard
 
  
=== GO meeting ===
+
=== OpenBiosystems RNAi clone IDs ===
* All are welcome to attend
+
* User looking to map Open Biosystems RNAi clone names to WB clone names
* Will discuss GAF format changes, etc.
+
* We may need to get a mapping file from Open Biosystems
* Ranjana: should she and Valerio attend to learn about GO changes that affect the gene descriptions pipeline?
 
** Kimberly: there could be a particular breakout group that Ranjana and Valerio could attend to discuss
 
  
=== New GAF 2.2 file ===
+
=== FPKM data ===
* Kimberly has reviewed and sent feedback to Michael P
+
* Wen has produced a csv file of FPKM values; can generate as part of the SPELL pipeline
* Valerio would like to stay in the loop to test the new files
+
* May be better to generate at Hinxton
  
=== Data mining tool comparison sheet ===
+
=== OA Dumpers ===
* https://docs.google.com/spreadsheets/d/1vBTDBOKfXn9GcdpF1bXI62VEJ7hwyz2hOyAZcoV1_ng/edit?usp=sharing
+
* Daniela and Juancarlos have been working on the Picture OA and Expr OA dumpers
* Needs an update
+
* Inconsistencies have accumulated for all OA dumpers as each has been made separately
* Could we make this available to users? A link in the Tools menu?
+
* Juancarlos is working on a generalized, modular way to handle dumping
* Is this useful to users? Would they understand it? Maybe be better as a curator resource
+
* Should we handle historical genes in the same way across OAs?  
* Could this be micropublished?
+
** Sure, but we need the "Historical_gene" tag in the respective ACEDB model
** Possible; may want to consider a series of publications with videos of webinars, etc.
+
** Decision: we will continue to only dump historical genes for specific OAs, with a plan to maybe make consistent across OAs in the future
 +
* Could we retroactively deal with paper-gene connections? We could possibly look in Postgres history tables to see which genes had been replaced previously (by Kimberly)
 +
 
 +
=== Gene name ambiguities ===
 +
* Jae noticed that some gene names associated with multiple WBGene IDs (e.g. one public name is the same as another gene's other name) have the same references attached
 +
* May require updating the paper-gene connections for some of these
 +
* One example is cep-1 gene. It associates with 3 diff WBgeneID and sharing papers in the reference widget.
 +
 
 +
=== NIH Supplement for AI readiness ===
 +
* Could we set up curation for neural circuits using a knowledge graph (e.g. GO-CAM)?
 +
** Maybe we could convert the anatomy function model to LinkML -> OWL statements?
 +
** Maybe setup a graphical curation interface?
 +
* Transcriptional regulation
 +
** Would be good to establish a common model (for the Alliance?)
 +
** CeNGEN project produced lots of predictions of TF binding sites based on single-cell expression data; Eduardo: these models should be able to be regenerated each time new data sets are published, but this requires greater integration in a central, sustainable resource
 +
* Paul S can send a link for the supplement
 +
 
 +
=== Variant First Pass Pipeline ===
 +
* Valerio: Are there any existing pipelines to make allele-paper and/or strain-paper associations?
 +
* Not sure, should ask Karen

Latest revision as of 19:13, 29 April 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

February

March


April 1, 2021

Antibodies

  • Alignment of the antibody class to Alliance:
    • Propose to move possible_pseudonym (192) and Other_animal (37) to remarks. Those tags are not currently used for curation.
      • Other animal is sometimes used for older annotations, e.g. authors say that the antibodies were raised both in rats and rabbits. Standard practice would create 2 records, one for the rat antibody and one for the rabbit.
      • Possible pseudonym was used when a curator was not able to unambiguously assign a previous antibody to a record. (we have a Other name -synonym- tag to capture unambiguous ones). When moving to remarks we can keep a controlled vocabulary for easy future parsing, e.g. “possible_pseudonym:”
    • Antigen field: currently separated into Protein, peptide, and other_antigen (e.g.: homogenate of early C.elegans embryos, sperm). Propose to use just one antigen field to capture antigen info.

All changes proposed above were approved by the group

textpress-dev clean up

  • Michael has asked curators to assess what they have on textpresso-dev as it will not be around forever :-(
  • is it okay to transfer data and files we want to keep to tazendra? and then to our own individual machines?
  • Direct access may be possible via Caltech VPN
  • Do we want to move content to AWS? May be complicated; it is still easy and cheap to maintain local file systems/machines

Braun servers

  • 3 servers stored in Braun server room; is there a new contact person for accessing these servers?
  • Mike Miranda replacement just getting settled; Paul will find out who is managing the server room and let Raymond know

Citace upload

  • Next Friday, April 9th, by end of the day
  • Wen will contact Paul Davis for the frozen WS280 models file


April 8, 2021

Braun server outage

  • Raymond fixed; now Spica, wobr and wobr2 are back up

Textpresso API

  • Was down yesterday affecting WormiCloud; Michael has fixed
  • Valerio will learn how to manage the API for the future

Grant opportunities

  • Possibilities to apply for supplements
  • May 15th deadline
  • Druggable genome project
  • Visualization, tools, etc.
  • Automated person descriptions?
  • Automated descriptions for proteins, ion channels, druggable targets, etc.?

New WS280 ONTOLOGY FTP directory

Odd characters in Postgres

  • Daniela and Juancarlos discovered some errors with respect to special characters pasted into the OA
  • Daniela would like to automatically pull in micropublication text (e.g. figure captions) into Postgres
  • We would need an automated way to convert special characters, like degree symbols ° into html unicode \&deg\;
  • Juancarlos and Valerio will look into possibly switching from a Perl module to a Python module to handle special characters


April 15, 2021

Special characters in Postgres/OA

  • Juancarlos working on/proposing a plan to store UTF-8 characters in Postgres and the OA which would then get converted, at dumping, to HTML entities (e.g. α) for the ACE files
  • There is still a bit of cleanup needed to fix or remove special characters (not necessarily UTF-8) that apparently got munged upon copy/pasting into the OA in the past
  • Note: copy/paste from a PDF often works fine, but sometimes does not work as expected so manual intervention would be needed (e.g. entering Greek characters by hand in UTF-8 format)
  • Would copy/pasting from HTML be better than PDF?
  • For Person curation it would be good to be able to faithfully store and display appropriate foreign characters (e.g. Chinese characters, Danish characters, etc.)
  • Mangolassi script called "get_summary_characters.pl" located here: /home/postgres/work/pgpopulation/grg_generegulation/20200618_summary_characters
    • Juancarlos will modify script to take a data type code as an argument on the command line and return all Postgres tables (and their respective PGIDs) that have special characters, e.g.
      • $ ./get_summary_characters.pl exp
      • $ ./get_summary_characters.pl int
      • $ ./get_summary_characters.pl grg
    • or could pass just the datatype + field (postgres table). e.g.
      • $ ./get_summary_characters.pl pic_description
    • Juancarlos will email everyone once it's ready. It's ready, email sent. Script is at /home/postgres/work/pgpopulation/oa_general/20210411_unicode_html/get_summary_characters.pl Symlink this to your directory and run it from there, it will create files in the directory you are at when running it.
  • Action items:
    • Juancarlos will update the "get_summary_characters.pl" script as described above
    • Curators should use the "get_summary_characters.pl" to look for (potentially) bad characters in their OAs/Postgres tables
    • Need to perform bulk (automated) replacement of existing HTML entities into corresponding UTF-8 characters
    • Curators will need to work with Juancarlos for each OA to modify the dumper
    • Juancarlos will write (or append to existing) Postgres/OA dumping scripts to:
      • 1) Convert UTF-8 characters to HTML entities in ACE files
      • 2) Convert special quote and hyphen characters into simple versions that don't need special handling

CeNGEN pictures

  • Model change went in to accommodate images from the CeNGEN project
  • Want gene page images for CeNGEN data; have the specifications for such images been worked out? Maybe not yet
  • Raymond and Daniela will work with data producers to acquire images when ready

Supplement opportunities

  • Money available for software development to "harden" existing software
  • Might be possible to make Eduardo's single cell analysis tools more sustainable
  • Could make WormiCloud adapted to Alliance?
  • Put Noctua on more stable production footing? (GO cannot apply as they are in final year of existing grant)

Student project for Textpresso

  • Create tool to allow user to submit text and return a list of similar papers
  • Use cases:
    • curator wants an alert to find papers similar to what they've curated
    • look for potential reviewers of a paper based on similar text content


April 22, 2021

LinkML hackathon

  • Need to consider who works on what and how to coordinate
  • Need to practice good Git practice
    • Merge main branch into local branch before merging back into main branch to make sure everything works
  • How will we best handle AceDB hash structures? likely use something like Mark QT demonstrated
    • Do we have any/many hash-within-hash structures? #Molecular_change is used as a hash and tags within that model all reference the #Evidence hash
  • GO annotation extensions offer an interesting challenge

IWM workshop

  • Need to submit a workshop schedule (who speaks about what and when) by next Thursday April 29th
  • An initial idea was to promote data in ACEDB that may be underutilized or many users may be unaware of
    • An example might be transcription factor data: the ?Transcription_factor class and the modENCODE TF data
    • Single cell data and tools? CeNGEN, Eduardo's single cell tools
    • RNA-Seq FPKM values for genes and related data; Wen will write script to pull out FPKM values from SRA data and send to Magdalena
  • In addition to WB data types, we will cover Alliance, AFP, and community curation
  • Google doc for workshop here: https://docs.google.com/document/d/1H9ARhBRMKBNuOhjyxVQ_1o6cysvpppI7uA-TJrO_UZ4/edit?usp=sharing

WB Progress Report


April 29, 2021

IWM Workshop Schedule

  • Schedule format due today (April 29th)
  • Tentative schedule here
  • Format proposal is 4, 15-minute talks followed by 30 minutes of open discussion / Q&A
  • Still need someone to speak (~15 minutes) about the Alliance

WB Progress Report

OpenBiosystems RNAi clone IDs

  • User looking to map Open Biosystems RNAi clone names to WB clone names
  • We may need to get a mapping file from Open Biosystems

FPKM data

  • Wen has produced a csv file of FPKM values; can generate as part of the SPELL pipeline
  • May be better to generate at Hinxton

OA Dumpers

  • Daniela and Juancarlos have been working on the Picture OA and Expr OA dumpers
  • Inconsistencies have accumulated for all OA dumpers as each has been made separately
  • Juancarlos is working on a generalized, modular way to handle dumping
  • Should we handle historical genes in the same way across OAs?
    • Sure, but we need the "Historical_gene" tag in the respective ACEDB model
    • Decision: we will continue to only dump historical genes for specific OAs, with a plan to maybe make consistent across OAs in the future
  • Could we retroactively deal with paper-gene connections? We could possibly look in Postgres history tables to see which genes had been replaced previously (by Kimberly)

Gene name ambiguities

  • Jae noticed that some gene names associated with multiple WBGene IDs (e.g. one public name is the same as another gene's other name) have the same references attached
  • May require updating the paper-gene connections for some of these
  • One example is cep-1 gene. It associates with 3 diff WBgeneID and sharing papers in the reference widget.

NIH Supplement for AI readiness

  • Could we set up curation for neural circuits using a knowledge graph (e.g. GO-CAM)?
    • Maybe we could convert the anatomy function model to LinkML -> OWL statements?
    • Maybe setup a graphical curation interface?
  • Transcriptional regulation
    • Would be good to establish a common model (for the Alliance?)
    • CeNGEN project produced lots of predictions of TF binding sites based on single-cell expression data; Eduardo: these models should be able to be regenerated each time new data sets are published, but this requires greater integration in a central, sustainable resource
  • Paul S can send a link for the supplement

Variant First Pass Pipeline

  • Valerio: Are there any existing pipelines to make allele-paper and/or strain-paper associations?
  • Not sure, should ask Karen