[Koha-bugs] [Bug 17500] Use Elasticsearch to search for patrons

[bugzilla-daemon at bugs.koha-community.org]

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

Nick Clemens <nick at bywatersolutions.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nick at bywatersolutions.com

--- Comment #15 from Nick Clemens <nick at bywatersolutions.com> ---
(In reply to Jonathan Druart from comment #7)
> - we will need to rethink the existing code as we would need to index/search
> something else than bibliographic records. And the code is too bib-centric
> at the moment

I think this can be done - I think is a good opportunity to consider accessing
ElasticSearch via perl modules from ES and not through catmandu

> - the patron attributes are not indexed and so not searchable

Yup

> - the index is not maintained when a patron record is updated

Yup

> - it makes ES mandatory as it removes the existing MySQL search. We will
> need to let the ability to choose/switch between both (at least for a given
> period).

If it replicates close enough I think this is a good opportunity to turn ES on
by default, then search testing is possible for all

> 
> It highlights the fact that we need to abstract our Elasticsearch code to
> make it more powerful and extensive.
> Moreover there is something hard to fix: at the moment it's possible to sort
> the table by library name or patron category name. But as we only index the
> code it is possible to order the results by these 2 fields, and it won't be
> possible unless we index them.
> But ofc if we index them, we will have to reindex everything if the
> description is updated in the admin config. Note that we will have this
> problematic for bibliographic records very soon as well and we will have to
> decide what to do.

I think the descriptions don't change very often - a warning that things need
to be reindexed I think suffices.  Bug 18950 proposed allowing user to reindex,
however, I think safer is to allow user to request reindex, then handle on
server by it staff to check if reindex requested and schedule.

Bug 18948 also serves to ease reindexing by doing it in the background and
preserving searching while done. Paves the way for allowing changes to
mappings/descriptions etc and only committing on reindex

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