Details
-
Story
-
Status: Open (View Workflow)
-
P3
-
Resolution: Unresolved
-
None
-
None
-
-
5
-
Prokopovych
Description
Purpose: Mark for deletion means that a cataloger, who holds the permission to do Mark instance for deletion, but do not hold the permission to do a deletion, is able to do 'Mark instance for deletion' of any given instance record by setting a boolean check mark in the instance record. Mark instance for deletion is done in the edit view of the instance.
When the instance has been marked for deletion (UIIN-333), then a cataloger colleague with super power and with permission to perform deletion, will go in and filter on all instances being marked for deletion (UIIN-1094), and then delete them one-by-one (and later in bulk edit).
Scope of this ticket is: Mark instance for deletion from the edit view of the instance.
Use case: As a cataloger I want to be able to mark any given instance record for deletion.
Scenarios:
- Scenario
- Scenario
- Scenario
- Scenario
- When the instance is already marked as Suppressed from discovery and Staff suppressed,
- then adding the checkmark Mark for deletion, do not cause any changes to the two check marks set in Suppress from discovery and Staff suppress
- Scenario
- When clicking the Save and close button the edited instance is saved
- Then the user is returned to the detailed view of the instance
- A new warning message will display in the top of the record,
- with the warning icon as an exclamation mark and the text: Warning: Instance is marked for DELETION
- Use capitalization of the word DELETION.
- See UX
- Scenario
- When viewing the detailed record
- Then similar as for Suppressed from discovery and Staff suppressed which are displayed in the instance record
- Then an exclamation mark icon and the text: Marked for deletion will display below the metadata component data, and next to: Staff suppressed (or Previously held, if that has been marked too)
Out of scope:
Check for dependencies related with other apps, e.g. Orders, Receiving app and more. Will create separate jira issues for this when getting to deletion of instances.
Documents:
- Slide deck reviewed by the MM-SIG (6/30/2022): https://docs.google.com/presentation/d/1ePfp0_fK1xW4mfpS6NRIkFwDQEyAvqMPTAlXI8hbxCI/edit#slide=id.p
- * List of use cases gathered by the MM-SIG (10/18/2018) : https://docs.google.com/spreadsheets/d/1XkHDYCfY5Xl7rpcP_MIg5ZAkQrbBfpsQ4rtNTEWSrdE/edit#gid=0
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-3742 Mark instance for deletion. 2nd iteration. Enable the user to mark an instance for deletion
-
- In Refinement
-
- has to be done before
-
MODOAIPMH-268 Deleted OAI/PMH record identifier should be configurable (HRID or UUID)
-
- Open
-
-
UIIN-2102 Inventory. Instance. Marked for deletion. Underlying MARC not editable in quickMARC
-
- Draft
-
-
UIIN-2105 NOT needed (As of now). Instance. Marked for deletion make the instance not editable
-
- Draft
-
- relates to
-
MODINV-411 Back end work. Instance. Mark and un-mark for deletion
-
- Open
-
-
MODINVSTOR-730 Back end work. Instance. Mark and un-mark for deletion.
-
- Open
-
-
UIIN-333 Instance. Action menu: Mark for deletion
-
- Open
-
-
UIIN-1979 Permissions - Inventory. Instance Mark for delete
-
- Blocked
-
- mentioned in
-
Page Loading...