1 New Feature: Generic CSV Notification Generator/Receiver
2 ========================================================
4 New Action/Trigger template and sample event definitions for creating a CSV
5 export file for various patron actions, primarily for the purpose of creating
6 patron notices via external notification mechanisms.
8 The reference implementation for this development is the TalkingTech iTiva
9 product, which consumes CSV files for generating phone/text notifications and
10 produces CSV results files for informing the ILS of notification statuses.
11 The template and send/receive scripts, however, should be generic enough to
12 create CSV for any type of 3rd-party notification product.
14 Action/Trigger Event Definition Configuration
15 ---------------------------------------------
17 * Supported hook core types include *circ*, *ahr*, *ausp*, and *au*
18 * Reactor is *ProcessTemplate*
20 Event Environment Requirements
21 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
23 * Patron object with card
33 Not all fields are relevant to all notice types.
35 Required Event Parameters
36 ~~~~~~~~~~~~~~~~~~~~~~~~~
38 * notify_media (e.g. phone)
39 * notify_type (e.g. overdue)
40 * notify_level (e.g. "1" -- first overdue)
42 The set of options for each event parameter is dependent on the 3rd-party
43 processing the CSV file.
45 iTiva Event Parameter Options
46 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
69 * action_trigger_aggregator.pl collects event output from requested event
70 definitions and stitches them together into a single file, which is sent
71 via (s)FTP to the 3rd party.
72 * Why don't we use the SendFile reactor directly?
73 ** The final file is meant to be a collection of event-def outputs, not
74 the output from a single event def
75 ** The final file may be too large to reasonably store directly in a
76 single action/trigger event_output row.
77 * csv_notify_fetcher.pl retrieves responses from the 3rd party and applies
78 the statuses to the async_output of each notified event.