User Story #3542 (new)
Opened 9 years ago
Last modified 18 months ago
Support exporting what was originally imported
| Reported by: | jamoore | Owned by: | |
|---|---|---|---|
| Priority: | critical | Milestone: | Usability Backlog |
| Component: | Export | Keywords: | n.a. |
| Cc: | mtbcarroll | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | 5.0d | Estimated Remaining Time: | n.a. |
Description (last modified by cxallan)
All methods of IMetadata should be implemented in the server to support an exhaustive metadata graph. This will also have to include queries to load relevant OMERO model objects.
The current OmeroReader implementation makes use of hand written methods getChannel(), getImage() etc to implement all of the other IRetrieve methods. If those methods are pushed into GraphState (see #3628) and if a hand-written layer exists to convert OMERO objects to OME-XML objects, then a code-generated layer can be used to fill out all of OmeroReader, along with many other uses.
Change History (7)
comment:1 Changed 9 years ago by jburel
- Description modified (diff)
comment:2 Changed 8 years ago by cxallan
- Milestone changed from OMERO-Beta4.3 to Unscheduled
comment:3 Changed 8 years ago by cxallan
- Component changed from General to Export
- Description modified (diff)
comment:4 Changed 8 years ago by cxallan
- Description modified (diff)
comment:5 Changed 8 years ago by saloynton
- Milestone changed from Unscheduled to Usability Backlog
comment:6 Changed 6 years ago by jamoore
- Priority changed from minor to critical
comment:7 Changed 18 months ago by mtbcarroll
- Cc mtbcarroll added; saloynton removed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Also see https://trello.com/c/FjKjbzio/18-generate-omerometadata.