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

Holdings record. Delete (only) - first phase

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      Core: F - Sprint 60, Core: F - Sprint 61, Core: F - Sprint 62
    • Story Points:
      8
    • Development Team:
      Prokopovych

      Description

      Purpose: Implementing the paneheader action menu component, and work on deletion of a holdings record

      As a cataloger I want to be able to delete any given holdings record. Deletion is only possible, if there is no items records associated with the holdings record.

      Scenarios:

      1. Scenario
        • Go to FOLIO snapshot stable http://folio-snapshot-stable.aws.indexdata.com/ and click on Inventory
        • Given any instance record with associated holdings records
        • When viewing the holdings record which is to be deleted
        • Then an arrow down next to the Pane header title is shown - see wireframe
      2. Scenario
        • when clicking on the arrow
        • then a drop-down actions menu should display as shown in wireframe
        • the action menu items are listed in alphabetic order
        • Following actions will be in scope of this story:
          • Delete holdings
      3. Scenario
        • Given a "Delete" holdings option in the actions drop-down
        • When clicked
        • Then a 'Confirm delete holdings' modal should appear as shown in wireframe
        • NOTE: Similar feature is implemented in The Cancel Request modal.
      4. Scenario
        • Given the 'Confirm delete holdings' modal
        • When displayed and
          • if no items records are associated with the holdings record
          • if no dependencies with other apps, here, e.g. Order app, then cataloger gets following message
        • "Holdings HRID [*the given Holdings HRID*] with location [*the given location*] has no items associated or other dependencies and will be deleted.
        • And then the cataloger can decide to go 'Cancel' or 'Delete'.
      5. Scenario
        • Given a click on the 'Cancel' button
        • Then the action is terminated
        • The cataloger gets back to the detailed view of the given holdings record
      6. Scenario
        • Given a 'Delete" button on the 'Confirm delete holdings' modal
        • When clicked
        • Then the delete action is performed
        • The holdings record is being deleted
      7. Scenario - Story moved to separate jira: UIIN-550
        • Given the 'Confirm delete holdings' model
        • When displayed and there are one or more item records associated with the holdings record, then the cataloger gets following message
        • if one item record
          • "[*the given Holdings HRID] with location [*the given location*] has one item record associated. To be able to continue deletion of this holdings record, then the associated item record must be deleted"
          • And the cataloger will not be able to perform the the delete action, before the associated item record is deleted.
        • if more than one item record
          • "[*the given Holdings HRID] with location [*the given location*] has [*number*] item records associated. To be able to continue deletion of this holdings record, then all associated item records must be deleted"
          • And the cataloger will not be able to perform the the delete action, before the associated item records are deleted.
        • at the bottom of the modal is a button 'Cancel'
      8. Scenario
        • Given a "Cancel" button on the delete record modal
        • When clicked
        • Then the Delete record modal will close and the deletion will be cancelled
        • And the cataloger get back to detailed view of the holdings record

      Note:

      1. Other actions, as Edit of the holdings record, and Duplicate of the holdings record are not in scope of this story - see: STCOM-353.
      2. Following dependencies is to be examined for Q2 2019:
        • Check out app
        • Request app
        • Order app
      3. A comprehensive list of all future dependencies is to be defined, and check for these to be implemented when these dependencies exist.
      4. In a later phase, will be implemented for catalogers with special permission to perform deletion - also in cases with associated item records
      5. In a later phase a 'waste basket' will be implemented, for catalogers to regret the performed deletion, and pull the record back into the collection

      The action menu will be updated according to UX consistency fixes - see UIIN-524.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                nielserik Niels Erik Gilvad Nielsen
                Reporter:
                charlotte Charlotte Whitt
                Tester Assignee:
                Charlotte Whitt Charlotte Whitt
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases