From 9d13c31e9b595f69a3af7941cc8be83d93e30bb4 Mon Sep 17 00:00:00 2001 From: Kathy Lussier Date: Wed, 16 Sep 2015 14:33:37 -0400 Subject: [PATCH] 2.8.4 release notes Release notes for the 2.8.4 point release. Signed-off-by: Kathy Lussier --- docs/RELEASE_NOTES_2_8.txt | 66 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 66 insertions(+) diff --git a/docs/RELEASE_NOTES_2_8.txt b/docs/RELEASE_NOTES_2_8.txt index 11ea0019e5..517b03a28e 100644 --- a/docs/RELEASE_NOTES_2_8.txt +++ b/docs/RELEASE_NOTES_2_8.txt @@ -1,5 +1,71 @@ Evergreen 2.8 Release Notes ============================= +Evergreen 2.8.4 +--------------- +This release contains several bugfixes improving on Evergreen 2.8.3 + +Circulation +~~~~~~~~~~~ +* Fixes an issue where transactions with checkin-generated fines that +previously had a balance of zero were prematurely closing. +* Fixes an issue where empty patron searches lead to heavy queries ending +in a client error. Empty patron searches will now exit early with no results. +* Provides validation on the patron self-registration form to prevent users +from entering the date of birth in the wrong date format. + +Cataloging +~~~~~~~~~~ +* Fixes an issue where all matches were not displaying during a Vandelay +authority record import. The fix ensures a row is added for every authority +record match in the Vandelay match grid, even when multiple matches refer to +the same authority record. + +Preventing improper data deletion from subfield $e +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +This release contains a fix for LP bug 1484281, "authority data may be +deleted during propagation with current values of +authority.control_set_authority_field." + +For more details see: https://bugs.launchpad.net/evergreen/+bug/1484281 + +The related upgrade script from this release removes subfield $e +in authority tags 100 and 110, but only from the Evergreen default +"LoC" authority control set configuration. If your Evergreen system is +set up with additional authority control sets besides the default +"LoC" one, you will need to run the following pieces of SQL code. + +First verify that you have an additional control set besides the +default of "LoC". Run the following SQL code and write down the ID +number for your additional control set. The number will be an integer +like 101. + +[source,sql] +-------------------------------------------------------------------- +select * +from authority.control_set +where name != 'LoC' +order by id +-------------------------------------------------------------------- + +In the following code you will need to change the two sections of +"control_set = XYZ". Change the part labeled with the text "XYZ", with +the ID number from the above query. + +If the above query displayed more than one additional authority +control set, then you will need to run the code below once for each +additional control set ID number. + +[source,sql] +-------------------------------------------------------------------- +UPDATE authority.control_set_authority_field +SET sf_list = REGEXP_REPLACE( sf_list, 'e', '', 'i') +WHERE tag = '100' AND control_set = XYZ AND sf_list ILIKE '%e%'; + +UPDATE authority.control_set_authority_field +SET sf_list = REGEXP_REPLACE( sf_list, 'e', '', 'i') +WHERE tag = '110' AND control_set = XYZ AND sf_list ILIKE '%e%'; +-------------------------------------------------------------------- Evergreen 2.8.3 --------------- -- 2.11.0