Ticket #556 (closed defect: fixed)
Opened 2010-09-10T17:18:24-05:00
Last modified 2010-10-25T14:23:21-05:00
OME-TIFF reader should use MetadataOnly rather than BinData
Reported by: | curtis | Owned by: | melissa |
---|---|---|---|
Priority: | minor | Milestone: |
|
Component: | bio-formats | Severity: | serious |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
When producing an output OME-XML block, the OME-TIFF reader should inject a MetadataOnly element rather than using a BinData with Length="0".
(In [6978]) OMETiffReader now populates its' MetadataStore in such as way as to produce valid OME-XML (hopefully). BinData elements are not populated; instead, a MetadataOnly element is inserted under any Pixels that do not have at least one TiffData. See #556.
The only problem with this is that OMETiffReader.getMetadataStore() no longer returns a MetadataStore that can be used with an IFormatWriter (assuming, of course, that an IMetadata was passed to setMetadataStore). The current solution is a new OMETiffWriter API method: 'MetadataStore getMetadataStoreForConversion()'. This will return a MetadataStore of the same type as 'getMetadataStore()', but that contains the required BinData elements.