|
From: Hilmar L. <la...@gn...> - 2001-11-27 19:46:10
|
Quoting "Jason E. Stewart" <ja...@op...>:
>
> Genex-2 enables you to protect *all* data: protocols, samples,
> contacts, etc. It also introduces audit information so you can track
> what was changed and by whom. And it introduces a generic
> authentication mechanism used by all CGI scripts -- so you have to
> login to the system before viewing data, making queries, manipulating
> data.
>
Is there an ERD for the new schema already? (BTW which tool did you use
to create the current one which is available on the website?)
> Because MAGE is now (mostly) finalized, a good deal of the plans for
> Genex-2 will be the renaming of objects/tables to fit with MAGE
> nomenclature plus the addition of a number of additional
> tables/objects specified by MAGE. Genex-2 will *not* be fully MAGE
> compliant, but it will have major pieces.
>
Do you already know which parts of MAGE will not be implemented
and/or covered by Genex-2?
> QuantitationDimension. That way if your data generates an array of 80
> floats for each spot (or Feature in MAGE speak), all of those 80
> numbers will go into a single row in the AM_Spots table for that
> technology. Genex-1 would force you to create 80 ArrayMeasurements
> each with a single value/spot in the AM_Spots table (yuck!).
So you're going to denormalize. Did you run into performance problems,
and if so, on which end, or in which situations? (Trying to learn from
your experience.)
-hilmar
--
-------------------------------------------------------------
Hilmar Lapp email: la...@gn...
GNF, San Diego, Ca. 92121 phone: +1-858-812-1757
-------------------------------------------------------------
|