2012 Annotation Meeting Stanford: Difference between revisions
Jump to navigation
Jump to search
(Created page with " ==Agenda== ===Ideas=== * Should focus on Annotation as a process and not the thing. How to facilitate the process of annotation? * Should enable developers to gather ideas for t...") |
No edit summary |
||
| Line 1: | Line 1: | ||
==Agenda== | ==Agenda== | ||
===Ideas=== | ===Ideas=== | ||
* Should focus on Annotation as a process and not the thing. How to facilitate the process of annotation? | * Intent is not to go over annotation specifics (how to annotate, what evidence etc, all of which can be done well over annotation conf. calls). Should focus on Annotation as a process and not the thing. How to facilitate the process of annotation? | ||
* Should enable developers to gather ideas for the CAF | * Should enable developers to gather ideas for the CAF | ||
* Possibly open protein2GO or the Pombase community annotation tool to curators so they can give feedback on what works and what doesn't | * Possibly open protein2GO or the Pombase community annotation tool to curators so they can give feedback on what works and what doesn't | ||
Revision as of 14:45, 16 November 2011
Agenda
Ideas
- Intent is not to go over annotation specifics (how to annotate, what evidence etc, all of which can be done well over annotation conf. calls). Should focus on Annotation as a process and not the thing. How to facilitate the process of annotation?
- Should enable developers to gather ideas for the CAF
- Possibly open protein2GO or the Pombase community annotation tool to curators so they can give feedback on what works and what doesn't
- Pick a subprocess as the theme and see the evolution of the ontology and annotations related to the subprocess
- dedicated session on PAINT training (hands on training) to propagate annotations made on the subprocess
- Possibly develop a model for annotating complexes and build on col-16 curation