Manager 6November2013: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
#Can we allow use of both a published paper and a GO_REF in the same annotation? Cardinality of the reference field can be >1, but the annotation documentation only refers to cases where a publication has identifiers in different databases, e.g. PubMed and a MOD database. I'd like to include a GO_REF for the WormBase Phenotype2GO-based annotations, but also still include the original publication from which the phenotype information was curated. The GO_REF would explain the methodology used to create the resulting Biological Process annotation. | '''Agenda Items''' | ||
#Can we allow use of both a published paper and a GO_REF in the same annotation? Cardinality of the reference field can be >1, but the annotation documentation only refers to cases where a publication has identifiers in different databases, e.g. PubMed and a MOD database. I'd like to include a GO_REF for the WormBase Phenotype2GO-based annotations, but also still include the original publication from which the phenotype information was curated. The GO_REF would explain the methodology used to create the resulting Biological Process annotation. [Kimberly] | |||
Revision as of 14:24, 5 November 2013
Agenda Items
- Can we allow use of both a published paper and a GO_REF in the same annotation? Cardinality of the reference field can be >1, but the annotation documentation only refers to cases where a publication has identifiers in different databases, e.g. PubMed and a MOD database. I'd like to include a GO_REF for the WormBase Phenotype2GO-based annotations, but also still include the original publication from which the phenotype information was curated. The GO_REF would explain the methodology used to create the resulting Biological Process annotation. [Kimberly]