Requests (UXPROD-790)

[UXPROD-4061] Requests: Add optional columns to results table and action menu Created: 10/Feb/23  Updated: 30/Nov/23  Resolved: 06/Jun/23

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

Type: New Feature Priority: P2
Reporter: Stephanie Buck Assignee: Stephanie Buck
Resolution: Done Votes: 0
Labels: LC-priority2, loc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by CIRC-1752 Remove search index fields from reque... Closed
is defined by CIRC-1753 Update mod-circulation to save call n... Closed
is defined by CIRCSTORE-398 Add effective call number and service... Closed
is defined by CIRCSTORE-399 Search index fields migration script ... Closed
is defined by CIRCSTORE-400 Search index fields migration script ... Closed
is defined by CIRCSTORE-401 Schema migration testing Closed
is defined by CIRCSTORE-408 Update request seach index when servi... Closed
is defined by FAT-5355 Test request filtering by call number Closed
is defined by FAT-5356 Test request sorting by service point... Closed
is defined by MODINVSTOR-1043 Publish a domain event when service p... Closed
is defined by UIREQ-898 Requests: Include call number in disp... Closed
is defined by UIREQ-899 Requests: Include call number in Acti... Closed
is defined by UIREQ-900 Requests: Include pickup service poin... Closed
is defined by UIREQ-901 Requests: Include pickup service poin... Closed
is defined by UIREQ-908 [Spike] Investigate possible to unche... Closed
is defined by CIRCSTORE-407 Update request seach index when item ... Closed
Duplicate
duplicates UXPROD-3758 Add "Pickup service point" as column ... Closed
duplicates UXPROD-3761 Include call number in display of res... Closed
Relates
relates to CIRCSTORE-406 [SPIKE] Investigate the possibility t... Closed
Release: Poppy (R2 2023)
Epic Link: Requests
Front End Estimate: Medium < 5 days
Front End Estimator: Stephanie Buck
Front-End Confidence factor: 80%
Back End Estimate: XXL < 30 days
Back-End Confidence factor: 90%
Development Team: Vega
PO Rank: 0
Rank: Cornell (Full Sum 2021): R1

 Description   

Current situation or problem: Institutions would like to add two (optional) columns to the Requests app results table: Effective call number string and Pickup service point

In scope: Add columns and add to Show columns list in the Action menu; search filter by call number "starts with"

Out of scope: Additional filters

Use case(s)

Effective call number string:

  • Patrons a lot of the times only know the title or call number.  So we may have to look up a request by call number or jumping from the patrons summary page, if they have a lot of open requests, we may have to find the item in the list by call number. 
  • Staff could use this column to verify they have the correct book in hand or if its second copy
  • An institution has closed stacks arranged by call number. All pages are retrieved based on call number location in the stacks. The retrieval staff must be able to filter the requests by call number

Pickup service point:

  • 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

MSEARCH-81 Closed and MSEARCH-12 Closed explain how call number search happens in Inventory. 

Questions

  1. What happens when multiple items are available in different locations/have different call numbers?
  2. Will fixed location & call number show up if data is stored in holding records?


 Comments   
Comment by Aly DesRochers [ 25/Apr/23 ]

It is also extremely important that the effective call number be a token that we can include on pick slips.

Comment by Aly DesRochers [ 25/Apr/23 ]

In reply to/closure of my above comment, this is already possible!

Though there is no one single token for call number, you can build it with the different tokens strung together:

item.callNumberPrefix item.callNumberSuffix item.callNumber item.volume item.enumeration item.chronology item.copy 

Comment by Khalilah Gambrell [ 05/Jun/23 ]

Hey Stephanie Buck  - can this move to In PO Review or Closed?

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