Requests
(UXPROD-790)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Sunflower (R3 2024) | Parent: | Requests |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Stephanie Buck | Assignee: | Stephanie Buck |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | lc-priority4, loc, requests | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||
| Release: | Not Scheduled | ||||||||||||||||||||||||
| Epic Link: | Requests | ||||||||||||||||||||||||
| Front End Estimate: | XXL < 30 days | ||||||||||||||||||||||||
| Front End Estimator: | Khalilah Gambrell | ||||||||||||||||||||||||
| Front-End Confidence factor: | 20% | ||||||||||||||||||||||||
| Back End Estimate: | XXL < 30 days | ||||||||||||||||||||||||
| Back End Estimator: | Khalilah Gambrell | ||||||||||||||||||||||||
| Development Team: | Vega | ||||||||||||||||||||||||
| PO Rank: | 0 | ||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R3 | ||||||||||||||||||||||||
| Description |
|
Current situation or problem: Staff in special collections need a way to preview requests before they begin the fulfillment process so they can decide if the patron can handle the requested material In scope Out of scope Use case(s)
Proposed solution/stories Links to additional info Questions 1. Where in the request workflow does mediation occur?
2. Are all requests mediated, or just some?
|
| Comments |
| Comment by Erin Nettifee [ 14/Feb/23 ] |
|
Stephanie Buck this is an explicit use case for the expansion of "Needed for" and "Process" over in item state. I'm interested in what is being talked about for this feature in terms of requirements. I think there are other use cases for mediation besides "Needed for", especially for libraries with small collections that maybe aren't special but have a need for mediation regardless... |
| Comment by Stephanie Buck [ 14/Feb/23 ] |
|
Thanks, Erin Nettifee. Is there a specific Jira I should look at for these use cases? |
| Comment by Mark Canney [ 15/Feb/23 ] |
|
Some of our special collections requests need approval from staff who do not complete the fulfillment of the request. But we need to record the approval and then push to request to the staff who page, ship or provide room use access to the item. |
| Comment by Erin Nettifee [ 16/Feb/23 ] |
|
Stephanie Buck the use cases for "needed for" are listed on
|
| Comment by Thomas Trutt [ 09/Mar/23 ] |
|
I'd agree with Erin this does seem a logical extension of "needed for". This IMO is also a case for the workflow engine. We have several rare locations so based on the location being requested different staff would have to review the request. I also feel this would have to be part of the request policy, ie 'Requires Review' or 'Needs Approval'. |