Annotation Conf. Call 2019-05-14: Difference between revisions
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
* Remind people about Gitter as an option to communicate with other curators | * Remind people about Gitter as an option to communicate with other curators | ||
* 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. | * 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 and guidelines: We'd like to have information about each group's annotation guidelines and how annotations are processes and presented/exporter to users. | |||
[[Category:Annotation Working Group]] | [[Category:Annotation Working Group]] | ||
Revision as of 09:52, 17 April 2019
Agenda
GOC meeting debrief/announcements
- TF annotations: All: People will need to migrate transcription factor annotations to specific TF binding terms to use GO+SO extensions
- Remind people about Gitter as an option to communicate with other curators
- 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 and guidelines: We'd like to have information about each group's annotation guidelines and how annotations are processes and presented/exporter to users.