Requests
(UXPROD-790)
|
|
| 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: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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
-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
Use case(s)
Proposed solution/stories{} Links to additional info
Questions
Original description from NLA Task: Add a 3rd dropdown in which a user can filter from the request UI screen. Acceptance Criteria
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 |