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

Refine Request record layout (Edit and View)

    XMLWordPrintable

Details

    • None
    • Very Small (VS) < 1 day
    • High
    • Estimate assumes proxy work, locations and other not-yet-existent elements are estimated separately
    • Medium < 5 days

    Description

      Purpose: To refine the layout and styling of the Request detail screen in View and Edit modes to align with decisions by the Resource Access SIG and UX designers

      Scenarios:

      1. Scenario
        • Given Request detail screen
        • When displayed in View mode
        • Then the following sections should appear, as shown in the attached wireframe 2_RequestDetailProxy.png:
          • Request information - Collapsible, open by default
          • Item information - Collapsible, open by default
          • Requester information - Collapsible, open by default
      2. Scenario
        • Given Request information section
        • When displayed in View mode
        • Then the following data elements should appear, as shown in the attached wireframe 2_RequestDetailProxy.png:
          • Record last updated
          • Request type
          • Request status
          • Request expiration date
          • Hold shelf expiration date (see note)
          • Position in queue (request's position in its item's request queue, see note)
      3. Scenario
        • Given Item information section
        • When displayed in View mode
        • Then the following data elements should appear, as shown in the attached wireframe 2_RequestDetailProxy.png:
          • Item barcode
          • Title
          • Author
          • Shelving location
          • Call number
          • Volume
          • Enumeration
          • Copy
          • Item status
          • Current due date (see note)
          • Requests (the number of open requests on this item)
      4. Scenario
        • Given Requester information section with
          • Fulfillment preference = “Hold shelf”
        • When displayed in View mode
        • Then the following data elements should appear, as shown in the attached wireframe 2_RequestDetailProxy.png:
          • 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)
      5. Scenario
        • Given Requester information section with
          • Fulfillment preference = “Delivery”
        • When displayed in View mode
        • Then the following data elements should appear, as shown in the attached wireframe 2_RequestDetailProxy.png:
          • 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)
      6. Scenario
        • Given Request detail screen
        • When displayed in Edit mode
        • Then the following sections should appear, as shown in the attached wireframe 3_EditRequestProxy.png:
          • Request information - Collapsible, open by default
          • Item information - Collapsible, open by default
          • Requester information - Collapsible, open by default
      7. Scenario
        • Given Request information section
        • When displayed in Edit mode
        • Then the following data elements should appear, as shown in the attached wireframe 3_EditRequestProxy.png:
          • Record last updated
          • Request type (not editable)
          • Request status (not editable)
          • Request expiration date (editable)
          • Hold shelf expiration date (editable, see note)
          • Position in queue (request's position in its item's request queue, see note) (not editable)
      8. Scenario
        • Given Item information section
        • When displayed in Edit mode
        • Then the following data elements should appear, as shown in the attached wireframe 3_EditRequestProxy.png:
          • Item barcode (not editable)
          • Title (not editable)
          • Author (not editable)
          • Shelving location (not editable)
          • Call number (not editable)
          • Volume (not editable)
          • Enumeration (not editable)
          • Copy (not editable)
          • Item status (not editable)
          • Current due date (not editable), see note
          • Requests (the number of open requests on this item) (not editable)
      9. Scenario
        • Given Requester information section with
          • Fulfillment preference = “Hold shelf”
        • When displayed in Edit mode
        • Then the following data elements should appear, as shown in the attached wireframe 3_EditRequestProxy.png:
          • Requester name and Requester barcode (not editable)
          • Patron group (not editable)
          • Fulfillment preference (editable)
          • Pickup location (editable)
          • Requester’s Proxy (if the request is being placed by a proxy on behalf of their sponsor) (not editable)
      10. Scenario
        • Given Requester information section with
          • Fulfillment preference = “Delivery”
        • When displayed in Edit mode
        • Then the following data elements should appear, as shown in the attached wireframe 3_EditRequestProxy.png:
          • Requester name and Requester barcode (not editable)
          • Patron group (not editable)
          • Fulfillment preference (editable)
          • Delivery address (editable)
          • Requester’s Proxy (if the request is being placed by a proxy on behalf of their sponsor) (not editable)

      NOTE: Hold shelf expiration date in View mode should only display data if the Request status = “Open - Awaiting pickup”
      NOTE: Hold shelf expiration date in Edit mode should only display data and be editable if the Request status = “Open - Awaiting pickup”
      NOTE: Position in queue - out of scope for this story
      NOTE: Current due date should only display data if the item is currently “Checked out”, “Checked out - Held”, or “Checked out - Recalled”

      TestRail: Results

        Attachments

          1. 2_RequestDetailProxy.png
            154 kB
            Tania Fersenheim
          2. 3_EditRequestProxy.png
            127 kB
            Tania Fersenheim
          3. HoldShelfExpiryDate.PNG
            26 kB
            Tania Fersenheim

          Issue Links

            Activity

              People

                mattjlc Matt Connolly
                taniafersenheim Tania Fersenheim
                Tania Fersenheim Tania Fersenheim
                Marc Johnson Marc Johnson
                Matt Connolly Matt Connolly
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases