Requests (UXPROD-790)

[UXPROD-3758] Add "Pickup service point" as column in Requests app Created: 26/Jul/22  Updated: 30/Nov/23  Resolved: 13/Feb/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Poppy (R2 2023)
Parent: Requests

Type: New Feature Priority: P3
Reporter: Erin Nettifee Assignee: Stephanie Buck
Resolution: Duplicate Votes: 0
Labels: resourceaccess, ui-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Duplicate
is duplicated by UXPROD-4061 Requests: Add optional columns to res... Closed
Release: Poppy (R2 2023)
Epic Link: Requests
Front End Estimate: Small < 3 days
Front End Estimator: Stephanie Buck
Front-End Confidence factor: 70%
Back End Estimate: Out of scope
Back End Estimator: Stephanie Buck
Development Team: Vega
PO Rank: 0
Rank: Cornell (Full Sum 2021): R1

 Description   

Current situation or problem:

Currently, the requests app has 10 columns:

  • Request date
  • Title
  • Year
  • Item barcode
  • Type
  • Request status
  • Queue position
  • Requester
  • Requester barcode
  • Proxy

It would help some libraries to be able to add a column for "Pickup service point" in between Position and Requester. It should be unchecked by default.

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

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.

Proposed solution/stories

Links to additional info

Questions



 Comments   
Comment by Khalilah Gambrell [ 06/Sep/22 ]

Erin Nettifee  - what position should we place this column?

Comment by Erin Nettifee [ 06/Sep/22 ]

I'll ask in the RA channel, we didn't discuss this as a feature at the SIG prior to me putting this in, since it seemed simple, but that means we missed that, sorry!

Comment by Erin Nettifee [ 06/Sep/22 ]

SIG feedback supports adding it after Position and before Requester - I will update the body of the ticket.

Comment by Stephanie Buck [ 06/Feb/23 ]

Hi Erin Nettifee. There is the dropdown box for Pickup service point. Is this ticket to add a column in results in addition to the filter in the left sidebar? 

 

Comment by Erin Nettifee [ 06/Feb/23 ]

Yes - the use case is to see the pickup location in the results list so we would want the option to have a column in addition to the filter. It could be unchecked by default if screen space is a concern.

Comment by Stephanie Buck [ 06/Feb/23 ]

Thanks!

Comment by Stephanie Buck [ 08/Feb/23 ]

Erin Nettifee, another question. Should a User be able to enter part of a Pickup service point into the search box and see results with all Pickup service points that contain that part? For example, if a user only remembers part of a Pickup service point name, like they know it's Desk 2, but not that it's  Reading room desk 2.  To put another way, if there is the Pickup service point column, and the dropdown filter, what should the Search box do?

Generated at Fri Feb 09 00:34:34 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.