[UIREQ-820] Add "Pickup service point" as column in Requests app Created: 08/Sep/22  Updated: 14/Mar/23  Resolved: 14/Mar/23

Status: Closed
Project: ui-requests
Components: None
Affects versions: None
Fix versions: None

Type: Story Priority: P3
Reporter: Erin Nettifee Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: delegate_candidate, ui-only, volaris-candidate
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File image-2022-09-09-11-56-20-373.png     PNG File image-2022-09-09-11-56-31-253.png     PNG File image-2022-09-09-11-59-24-355.png    
Sprint:
Development Team: Volaris
RCA Group: TBD

 Description   

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) 
      • Erin Nettifee  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
    • Erin Nettifee  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


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

Hey Erin Nettifee  it appears there is another request to add Item call number. https://folio-org.atlassian.net/browse/UXPROD-3761

I am growing concern about the number of columns to display on the request results list. One of the goals of a three pane layout is to make it easy to find additional information so I have two questions 

  1. Are there any result list column fields that should not show by default?
  2. What should go in the Item call number column given we support Title level request?

What is the best way to get answers to these questions? 

Comment by Thomas Trutt [ 13/Mar/23 ]

Khalilah Gambrell  Looping through my backlog.  Erin Nettifee please feel free to disagree.. In my opinion i would drop Requester barcode, Proxy and maybe Queue position from the table. I feel the user name could be made into a link that opens the user's record. As for proxy information i feel that could be moved to the details pane. that would allow for the addition of this column as well as call number which IMO is more helpful to frontline staff. 

Comment by Khalilah Gambrell [ 13/Mar/23 ]

cc: Stephanie Buck 

Comment by Stephanie Buck [ 13/Mar/23 ]

This (I think) will be covered in scope of UXPROD-4061 Closed , specifically UIREQ-900 Closed and UIREQ-901 Closed . I'd like to close this as a duplicate if there are no objections.

Comment by Thomas Trutt [ 13/Mar/23 ]

Stephanie Buck I have no objections to closing this issue as a duplicate.

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