Patron Notices
(UXPROD-18)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Patron Notices |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Darcy Branchini | Assignee: | julie.bickle |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | notice_enhancement, notice_multiples, patron_notice, round_iv, split | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||||||
| Epic Link: | Patron Notices | ||||||||||||||||||||||||||||
| Front End Estimate: | Large < 10 days | ||||||||||||||||||||||||||||
| Front-End Confidence factor: | Medium | ||||||||||||||||||||||||||||
| Back End Estimate: | XXL < 30 days | ||||||||||||||||||||||||||||
| Development Team: | Volaris | ||||||||||||||||||||||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 8 | ||||||||||||||||||||||||||||
| PO Rank: | 20 | ||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R4 | ||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R2 | ||||||||||||||||||||||||||||
| Rank: Grand Valley (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||
| Rank: hbz (TBD): | R2 | ||||||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R1 | ||||||||||||||||||||||||||||
| Rank: Mainz (Full TBD): | R1 | ||||||||||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R1 | ||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R3 | ||||||||||||||||||||||||||||
| Description |
|
Dec 2019 - split from:
Jan 2020 - narrowing the scope of this feature to multiples on request notices and created a new feature -
Purpose/Problem: Frequently a single patron has several requested items available and awaiting pick up (from a service point's hold shelf) at the same time. Instead of sending several reminder notices that items are awaiting pick up, it is preferred to send a single notice that refers to all items. Other request notice examples with multiple items might include a request expiration and/or even request confirmation notices (all requested items within a certain period of time). If policies that define when/how to send are not set to real-time, then a frequency for bundling and sending together needs to be determined. Daily may meet most needs and this is what is currently implemented for loan overdue and courtesy notices. Description:
Implementation Thoughts:
Additional Information
|
| Comments |
| Comment by Kristin Martin [ 30/Dec/19 ] |
|
From Chicago: This is particularly crucial for courtesy notices. We must be able to send a single notice for all quarterly and annual loans, not 300 separate notices. Checkout receipts would have to be turned off if we didn't have this feature, which we could perhaps live with in the short term. Check-in receipts (which we don't currently have) could not be implemented, but since we don't have that feature, it's less critical. |
| Comment by Siska [ 16/Jan/20 ] |
|
Darcy Branchini Is this issue only for fees/fines? What are the "remaining notices"? |
| Comment by Darcy Branchini [ 24/Jan/20 ] |
|
Siska, the spreadsheet linked above lists all notices currently implemented, and which are intended to include multiple items - https://docs.google.com/spreadsheets/d/1I8i1IUbuDz9XgBgSZ8xXmFymIQ9_R-Gc63I8RndEWiI/edit?usp=sharing. Feel free to comment on that spreadsheet or here if you have specific needs that haven't been considered yet. |
| Comment by Charlotte Whitt [ 27/Nov/23 ] |
|
Hi julie.bickle - I notice that the latest comment is back from early 2020, and I'm wondering now we have the implementation on multiple loans using the tagging:
{{#loans}}
...
{{/loans}}
that this feature will not be that huge development task as original estimated: Back End: XXL < 30 days (= 6 weeks work for a full time developer)
|