[ome-devel] Customizing import process

[Ilya Goldberg]

There is support for MetaMorph's HTDF in the OME back-end, which uses a 
companion text-file to describe a collection of tiff images.  You can 
use a similar approach with a "customized" back-end importer.  Kevin's 
approach sounds like a better solution, but if you want something easy 
in the interim, a companion text file is probably easiest.

-I

On Nov 22, 2004, at 9:41 AM, Kevin W Eliceiri wrote:

> Hi Richard,
>
> We have done some programming with ImagePro 4.5 and it is possible to
> customize the saving options with its Software development kit
> (http://www.mediacy.com/sdkpg.htm). We used this to create custom
> acquisition windows and I think it can be used to write additional
> metadata to the .tiff header. ImagePro 5 has a new SDK out, so if you
> haven't started programming in 4.5 I would use this. The ImagePro
> support people should be able to help you with writing custom fields to
> the tiff file or just dumping to a custom companion text file that 
> could
> be parsed by the OME importer.
>
> Our group is working on a JAVA OME XML writer that can be interfaced to
> acquisition programs to write a fully compliant OME XML file. We plan 
> on
> making this available when finished in about a month. This would allow
> you to write directly to OME XML from ImagePro (you would need to write
> a native library in ImagePro using the SDK to interface with the XML
> writer).
>
> Best regards,
> kevin
>
> Kevin W. Eliceiri
> Assistant Director
> Laboratory for Optical and Computational Instrumentation
> http://www.loci.wisc.edu
> Room 271 Animal Sciences
> 1675 Observatory Drive
> Madison, WI 53706
> Phone: 608-263-6288
> Fax: 608-262-4570
>
> ----- Original Message -----
> From: Richard Beare <Richard.Beare at csiro.au>
> Date: Sunday, November 21, 2004 11:45 pm
> Subject: [ome-devel] Customizing import process
>
>> Hi Everyone,
>>
>> I'm wondering what you might recommend in the following scenario.
>> We are
>> capturing images using image pro. These are being saved as tifs and
>> can
>> be imported without any problems by the default tif importer. I'm
>> wondering how best to get the meta data imported as well. The
>> options I
>> can imagine are
>>
>> 1) mimicing a proprietary format.
>>
>> 2) Writing a meta file associated with each tif and having a custom
>> import mechanism (or is there something already supporting this
>> approach)
>> 3) Perhaps an xml file can reference the tif while containing the
>> rest
>> of the meta data.
>>
>> The problem is that the meta data isn't yet associated with the tif
>> file. We have a fair bit of freedom about how we might do this
>> (although
>> tif tags  seem a bit trick from image pro).
>>
>> What is your experience with this sort of thing?
>>
>> Thanks
>>
>> -- 
>> Richard Beare, CSIRO Mathematical & Information Sciences
>> Locked Bag 17, North Ryde, NSW 1670, Australia
>> Phone: +61-2-93253221 (GMT+~10hrs)  Fax: +61-2-93253200
>>
>> Richard.Beare at csiro.au
>> _______________________________________________
>> ome-devel mailing list
>> ome-devel at lists.openmicroscopy.org.uk
>> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel
>>
> _______________________________________________
> ome-devel mailing list
> ome-devel at lists.openmicroscopy.org.uk
> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel
>