Bug 10811: (follow-up) use "local-number" rather than "Local-Number"

At present, the QueryParser search mode expects that search field names
and aliases are case-sensitive.  This may change (see bug 11353), but
for now, this patch ensures that the local-number searches used by
the KohaBiblio rule will work regardless of the value of the
UseQueryParser system preference.

To test:

[1] Use the KohaBiblio 999$c matching rule with UseQueryParser both
    on and off.  Verify that matching by biblionumber works correctly.

Signed-off-by: Galen Charlton <gmc@esilibrary.com>

diff --git a/installer/data/mysql/en/marcflavour/marc21/optional/marc21_default_matching_rules.sql b/installer/data/mysql/en/marcflavour/marc21/optional/marc21_default_matching_rules.sql
index 1160094..801f04a 100644 (file)
--- a/installer/data/mysql/en/marcflavour/marc21/optional/marc21_default_matching_rules.sql
+++ b/installer/data/mysql/en/marcflavour/marc21/optional/marc21_default_matching_rules.sql
@@ -38,9 +38,9 @@ INSERT INTO matchpoint_component_norms (matchpoint_component_id, sequence, norm_
 
 INSERT INTO marc_matchers (code, description, record_type, threshold)
     VALUES ('KohaBiblio', '999$c', 'biblio', 1000);
-INSERT INTO matchpoints (matcher_id, search_index, score) SELECT MAX(matcher_id), 'Local-Number', 1000 FROM marc_matchers;
+INSERT INTO matchpoints (matcher_id, search_index, score) SELECT MAX(matcher_id), 'local-number', 1000 FROM marc_matchers;
 INSERT INTO matcher_matchpoints SELECT MAX(matcher_id), MAX(matchpoint_id) FROM matchpoints;
 INSERT INTO matchpoint_components (matchpoint_id, sequence, tag, subfields)
     SELECT MAX(matchpoint_id), 1, '999', 'c' FROM matchpoints;
 INSERT INTO matchpoint_component_norms (matchpoint_component_id, sequence, norm_routine)
-    SELECT MAX(matchpoint_component_id), 1, 'Biblionumber' FROM matchpoint_components;
\ No newline at end of file
+    SELECT MAX(matchpoint_component_id), 1, 'Biblionumber' FROM matchpoint_components;