- Added release notes.
- Added note about script to support scripts doc.
- Added script to makefile for confile processing and installation.
- Added processed version of the script to .gitignore
I tested out the script with our production data and it worked as described.
Signed-off-by: Josh Stompro <stompro@stompro.org>
Signed-off-by: Galen Charlton <gmc@equinoxinitiative.org>
Open-ILS/src/python/Evergreen.egg-info/
Open-ILS/src/python/Makefile
Open-ILS/src/python/Makefile.in
+Open-ILS/src/support-scripts/action_trigger_aggregator.pl
Open-ILS/src/support-scripts/action_trigger_runner.pl
Open-ILS/src/support-scripts/authority_authority_linker.pl
Open-ILS/src/support-scripts/authority_control_fields.pl
@srcdir@/extras/import/marc2bre.pl \
@srcdir@/extras/import/marc2sre.pl \
@srcdir@/extras/import/parallel_pg_loader.pl \
+ $(supportscr)/action_trigger_aggregator.pl \
$(supportscr)/action_trigger_runner.pl \
$(supportscr)/authority_control_fields.pl \
$(supportscr)/authority_authority_linker.pl \
$(do_subst) @srcdir@/extras/import/parallel_pg_loader.pl.in > "$@"
chmod 755 "$@"
+$(supportscr)/action_trigger_aggregator.pl: Makefile $(supportscr)/action_trigger_aggregator.pl.in
+ $(do_subst) $(supportscr)/action_trigger_aggregator.pl.in > "$@"
+ chmod 755 "$@"
+
$(supportscr)/action_trigger_runner.pl: Makefile $(supportscr)/action_trigger_runner.pl.in
$(do_subst) $(supportscr)/action_trigger_runner.pl.in > "$@"
chmod 755 "$@"
use OpenILS::Utils::RemoteAccount;
use OpenILS::Utils::Fieldmapper;
-my $osrf_config = '/openils/conf/opensrf_core.xml';
+my $osrf_config = '@sysconfdir@/opensrf_core.xml';
my $default_start_date = DateTime->now->strftime('%F');
my $date = '';
my $start_date = '';
--cleanup
Remove the local file after script is done.
- --event-defs
+ --event-defs
action_trigger.event_definition IDs to include
--granularity
--osrf-config
To set the OpenSRF config to something other than the default of
- '/openils/conf/opensrf_core.xml'
+ '@sysconfdir@/opensrf_core.xml'
--output-file [default STDOUT]
Output goes to this file.
--- /dev/null
+Ability to specify specific date in action_trigger_aggregator.pl
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+An option, `--date`, has been added to the `action_trigger_aggregator.pl`
+support script that allows the user to specify a specific date to aggregate
+event output for. This new argument cannot be used with either `--start-date`
+or `--end-date`. This option was added to simplify pulling event output for a
+single day.
Here is a summary of the most commonly used scripts. The script name links
to more thorough documentation, if available.
+ * action_trigger_aggregator.pl
+ -- Groups together event output for already processed events. Useful for
+ creating files that contain data from a group of events. Such as a CSV
+ file with all the overdue data for one day.
* <<_processing_action_triggers,action_trigger_runner.pl>>
-- Useful for creating events for specified hooks and running pending events
* authority_authority_linker.pl