From 54dc1aac3802103df9113fd18c2ed2bffaa8a1ed Mon Sep 17 00:00:00 2001 From: Bill Erickson Date: Thu, 30 Mar 2017 11:47:20 -0400 Subject: [PATCH] LP#1677661 Targeter V2 extras release notes Signed-off-by: Bill Erickson Signed-off-by: Jason Stephenson --- .../hold-targeter-v2-improvements.adoc | 36 ++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 docs/RELEASE_NOTES_NEXT/Administration/hold-targeter-v2-improvements.adoc diff --git a/docs/RELEASE_NOTES_NEXT/Administration/hold-targeter-v2-improvements.adoc b/docs/RELEASE_NOTES_NEXT/Administration/hold-targeter-v2-improvements.adoc new file mode 100644 index 0000000000..06a357af5d --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Administration/hold-targeter-v2-improvements.adoc @@ -0,0 +1,36 @@ +Hold Targeter V2 Repairs and Improvements +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +* Make the batch targeter more resilient to a single-hold failure. +* Additional batch targeter info logging. +* Set OSRF_LOG_CLIENT in hold_targeter_v2.pl for log tracing +* Removes the confusingly named --target-all option + ** The same behavior can be achieved by using --retarget-interval "0s" +* Removes --skip-viable (see --soft-retarget-interval below) + +New --next-check-interval Option +++++++++++++++++++++++++++++++++ +Specify how long after the current run time the targeter will retarget +the currently affected holds. Applying a specific interval is useful +when the retarget-interval is shorter than the time between targeter +runs. + +For example, if the targeter is run nightly at midnight with a +--retarget-interval 36h, you would set --next-check-interval to 48hr, +since the holds won't be processed again until 48 hours later. This +ensures that the org unit closed date checks are looking at the correct +date. + +This setting overrides the default behavior of calculating the next +retarget time from the retarget-interval. + +New --soft-retarget-interval Option ++++++++++++++++++++++++++++++++++++ +This is a replacement for (and rebranding of) the --skip-viable option. +The new option allows for time-based soft-targeting instead simple binary +on/off soft-targeting. + +How soft-targeting works: +* Update hold copy maps for all affected holds +* Holds with viable targets (on the pull list) are otherwise left alone. +* Holds without viable targets are retargeted in the usual manner. + -- 2.11.0