Difference between revisions of "WBConfCall 2018.05.17-Agenda and Minutes"

From WormBaseWiki
Jump to navigationJump to search
Line 18: Line 18:
 
*On call: Adam, Cecilia, Chris, Daniela, Juancarlos, Karen, Kimberly, Raymond, Scott, Sibyl, Todd, Valerio, Wen, Kevin, Paul D, Gary, Matt, Paul K
 
*On call: Adam, Cecilia, Chris, Daniela, Juancarlos, Karen, Kimberly, Raymond, Scott, Sibyl, Todd, Valerio, Wen, Kevin, Paul D, Gary, Matt, Paul K
  
===HelpDesk - Kimberly===
+
==HelpDesk - Kimberly==
 
'''Helpdesk Issues Still Open'''
 
'''Helpdesk Issues Still Open'''
 
*[https://github.com/WormBase/website/issues/6417 I am trying to have access to fosmid ...]
 
*[https://github.com/WormBase/website/issues/6417 I am trying to have access to fosmid ...]

Revision as of 15:45, 17 May 2018

Agenda

HelpDesk - Kimberly

Helpdesk Issues Still Open

WBStrain ids

  • would be good to get a list of people who need to be able to create new strains
  • will reside temporary in the old NameServer at Sanger and then move to the new Datomic one on AWS

SAB - Toronto, CA

AGR

Minutes

  • On call: Adam, Cecilia, Chris, Daniela, Juancarlos, Karen, Kimberly, Raymond, Scott, Sibyl, Todd, Valerio, Wen, Kevin, Paul D, Gary, Matt, Paul K

HelpDesk - Kimberly

Helpdesk Issues Still Open

  • I am trying to have access to fosmid ...
    • On staging, we will begin providing the end sequences
    • We've never had the full sequence, so if we were providing a "fosmid" sequence, it might have been the intervening genomic sequence
    • What would users want?
    • It seems we could provide the intervening sequence but we need to communicate with users about what they're actually getting, i.e. a prediction.
    • Would this be a potential source of confusion to users, though, who may need to validate the sequence against a clone they order from Don Moerman's group?
    • Resolution: for next release, provide intervening genomic sequence but make it clear that it's predicted from genomic.
    • Chris will check and close the original ticket, if the changes Adam pushed are okay.

WBStrainIDs

  • Bulk assigning strain IDs to existing strains is easy.
  • How do we assign new strain IDs at the point of curation?
  • Will treat similarly to variations, i.e. use a name service to check if an ID already exists; if not, can request a new strain ID to use in postgres curation database.
  • Who needs access to the name server for this?
    • Ranjana,