Re: [GeneX-dev] Hybridization field in schema (2/8/01)

[Todd P. <tf...@nc...>]

I am actively converting the ERWin diagram to an opensource modeling tool
called DOME (http://www.htc.honeywell.com/dome). This will allow
modification to the model by somebody not sitting at our only machine with
an ERWin license. The DOME tool allows the developer to customize auto-code
or even the modeling environment. I have used an earlier (and more crude)
version of the tool to auto-generate CLOS class files from a Coad-Yourdon
class diagram (more complicated than our current diagram) and it worked
great.

Anyway, I still have a bit of work to do on the model and then will release
the new diagram and data. Thanks for everybody's patience.

As far as modification to the model for hyb name...the parameters are in the
XML files and are handled by the curation tool. The programs XML2DB and
DB2XML would need to be looked at (what are they doing now with hyb name?).

Todd

----- Original Message -----
From: "Jason E. Stewart" <ja...@op...>
To: <gen...@li...>
Sent: Monday, February 26, 2001 9:04 AM
Subject: Re: [GeneX-dev] Hybridization field in schema (2/8/01)


> "Michael Pear" <mic...@ho...> writes:
>
> > I looked at the latest schema available at
> > http://www.ncgr.org/research/genex/GeneXSchema.pdf and see that the
> > field "hybridization_name" no longer appears. This is an important
> > field as there is currently no otherway to tie array measurements
> > together other than in an experiment set (at least that I can
> > see). We plan on using it, for example, to identify array
> > measurements from the same glass slide using a bar code reference.
> >
> > Is this an error, or do I lose this field if I update to the latest
> > release on sourceforge?
>
> You will not lose anything (and there is no latest version on SF :-(
>
> That diagram is created by data from the ERWin program. Currently that
> program is not used to actually create the database (it cannot produce
> Postgres td scripts). Todd has been working to keep ERWin up-to-date
> with the state of the DB, but unfortunately I have not been very good
> at communicating changes, nor have I checked the diagram.
>
> I'm still working to get a new version of the updater available, but
> I've been busy at the OMG meeting.
>
> jas.
>
> _______________________________________________
> Genex-dev mailing list
> Gen...@li...
> http://lists.sourceforge.net/lists/listinfo/genex-dev
>