Re: [GeneX-dev] Conf call summary

[Greg D. C. <gd...@nc...>]

>Delivered-To: fix...@li...@fixme
>To: gen...@li...
>Mime-Version: 1.0 (generated by tm-edit 1.5)
>From: ja...@op... (Jason E. Stewart)
>Subject: [GeneX-dev] Conf call summary
>Date: 06 Mar 2001 23:11:13 -0700
>
>Michael, Harry, and I had a call today about the status of the data
>loader. 
>
>
>Loader
>======
>Next, we identified the pieces which are critical for the entry of
>ArrayLayouts:
>
>* Assuming that the SequenceFeature information is not present already
>  in the DB, the SF info will be taken from the layout file.
>* the spot type for each layout spot (blank, sequence_feature, control)
>* the species to which all the SF belong, or a listing of species on
>  a per-SF basis.

Interesting. This is all in agreement with the specs I was going to detail in my 
Word document.

The Curation Tool cannot do the first step, because we all agreed many moons ago 
not to send the existing USF info over as part of the Control Bundle, due to the 
fear of update implications. The problem is, what if the USF already exists, but 
some of the other USF related information has changed? That requires a 
reconciliation and possibly an update process.

>* a unique identifier for each SF (and we need to add
>  unique_identifier to the SF_Type controlled vocab).

You mean like a USF_ID number? Analogous to the SPOT_ID number concept?

If so, is the point of this to allow referencing of USF's in the Array Layout by 
USF_ID number?

>* a unique identifier for each layout spot

Yep. A real good idea. Makes a great reference ID for the Array Measurement 
files.

Greg