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

From WormBaseWiki
Jump to navigationJump to search
Line 2: Line 2:
  
 
== Helpdesk Issues ==
 
== Helpdesk Issues ==
* [Addressed by Stavros and Cecilia but needs attention by WebTeam] Colin Dolphin can't login to WormBase https://github.com/WormBase/website/issues/9417
+
* [Addressed by Stavros and Cecilia] Colin Dolphin can't login to WormBase https://github.com/WormBase/website/issues/9417
 +
- Everything seems ok
 
* [Possibly not addressed, Stavros self-assigned] snpc-1.4 misannotated https://github.com/WormBase/website/issues/9418
 
* [Possibly not addressed, Stavros self-assigned] snpc-1.4 misannotated https://github.com/WormBase/website/issues/9418
 
+
- Stavros is on it
  
  
Line 15: Line 16:
 
== Agenda Items ==
 
== Agenda Items ==
 
* Alliance code security warnings (notification by Michael Paulini through wormbase-help) - OICR?
 
* Alliance code security warnings (notification by Michael Paulini through wormbase-help) - OICR?
 +
- dependabot emails on npm libraries. Chris will take a look.
 +
- remove people from repos after they leave the Alliance/WB
  
* Invalid LAB and allele designations sneaking into WormBase - advice needed please. #9409 [SKD]
+
* Invalid LAB and allele designations sneaking into WormBase - advice needed please. #9409 [SKD]
 
[Tim] Strains with invalid strain names and allele names should not be curated.   
 
[Tim] Strains with invalid strain names and allele names should not be curated.   
  
 
[Karen] The strains are real so they should be captured. However the authors need to rename them to adhere to our nomenclature rules, regardless, so they need to be contacted for sure.
 
[Karen] The strains are real so they should be captured. However the authors need to rename them to adhere to our nomenclature rules, regardless, so they need to be contacted for sure.
 
I would vote to NOT  curate the strains unless the authors change the names, but for the one that has been curated, remove the name from the public_name field, leaving that blank, since the strain has a WBStrainID it is trackable. Add the incorrect name into a remark field.     
 
I would vote to NOT  curate the strains unless the authors change the names, but for the one that has been curated, remove the name from the public_name field, leaving that blank, since the strain has a WBStrainID it is trackable. Add the incorrect name into a remark field.     
 +
 +
[Stavros] will check how many there are for WS293.
 +
[Ranjana] asks how many there are from caltech before deciding.
  
 
* Updating the C. elegans ribosomal subunit gene names and protein names. [Tim]
 
* Updating the C. elegans ribosomal subunit gene names and protein names. [Tim]

Revision as of 16:42, 1 February 2024

Agenda/Minutes

Helpdesk Issues

- Everything seems ok

- Stavros is on it


Agenda Items

  • Alliance code security warnings (notification by Michael Paulini through wormbase-help) - OICR?

- dependabot emails on npm libraries. Chris will take a look. - remove people from repos after they leave the Alliance/WB

  • Invalid LAB and allele designations sneaking into WormBase - advice needed please. #9409 [SKD]

[Tim] Strains with invalid strain names and allele names should not be curated.

[Karen] The strains are real so they should be captured. However the authors need to rename them to adhere to our nomenclature rules, regardless, so they need to be contacted for sure. I would vote to NOT curate the strains unless the authors change the names, but for the one that has been curated, remove the name from the public_name field, leaving that blank, since the strain has a WBStrainID it is trackable. Add the incorrect name into a remark field.

[Stavros] will check how many there are for WS293. [Ranjana] asks how many there are from caltech before deciding.

  • Updating the C. elegans ribosomal subunit gene names and protein names. [Tim]