[Koha-bugs] [Bug 32707] ElasticSearch should not auto truncate (even if QueryAutoTruncate = 1) for identifiers (and some other fields)
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Sun Mar 24 15:04:57 CET 2024
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32707
--- Comment #23 from Janusz Kaczmarek <januszop at gmail.com> ---
(In reply to Janusz Kaczmarek from comment #22)
> (In reply to Victor Grousset/tuxayo from comment #21)
> > For test plan B, what is a clean way to have an analytical record with 773
> > $w = 1 ?
> > I after learning about analytics records, I tried to fill the gaps but in
> > the end I still get 111 results with that link:
> > http://localhost:8081/cgi-bin/koha/catalogue/search.pl?q=Control-number:1
> > Which for step B 7. doesn't make sense.
>
> Did you put "control-number" in the new ESPreventAutoTruncate preference?
I'm sorry--for analytical records to work correctly, you should put both:
control-number and record-control-number in the ESPreventAutoTruncate
preference.
Explanation: with searchfield control-number you go "up", i.e. from 773 $w to
the host record; with record-control-number you go "down", i.e. from the host
record the linked analytical records.
A patch with corrected test plan follows.
--
You are receiving this mail because:
You are watching all bug changes.
More information about the Koha-bugs
mailing list