[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 #71 from Katrin Fischer <katrin.fischer at bsz-bw.de> ---
(In reply to Robin Sheat from comment #70)
> (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.

Thx!

> 
> > 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.

We currently do it alphabetically - which is kind of ok, but as we pick the
facets quite randomly out of 20 records... 

I understand about not changing behaviour significantly for now, but I think
there are a lot of weirdnesses that we shouldn't translate to Elastic Search if
we can help it. And our facets are quite weird right now.

> > 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.

Sorry, I don't understand, what do you mean by "(roughly, but I think mostly
accurate for the scale of results in a Koha system.)"? 

The demo database seems to be quite small and from here it's not very fast, so
wondering about how performance looks for you. Have you done testing with a
bigger database by chance? (100.000+?). We are running into a lot of
never-noticed problems right now with the bigger databases and searching.

About the number - I think limiting to 10 could be problematic for things like
itemtypes, locations and branches. It could be good to have that configurable
at some point or an option to just show 'all' for some of the facets.

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