[Koha-bugs] [Bug 19893] Alternative optimized indexing for Elasticsearch

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Fri Sep 7 15:09:09 CEST 2018


https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19893

--- Comment #98 from Ere Maijala <ere.maijala at helsinki.fi> ---
(In reply to David Gustafsson from comment #97)
> I just realized that splitting up the fields would not make any difference
> with the Koha-specific implementation, it makes no distinction if subfield
> mappings are defined together in one mapping or separately. I would guess

True, but in my version in bug 20244 it does make a difference.

What comes to the indexing of 100 etc. I can't see the problem with indexing
the whole field as an entity. Since everything in it is in a single field, it's
bound to be something belonging together. If, however, that turns out to be a
problem, it would be way better to be able to define e.g. that 100abcde is one
field and the rest is another.

-- 
You are receiving this mail because:
You are watching all bug changes.


More information about the Koha-bugs mailing list