Ticket #148 (closed defect: fixed)
Opened 2007-06-21T08:25:47-05:00
Last modified 2007-06-29T13:37:54-05:00
Do something about large quantities of metadata
| Reported by: | melissa | Owned by: | melissa |
|---|---|---|---|
| Priority: | critical | Milestone: | |
| Component: | bio-formats | Severity: | |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
We have several recently acquired datasets that have more metadata than Bio-Formats can handle. In some cases, this means 150+ MB of metadata alone; while this is OK when working on the command line, trying to import in ImageJ becomes a nightmare (especially since the importer feeds an OMEXMLMetadataStore to ImageReader, effectively doubling the amount of space needed to store metadata).
Ideally, we should come up with a solution that significantly reduces the amount of space required to store metadata, but doesn't require us to leave out any of the key/value pairs currently being stored.
Change History
comment:1 Changed 2007-06-29T13:37:54-05:00 by melissa
- Status changed from new to closed
- Resolution set to fixed
r2922 disables automatic population of OriginalMetadata nodes in OMEXMLMetadataStore. For now, this solves the problem - when using ImageJ, the amount of memory needed for metadata is halved.