<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Hi Michael<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 16 Aug 2017, at 11:05, Michael Ellis <<a href="mailto:michael.ellis@dsuk.biz" class="">michael.ellis@dsuk.biz</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Dear all,<br class="">
<br class="">
ITAC?= Is This Assumption Correct?<br class="">
IJBFIIP = ImageJ BioFormats Image Importer Plugin<br class="">
<br class="">
I am at a loss, can you point me in the right direction?<br class="">
<br class="">
Sometime back I submitted a pull request on the IJBFIIP so that image slice labels could be set from channel names stored within .OME.TIFF files.<br class="">
<br class="">
I was informed this pull request would be shelved as it amounted to a functional change and not just a bug fix.<br class="">
<br class="">
Eventually I was pointed at using Trello and to follow the Bio-Formats 5.6.0 board. This I did and added some further comments in relation to the proposed final solution.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>For full reference, the design discussion took place in [1] and the proposed implementation is available in [2].</div>
<div><br class="">
</div>
<blockquote type="cite" class="">
<div class="">
<div class="">I sit, i wait, I soldier on with my own patch to the IJBFIIP.<br class="">
<br class="">
Yesterday I see that the Trello Bio-Formats 5.6.0 board is closed and I do not know where to go to track what is happening to the proposed changes for the next major release?<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>We had certainly planned to include this feature as part of 5.6.0. Unfortunately, the last</div>
<div>round of reviews were not meeting all quality criteria. Thus we decided to postpone the</div>
<div>delivery of this feature to an upcoming patch release of Bio-Formats 5.6.x.</div>
<div><br class="">
</div>
<div>At this stage, subscribing to the open Pull Request is certainly the best option to track</div>
<div>changes. Once merged, they will be included in the following release of Bio-Formats.</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div class="">Further, I am implementing a computer assisted microscope package (SmartCapture 4), I’ve chosen to use the BioFormats.jar package and save in OME.TIF format as this is a nigh on perfect match for our requirements of being able to save 5D images
will instrument and experiment metadata - Yipee!<br class="">
<br class="">
My intention is for SmartCapture 4 to hand off image processing to other applications, principally ImageJ/Fiji and our own SmartType karyotyping application. Transferring images as OME.TIF files is ideally suited.<br class="">
<br class="">
However, I do have further observations in respect of the IJBFIIP that I would at least like to put forward without feeling they these requests just disappear into the wind.<br class="">
<br class="">
Specifically,<br class="">
<br class="">
If the .OME.TIF file format is considered the most complete or canonical image file format for OME metadata (ITAC?) then it would seem at least desirable that the IJBFIIP utilise as much metadata from .OME.TIF files as possible (for instance channel colour
as well as channel name).<br class="">
<br class="">
I do see that there is a potential for semantic mismatches or ambiguities in how some metadata might be used, but even if only a part of the metadata is used to set ImageJ ImagePlus image properties, should not *all* the metadata be accessible *after* the IJBFIIP
has completed the import?</div>
</div>
</blockquote>
<blockquote type="cite" class=""><br class="">
</blockquote>
<blockquote type="cite" class="">
<div class="">
<div class="">The argument that I can patch IJBFIIP and do whatever I want seems a weak one. If I have to patch the IJBFIIP, I am burdened with having to track and merge all of your changes (as will anyone else wanting something extra from the metadata).<br class="">
<br class="">
My suggestion (is this already possible?), is that the IJBFIIP provides a mechanism for accessing the metadata for any ImageJ ImagePlus that has been imported by the IJBFIIP.<br class="">
<br class="">
If (as I suspect) there is no hook on an ImagePlus for hanging the XML metadata, then perhaps this could be hived off into a file and reference to that file could be attached to the ImagePlus? I’d then at least be able to write my own ImageJ plugins that could
inspect an ImagePlus, determine if it had associated OME data and use the BioFormats.jar library to gain access to the extra metadata without having to have my own version of the IJBFIIP.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>With regard to the hook for the metadata, the Bio-Formats ImageJ plugins populate</div>
<div>the FileInfo of the created ImagePlus objects with various information including</div>
<div>the metadata in the description attribute.</div>
<div><br class="">
</div>
<div>With the current version of the plugin, you should be able to inspect the metadata</div>
<div>using the ImagePlus.getOriginalFileInfo() API [3]. In the OME-TIFF case, the description</div>
<div>attribute should include the metadata that is also stored in the ImageDescription tag of</div>
<div>the file.</div>
</div>
<div><span class=""><br class="">
</span></div>
<div>
<blockquote type="cite" class="">
<div class="">
<div class="">I really want to make use of BioFormats, it’s such a perfect match for our needs. But, having IJBFIIP filter our so much of the metadata seems just counter intuitive if, as I suspect, ImageJ is the most widely used application for reading OME.TIF
files?<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>Putting precise numbers on the usage of individual file formats is always challenging</div>
<div>but it is correct that from our perspective, the ImageJ/Fiji ecosystem certainly remains</div>
<div>one of the most important community where Bio-Formats is consumed.</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div class="">With best regards to all — Michael Ellis<br class="">
Digital Scientific UK Ltd<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
Best,</div>
<div>Sebastien</div>
<div><br class="">
</div>
<div>[1] <a href="https://trello.com/c/KHxM1IIe/1-imagej-imageplus-slicelabel-modification" class="">https://trello.com/c/KHxM1IIe/1-imagej-imageplus-slicelabel-modification</a> </div>
<div>[2] <a href="https://github.com/openmicroscopy/bioformats/pull/2891" class="">
https://github.com/openmicroscopy/bioformats/pull/2891</a></div>
<div>[3] <font color="#0069d9" class=""><u class=""><a href="https://imagej.nih.gov/ij/developer/api/ij/ImagePlus.html#getOriginalFileInfo--" class="">https://imagej.nih.gov/ij/developer/api/ij/ImagePlus.html#getOriginalFileInfo--</a></u></font></div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">
<div class=""><br class="">
_______________________________________________<br class="">
ome-devel mailing list<br class="">
<a href="mailto:ome-devel@lists.openmicroscopy.org.uk" class="">ome-devel@lists.openmicroscopy.org.uk</a><br class="">
http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-devel<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
<br>
<span style="font-size:10pt;">The University of Dundee is a registered Scottish Charity, No: SC015096</span>
</body>
</html>