Difference between revisions of "WormBase-Caltech Weekly Calls"

From WormBaseWiki
Jump to navigationJump to search
Line 1: Line 1:
==June 11, 2009==
+
= Previous Years =
*Discussion of allele-paper connections
 
**Jolene has a Textpresso-based pipeline for identifying alleles in papers
 
**Alleles get associated with a paper if there is phenotypic or molecular data
 
**List of all alleles associated with a paper could possibly be passed on to Sanger for subsequent connection
 
  
*Discussion of gene-paper connections
+
[[WormBase-Caltech_Weekly_Calls_2009|2009 Meetings]]
**What criteria should be used for associating genes with papers?
 
**Currently being associated manually by a curator during first-pass
 
**Could Textpresso be harnessed for this task?
 
**There are different evidences attached to gene-paper connections
 
**Genes associated with a paper via Textpresso searches could be presented to the first-pass curator for approval in the first-pass form
 
**Need to fix current abstract-gene associating script to include proteins (e.g. PIE-1)
 
  
*Incorporate a customized Textpresso query on WormBase object pages so users could look for additional info if they want
+
[[WormBase-Caltech_Weekly_Calls_2011|2011 Meetings]]
**Data type curator could help design a useful query
 
  
*Other gene-object connections
+
[[WormBase-Caltech_Weekly_Calls_2012|2012 Meetings]]
**Develop a canned query for all objects that should be associated with the gene page
 
  
*Worm Meeting
+
[[WormBase-Caltech_Weekly_Calls_2013|2013 Meetings]]
**Pre-meeting - meeting rooms?
 
**Pre-meeting - practice talks for WormBase workshop
 
**Storage for swag - pavillion should be okay
 
  
==June 18, 2009==
+
[[WormBase-Caltech_Weekly_Calls_2014|2014 Meetings]]
  
*Worm Meeting and Pre-Meeting
+
[[WormBase-Caltech_Weekly_Calls_2015|2015 Meetings]]
**WormBase Help Desk Schedule - set for worm meeting
 
**Wen may need help carrying boxes of swag
 
**Do any Sanger or WashU people need rides to UCLA?
 
**Mary Alvarez is working on finding rooms for the pre-meeting
 
**Be prepared to report on curation status of your data type and what we might need
 
  
*Author contact information on first-pass form
+
[[WormBase-Caltech_Weekly_Calls_2016|2016 Meetings]]
**email goes to the first email address found by Textpresso
 
**Raymond - we do care where this data comes from
 
**Erich - can we send it to the designated corresponding author
 
**first-pass curation could capture the corresponding author
 
**if the email didn't go to the corresponding author, it may affect our response rate
 
**two-stage approach proposal
 
***respond to Bernard - we'll try to find corresponding author in the future and add his name to the comments field for now
 
***going forward, how best to determine corresponding author?
 
***keep track of IP address from which the data was sent?
 
***add text to email saying that authors may include their contact information in the comments box, if they wish
 
***Raymond will proof-read papers to check on corresponding author designation and email addresses
 
  
*Zfin visit - PATO progress, worth looking at
+
[[WormBase-Caltech_Weekly_Calls_2017|2017 Meetings]]
**Erich noted no genome browser - what is the issue?
 
**Their experience with getting figures from journals might be helpful.
 
  
 +
[[WormBase-Caltech_Weekly_Calls_2018|2018 Meetings]]
  
==February 10, 2011==
+
[[WormBase-Caltech_Weekly_Calls_2019|2019 Meetings]]
  
*Should we have a Caltech project/site manager? We'll look at the issues to be solved first
 
  
*Todd would like to know more about what's going on at Caltech
 
**What would Todd like to know about? New ideas, data types?
 
**What can we communicate more effectively to Todd?
 
  
*Should we take minutes of Caltech WormBase group meetings and send around?
 
  
*Kimberly: helpful (for off site individuals) if we go around the room to talk about what each of us is working on
+
= 2020 Meetings =
  
