Uploaded image for project: 'ui-inventory'
  1. ui-inventory
  2. UIIN-2105

NOT needed (As of now). Instance. Marked for deletion make the instance not editable

    XMLWordPrintable

Details

    • 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:

      1. 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
      2. 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:

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                charlotte Charlotte Whitt
                Charlotte Whitt Charlotte Whitt
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases