Patron Notices (UXPROD-18)

[UXPROD-1386] Send patron notices via email for user initiated loan events, such as check in/out (i.e., check in or out receipt) Created: 04/Dec/18  Updated: 16/Sep/20  Resolved: 15/Mar/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q1 2019
Parent: Patron Notices

Type: New Feature Priority: P1
Reporter: Cate Boerema (Inactive) Assignee: Darcy Branchini
Resolution: Done Votes: 0
Labels: q1-2019-at-risk
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Slide1.png     PNG File Slide2.png     PNG File Slide3.png     PNG File Slide4.png     PNG File Slide5.png     PNG File Slide6.png     PNG File Slide7.png     PNG File Slide8.png    
Issue links:
Blocks
blocks UIU-710 Notify patron of new manual fee/fine ... Closed
blocks UIU-711 Notify patron of fee/fine payment rec... Closed
is blocked by UXPROD-1387 Add Request-Related Notice Settings t... Closed
Relates
relates to MODSENDER-4 SPIKE: Determine Technical approach f... Closed
relates to UICIRC-154 End to End Testing: Send loan-related... Closed
relates to UXPROD-676 CRUD Patron Notice Policies - Loan-re... Closed
Requires
requires MODSENDER-6 Spike: Define technical approach how ... Closed
is required by CIRC-222 Send loan-related notices on check-ou... Closed
is required by MODNOTIFY-50 Implement API for sending patron notices Closed
Epic Link: Patron Notices
Front End Estimate: XL < 15 days
Front End Estimator: Kostyantyn Khodarev
Back End Estimate: XXL < 30 days
Back End Estimator: Kostyantyn Khodarev
Development Team: Vega
Rank: BNCF (MVP Feb 2020): R4
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: GBV (MVP Sum 2020): R1

 Description   

2019 03 15 - Splitting this into several separate features:
Send patron notices for user initiated loan events, such as check in/out (i.e., check in receipt and check out receipt) via email
Send patron notices for user initiated request events, such as recall request, page request, hold request. cancel, etc. (i.e., recall notice) via email
Send patron notices for time based loan events, such as due date/time (i.e., courtesy notices and overdue notices) via email
Send patron notices for time based request events, such as hold expiration or request expiration (i.e., hold expiration notice) via email
Send patron notices for user initiated fee/fine events, such as a new manual charge or payment (i.e., fee/fine receipt or new charge notice) via email
Send patron notices for item status changes (request related), such as available - awaiting pickup (i.e., available notice for recalled item) via email

Earlier:
This feature covers the work needed to make the patron notice policies effective. This is being split out of UXPROD-676 Closed which was originally intended to cover Patron notice CRUD and making patron notice effective, but only CRUD is now expected for Q4.

This feature includes the scheduling functionality required to trigger time-based events/notices.



 Comments   
Comment by Darcy Branchini [ 21/Dec/18 ]

Attached workflow diagrams as PDF.

Generated at Fri Feb 09 00:15:10 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.