*Bitbucket use
+
[[WormBase-Caltech_Weekly_Calls_January_2020|January]]
**How do we see only what pertains to us, individually?
 
**Paul: good way to document bugs and fixes, problems/solutions
 
**Bitbucket Wiki - does that capture what people want/need to see?
 
**Who should Todd follow? What would Todd like to know about?
 
**Raymond: used for code development/versioning by OICR; may be the best use for Bitbucket
 
**Should we develop best practices guideline for Bitbucket use?
 
***Avoid posting topics that are too specific or too vague?
 
***What do we want most to get out of Bitbucket?
 
**Curation efforts? No
 
  
*SAB Meeting
+
[[WormBase-Caltech_Weekly_Calls_February_2020|February]]
**Not much feedback for literature curators
 
**User interface stuff took precedence
 
**Paul: Testing, spot-checking website for errors
 
**Web issues, e-mails from Gary and Oliver
 
  
*WormBase-wide conference call twice per month
+
[[WormBase-Caltech_Weekly_Calls_March_2020|March]]
**First & third Thursday of the month
 
**Starting next Thursday (2-17) @ 8:30am PST
 
**Web redesign meetings on Thursdays will have to be every other week? Do both same day?
 
  
*Raymond: WormBase mirrors
+
[[WormBase-Caltech_Weekly_Calls_April_2020|April]]
**Do we want to implement the Genome Browser for the mirror(s)? If practical
 
**It seems as though Caltech mirror has been crashing often
 
**Has the Caltech mirror been working for people lately? Yes, more or less
 
  
 +
[[WormBase-Caltech_Weekly_Calls_May_2020|May]]
  
== February 17, 2011 ==
+
[[WormBase-Caltech_Weekly_Calls_June_2020|June]]
  
Interaction dumping script
+
[[WormBase-Caltech_Weekly_Calls_July_2020|July]]
*Spot check table
 
*Push changes to Git? Yes, to main branch
 
  
  
Interactions automatically downloaded to FTP every release? Yes
+
==August 6th, 2020==
*People should check their own curation data
 
*Users query frequently?
 
*Can WormMart work instead?
 
*Ruihua - feature can be added
 
*Todd - good to have pre-defined queries generated automatically
 
*Parse/remove predicted interactions (400,000) from others during dump? Yes
 
*Paul - Wei Wei wants to help with updates - who should she contact at WB?
 
  
 +
===Experimental conditions data flow into Alliance===
 +
*Experimental conditions in disease annotations: WB has inducers (used to recapitulate the disease condition) and modifiers (a modifier can ameliorate, exacerbate, or have no effect, on the disease condition)
 +
*We use the WB Molecule CV for Inducers and Modifiers in disease annotation
 +
*Experimental conditions in phenotype annotations: are free text (captured in remarks); will probably need to formalize later on
 +
*So for data flow into Alliance:
 +
**In the short term we will load the Molecule CV into the Alliance (Ranjana and Michael P. will work on this)
 +
**Groups will switch to using common data model that works for all and common ontology/ontologies in the near future.
 +
* How do we handle genetic sex? Part of condition?
 +
** Condition has been intended for external/environmental conditions, whereas genetic sex is inherent to the organism of study
 +
** Expression pattern curation needs genetic sex; needs a model at the Alliance for capturing sex
  
Ranjana - Solar flares causing static on phone? ;)
 
  
 +
== August 13, 2020 ==
  
