[UXPROD-18] Patron Notices Created: 18/Jan/18  Updated: 30/Nov/23

Status: In Progress
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: Epic Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: julie.bickle
Resolution: Unresolved Votes: 0
Labels: resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Name: Patron notices
Analysis Estimator: Darcy Branchini
Front End Estimator: Jakub Skoczen
Back End Estimator: Jakub Skoczen
Development Team: Volaris
UX Lead: Darcy Branchini
Start date (migrated):
End date:

 Description   

Circulation activities of all types generate notices that need to be sent to patrons by whatever means the system allows (email, snailmail, etc.). Notices that may be required include: overdue, recall, hold expired, hold is in house, replacement fee due, ordered item has been delivered (ACQ). JL: also need courtesy reminder notices (book is coming due in xx days).

Epic/umbrella issue to hold the stories for patron notifications. Generally speaking, we need functionality that provides CRUD interface for patron notifications. User needs to define a trigger that initiates a notification, how that notification is sent (email, sms, and/or mail), who receives the notification, and format the notification. Formatting includes layout, font sizes and placement of fields as well as tokens (values from specific fields). Batch notifications are also necessary, but not all patron notifications will be sent in batch.

Epic name in v1 roadmap was "generate notices".


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