From 2f60ce5813ef2b0435d00c99a7d8ff698a8431d9 Mon Sep 17 00:00:00 2001 From: Dan Scott Date: Tue, 3 Apr 2012 09:33:24 -0400 Subject: [PATCH] Remove located URI scope notes from 2.2 Release Notes The located URI scope change occurred in the 2.1 time frame, not in 2.2, so remove from the Release Notes. Signed-off-by: Dan Scott --- docs/RELEASE_NOTES_2_2.txt | 31 ------------------------------- 1 file changed, 31 deletions(-) diff --git a/docs/RELEASE_NOTES_2_2.txt b/docs/RELEASE_NOTES_2_2.txt index fc38aa5b8d..36f8ed5d81 100644 --- a/docs/RELEASE_NOTES_2_2.txt +++ b/docs/RELEASE_NOTES_2_2.txt @@ -4,37 +4,6 @@ Release notes Upgrade notes ------------- -Located URI search scope -~~~~~~~~~~~~~~~~~~~~~~~~ -Recognizing that electronic resources are often licensed for an entire library -system rather than just a single library, the search scope for located URIs has -changed to match from the highest point in the hierarchy down, rather than from -the bottom up. In previous releases of Evergreen, if you had a MARC record with -a URI located at 'BR1', a search for that record at the 'SYS1' scope would -include the record in its results. The current release of Evergreen would not -include the record in its results; the scope needs to be set at the level of -'BR1' in the hierarchy or below. - -Therefore, you may want to run a SQL statement like the following, edited to -match the short names of your branches and systems, to change the located -URIs so that searches at the system level continue to return results for -located URIs: - ------------------------------------------------------------------------------- -UPDATE biblio.record_entry - SET marc = replace( - replace( - marc, - 'BR1', - 'SYS1' - ), - 'BR3', - 'SYS2' - ) WHERE marc LIKE 'BR1' - OR marc LIKE 'BR3' -; ------------------------------------------------------------------------------- - Z39.50 server definitions ~~~~~~~~~~~~~~~~~~~~~~~~~ Z39.50 server target definitions have been removed from the sample -- 2.43.2