Uploaded image for project: 'ui-requests'
  1. ui-requests
  2. UIREQ-63

Refine Request record layout (Create)

    XMLWordPrintable

    Details

    • Template:
    • Analysis Estimate:
      None
    • Back End Estimate:
      Very Small (VS) < 1 day
    • Confidence factor:
      High
    • Estimation Notes and Assumptions:
      Estimate assumes proxy work, locations and other not-yet-existent elements are estimated separately
    • Front End Estimate:
      Medium < 5 days

      Description

      Purpose: To refine the layout and styling of the New request screen in FOLIO to align with decisions by the Resource Access SIG and UX designers

      Scenarios:

      1. Scenario
        • Given New request screen
        • When displayed prior the input of item and requester
        • Then the following sections should appear, as shown in the attached wireframe 1_CreateRequest.png:
          • Request information - Not collapsible
          • Item information - Not collapsible
          • Requester information - Not collapsible
      2. Scenario
        • Given the Request information section on New request screen, prior to input of item and requester
        • When displayed
        • Then the following data elements should appear, as shown in the attached wireframe 1_CreateRequest.png:
          • Request type
          • Request expiration date
      3. Scenario
        • Given the Item information section on New request screen, prior to input of item and requester
        • When displayed
        • Then the following data element should appear, as shown in the attached wireframe 1_CreateRequest.png:
          • [unlabelled field to input item barcode]
      4. Scenario
        • Given the Requester information section on New request screen, prior to input of item and requester
        • When displayed
        • Then the following data element should appear, as shown in the attached wireframe 1_CreateRequest.png:
          • [unlabelled field to input requester barcode]
      5. Scenario
        • Given New request screen
        • When displayed after the input of item and requester
        • Then the following sections should appear, as shown in the attached wireframe 1_CreateRequestProxy.png:
          • Request information - Not collapsible
          • Item information - Not collapsible
          • Requester information - Not collapsible
      6. Scenario
        • Given the Request information section on New request screen, after input of item and requester
        • When displayed
        • Then the following data elements should appear, as shown in the attached wireframe 1_CreateRequestProxy.png:
          • Request type
          • Request expiration date
      7. Scenario
        • Given the Item information section on New request screen, after input of item and requester
        • When displayed
        • Then the following data elements should appear, as shown in the attached wireframe 1_CreateRequestProxy.png:
          • [unlabelled field to input item barcode]
          • Item barcode
          • Title
          • Author
          • Shelving location
          • Call number
          • Volume
          • Enumeration
          • Copy
          • Item status
          • Current due date
          • Requests (the number of active requests on this item)
      8. Scenario
        • Given the Requester information section on New request screen, after input of item and requester, with
          • Fulfillment preference = “Hold shelf”
        • When displayed
        • Then the following data elements should appear, as shown in the attached wireframe 1_CreateRequestProxy-HoldShelf.png:
          • [unlabelled field to input requester barcode]
          • Requester name and Requester barcode
          • Patron group
          • Fulfillment preference
          • Pickup location
          • Requester’s Proxy (if the request is being placed by a proxy on behalf of their sponsor)
      9. Scenario
        • Given the Requester information section on New request screen, after input of item and requester, with
          • Fulfillment preference = “Delivery”
        • When displayed
        • Then the following data elements should appear, as shown in the attached wireframe 1_CreateRequestProxy.png:
          • [unlabelled field to input requester barcode]
          • Requester name and Requester barcode
          • Patron group
          • Fulfillment preference
          • Delivery address
          • Requester’s Proxy (if the request is being placed by a proxy on behalf of their sponsor)

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                mattjlc Matt Connolly
                Reporter:
                taniafersenheim Tania Fersenheim
                Analysis Estimator:
                Tania Fersenheim Tania Fersenheim
                Back End Estimator:
                Marc Johnson Marc Johnson
                Front End Estimator:
                Matt Connolly Matt Connolly
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases