|
From: Naama M. <nm...@co...> - 2009-09-24 04:04:14
|
Yes, If using an organismgroup table, the 'type' field should really be a
cvterm_id.
I'm not sure if organismprop is the best table for this .
How do you think group names and types should be stored?
If I have a unigene build or a library from sequences of 100 species,
storing this information in organism prop will require
inserting the group name in the value field for each organism and type_id =
a cvterm for the group type ('unigene build' and a cv with name = 'organism
groups' ).
If the group name is stored as a cvterm , it will require adding a cv for
each group type (e.g. 'unigene build' , 'common name' ..)
-Naama
On Wed, Sep 23, 2009 at 5:07 PM, Hilmar Lapp <hl...@du...> wrote:
>
>
> As stated so far the rationale behind it doesn't strike me as having much
> or anything to do with phylogeny, so I vote for A.
>
> Organismprop could be used too. If you wanted to attach semantics to the
> grouping, it'd probably be the better way of doing this. Or the group table
> should have a link to cvterm.
>
> -hilmar
> --
> ===========================================================
> : Hilmar Lapp -:- Durham, NC -:- hlapp at duke dot edu :
> ===========================================================
>
>
>
>
>
|