LP1353643: Release Notes added user/ldw/LP1353643_Consolidated_SQL_Added_Comments
authorLiam Whalen <liam.whalen@bc.libraries.coop>
Wed, 12 Aug 2015 22:39:21 +0000 (15:39 -0700)
committerLiam Whalen <liam.whalen@bc.libraries.coop>
Wed, 12 Aug 2015 22:39:21 +0000 (15:39 -0700)
Release notes have been added to explain how to use the changes to the
located URIs code.

Signed-off-by: Liam Whalen <liam.whalen@bc.libraries.coop>
docs/opac/luri_as_copy.txt [new file with mode: 0644]

diff --git a/docs/opac/luri_as_copy.txt b/docs/opac/luri_as_copy.txt
new file mode 100644 (file)
index 0000000..ce86b9e
--- /dev/null
@@ -0,0 +1,28 @@
+Upgrade Notes
+
+How EG evaluates a URI as a copy has been changed.
+
+Seven new settings have been created.
+
+1. opac.luri_anc_vis_depth
+2. opac.luri_ancestor_record_visibility_depth
+3. opac.luri_des_vis_depth
+4. opac.luri_descendants_record_visibility_depth
+5. opac.luri_pref_ancestor_record_visibility_depth
+6. opac.luri_pref_descendants_record_visibility_depth
+7. opac.luri_results_uri_limit
+
+luri_anc_vis_depth and luri_des_vis_depth limit how URIs are displayed for a
+record.  These depths limit how far up and down the OU tree the TPAC will
+display located URIs.
+
+luri_ancestor_record_visibility_depth, luri_descendant_record_visibility_depth,
+luri_pref_ancestor_record_visibility_depth,
+luri_pref_descendants_record_visibility_depth limit how records are returned
+in the search results based on if a library or its ancestors or descendants
+have a located URI in the record.  If the library has a located URI the record
+will be displayed, however the *_visibility_depth settings limit how far up
+the tree and down the tree the TPAC will go to display relevant records.
+
+opac.luri_results_uri_limit limits the number of URIs displayed on the search
+results list.  The full number of URIs are displayed on the record.