On Apr 27, 2006, at 12:13 PM, Terry Casstevens wrote:
> I've added these to the pending issues list. I'll post
> the updated file to the web site soon.
> One comment... the accename field is a standard IPGRI
> passport descriptor. Which is why I've included it
> in GDPDM. Not sure that we'd want to remove that.
You'd not be removing it so much as "moving" it. Putting *all* the
names into one table makes it easier to search, and then you can
attribute each in the same way using the synonym type.
> On 4/18/06, Ken Youens-Clark <kclark@...> wrote:
>> As we discussed on this morning's Gramene conference call, here are a
>> couple of ideas for possible inclusion in future GDPDM schema
>> - Allow a many-to-many relationship between div_passport and
>> cdv_source: According to Isaak, germplasms may be available from
>> more than one source. Also, I would prefer to deprecate the
>> "div_passport.source" field and move this info to the normalized
>> "cdv_source" table.
>> - Allow for annotations/xrefs on germplasm names/synonyms: This is a
>> combination of ideas. First off, it would be nice to attribute a
>> germplasm's synonyms, e.g., to say that "IRGC 3575" is an IRRI
>> synonym. This could be accomplished by adding a "synonym_type" table
>> with a FK to "div_synonym":
>> CREATE TABLE div_synonym_type (
>> div_synonym_type_id int PK,
>> synonym_type varchar(50), -- e.g., "IRRI"
>> xref_url text -- e.g., sprintf-type URL template,
>> -- "http://www.iris.irri.org/action/
>> This would be even more useful if ALL germplasm names could be
>> attributed and xref'd, so you'd remove the "div_passport.accename"
>> and add a "div_display_synonym_id" field instead to indicate which
>> synonym is used for the display. It creates a somewhat bizarre
>> circular reference (no worse than others already in GDPDM, like those
>> that reference other records in the same table [div_parent_id]), but
>> it makes for a very flexible way to both search just one table for
>> germplasm names and to put their sources into the db. It's possible
>> some sort of "annotation" table could also be used, but this way just
>> makes everything explicit.
>> This SF.Net email is sponsored by xPML, a groundbreaking scripting
>> that extends applications into web and mobile media. Attend the
>> live webcast
>> and join the prime developer group breaking into this new coding
>> Gdpdm-devel mailing list