User Story #8341 (new)
Opened 12 years ago
Last modified 8 years ago
OME formats downgrade in B-F
| Reported by: | jburel | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | GatherReqs |
| Component: | General | Keywords: | schema |
| Cc: | jamoore, cxallan, ajpatterson, mlinkert | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
Currently the downgrade of OME-TIFF/OME-XML has been implemented in insight for 4.4, main reason was to disrupt as little as possible. The worflow is a follow:
- parse the catalog file from specification.jar
- display the possible downgrade e.g. 2010-06 and the quality of the downgrade.
- When a version is selected, generate a current OME-TIFF and downgrade by applying the sequence of stylesheets.
When a new version of the schema is released, a new entry will be added to the catalog.
Change History (3)
comment:1 Changed 12 years ago by jburel
- Milestone changed from OMERO-Beta4.4.1 to OMERO-Beta4.5
comment:2 Changed 11 years ago by ajpatterson
- Keywords schema added
comment:3 Changed 8 years ago by jamoore
- Cc changed from jamoore,cxallan, ajpatterson, mlinkert to jamoore, cxallan, ajpatterson, mlinkert
- Milestone changed from 5.x to GatherReqs
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
The export related work is part of the model-omero alignment.