From eabd8160c6b88dd6e04e22b0d2b26e62f0d118cb Mon Sep 17 00:00:00 2001 From: Jason Stephenson Date: Sun, 11 Oct 2015 14:30:11 -0400 Subject: [PATCH] LP 1499123: Add release notes. Signed-off-by: Jason Stephenson Signed-off-by: Kathy Lussier --- .../standing_penalty_ignore_proximity.txt | 30 ++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 docs/RELEASE_NOTES_NEXT/Circulation/standing_penalty_ignore_proximity.txt diff --git a/docs/RELEASE_NOTES_NEXT/Circulation/standing_penalty_ignore_proximity.txt b/docs/RELEASE_NOTES_NEXT/Circulation/standing_penalty_ignore_proximity.txt new file mode 100644 index 0000000000..7bdc5b8d44 --- /dev/null +++ b/docs/RELEASE_NOTES_NEXT/Circulation/standing_penalty_ignore_proximity.txt @@ -0,0 +1,30 @@ +Standing Penalty Ignore Proximity +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +Standing penalties now have an ignore_proximity field that takes an +integer value. When set, the value of this field represents the +proximity from the user's home organizational unit where this penalty +will be ignored for purposes of circulation and holds. Typical values +for this field would be 0, 1, or 2 when using a standard hierarchy of +Consortium -> System -> Branch -> Sublibrary/Bookmoblie. A value of 1 +would cause the penalty to be ignored at the user's home organization +unit, it's parent and/or immediate child. A value of 2 should cause +it to be ignored at the above as well as all sibling organizational +units to the user's home. In all cases, a value of zero causes the +penalty to be ignored at the user's home and to apply at all other +organizational units. If the value of this field is left unset (or +set to a negative value), the penalty will still take effect +everywhere using the normal organizational unit and depth values. If +you use a custom hierarchy, you will need to figure out any values +greater than 0 on your own. + +The ignore_proximity does not affect where penalties are applied. It +is used when determining whether or not a penalty blocks an activity +at the current organizational unit or the organizational unit that +owns the copy involved in the current transaction. For instance, if +you set the ignore_proximity to 0 on patron exceeds overdue fines, +then the patron will still be able to place holds on and checkout +copies owned by their home organizational unit at their home +organizational unit. They will not, however, be able to receive +copies form other organizational units, nor use other organizational +units as a patron. -- 2.11.0