scratchpad:notification_system
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
scratchpad:notification_system [2008/07/08 18:46] – stompro | scratchpad:notification_system [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | [[user-comments: | ||
+ | |||
+ | |||
+ | ====== Notification System ====== | ||
+ | |||
+ | This page is intended to discuss the design of evergreens notification system. | ||
+ | |||
+ | ===== Discussion | ||
+ | Open-ILS-Dev list discussion. | ||
+ | * http:// | ||
+ | * http:// | ||
+ | * http:// | ||
+ | * http:// | ||
+ | * http:// | ||
+ | * http:// | ||
+ | * http:// | ||
+ | * http:// | ||
+ | * http:// | ||
+ | * http:// | ||
+ | * http:// | ||
+ | |||
+ | ===== Notification Triggers ===== | ||
+ | Possible events where patron notification may be desired. | ||
+ | |||
+ | * Checkouts - Digital receipt type functionality | ||
+ | * Checkins - Digital receipt, those that want to know that the library really received their returned items. | ||
+ | * Renewal - Digital receipt. | ||
+ | * Almost Due - Reminder service, configurable by number of days/hours before item is due. | ||
+ | * Due | ||
+ | * Overdue (1st , 2nd, Nth overdue) | ||
+ | * Billed (1st, 2nd, Nth Bill) | ||
+ | * Customer Record Expired - or about to expire. | ||
+ | * Item placed on hold - Digital receipt. | ||
+ | * Item available for pickup. | ||
+ | * Item available on shelf - Notify when hold placed on item that is at a customers library. | ||
+ | * Item no longer available on shelf - Notify when item is no longer available on shelf, customer will be notified again when it is available. | ||
+ | * Hold Fulfillment issue - Item not being filled in a timely manner, suggest trying an alternative format. | ||
+ | * Hold canceled - Hold has been canceled for various reasons. | ||
+ | * Item Recalled - someone more important than you needs this item :) | ||
+ | * Fines Owed, over a certain amount(customer preference or Libraries) | ||
+ | * New item by watched author, series, search - might duplicate rss feeds. | ||
+ | * Customer Record Changed (Account Added=> | ||
+ | * Fines or Bills paid | ||
+ | * Notification method failed(Send email if SMS failed "We tried to text you, but we had a problem, please make sure we have your correct information" | ||
+ | * Staff Placed email, both on individual patrons, and for groups of patrons. | ||
+ | * Item being mailed to customer, if library supports that method. | ||
+ | * Account Information change - Change in account information, | ||
+ | * Stored balance change - if customer has a stored balance on their account. | ||
+ | |||
+ | ===== Notification Methods ===== | ||
+ | Possible forms of notification. | ||
+ | |||
+ | Current Forms: | ||
+ | |||
+ | * Postal Mail - Postcards, secure mailers, press and seal. | ||
+ | * Email (basic and enhanced) - Much can be learned from Library Elf. | ||
+ | * Instant Message/ Blackberry Gateway (email gateway) - Shorter messages, handle replies in an intelligent manner. | ||
+ | * Automated Phone - Post on open-ils-dev http:// | ||
+ | * Staff Initiated Phone (Management for calls that staff place to coordinate the whole process, get a busy signal, mark it down and the notice will come up again in a couple hours, number out of service, mark the notice as undeliverable, | ||
+ | * SMS (email gateway) - Because SMS messages usually cost the receiver money, there should be a way to set limits on the number of notifications sent this way. Notices also must be formated for a limited number of characters. | ||
+ | * Exchange Calendar Appointments/ | ||
+ | * RSS Feeds | ||
+ | * Third Party Notification/ | ||
+ | |||
+ | |||
+ | ===== Notification Order/ | ||
+ | The system should be be flexible on how the ordering of notification methods is handled. | ||
+ | |||
+ | |||