Change #8118
Category | None |
Changed by | Mike Rylander <mrylander | @gmail.com>
Changed at | Thu 23 Sep 2021 11:20:30 |
Repository | git://git.evergreen-ils.org/Evergreen.git |
Project | Evergreen |
Branch | master |
Revision | fe23d265f02bd4ef9a5bf61b2abca0898f74c7be |
Comments
LP#1864516: case-insensitive browse entry display value comparison Following up on bug 1350831, there remains one complaint relating to "bad data makes browse suboptimal" that can't actually be handled today by the existing Evergreen code or a pullrequested branch: case differences, particularly in titles. We should allow an Evergreen admin to decide on a field-by-field basis whether case should be considered when determining the uniqueness of a browse entry coming from a bibliographic record, effectively allowing case folding. Note that authority fields, being by definition the authorized value that should be used, do not support this case folding. However, if authority records are processed first, then bibliographic fields can fold /into/ those authority fields, achieving the desired result and, in fact, using the best possible case-preserving display value. Signed-off-by: Mike Rylander <mrylander@gmail.com> Signed-off-by: Elaine Hardy <ehardy@georgialibraries.org> Signed-off-by: Chris Sharp <csharp@georgialibraries.org>
Changed files
- Open-ILS/examples/fm_IDL.xml
- Open-ILS/src/sql/Pg/002.schema.config.sql
- Open-ILS/src/sql/Pg/030.schema.metabib.sql
- Open-ILS/src/sql/Pg/upgrade/XXXX.schema.case-insensitive-browse-field-match.sql