Manager Call 2018-04-05: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 11: Line 11:
== Working Groups/Projects ==
== Working Groups/Projects ==
===Software===
===Software===
* GO website:
====GO website====
Chris:  
Chris:  
Seth is switching Drupal to administrative mode. This is to prevent the site being hacked due to recently uncovered security holes in drupal core. Note that there will be no updates to Drupal after this happens.
Seth is switching Drupal to administrative mode. This is to prevent the site being hacked due to recently uncovered security holes in drupal core. Note that there will be no updates to Drupal after this happens.
Line 31: Line 31:




* Release pipeline: informing users/curators of the releases, so we can know what data we are looking at (Pascale: For annotation reviews this has been problematic for me)
====Release pipeline====
* New qualifier: Adding a qualifier to every annotation in a GAF file changes the file dramatically. It would impact any user or tool that filters annotations by looking for a null value in the qualifier field.  
informing users/curators of the releases, so we can know what data we are looking at (Pascale: For annotation reviews this has been problematic for me)
** Do we really want to make this large change to annotations in the gaf file, or do we want to encourage users who want the additional information to start consuming GPAD, where the qualifier is required?
====New qualifier====
* Adding a qualifier to every annotation in a GAF file changes the file dramatically. It would impact any user or tool that filters annotations by looking for a null value in the qualifier field.  
* Do we really want to make this large change to annotations in the gaf file, or do we want to encourage users who want the additional information to start consuming GPAD, where the qualifier is required?


== Working Groups/Projects ==
== Working Groups/Projects ==

Revision as of 03:47, 29 March 2018


Agenda

NYC Meeting Agenda

Working Groups/Projects

Software

GO website

Chris: Seth is switching Drupal to administrative mode. This is to prevent the site being hacked due to recently uncovered security holes in drupal core. Note that there will be no updates to Drupal after this happens.

Seth has warned about this in the past. We either need to commit resources to administering Drupal, or we need to switch the website out, e.g. for a static site built using github pages. My person preference is for github pages. But either way this will divert efforts from other tasks.

Seth: To actually qualify this a bit more, now that I am looking at the issues (critical remote exploits) and possibilities to fix a bit closer, there is no "safe" mode available in our installation of Drupal. This means that we either migrate away very very fast indeed or I will drop it off the web temporarily today to do some of the needful updates. I believe the latter is the only realistic action as of right now.

Moving forward though, we should probably decide if there is to be a Drupal "role" or if we should hasten a migration to something that requires a less centralized role.


Release pipeline

informing users/curators of the releases, so we can know what data we are looking at (Pascale: For annotation reviews this has been problematic for me)

New qualifier

  • Adding a qualifier to every annotation in a GAF file changes the file dramatically. It would impact any user or tool that filters annotations by looking for a null value in the qualifier field.
  • Do we really want to make this large change to annotations in the gaf file, or do we want to encourage users who want the additional information to start consuming GPAD, where the qualifier is required?

Working Groups/Projects

GO Curation Survey

  • Draft Survey
  • Action from last meeting: (Kimberly): Move to Survey monkey, make changes discussed, and send it around


Protein Complexes

HTP Codes

RCA Evidence Code

  • Need to work with several groups to review their annotations:
    • Gramene (35815 annotations)
    • As an example, 2929 RCA Molecular Function annotations
      • Date: 20060831
      • Reference: GR_REF:8030
      • Manual review of mappings; can we suggest ISM?
    • GeneDB
      • Some annotations from reviews, but some to papers that describe a systems analysis that is probably more in line with the original intent of RCA
      • RCA -> CCA (combined computational analysis)??
    • EcoCyc
    • AgBase
    • AspGD
    • PAMGO_MGG
  • If we decide to keep RCA, then we'd need to remove the one-year limit; it doesn't make sense.

Documentation

QA/QC

Working Group Meetings

  • Quarterly?
    • Rotate between ontology and annotation (small, focused groups)
    • Test virtual meetings, but still focused on the task

Noctua

1.0 Rollout

  • Merge Tremayne's fork with Noctua-dev for further testing
  • Some outstanding issues on SAE
  • Single source file for MODs to consume

Reactome Imports

  • David, Kimberly have looked at some imports/translations
  • Ben's work looks to be potentially very useful and promising for seeding templates, models
  • Will probably require significant manual input, refinement, testing

End User Tools

GO Helpdesk

Discuss this ticket: https://github.com/geneontology/go-site/issues/584

Ontology

Announcing changes to the wider user community

  • This was brought up by Birgit in the protein complex merge ticket - she was suggesting we make an announcement. However we never made annoucements before (except for obsoletions); should we start? What would be the guidelines? For example when a merge affects more than 100, 1000 annotations ? EXP only ?
  • Pascale: changes to definitions of root terms: https://github.com/geneontology/go-ontology/issues/14899; isn't this a big change ? How should we notify people?
    • Should we create a label in GH 'Major change', so we can easily pull out the tickets and show them at Ontology and Annotation calls ? (perhaps in annual reports as well)
  • Pascale: suggestion: create a new label 'major change' and announce them either on twitter and/or on the website as user stories (or whatever it's called).


Minutes

  • On call: