Patron Notices (UXPROD-18)

[UXPROD-1771] Patron notices sent/printed ad-hoc Created: 13/Jun/19  Updated: 23/Feb/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Patron Notices

Type: New Feature Priority: P4
Reporter: Darcy Branchini Assignee: julie.bickle
Resolution: Unresolved Votes: 0
Labels: notice_enhancement, notice_timing, patron_notice
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Patron Notices
Development Team: Volaris
UX Lead: Darcy Branchini
Kiwi Planning Points (DO NOT CHANGE): 1
PO Rank: 8
PO Ranking Note: Not ranked by very many.
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R2
Rank: GBV (MVP Sum 2020): R4
Rank: hbz (TBD): R4
Rank: Lehigh (MVP Summer 2020): R4
Rank: Mainz (Full TBD): R2
Rank: MO State (MVP June 2020): R2
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R4

 Description   

Use cases:

  1. Query users for specific criteria, such as near expiration date (or graduation date) and owe the library more than $100, in order to send these users an ad-hoc notice.
  2. Query users once a quarter for outstanding fee/fines and send reminder notices with a comprehensive list of all fee/fines on a single notice per patron.
  3. From Duke: It may be the case that we want to do a second notice for a hold pickup ad-hoc, rather than systematically. I can see branches that might want both - our bigger branches wanting second notices to go automatically to save overhead, whereas smaller branches want to do it for particular patrons but not bother others.


 Comments   
Comment by David Bottorff [ 09/Jul/19 ]

This is not a need feature for Chicago

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