Requests: Edit v1

Purpose: To begin work on item Requests in FOLIO. Search and filter will be covered in separate stories.

As a circulation staff person
I want to be able to edit a recall request on a loaned item
So I can change key details like expiration date and fulfillment type

Scenarios:

1. Scenario
   • Given the view mode of an existing request (see UIS-44 for details)
   • When displayed
   • Then the "Edit" button should be displayed as shown in the attached wireframes
2. Scenario
   • Given the Edit button
   • When clicked
   • Then the edit Request form should display as shown in the attached wireframes (scenarios below indicate what is in/out of scope from the wireframes)
3. Scenario
   • Given the Request Type field
   • When displayed
   • Then it is read-only (cannot change the request type for an existing request)
4. Scenario
   • Given the Item field in the "Item info" section of the create/edit request form
   • When displayed
   • Then it is read-only (cannot change the item for an existing request)
5. Scenario
   • Given a selected item
   • When displayed on the edit request form
   • Then the following data should display:
     • Item barcode - Link to view item record CB: The link is failing now. The link takes you to an undefined space in Items which doesn't display the record and throws an error when you try to right click and open in new tab. ERROR: in module @folio/items, operation GET on resource 'selectedItem' failed, saying: Not Found This is working as of 2/28/18 PDW
     • Item title - Will add link to view title record when we have title records in FOLIO. For now just plain text.
     • Shelving location - Temporary shelving location, if available, else permanent shelving location CB: This isn't actually displaying location right now but that's fine since that functionality is still in development. We'll come back in and update requests later when that's ready.
     • Loaned to - User to whom this item is currently on loan. Link to user record.
     • Patron group - Patron group for user to whom this item is currently on loan
     • Status - Item status
   • Out of scope for this story (will be added later when this data is available in FOLIO): Author, Call Number, Volume, Copy, Enumeration, Current Due Date and Number of Requests
6. Scenario
   • Given the Requester field in the "Requester info" section of the edit request form
   • When displayed
   • Then it is read-only (cannot change the requester for an existing request)
7. Scenario
   • Given the "Requester info" section of the edit request form
   • When displayed
   • Then Fulfillment Preference should be editable
   • Out of scope for this story: Pickup location (will be added later when we have location CRUD)
8. Scenario
   • Given the Request Details section
   • When displayed
   • Then the following data should be editable:
     • Request expiration date - Date picker (should be locale-responsive)
     • Hold shelf expiration date - Date picker (should be locale-responsive)
9. Scenario
   • Given the edit request form
   • When displayed
   • Then a "Update request" button should displayed as shown in the wireframe
10. Scenario CB: Getting some weird invalid date problems. I'll submit a separate issue for that: UIREQ-35
    • Given the "Update request" button on a request form
    • When clicked
    • Then:
      • Request should be saved
      • View/preview mode of the request details should be displayed (UIS-44 has details)
11. Scenario CB: This is broken now. I am finding that if I simply open a record edit page and then close it again (using the X in the upper left) I am getting the unsaved changes modal. This happens even when I haven't made any changes. It's intermittent and only seems to happen on the edit page.
    • Given the edit request form with unsaved data
    • When I navigate away to another part of FOLIO
    • Then the unsaved changes notification should display
12. Scenario
    • Given the Request Type, Requester Info and Item Info labels
    • When displayed on the edit form
    • Then an asterisk should not display since the required data has already been supplied