Manager Call 2017-12-06: Difference between revisions
Line 34: | Line 34: | ||
== Documentathon == | == Documentathon == | ||
*Agenda items: | *Agenda items: | ||
**Annotation relations | **Annotation guidelines | ||
***https://github.com/geneontology/go-annotation/issues/1690 | ***Annotation relations | ||
***https://github.com/geneontology/go-annotation/issues/1687 | ****https://github.com/geneontology/go-annotation/issues/1690 | ||
***GAF/GPAD | ****https://github.com/geneontology/go-annotation/issues/1687 | ||
***GO-CAM | ****GAF/GPAD | ||
****GO-CAM | |||
***Annotation extensions | ***Annotation extensions | ||
**Annotation file pipelines | ***Annotation file pipelines | ||
***https://github.com/geneontology/go-annotation/issues/1683 | ****https://github.com/geneontology/go-annotation/issues/1683 | ||
***https://github.com/geneontology/go-annotation/issues/1682 | ****https://github.com/geneontology/go-annotation/issues/1682 | ||
***https://github.com/geneontology/go-annotation/issues/1674 | ****https://github.com/geneontology/go-annotation/issues/1674 | ||
***Submission SOP | ****Submission SOP | ||
***Error checks and Jenkins jobs/reports | ****Error checks and Jenkins jobs/reports | ||
***Dealing with redundant annotations | ****Dealing with redundant annotations | ||
**Evidence codes | ***Evidence codes | ||
**Noctua | **Noctua | ||
***User guide | |||
**Readthedocs | **Readthedocs | ||
***Can we make better use of this? | ***Can we make better use of this? | ||
***Nice example of formatting: http://firefox-puppeteer.readthedocs.io/en/master/index.html | ***Nice example of formatting: http://firefox-puppeteer.readthedocs.io/en/master/index.html | ||
**Using GO | |||
***File formats available | |||
***Annotation basics | |||
***Reference proteomes vs complete proteomes | |||
= Minutes = | = Minutes = |
Revision as of 14:19, 1 December 2017
Joining the Call on Bluejeans
https://bluejeans.com/588333403
Agenda
GO helpdesk
The current solution is really not appropriate for most of our users. The bar is too high to submit any request. Can we re-evaluate the decision to have a simple form/email mechanism ? See discussion in https://github.com/geneontology/go-annotation/issues/1670
GH tickets reminder
https://github.com/geneontology/helpdesk/issues/78 From geneontology/go-annotation#1388
We all need a way to be reminded which tickets are assigned to us!
Can this be done in some sort of "git hub" management mode (i.e select all tickets and send a message saying "you are the assignee of this ticket, please check if it can be closed").... A monthly alert......I will never look otherwise.... I think this would get a lot of GitHub tickets "unstuck"
At least for the go-ontology and go-annotation repos that would be really nice.
Thanks, Pascale
Guidelines for Annotation Display
- GO annotation fields required for correct display
- Rachael brought these guidelines to our attention
- Can these be tidied up and put on the website?
Obsolete terms in slims: need a SOP
See https://github.com/geneontology/go-ontology/issues/14677
GO at ISB, April 2018
- What presence will we have? Is anyone submitting an abstract?
- https://www.biocuration.org/biocuration-2018-call-for-abstracts/
Documentathon
- Agenda items:
- Annotation guidelines
- Annotation relations
- Annotation extensions
- Annotation file pipelines
- https://github.com/geneontology/go-annotation/issues/1683
- https://github.com/geneontology/go-annotation/issues/1682
- https://github.com/geneontology/go-annotation/issues/1674
- Submission SOP
- Error checks and Jenkins jobs/reports
- Dealing with redundant annotations
- Evidence codes
- Noctua
- User guide
- Readthedocs
- Can we make better use of this?
- Nice example of formatting: http://firefox-puppeteer.readthedocs.io/en/master/index.html
- Using GO
- File formats available
- Annotation basics
- Reference proteomes vs complete proteomes
- Annotation guidelines