Revision as of 11:12, 8 August 2018

Pipeline - what data should groups display?

https://github.com/geneontology/paint/issues/53#issuecomment-410834662

PAINT annotations

Pascale: Right now we suggest that MODs/groups consume the PAINT annotations as part of their groups' entire file (ie, including their own annotations). Does that really make sense ? I thought that the 'full annotation file' (ie, including PAINT); was meant to external users rather than for contributing groups. Given that most MODs either curate locally, or import from UniProt, does it make sense to re-import their own data via GOC *or* to filter the entire file to only import PAINT files ?

See https://github.com/geneontology/go-annotation/issues/1939#issuecomment-410616491

Follow up from last week

Feedback form update

Did we figure out the payment ? What's the time line for deployment? https://github.com/geneontology/go-site/issues/750

New GO-announcement repo

Twitter/facebook: SuziA is this done ?

New GAF Submissions

SuziA: Update on documentation

Ontology Editors' Meeting

David: Who would attend each meeting ? Pascale: needed to follow up with Paul regarding funds to hold these

GO Web Site Migration

Drupal move: new home of documentation is https://github.com/geneontology/go-docs/tree/master/documentations

Job descriptions for each manager

Pascale and Kimberly stared to create job descriptions for all managers roles:

https://drive.google.com/drive/folders/1F7e2D7T4hleIq8VaH7YW60D9wxQnRFRV

Every manager should add what they believe are their tasks. And then we discuss it here.

Review Project Priorities for each group

(Note that this should be a recurring discussion on these calls) https://github.com/orgs/geneontology/projects/1

@@ Line 1: / Line 1: @@
+= Pipeline - what data should groups display?=
+https://github.com/geneontology/paint/issues/53#issuecomment-410834662
+=PAINT annotations=
+Pascale: Right now we suggest that MODs/groups consume the PAINT annotations as part of their groups' entire file (ie, including their own annotations). Does that really make sense ? I thought that the 'full annotation file' (ie, including PAINT); was meant to external users rather than for contributing groups.  Given that most MODs either curate locally, or import from UniProt, does it make sense to re-import their own data via GOC *or* to filter the entire file to only import PAINT files ?
+See https://github.com/geneontology/go-annotation/issues/1939#issuecomment-410616491
@@ Line 20: / Line 28: @@
 Drupal move: new home of documentation is https://github.com/geneontology/go-docs/tree/master/documentations
-=PAINT annotations=
-Pascale: Right now we suggest that MODs/groups consume the PAINT annotations as part of their groups' entire file (ie, including their own annotations). Does that really make sense ? I thought that the 'full annotation file' (ie, including PAINT); was meant to external users rather than for contributing groups.  Given that most MODs either curate locally, or import from UniProt, does it make sense to re-import their own data via GOC *or* to filter the entire file to only import PAINT files ?
-See https://github.com/geneontology/go-annotation/issues/1939#issuecomment-410616491
 =Job descriptions for each manager=
@@ Line 32: / Line 37: @@
 Every manager should add what they believe are their tasks. And then we discuss it here.
-= Pipeline - what data should groups display?=
-https://github.com/geneontology/paint/issues/53#issuecomment-410834662
 =Review Project Priorities for each group=

Manager Call 2018-08-15: Difference between revisions