Annotation Conf. Call 2019-05-14: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
| Line 6: | Line 6: | ||
=== Communication === | === Communication === | ||
* Remind people about [https://gitter.im/geneontology/go-annotation Gitter] as an option to communicate with other curators | |||
=== Transcription Factor Annotations === | === Transcription Factor Annotations === | ||
| Line 15: | Line 15: | ||
=== Annotation Pipelines === | === Annotation Pipelines === | ||
* Annotation pipelines and guidelines: We'd like to have information about each group's annotation guidelines and how annotations are processes and presented/exporter to users. | * Annotation pipelines and guidelines: We'd like to have information about each group's annotation guidelines and how annotations are processes and presented/exporter to users. | ||
== MOD Import into Noctua == | == MOD Import into Noctua == | ||
Revision as of 13:32, 13 May 2019
Agenda
GOC meeting debrief/announcements
Communication
- Remind people about Gitter as an option to communicate with other curators
Transcription Factor Annotations
- TF annotations: All: People will need to migrate transcription factor annotations to specific TF binding terms to use GO+SO extensions
PAINT
- Remind people they can provide guidance for PAINT annotation: PAINT Annotations: to prevent over-propagation to paralogs: submit GitHub tickets explaining that the list of gene products associated with this process is complete and that paralogs should not be associated with the term.
Annotation Pipelines
- Annotation pipelines and guidelines: We'd like to have information about each group's annotation guidelines and how annotations are processes and presented/exporter to users.
MOD Import into Noctua
- MGI and WB are working on a pipeline to import all of their manual annotations into Noctua
Minutes
- Present: