From eb4fc15d55d1a74a9fafe24a033955a6a757a2c6 Mon Sep 17 00:00:00 2001 From: Jason Stephenson Date: Wed, 10 Apr 2013 17:29:28 -0400 Subject: [PATCH] Update the purge_holds.txt release notes. Signed-off-by: Jason Stephenson Signed-off-by: Dan Wells --- docs/RELEASE_NOTES_NEXT/purge_holds.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/RELEASE_NOTES_NEXT/purge_holds.txt b/docs/RELEASE_NOTES_NEXT/purge_holds.txt index f015f6d391..75d2371a40 100644 --- a/docs/RELEASE_NOTES_NEXT/purge_holds.txt +++ b/docs/RELEASE_NOTES_NEXT/purge_holds.txt @@ -2,6 +2,8 @@ New Feature: "Purge Holds" ========================== Similar to purging circulations one may wish to purge old (filled or canceled) hold information. This feature adds a database function and settings for doing so. +Purged holds are moved to the action.aged_hold_request table with patron identifying information scrubbed, much like circulations are moved to action.aged_circulation. + The settings allow for a default retention age as well as filled, canceled, and canceled by cancel cause ages. The most specific one wins unless a patron is retaining their hold history. In the latter case the patron's holds are retained either way. -Note that the function still needs to be called, which could be set up as a cron job or done more manually, say after statistics collection. +Note that the function still needs to be called, which could be set up as a cron job or done more manually, say after statistics collection. A new script, purge_holds.srfsh, is added that can be used to purge holds from cron. -- 2.43.2