Requests
(UXPROD-790)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Requests |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Erin Nettifee | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | enettifee-reviewed, requests, resourceaccess | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Epic Link: | Requests |
| Development Team: | Vega |
| PO Rank: | 0 |
| Rank: Cornell (Full Sum 2021): | R2 |
| Description |
|
Current situation or problem: This feature is written to capture the development needs for a "pause request" feature for FOLIO. In scope
Out of scope Use case(s)
Proposed solution/stories
Links to additional info Questions
|
| Comments |
| Comment by Laurence Mini [ 14/Jul/22 ] |
|
A UMass colleague who does reserves work mentioned as a "super helpful feature for reserves work": In the past, when requesting an item through the Course Reserves module in Aleph, it delayed the hold automatically until 2 weeks before the term started. And when the hold activated, it had the Reserves patron as #1 in the queue because these requests had priority." |
| Comment by Laszlo Jakusovszky [ 13/Oct/22 ] |
|
This is the same for Stanford libraries using SirsiDynix. The delay prevents recalls during our dead/finals weeks, when access to those books is critical for users. |
| Comment by Erin Nettifee [ 13/Oct/22 ] |
|
Laszlo Jakusovszky can you say more about how you all use this feature with SirsiDynix? Do you apply an across-the-board freeze to requests, or how does it work? FWIW, in FOLIO, a recall would have already changed the due date when it was placed, and so I'm not sure I have a sense of how this feature would prevent recalls from occurring. |
| Comment by Laszlo Jakusovszky [ 13/Oct/22 ] |
|
Sorry, this is wrapped up in how we build reserves. Sirsi allows us to build records dormant, not live like FOLIO. So the recall is suppressed by design. When those records are flipped "live" (beginning of term), the recall triggers at that point. To my understanding FOLIO reserve items are always built live, so when a reserve is placed the recall is triggered immediately. We don't want a student to have their book recalled during finals week, etc. |
| Comment by Erin Nettifee [ 14/Oct/22 ] |
|
Right - I guess it depends on if the reserve item is out on loan or not. So it sounds like you all are doing things like prepping winter quarter reserves during fall finals and you wouldn't want to accidentally recall an item that was out on loan at that point? It's worth noting that at least right now putting something on reserve doesn't trigger anything if its out on loan, so it wouldn't be disruptive to your patrons at that point if they had the item out. |