2011 USC Meeting Action Items: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
* Annotation: Report on taxon constraints needs to be implemented ASAP! | * '''Annotation''': Report on taxon constraints needs to be implemented ASAP! | ||
* Annotation: Contact Rama and Emily if you can help organizing and editing the annotation pages on the GO website | * '''Annotation''': Contact Rama and Emily if you can help organizing and editing the annotation pages on the GO website | ||
* GO Help: create an aggregator for GO-related stuff on other sites - BioStar, Twitter, Facebook, Myspace, Boing Boing, etc. | * '''GO Help''': create an aggregator for GO-related stuff on other sites - BioStar, Twitter, Facebook, Myspace, Boing Boing, etc. | ||
* GO Help: designate a point person for software group queries (Seth seems to have volunteered) | * '''GO Help''': designate a point person for software group queries (Seth seems to have volunteered) | ||
* GO Help: if you're interested in joining GO help--and it's very rewarding, great fun, and a superb way to enhance your day--please contact Rama and Emily. | * '''GO Help''': if you're interested in joining GO help--and it's very rewarding, great fun, and a superb way to enhance your day--please contact Rama and Emily. | ||
* Evidence Codes: convene a working group to discuss ECO in more depth. | * '''Evidence Codes''': convene a working group to discuss ECO in more depth. | ||
* Annotation deliverables: What are the annotation items that we are going to present to the world? Formulate guidelines and deliverables. | * '''Annotation deliverables''': What are the annotation items that we are going to present to the world? Formulate guidelines and deliverables. | ||
* Ontology development: comments on annotation should go into GONUTS (e.g. how to annotate transcription factors), not the GO wiki. | * '''Ontology development''': comments on annotation should go into GONUTS (e.g. how to annotate transcription factors), not the GO wiki. | ||
* Ontology development: notification of GO changes to GO friends | * '''Ontology development''': notification of GO changes to GO friends | ||
* Ontology development: def diffs to the list | * '''Ontology development''': def diffs to the list | ||
* PRO: | * '''PRO''': feel free to use PRO IDs in col 17 and ask the PRO team for new IDs. No formal shift to PRO for the time being. | ||
Revision as of 11:58, 20 May 2011
- Annotation: Report on taxon constraints needs to be implemented ASAP!
- Annotation: Contact Rama and Emily if you can help organizing and editing the annotation pages on the GO website
- GO Help: create an aggregator for GO-related stuff on other sites - BioStar, Twitter, Facebook, Myspace, Boing Boing, etc.
- GO Help: designate a point person for software group queries (Seth seems to have volunteered)
- GO Help: if you're interested in joining GO help--and it's very rewarding, great fun, and a superb way to enhance your day--please contact Rama and Emily.
- Evidence Codes: convene a working group to discuss ECO in more depth.
- Annotation deliverables: What are the annotation items that we are going to present to the world? Formulate guidelines and deliverables.
- Ontology development: comments on annotation should go into GONUTS (e.g. how to annotate transcription factors), not the GO wiki.
- Ontology development: notification of GO changes to GO friends
- Ontology development: def diffs to the list
- PRO: feel free to use PRO IDs in col 17 and ask the PRO team for new IDs. No formal shift to PRO for the time being.