LP#1744385: Additions and edits to release note entry

Minor edits to the release notes entry. Also, I highlighted the increased
use of Display Fields in the client since I thought it would be of
interest to some users. I also incorporated information regarding
default weights, which were added after Mike wrote up his release
note for this feature.

Signed-off-by: Kathy Lussier <klussier@masslnc.org>
Signed-off-by: Dan Wells <dbw2@calvin.edu>

diff --git a/docs/RELEASE_NOTES_NEXT/Architecture/search-display-infrastructure-improvements.adoc b/docs/RELEASE_NOTES_NEXT/Architecture/search-display-infrastructure-improvements.adoc
index 88b2f8c..0ed9de6 100644 (file)
--- a/docs/RELEASE_NOTES_NEXT/Architecture/search-display-infrastructure-improvements.adoc
+++ b/docs/RELEASE_NOTES_NEXT/Architecture/search-display-infrastructure-improvements.adoc
@@ -19,9 +19,9 @@ search. It is also fairly ineffective at achieving the goal of weighted keyword
 fields. Virtual Index Definitions will substantially alleviate the need for
 these workarounds and their consequences.
 
-  * A Virtual Index Definition is not required supply any configuration for
+  * A Virtual Index Definition does not require any configuration for
 extracting bibliographic data from records, but instead can become a sink for
-data collected by other index definitions which is then colocated together to
+data collected by other index definitions, which is then colocated together to
 supply a search target made up of the separately extracted data. Virtual Index
 Definitions are effectively treated as aggregate definitions, matching across
 all values extracted from constituent non-virtual index definitions.  They can
@@ -51,11 +51,14 @@ field.
 
 Increased use of Metabib Display Fields
 +++++++++++++++++++++++++++++++++++++++
-In extention of changes proposed in other available branches, we here use
-Metabib Display Fields to render catalog search results, intermediate metarecord
-results, and record detail pages.This will requires the addition of several new
-Metabib Display Field definitions, as well as Perl services to gather and render
-the data.
+We use Metabib Display Fields (newly available in 3.0) to render catalog search
+results, intermediate metarecord results, and record detail pages.This requires
+the addition of several new Metabib Display Field definitions, as well as Perl
+services to gather and render the data.
+
+We also use more Metabib Display Fields in the client. As a result, 
+bibliographic fields will display in proper case in more client interfaces and
+in Evergreen reports.
 
 Search Term Highlighting
 ++++++++++++++++++++++++
@@ -75,7 +78,7 @@ fields are searched as well as exposing concepts like stemming.
 Interfaces
 ++++++++++
 A new AngularJS "MARC Search/Facet Fields" interface has been created to replace
- the Dojo version, and both have been extended to support Virtual Index
+the Dojo version, and both have been extended to support Virtual Index
 Definition data supplier mapping and weighting.
 
 Settings & Permissions
@@ -112,6 +115,22 @@ been augmented to be able to return a data structure describing how the search
 was performed, in a way that allows a separate support API to gather a
 highlighted version of the Display Field data for a given record.
 
+Default Weights
++++++++++++++++
+By default, the following fields will be weighted more heavily in keyword 
+searches. Administrators can change these defaults by changing the values in the
+ "All searchable fields" virtual index in the "MARC Search/Facet Fields"
+interface.
+
+  * Title proper
+  * Main title (a new index limited to the words in the 245a)
+  * Personal author
+  * All subjects
+
+In addition, note indexes and the physical description index will receive
+less weight in default keyword searches.
+
+
 Re-ingest or Indexing Dependencies
 ++++++++++++++++++++++++++++++++++
 With the addition and modification of many Index Definitions, a full reingest is