Duplicate
Details
Assignee
UnassignedUnassignedReporter
(OLD ACCOUNT) Erin Nettifee(OLD ACCOUNT) Erin NettifeePriority
P3Development Team
VolarisTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Unassigned
UnassignedReporter
(OLD ACCOUNT) Erin Nettifee
(OLD ACCOUNT) Erin NettifeePriority
Development Team
Volaris
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created September 8, 2022 at 7:55 PM
Updated March 14, 2023 at 3:29 PM
Resolved March 14, 2023 at 3:29 PM
Use case(s): A patron complains that they got an email that all of their items were ready for pickup, but not all of them were there. The library staff member searches for the patron in the requests app, and sees in the Pickup service point location that one of the items is ready for pickup at another service point that was selected by accident.
Current situation or problem:
Currently, the Requests app's Results list has 10 columns:
Request date
Title
Year
Item barcode
Type
Request status
Queue position
Requester
Requester barcode
Proxy
Requirements:
Requests app - Results list: Add a new column for "Pickup service point" and also add to Results List Actions menu > Show Columns list
Below is the Pickup service point field on a Requests detail record
Results List Actions Menu > Show Columns list
Add after Queue position
Default: Uncheck (in other words column does not display on result by default)
any other fields that should be set to not display by default?
Below is a rough mockup
Results List Column display: When user selects this column to display then this column displays between Queue position and Requester columns
should this Pickup service point column be sortable?
In scope
Changes to ui-requests to allow the column to be available for selection in the UI
Out of scope
Changes to the underlying request record
Changes to any reports or search export functionality already built