Hierarchy for storing processed image data
Posted: Fri Jun 10, 2011 4:14 pm
We have installed an OMERO server in our department (Oxford Biochemistry / Micron advanced Imaging facility), and have been using the system in anger for a few months now. One of the main gripes we hear from our users is that there appears to be no easy way to associate processed image data with its original source. A very common example is where a user deconvolves wide-field data (which is slow), and wants to keep the source data as well as the deconvolved result. Basically, it seems to us that the current hierarchy lacks one level. The ideal solution for us would be to introduce a "processed image" one level below the raw data (a bit like the way an 'ROI' is currently associated with an 'image' perhaps?) Even better would be for the importer to associate raw and processed data in such a way upon import by using filenames, filters or metadata. One step at a time though.
Although one *could* use a 'Dataset' for each image file, and store various processed versions within the dataset, this is not how we tend to use a dataset - rather, we use a dataset to organize related images (e.g. repeats of the same experiment). However we look at it, one more level in the hierarchy would be extremely useful.
I hope I have described clearly what our problem is - please let me know if it is not clear, or if I have missed a solution in the current implementation.
Thanks & best regards,
Graeme
Although one *could* use a 'Dataset' for each image file, and store various processed versions within the dataset, this is not how we tend to use a dataset - rather, we use a dataset to organize related images (e.g. repeats of the same experiment). However we look at it, one more level in the hierarchy would be extremely useful.
I hope I have described clearly what our problem is - please let me know if it is not clear, or if I have missed a solution in the current implementation.
Thanks & best regards,
Graeme