Differences

This shows you the differences between two versions of the page.

--- dev:proposal:search_modifications [2012/11/12 14:04] – jbond
+++ dev:proposal:search_modifications [2022/02/10 13:34] (current) – external edit 127.0.0.1
@@ Line 11: / Line 11: @@
 Search modifications will alter the way searches perform in the following ways:
-     - Exact Match: Now exactly matches what is typed in under normalization rules.
+. Exact Match: Now exactly matches what is typed in under normalization rules.
           Example:
                   * Before: Search for: title| exact match | horses | results found 44: Horses, Runway horses., Crazy over horses, etc...
@@ Line 20: / Line 22: @@
-     - Contains Phrase: Will now require that the phrase appear in the index being searched on. (This feature appears to be in master at the moment. The only change, now, will be that the phrase is normalized and checked against a normalized table of values).
+. Contains Phrase: Will now require that the phrase appear in the index being searched on. (This feature appears to be in master at the moment. The only change, now, will be that the phrase is normalized and checked against a normalized table of values).
            Example:
                  * Before: subject | contains phrase | art greek | results found 1: Greek Art
                  * Now: subject | contains phrase | art greek | results found 3: Greek art, The art of Crete.., A handbook of Greek art
-     - Normalized Indexes: Some indexes contain content that are all normalized characters. This will detect that anomaly and force a search without using text normalization.
+. Normalized Indexes: Some indexes contain content that are all normalized characters. This will detect that anomaly and force a search without using text normalization.
            Example:
                  * Before: contains | !!! | results found 0: No results found
@@ Line 61: / Line 67: @@
 Remaining changes will be to the database, they include adding 5 tables of normalized text fields that are created from triggers from the field_entry tables. The text fields will be indexed using an extension called Pg_trgm.
-                 - Added 5 new tables, these tables are mapped to the *_field_entry tables. Each table contains an id which is one to one with the matching *_field_entry table. The other two columns contain the source and a value, which is a normalized value of the value field in the *_field_entry table.
+                 * Added 5 new tables, these tables are mapped to the *_field_entry tables. Each table contains an id which is one to one with the matching *_field_entry table. The other two columns contain the source and a value, which is a normalized value of the value field in the *_field_entry table.
-                 - Added an extension to index the normalized_*_field_entry tables. The index allows searching using the LIKE operator and is optimized for phrase matching as well as fuzzy matching. For more information on pg_trgm visit this site [[http://www.postgresql.org/docs/9.1/static/pgtrgm.html|Postgres Pg_Trgm]].
+                 * Added an extension to index the normalized_*_field_entry tables. The index allows searching using the LIKE operator and is optimized for phrase matching as well as fuzzy matching. For more information on pg_trgm visit this site [[http://www.postgresql.org/docs/9.1/static/pgtrgm.html|Postgres Pg_Trgm]].
-                 - Added a trigger to populate the normalized_*_field_entry tables from the *_field_entry tables.
+                 * Added a trigger to populate the normalized_*_field_entry tables from the *_field_entry tables.
+==== Pull Request ====
+https://github.com/evergreen-library-system/Evergreen/pull/5
+==== Blue Print ====
+https://blueprints.launchpad.net/evergreen/+spec/search-modifications
 ==== Deliverable ====