Patron Notices
(UXPROD-18)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Patron Notices |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Darcy Branchini | Assignee: | julie.bickle |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | notice_enhancement, notice_timing, patron_notice, round_iv | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Epic Link: | Patron Notices |
| Development Team: | Volaris |
| Kiwi Planning Points (DO NOT CHANGE): | 4 |
| PO Rank: | 70 |
| Rank: Chalmers (Impl Aut 2019): | R4 |
| Rank: Chicago (MVP Sum 2020): | R1 |
| Rank: Cornell (Full Sum 2021): | R1 |
| Rank: Duke (Full Sum 2021): | R1 |
| Rank: 5Colleges (Full Jul 2021): | R4 |
| Rank: GBV (MVP Sum 2020): | R2 |
| Rank: Grand Valley (Full Sum 2021): | R1 |
| Rank: hbz (TBD): | R4 |
| Rank: Lehigh (MVP Summer 2020): | R2 |
| Rank: MO State (MVP June 2020): | R2 |
| Rank: U of AL (MVP Oct 2020): | R2 |
| Description |
|
Split from
Context: Purpose: Description: Questions:
Google Doc for reference: |
| Comments |
| Comment by Holly Mistlebauer [ 17/Jun/20 ] |
|
Chicago comment from Round IV Outliers spreadsheet: This is important for us as we don't know how well folio will handle out huge quarterly courtesy and overdue notice runs. Nor do we what kinds of batch jobs will be run from other modules and lead to contention. -Tod Olson |
| Comment by David Bottorff [ 17/May/21 ] |
|
There is also an implication for items that age to lost. If items are sent to be due at the end of the day, the aged to lost and aged to lost item fee will NOT have finished running before batch notices are sent at midnight. This will create a scenario in which someone is blocked (either due to aged to lost status or lost item fee) but the notice is not sent for nearly 24 hours after the fact (if I am interpreting how the various batch process work). |
| Comment by Erin Nettifee [ 17/May/21 ] |
|
Right David Bottorff - that argues for not sending the notice until a day after it ages to lost, but then the blocks happen automatically, and you can't delay those for a day either (Holly Mistlebauer) |
| Comment by David Bottorff [ 17/May/21 ] |
|
It seems like this would be solved by being able to select a time for batch notices to run. Then you could select the age to lost batch jobs to run at (for example) 1:00 am (catching all items due at the end of a day) and the batch notice job to run at 2 a.m. (which would catch all items aged to lost at 1:00 a.m. |
| Comment by Erin Nettifee [ 17/May/21 ] |
|
I agree, and that seems to be what this feature is meant to do – just no idea of when it will happen. |
| Comment by Erin Nettifee [ 09/Jun/22 ] |
|
It would be nice as well to be able to extend this feature such that batches of notices for items at a specific library or service point send at X time and batches for items at another library send at Y point. This would help with consortial and multi-tenant solutions, I believe (something Duke is interested in in order to support our China campus.) |