Editors cross-product implementation plan

• Start with internal xps first - do external later. Files distributed as follows:

XP:biological process xp self - Jen
XP:cellular component xp go - Midori
XP:cellular component xp self - Jane
XP:molecular function xp regulators - David & Tanya
XP:biological process xp regulation - David & Tanya
XP:biological process xp multi organism process - Jane
XP:biological process xp cellular component - Midori

• First phase will be transition phase = files being edited outside of GO files. Essentially the person in charge of that file will check all of the XP definitions are okay, and edit as they see fit. The editing will probably be done manually.
• Minimise duration of transition phase: we will aim for XPs being in the editors file at start of Jan 2009. This will be the second phase. Note that this is dependent on OE2 being released unless we use the OE2 beta for editing the editors file.
• Start the editor training (i.e. editors outside of editorial office) before Jan 2009: one WebEx training session some time before Christmas
• End of March 2009 - final phase = XPs in GO users file & OE2 released!

See also Chris's email 7-11-2008

Questions we explored in this meeting:

Q/ Annotators have asked if new cross product terms will always need to be instantiated in the ontology or if they might one day be able to do, for example, a binding term annotation by annotating to the GO term 'binding' and the ChEBI term for the substance bound.

A/ The conclusion was that we will always instantiate cross product terms in the ontology. For such simple term requests we could in the future allow annotators to automatically request terms by just quoting the ids for the constituent terms and having software generate the terms overnight. The terms would be checked by curators, but the process would be essentially automatic and almost immediate.

Back to Cross Product Guide