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

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Wed Oct 26 15:25:21 CEST 2016


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

Jonathan Druart <jonathan.druart at bugs.koha-community.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |In Discussion

--- Comment #7 from Jonathan Druart <jonathan.druart at bugs.koha-community.org> ---
This patchset is a POC and cannot be pushed as it for several reasons:

- 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
- the patron attributes are not indexed and so not searchable
- the index is not maintained when a patron record is updated
- 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).

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.

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


More information about the Koha-bugs mailing list