Details
-
Story
-
Status: Draft (View Workflow)
-
P3
-
Resolution: Unresolved
-
None
-
None
-
-
Prokopovych
Description
Purpose: When an instance has been marked for deletion (UIIN-1504) then this instance should not be editable except for un-marking the Marked for deletion flag. This behavior is consistent with that the Mark for deletion marking makes the MARC record in quickMARC not editable, and the MARC in SRS can not be overlaid by any Data Import jobs etc.
Scope of this ticket is: An instance being Marked for deletion can not be edited - except the check box Mark for deletion, where it's possible to un-mark the marked for deletion flag (UIIN-2099).
At the MM-SIG meeting 6/30 we did talk about that editing the Tags associated with the instance would not be blocked. There is two reasons behind that: 1) the Tags component is an app on it's own, and 2) the SMEs could see, that there could be situations where the libraries would like to asign a tag label to this kinds of records. We hav to take into considerations that libraries do have individual work flows.
Use case: As a cataloger I want to prevent any unintentional updates of an marked for deletion instance.
Scenarios:
- Scenario
- Go to FOLIO snapshot as user diku_admin,
- Go to Inventory
- Given any instance record with instance source = FOLIO and being Marked for deletion
- When displayed in edit view
- Then all data properties (except one - see below) are being in a blocked/frozen/not editable state (the look will be similar to how data elements being blocked by having an underlying MARC record in SRS),
- the only editable property is the check box Mark for deletion, where the check mark can be un-checked
- Scenario
- Given any instance record with instance source = MARC and being Marked for deletion
- When displayed in edit view in Inventory
- Then all properties (except one - see below) are being in a blocked/frozen/not editable state (the look will be similar to how data elements being blocked by having an underlying MARC record in SRS)
- the only editable property is the check box Mark for deletion, where the check mark can be un-checked
- See UX where the orange box mark those elements we need to make blocked/frozen/not editable now, which is not blocked/frozen/not editable in the regular situation with underlying MARC record in SRS
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
- has to be done after
-
UIIN-1504 Instance. Flag is set for Mark for deletion (edit/detailed view)
-
- Open
-
- 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
-
- 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...