Difference between revisions of "WormBase-Caltech Weekly Calls"

From WormBaseWiki
Jump to navigationJump to search
 
(347 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
  
 +
=== Citace upload ===
 +
* Next Friday, April 9th, by end of the day
 +
* Wen will contact Paul Davis for the frozen WS280 models file
  
==July 9th, 2020==
 
===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
+
== April 8, 2021 ==
*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===
+
=== Braun server outage ===
*Please test and leave any feedback on the word cloud tool (Wormicloud), https://wormicloud.textpressolab.com/
+
* Raymond fixed; now Spica, wobr and wobr2 are back up
*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===
+
=== Textpresso API ===
*Caltech summer student will try using Noctua initially for dauer (neuronal signaling) pathways
+
* Was down yesterday affecting WormiCloud; Michael has fixed
 +
* Valerio will learn how to manage the API for the future
  
===Nightly names service updates to postgres===
+
=== Grant opportunities ===
*Nightly using Matt's wb-names-export.jar to get full output of genes from datomic/names service, and updating postgres based on that.
+
* 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.?
  
 +
=== New WS280 ONTOLOGY FTP directory ===
 +
* Changes requested here: https://github.com/WormBase/website/issues/7900
 +
* Here's the FTP URL: ftp://ftp.wormbase.org/pub/wormbase/releases/WS280/ONTOLOGY/
 +
* Known issues (Chris will report):
 +
** Ontology files are provided as ".gaf" in addition to ".obo"; we need to remove the ".gaf" OBO files
 +
** Some files are duplicated and/or have inappropriate file extensions
  
==July 16th, 2020==
+
=== Odd characters in Postgres ===
===Citing ontologies and their versions===
+
* Daniela and Juancarlos discovered some errors with respect to special characters pasted into the OA
*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.
+
* Daniela would like to automatically pull in micropublication text (e.g. figure captions) into Postgres
*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.
+
* We would need an automated way to convert special characters, like degree symbols ° into html unicode \&deg\;
*Some useful links
+
* Juancarlos and Valerio will look into possibly switching from a Perl module to a Python module to handle special characters
**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 ===
 
* 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 ===
+
== April 15, 2021 ==
* 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
 
  
 +
=== 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
  
== July 23rd, 2020 ==
+
=== 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
  
=== Alliance pathway working group ===
+
=== Supplement opportunities ===
* Integrating pathways from GO-CAM, Reactome, Meta-cyc
+
* Money available for software development to "harden" existing software
* Raymond, Chris interested
+
* Might be possible to make Eduardo's single cell analysis tools more sustainable
* Laurent-Philippe wants to work on user-friendly displays of GO-CAM models
+
* 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)
  
=== Working on Alliance paralogs ===
+
=== Student project for Textpresso ===
* In the works
+
* 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
  
=== Summer project ===
 
* Neuronal regulation of dauer formation
 
* Fernando has been collecting literature
 
* Will work on GO-CAMs and build a relevant model(s)
 
  
=== Disk failures ===
+
== April 22, 2021 ==
* 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 ===
+
=== LinkML hackathon ===
* Paulo working on importing new classes: SO_term, disease_model_annotation, transgene, construct, molecule, wbprocess, interaction
+
* Need to consider who works on what and how to coordinate
* Chris is working with Paulo to move them in; talk to Paulo and/or Chris if interested in discussing
+
* Need to practice good Git practice
* Spreadsheet to map ACEDB/XML attributes to ACEDB attributes: https://docs.google.com/spreadsheets/d/1-fpzVU3rblN3Rp38wQjd3121z3rVkxmR9_i5T0EIPNo/edit?usp=sharing
+
** Merge main branch into local branch before merging back into main branch to make sure everything works
* Still have some loader headaches
+
* How will we best handle AceDB hash structures? likely use something like Mark QT demonstrated
* Do we know the usage stats of WormMine?
+
** 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
* BlueGenes
+
* GO annotation extensions offer an interesting challenge
** 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 ===
+
=== IWM workshop ===
* Need to sort out what will get moved over; will be more limited space
+
* Need to submit a workshop schedule (who speaks about what and when) by next Thursday April 29th
* How late can move happen? If all is OK, move will happen 2nd week of January 2021
+
* 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
  
=== Caltech BBE retreat ===
+
=== WB Progress Report ===
* Will be online; may be more accessible
+
* Due April 30th
* Wen will submit a request to present on the Alliance
+
* 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
  
=== 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 ===
+
== April 29, 2021 ==
* 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)
 
  
 +
=== IWM Workshop Schedule ===
 +
* Schedule format due today (April 29th)
 +
* [https://docs.google.com/document/d/1H9ARhBRMKBNuOhjyxVQ_1o6cysvpppI7uA-TJrO_UZ4/edit#bookmark=id.jrjo4xhfnh7b 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
  
== July 30, 2020 ==
+
=== WB Progress Report ===
 +
* 2021 documents in [https://drive.google.com/drive/folders/1p8x9tEOfZ4DQvTcPSdNR5-JoPJu--ZAu?usp=sharing this Google Drive folder]
 +
* 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]
 +
* Existing future plans text has been moved to the "Future Plans" document
  
=== Gene Name Sanitizer ===
+
=== 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
  
=== Help Desk ===
+
=== 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
  
* https://github.com/WormBase/website/issues/7803
+
=== OA Dumpers ===
* 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!
+
* Daniela and Juancarlos have been working on the Picture OA and Expr OA dumpers
* Ask Gary Williams
+
* 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)
  
=== Summer project ===
+
=== Gene name ambiguities ===
* Fernando has made curation progress on neural control of dauer development (couple papers)
+
* 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
* Acquiring list of papers is important:
+
* May require updating the paper-gene connections for some of these
** Bargmann (1991) ablation paper; start at beginning
+
* One example is cep-1 gene. It associates with 3 diff WBgeneID and sharing papers in the reference widget.
** WormBook chapter (old but good)
+
 
** WormAtlas, check references
+
=== NIH Supplement for AI readiness ===
** Look at Nikhil Bhatla's worm web tools and references (wormweb.org)
+
* Could we set up curation for neural circuits using a knowledge graph (e.g. GO-CAM)?
* Ablation, mosaic analysis
+
** 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