Note located URI changes in Release Notes

Located URIs now define what org unit and below in the hierarchy will be
matched for a given search scope, rather than the copy-like behaviour
from before; for example, a located URI at BR1 will no longer be found
in a SYS1 search scope; rather, a located URI at SYS1 will be found with
either a SYS1 or a BR1 search scope.

Put some info and rough suggested fix into the release notes.

Signed-off-by: Dan Scott <dscott@laurentian.ca>
Signed-off-by: Bill Erickson <berick@esilibrary.com>

diff --git a/RELEASE_NOTES b/RELEASE_NOTES
new file mode 100644 (file)
index 0000000..2010c99
--- /dev/null
+++ b/RELEASE_NOTES
@@ -0,0 +1,36 @@
+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, 
+            '<subfield code="9">BR1</subfield>',
+            '<subfield code="9">SYS1</subfield>'
+        ),
+        '<subfield code="9">BR3</subfield>',
+        '<subfield code="9">SYS2</subfield>'
+    ) WHERE marc LIKE '<subfield code="9">BR1</subfield>'
+        OR marc LIKE '<subfield code="9">BR3</subfield>'
+;
+------------------------------------------------------------------------------