Task #12237 (new)
Opened 10 years ago
Last modified 6 years ago
Bug: LIFReader: Original metadata regression from 4.4
Reported by: | rleigh | Owned by: | jburel |
---|---|---|---|
Priority: | minor | Milestone: | Unscheduled |
Component: | Bio-Formats | Version: | 5.0.0 |
Keywords: | LIFReader our-fault | Cc: | pierre.pouchin@… |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | n.a. |
Description
See: https://www.openmicroscopy.org/community/viewtopic.php?f=13&t=7503
Reproducible with: leica-lif/chris/free edge 6.lif
Several original metadata keys in 4.4 are squashed to a single key in 5.x. This looks like it's due to the switch to using addSeriesMetadataList; looks like some keys end up using addSeriesMetadata when they should be using addSeriesMetadataList. Looks like a single conditional at fault, but not sure at first glance how to best adjust it to restore the previous behaviour.
Change History (10)
comment:1 Changed 10 years ago by rleigh
- Component changed from General to Bio-Formats
- Owner set to mlinkert
comment:2 Changed 10 years ago by jburel
- Keywords LIFReader our-fault added
comment:3 Changed 9 years ago by mlinkert
- Milestone changed from Unscheduled to 5.1.1
comment:4 Changed 9 years ago by jburel
- Owner changed from mlinkert to jburel
To be discussed with Roger, I have fixed issue reported in #12741 + some encoding problem noticed.
comment:6 Changed 9 years ago by jamoore
- Milestone changed from 5.1.4 to B-F-5.1.4
Splitting 5.1.4 due to milestone decoupling
comment:7 Changed 9 years ago by sbesson
- Milestone changed from B-F-5.1.4 to BF-5.1.5
comment:8 Changed 8 years ago by mlinkert
See http://lists.openmicroscopy.org.uk/pipermail/ome-users/2016-January/005805.html and file in inbox/leica-lif/ for an example that exhibits the Laser Line issue.
comment:9 Changed 8 years ago by sbesson
- Milestone changed from B-F-5.2.0 to Unscheduled
comment:10 Changed 6 years ago by sbesson
See also https://www.openmicroscopy.org/community/viewtopic.php?f=13&t=8422 and QA 18854 for another report of this issue.
Moving to 5.1.1 for triage.