Newsletter for new website release? Yes
+
=== Species in Postgres and ACEDB/Datomic ===
*Todd - 5 development milestones
+
* Want to dump "Affected By Pathogen" fields in Phenotype OA and RNAi OA
**teleconference with Gary Ruvkun's lab next week
+
* Want to be sure that what gets dumped aligns with species loaded into ACEDB
**Go live with Beta version in June (@IWM)
+
* Currently one species annotated not in WS277: Streptococcus gallolyticus subsp. gallolyticus
**Go live live with new site in September
+
* We currently have multiple Postgres tables for storing species lists:
**Retire old site at end of year
+
** pap_species_index (used by "Affected By Pathogen" fields, AFP); Kimberly uses to assign species to papers and occasionally adds new ones
**Need outreach, documentation, screencasts
+
** obo_name_ncbitaxonid
 +
** obo_name_taxon (original, smaller list)
 +
** h_pap_species_index (history for pap_species_index)
 +
* How do species get loaded into ACEDB? Dumps from Postgres? Which table(s)?
 +
* WS277 has 7,906 species (1,936 have no NCBI Taxon ID)
 +
* Kimberly has occasionally uploaded a species.ace file in the context of GO curation; but Hinxton otherwise handles it; should ask them
 +
* New species are associated with paper objects, but otherwise no additional data for those species come from Caltech
 +
* It might be useful to have species pages in WB that at least list papers for which we have species associations, maybe include other information?
  
 +
=== WS279 Citace upload ===
 +
* When is it happening? Not sure; not on release schedule right now
  
BioGRID
+
=== SOLR server security (IMSS) ===
*WormBase to BioGRID curation
+
* IMSS network security blocked network on our server due to its open SOLR web access.
*Issues of mapping interaction types: WB -> BioGRID vs. BioGRID -> WB
+
* Part of AMIGO stack, very old version, drives our ontology browser directly, SObA, Enrichment tools indirectly.
*Moving towards using WB interaction types
+
* Added some firewall/URL filter and IMSS opens up the network (for now). IMSS still gripes about its service is open to the world.
*Definitions of our interaction types
 
*Rose will propose to BioGRID community
 
*Physical interactions - BioGRID has a better format
 
**break physical interactions away from other interaction types?
 
**Kimberly can propose changes to model: YH separate from other interactions?
 
**Physical vs Genetic interactions? keep separate
 
*We need an interaction ontology, of some sort
 
*Who should Wei Wei contact, how to coordinate with Hinxton; getting data from FlyBase and SGD?
 
**Automation?
 
*Interaction pages - explain what the interaction is based on; provenance/reference
 
*Gene Orienteer shows data, but user has to link out
 
  
 
+
=== Alzheimer's disease portal ===
WormBase IWM souvenir?
+
* Supplement grant awarded to Alliance for an Alzheimer's disease portal
*Computer stress ball? with new site address?
+
* Could involve automated/concise descriptions, interactions, etc.
*bouncy ball?
+
* Could establish useful pipelines that could be reused in other contexts
*worm rubber band thing?
 
*Screen shield?
 
*Complementary iPads? ;)
 
*Antifungal socks? wristbands?
 
 
 
 
 
SPELL
 
*new data doesn't load; problem runnning search engine; can load it on athena, not generalizable problem?
 
*OS was not complete with an update; try again
 
*two virtual machines working back and forth for support
 
*how often is SPELL being used? log?; had 6-7 users within two weeks complaining of SPELL problems
 
*Todd - can send Google analytic tool to put at bottom of page
 
