[ome-devel] Bug 274 : Incremental Import

Jason Swedlow jason at lifesci.dundee.ac.uk
Tue Aug 31 14:43:54 BST 2004


Josh-

Can you define use case-- specifically, what is the amount of data at 
the point the user wants to evaluate progress, and what is the final 
amount of data.  We will need to be convinced that a simple visual 
client running locally at the evaluation point is insufficient for this 
to convince us to substantially change OME design and principles.  I 
understand the importance of saving (and collecting) only useful data.  
But OME is fundamentally not a filesystem.  It is a data warehouse.  
There are very good reasons not restrict data deletion..  However, we 
need to be able fix botched imports ("Oooops, I just imported the whole 
filesystem").  Note that there are many legal requirements that argue 
against deletion of primary electronic data 
(http://www.fda.gov/ora/compliance_ref/part11/).

Anyway, give us some details and let us work this out.  We have 
discussed this at length for the last 3 years and have various ideas we 
are thinking of implementing.  Any comments from other sites?

Cheers,

Jason


On 30 Aug 2004, at 13:57, Joshua Moore wrote:

> Ok, guys and gals,
>
> You knew it was coming. Now that Arpun et al. have come up with such a 
> nice Tiff import solution, we're clamoring for more: specifically 
> incremental imports.
>
> I mentioned this earlier and hope we can return to the discussion. Our 
> use case is thus:
>
>    Members of our project are using LabView 
> (http://www.ni.com/labview) to automate their microscopy. Eventually 
> they will be capturing in a single run several thousand wells over 
> several days. They will be using OME as their final repository and 
> want to free themselves as much as possible from their filesystem.
>
>    For this they need to import roughly in real-time; that is, they 
> must import the first time period of images, view them through OME 
> software, decide whether or not the images will be "viable", and if 
> not, inform LabView to no longer image that well.
>
> I've include possibilites for this mentioned by Ilya on the list on 
> the bug page (http://bugs.openmicroscopy.org.uk/show_bug.cgi?id=274)
>
> Best wishes,
> Josh.
> _______________________________________________
> ome-devel mailing list
> ome-devel at lists.openmicroscopy.org.uk
> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel
>

NOTE NEW EMAIL ADDRESS: jason at lifesci.dundee.ac.uk
**************************
MSI/WTB Complex
The University of Dundee
Dow Street
Dundee  DD1 5EH
United Kingdom

phone (01382) 345819
Intl phone:  44 1382 345819
FAX   (01382) 348072
email: jason at lifesci.dundee.ac.uk

Lab Page: http://www.dundee.ac.uk/lifesciences/swedlow/
Open Microscopy Environment: http://www.openmicroscopy.org
**************************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 2868 bytes
Desc: not available
Url : http://lists.openmicroscopy.org.uk/pipermail/ome-devel/attachments/20040831/efe2f0a6/attachment.bin


More information about the ome-devel mailing list