[Koha-bugs] [Bug 12478] Elasticsearch support for Koha

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

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12478

--- Comment #70 from Robin Sheat <robin at catalyst.net.nz> ---
(In reply to Katrin Fischer from comment #69)
> 1) Can you show the number of results behind the facets? There is currently
> a preference for this, but I couldn't turn it on/chefk if it turned on.

I've turned it on now.

> 2) Can facets be sorted by most used to less used in a result list? 

This is a Koha question, not a search question. We can re-order them however we
like (though, I don't know how meaningful that'd be tbh.) I'm trying to not
change the behaviour significantly beyond what zebra can do.

> 3) Can you show all entries for a big result list? How does it limit which
> facets to show?

That's not how facets work in this case. It calculates facets across all the
results (roughly, but I think mostly accurate for the scale of results in a
Koha system.) It then returns the most frequent 10. At the moment, that's
what's displaying. When I get to that point in my todo list, it'll show 5 until
you click on the "show more" thing. Which forces a full page reload for
hysterical raisins.

> 4) If you search for () it explodes rather spectacularly.

It sure does.

There's an option to make the string parsing more lenient I need to enable. I
also need to catch that error better. Basically, if you give it anything that
can't be parsed as a properly lucene query, you'll see this.

The real solution is to parse the query in Koha into a tree, then turn that
tree into a proper Elasticsearch query. For obvious reasons (it's hard!), I'm
not doing that yet.

The other part of the real solution is to catch and parse that ES response and
say something sensible, rather than just output it verbatim.

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