*Wen - SPELL testing server; official and mirror; want a separate testing server for new releases; mirror on athena (Wen's working machine); Raymond says don't want to attract users to that machine; WB's running SPELL on altair; heavily loaded and has had problems; relying on athena may be problematic
 
*maybe we need analysis of all of our machines to see big picture; can we consolidate machines; make use of ones we have? If not we can get another machine.
 
*what type of machine do we need?
 
*Log of all machines with purchase date and functionality?
 
*Linux vs Mac curators? athena development machine;
 
*how much power do the scripts need? can check
 
*may not be appropriate as official server if main machine goes down
 
*WB and athena can run SPELL server, but not others. security problems?
 
*prefer work machine is readily re-bootable; reconfigure software easily without affecting other things that people rely on
 
*need 10GB space; 4GB memory? SPELL production server; want it stable for outside world; hardware designed for that purpose; farm it out to IMSS?
 
*complexity of the application; Linux can run multiple applications; caprica has SVM production and WormMart; understand demand of the application; requirements; development vs running scripts, how often? Efficient use of machines. Have 2 computers, getting a third; for WormMart need power; traffic suddenly increased yesterday; monitor traffic; not much personal experience with server maintenance; cluster needs lots of expertise
 
*building official sever of SPELL at OICR? Yes
 
 
 
 
 
WormMart
 
*with WormMart and WormBase, people just want to know if it's down, just to know to lessen frustration; Official statement from dev team
 
*WormMart - we give users testing url; can we just change WormBase link to that testing server?
 
*going to change HTML to update users with most recent information; discuss with Lincoln, 5 datasets on testing server; remaining 3 datasets. if WormMart not working, put a message on main site
 
*it doesn't look good to have a link to a tool linked from a production server; if we don't trust the data we shouldn't put it up.
 
*would like to keep the html page as a testing server; could modify page
 
*if WormMart is working OK but not perfect, that's OK; Comment in the banner
 
*the html page is a useful tool to get feedback from users
 

Revision as of 21:01, 13 August 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 6th, 2020

Experimental conditions data flow into Alliance

  • Experimental conditions in disease annotations: WB has inducers (used to recapitulate the disease condition) and modifiers (a modifier can ameliorate, exacerbate, or have no effect, on the disease condition)
  • We use the WB Molecule CV for Inducers and Modifiers in disease annotation
  • Experimental conditions in phenotype annotations: are free text (captured in remarks); will probably need to formalize later on
  • So for data flow into Alliance:
    • In the short term we will load the Molecule CV into the Alliance (Ranjana and Michael P. will work on this)
    • Groups will switch to using common data model that works for all and common ontology/ontologies in the near future.
  • How do we handle genetic sex? Part of condition?
    • Condition has been intended for external/environmental conditions, whereas genetic sex is inherent to the organism of study
    • Expression pattern curation needs genetic sex; needs a model at the Alliance for capturing sex


August 13, 2020

Species in Postgres and ACEDB/Datomic

  • Want to dump "Affected By Pathogen" fields in Phenotype OA and RNAi OA
  • Want to be sure that what gets dumped aligns with species loaded into ACEDB
  • Currently one species annotated not in WS277: Streptococcus gallolyticus subsp. gallolyticus
  • We currently have multiple Postgres tables for storing species lists:
    • pap_species_index (used by "Affected By Pathogen" fields, AFP); Kimberly uses to assign species to papers and occasionally adds new ones
    • obo_name_ncbitaxonid
    • obo_name_taxon (original, smaller list)
    • h_pap_species_index (history for pap_species_index)
  • How do species get loaded into ACEDB? Dumps from Postgres? Which table(s)?
  • WS277 has 7,906 species (1,936 have no NCBI Taxon ID)
  • Kimberly has occasionally uploaded a species.ace file in the context of GO curation; but Hinxton otherwise handles it; should ask them
  • New species are associated with paper objects, but otherwise no additional data for those species come from Caltech
  • It might be useful to have species pages in WB that at least list papers for which we have species associations, maybe include other information?

WS279 Citace upload

  • When is it happening? Not sure; not on release schedule right now

SOLR server security (IMSS)

  • IMSS network security blocked network on our server due to its open SOLR web access.
  • Part of AMIGO stack, very old version, drives our ontology browser directly, SObA, Enrichment tools indirectly.
  • Added some firewall/URL filter and IMSS opens up the network (for now). IMSS still gripes about its service is open to the world.

Alzheimer's disease portal

  • Supplement grant awarded to Alliance for an Alzheimer's disease portal
  • Could involve automated/concise descriptions, interactions, etc.
  • Could establish useful pipelines that could be reused in other contexts