I see your point with changing ontologies. The reason I asked about making them predefined in the first place is that (for example) the export plugin could expect an annotation of certain name/id to exist in BASE, and could automatically pick it up for a user. No need to configure the plugin or its execution, so easier for a user and an admin.
On the other hand, every BASE installation admin could make a plugin configuration, that would include the right, locally created annotation types to use. That makes the connection of the plugin to annotation type's name/id less tight, which is better from the design point of view. Pawel On 25/10/11 13:34, Bob MacCallum wrote: > On Tue, Oct 25, 2011 at 12:16 PM, Nicklas Nordborg<[email protected]> wrote: >> On 2011-10-25 09:22, Pawel Sztromwasser wrote: >>> Hi >>> >>> Working with the MageTab export I have noticed that it would be great to >>> have additional properties for experiments that could hold MGED Ontology >>> annotations, e.g. Experiment Design, Replicate Type, Quality Control >>> Type. Up to now we've been using the Experiment Design and Experiment >>> Type fields of experiments to hold this information, but it is a bit >>> counterintuitive and does not restrict to available MO terms. >>> >>> In order to attach a fixed vocabulary term to an experiment it is >>> probably easiest to make experiments annotatable and create one >>> annotation type with selection of terms for every property. Further, the >>> MO annotation types could be present in BASE by default (like the >>> default protocol types), together with selections of MO terms. What do >>> you think? >> I have also noticed that many of the experiment properties are >> annotation-like and that it would be better to simply use annotations >> instead. Unfortunately, it's too late to include this in the BASE 3 >> release, so I guess it will have to wait for BASE 3.1. Making the >> experiment annotable is fairly easy. The existing information must stay >> as it is. > +1 for annotatable experiments > >> Regarding default annotation types, I think it is best to not include >> any in a standard installation. Ontologies tend to change every now and >> then, so it's better to let administrators handle that. >> >> /Nicklas >> >> ------------------------------------------------------------------------------ >> The demand for IT networking professionals continues to grow, and the >> demand for specialized networking skills is growing even more rapidly. >> Take a complimentary Learning@Cisco Self-Assessment and learn >> about Cisco certifications, training, and career opportunities. >> http://p.sf.net/sfu/cisco-dev2dev >> _______________________________________________ >> The BASE general discussion mailing list >> [email protected] >> unsubscribe: send a mail with subject "unsubscribe" to >> [email protected] >> > ------------------------------------------------------------------------------ > The demand for IT networking professionals continues to grow, and the > demand for specialized networking skills is growing even more rapidly. > Take a complimentary Learning@Cisco Self-Assessment and learn > about Cisco certifications, training, and career opportunities. > http://p.sf.net/sfu/cisco-dev2dev > _______________________________________________ > The BASE general discussion mailing list > [email protected] > unsubscribe: send a mail with subject "unsubscribe" to > [email protected] ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ The BASE general discussion mailing list [email protected] unsubscribe: send a mail with subject "unsubscribe" to [email protected]
