Task #1187 (closed)
Opened 15 years ago
Closed 12 years ago
Shares should store graphs and not flat objects
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | major | Milestone: | OMERO-4.4 |
| Component: | API | Version: | 3.0-M1 |
| Keywords: | n.a. | Cc: | atarkowska |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
The current IShare stores objects as rows rather than graphs. Either this should change to storing graphs, or both should be supported. For example,
ishare.addObject( datasetWithImage ) list = ishare.getContents()
The size of list is 3 since it flattens datasetWithImage into dataset, link, image.
See #1172 for more info
Change History (4)
comment:1 Changed 15 years ago by jmoore
comment:2 Changed 14 years ago by jmoore
comment:3 Changed 14 years ago by jmoore
- Type changed from User Story to Task
comment:4 Changed 12 years ago by jmoore
- Milestone changed from Unscheduled to OMERO-Beta4.4
- Resolution set to fixed
- Status changed from new to closed
For some limited cases (images) this is already the case. I'm closing this as "fixed" since all of our current use cases seem to be covered (correct me if I'm wrong, Ola). Note, however, that it doesn't do this by actually flattening the list on write, but rather on querying for linkage on read.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
When doing this conversion, care should also be taken to keep the sharedata consistent, especially with regards to all items being unique in both map, list and then graph.