User Story #2660 (new)
Opened 14 years ago
Last modified 12 years ago
User can query/filter if an object will be deleted.
| Reported by: | jamoore | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | General | Keywords: | n.a. |
| Cc: | jburel, cxallan, developer | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | 4.0d | Estimated Remaining Time: | n.a. |
Description (last modified by jmoore)
Since deleting some objects takes a significant amount of time, an intermediate "delete queue" should be track which objects are up for deletion.
There should be some way to filter out objects which are so marked, or to explicitly list them so clients can warn about/prevent unnecessary modifications.
Possible pieces of an implementation:
- A flag on top-level containers in the DB
- An in-memory collection
There are many chances for stale state and work arounds, so this isn't an attempt to completely prevent the loss of changes, but to minimize the surprises for the user.
See also: #2674 "Either via EventLogs? or some other report object, users should be able to track what was deleted at a given time...after moving an image out of a group, various links may need to be broken. If the image is moved back, it may make sense to offer to re-create those links."
Change History (2)
comment:1 Changed 14 years ago by jmoore
- Cc developer added
- Milestone changed from OMERO-Beta4.2.1 to Unscheduled
comment:2 Changed 12 years ago by jmoore
- Description modified (diff)
Moving out of 4.2.1 as discussed during Sep.2 mtg