Hi Michael,
we looked into this ages ago and it didn't seem possible to achieve both
- treating hyphen (-) as a space and not a space at the same time. Maybe
we missed something - If there is a solution, I'd be interested in a
how-to! :)
Katrin
On 24.09.19 20:47, Michael Kuhn wrote:
Hi David
Many thanks for your reply and the hints!
After a standard installation of Koha 18.11 the CHR indexing is used,
thus the configuration is done in file "word-phrase-utf.chr".
A catalog search
* for "Sintiswing" shows 1 hit
* for "Sinti-Swing" shows 18 hits, the hyphen is used as a breaking
character, so any record containing "Sinti-Swing" or "Sinti" and
"Swing" is found, but not "Sintiswing"
I changed the following line, omitting the hyphen (between comma and
dot):
space
{\001-\040}!"#$%&'\()*+,./:;<=>?@\[\\]^_`\{|}~’{\x88-\x89}{\x98-\x9C}¡¿«»
After a Zebra reindexing a catalog search
* for "Sintiswing" shows 1 hit
* for "Sinti-Swing" now shows only 8 hits, the hyphen is no more used
as a breaking character, so any record containing "Sinti Swing" or
"Sinti-Swing" is found, but not "Sintiswing"
I also tried to add "map (-) @" but this leads to the original results.
In short: My change of configuration didn't lead to the desired
result... If searching for "Sintiswing" also "Sinti-Swing" should be
found, and vice versa. This is not the case.
Since I couldn't find any documentation about CHR indexing - does
anyone know where to find out more about the CHR way of indexing?
Best wishes: Michael
_______________________________________________
Koha mailing list http://koha-community.org
[email protected]
https://lists.katipo.co.nz/mailman/listinfo/koha
