User Story #2660 (new)
Opened 14 years ago
Last modified 12 years ago
User can query/filter if an object will be deleted. — at Initial Version
| Reported by: | jamoore | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | OMERO-Beta4.2.1 |
| 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
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.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
