Add "Pickup service point" as column in Requests app

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) 

      •   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

Environment

None

Potential Workaround

None

Attachments

3

Checklist

hide

TestRail: Results

Activity

Show:

Thomas TruttMarch 13, 2023 at 9:25 PM

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

Stephanie BuckMarch 13, 2023 at 8:38 PM

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

Khalilah GambrellMarch 13, 2023 at 7:15 PM

cc:  

Thomas TruttMarch 13, 2023 at 3:20 PM

  Looping through my backlog.   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. 

Khalilah GambrellSeptember 9, 2022 at 4:44 PM

Hey   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? 

Duplicate

Details

Assignee

Reporter

Priority

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
TestRail: Cases
TestRail: Runs