Requests (UXPROD-790)

[UXPROD-4470] Filter requests by Retrieval service point Created: 18/Sep/23  Updated: 07/Feb/24

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: Quesnelia (R1 2024)
Parent: Requests

Type: New Feature Priority: P3
Reporter: Brad Berkotte Assignee: Brad Berkotte
Resolution: Unresolved Votes: 0
Labels: IC_review, LC-priority3, Requests, at-risk, loc, nla, requests, requests_printing, requires-discussion
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File NLA mockup - needs updating 1.png     PNG File NLA mockup - needs updating 2.png    
Issue links:
Defines
is defined by CIRC-2022 [SPIKE] PoC - intercept and replace C... In Progress
is defined by UIREQ-989 Add a dropdown box for the service po... Closed
is defined by UIREQ-990 Add Item service point dropdown to ui... Draft
is defined by CIRCSTORE-482 CLONE - Add itemEffectiveLocationId t... Draft
is defined by CIRCSTORE-483 CLONE - Data migration for itemEffect... Draft
is defined by CIRCSTORE-484 CLONE - Data migration for itemEffect... Draft
is defined by CIRCSTORE-485 CLONE - Keep request search index up ... Draft
Relates
relates to UXPROD-4688 Add "Item effective location" as an o... Open
relates to CIRC-1930 Create design documentation for UXPRO... Closed
relates to UXPROD-4404 Requests: Deter Duplicate Pick Slip P... Draft
relates to UXPROD-4669 Add "Retrieval service point" as an o... Draft
relates to CIRC-1930 Create design documentation for UXPRO... Closed
relates to UXPROD-2285 Filter requests by item effective loc... Draft
relates to CIRC-1886 Backend code change for - Add Item se... Blocked
Release: Quesnelia (R1 2024)
Epic Link: Requests
Front End Estimate: Large < 10 days
Front-End Confidence factor: 80%
Back End Estimate: XXL < 30 days
Back-End Confidence factor: 80%
Development Team: NLA
PO Rank: 0

 Description   

Description

Current situation or problem: Currently in FOLIO, there is not a way to filter Requests by the Service point nearest where titles / items are shelved (a.k.a.., Retrieval service point). The FOLIO community, including Cornell, NLA, and Library of Congress, want to be able to filter based on Retrieval service point.

In Scope

  • Add a filter accordion containing Service points in Requests app. to "Search & filter" pane below Pickup service point.

              -Filter should contain an auto-complete filtered multi-select menu of all of the library's Service points

              -Accordion should enable User to select one or more Service points

              -When selected, requests are filtered by titles / items with an effective location of that Service point (e.g., "servicePointId")

 

Out of scope

  • Filtering requests by Item effective location - UXPROD-2285 Draft
  • Add the option to see "Retrieval service point" as a column in the results pane, unchecked by default

Use case(s)

  • Library divisions need to filter by Retrieval service point in order for certain staff groups to fill requests for their own custodial division and make efficient use of their time.
  • Libraries field many requests across several retrieval locations. Circulation staff wants to be able filter on Retrieval service point in order to view patron requests that will be retrieved at particular locations as efficiently as possible, easily adjust queues, and use location filters to see which branches may need extra copies of physical items.

Proposed solution/stories{}

Links to additional info

  • Note from CIRC-1933 Closed - Effective location of the requested item is tied to the primary service point with ID received in the request (path parameter "servicePointId", which is the ID of the service point currently selected in the UI).

Questions

 

Original description from NLA

Task: Add a 3rd dropdown in which a user can filter from the request UI screen. 

Acceptance Criteria

Criteria
Create a new dropdown box that displays under the existing "pickup service point"  
Drop down displays under the header “Item service point”   
Service points display. See: Setting>Tenant>Service points for expected results. This will vary for all locations.   
When a service point is selected, it is expected the requests will filter to the specified location.   

Background: {{item.effectiveLocationSpecific}}will allow us to confirm requests. 

Additional info: 

To populate the drop down the (ServicePoint) code will need to be used, this allows the already existing service point code to be leveraged. 

User must have the view request permission. Users: View requests, this should also limit them to their assigned service point/s. (This may need to be updated to suit general open source) This does match the generic permission in snapshot. 

 

Target release: Poppy 

Questions

to adjust queues and see which branches need extra copies.

 

Notes:

From Chalmers: When looking at Requests the staff wants to be able to filter based on location (effective location for requested item) to adjust queues and see which branches need extra copies.



 Comments   
Comment by Khalilah Gambrell [ 18/Sep/23 ]

Hey Brad Berkotte  - Typically features are only in UXPROD so that the community can view and provide insights. So I cloned uireq-990 and made it a feature. 

Here is documentation and we can discuss https://folio-org.atlassian.net/wiki/display/COMMUNITY/Getting+Started+for+Product+Owners 

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