<div dir="ltr"><div><div>Hello Claes,<br></div><font size="2" face="Calibri"><span style="font-size:11pt"><br>About Zebra first: maxRecordsForFacets is only used if facets are not built from Zebra (use_zebra_facets=0).<br></span></font></div><font size="2" face="Calibri"><span style="font-size:11pt">If facets are retrieved from Zebra you may face performance issue depending on the number of records you have in your catalogue (see bug 13665). You can then play with the parameter "facetNumRecs" in your zebra config file (default is 1000).<br></span></font><div><div><div><br></div><div>Regarding Elastic: Facets are not configurable yet, but will be with the patches on bug 18235. It is a priority for me and that is why I proposed a patch one year ago. You can easily test it and provide us feedback.<br><br></div><div>Regards,<br></div><div>Jonathan<br><br></div><div><div class="gmail_quote"><div dir="ltr">On Tue, 20 Feb 2018 at 10:23 Claes Eriksson <<a href="mailto:claes.eriksson@vti.se">claes.eriksson@vti.se</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="SV">
<div class="m_-4279159667496240014WordSection1">
<div id="m_-4279159667496240014divtagdefaultwrapper">
<ol start="1" type="1">
<li class="MsoNormal" style="color:black">
<span style="font-size:12.0pt" lang="EN-US">To begin with: “use_zebra_facets” was set to 1 in koha-conf.xml file, so that was not the problem.<u></u><u></u></span></li><li class="MsoNormal" style="color:black">
<span style="font-size:12.0pt" lang="EN-US">Regarding Zebra’s native faceting I find some traces in an old RCF saying that it would be nice to replace "</span><span style="font-size:9.5pt;font-family:"Arial",sans-serif" lang="EN-US">homegrown and inefficient
routines for faceting" with </span><span style="font-size:12.0pt" lang="EN-US">Zebra’s native faceting. </span><span style="font-size:12.0pt"><a href="https://wiki.koha-community.org/wiki/C_%26_P_Search_Rewrite_RFC#.28e.29_Implement_search_engine_native_faceting" target="_blank">https://wiki.koha-community.org/wiki/C_%26_P_Search_Rewrite_RFC#.28e.29_Implement_search_engine_native_faceting</a>.</span><span style="font-size:12.0pt" lang="EN-US"><u></u><u></u></span></li><li class="MsoNormal" style="color:black">
<span style="font-size:12.0pt" lang="EN-US">I have also checked some libraries around the world with Koha </span><span style="font-size:9.5pt;font-family:"Arial",sans-serif" lang="EN-US">set up by some of the larger consultants and they all handle facets in
this way. I may ad to my ranting that it becomes a serious problem when it comes to subject facets. Narrowing down a search using subject facets that does only reflect the first 20 results is not helping a student or researcher. BTW, we tested setting default
to 50 first results and response time increased with 5-8 seconds = not acceptable.</span><span style="font-size:12.0pt" lang="EN-US"><u></u><u></u></span></li><li class="MsoNormal" style="color:black">
<span style="font-size:9.5pt;font-family:"Arial",sans-serif" lang="EN-US">As I understand facets are hardcoded in Zebra and not at all configurable. If I am wrong I would be most grateful if you could hint me in the right direction. In ElasticSearch it is under
discussion and not solved according to </span><span style="color:windowtext" lang="EN-AU">bug 18235</span><span style="font-size:9.5pt;font-family:"Arial",sans-serif" lang="EN-US">?</span><span style="font-size:12.0pt" lang="EN-US"><u></u><u></u></span></li></ol>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black" lang="EN-US"><u></u> <u></u></span></p>
<p><span style="font-size:9.5pt;font-family:"Arial",sans-serif;color:black">The best</span><span style="font-size:12.0pt;color:black"><u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:9.5pt;font-family:"Arial",sans-serif;color:black">Claes</span><span style="font-size:12.0pt;color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:7.5pt;color:#767171" lang="EN-US">------------------------------------<br>
</span><b><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:black" lang="EN-US">Claes Eriksson</span></b><b><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:#767171" lang="EN-US"><br>
</span></b><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:#7f7f7f" lang="EN-US">Information specialist<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Verdana",sans-serif;color:#7f7f7f" lang="EN-US"><br>
</span><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:#7f7f7f" lang="EN-US">Department of Communication, Marketing and Library</span><span style="color:black" lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:#7f7f7f" lang="EN-US">Swedish National Road and Transport Research Institute</span></b><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:#7f7f7f" lang="EN-US">
(VTI)<br>
VTI, SE-581 95 Linkoeping, Sweden<br>
Tel: <a href="tel:+46%2013%2020%2040%2000" value="+4613204000" target="_blank">+46-13-20 40 00</a> Direct: <a href="tel:+46%2013%2020%2041%2099" value="+4613204199" target="_blank">+46-13-20 41 99</a><br>
E-mail: <a href="mailto:claes.eriksson@vti.se" target="_blank">claes.eriksson@vti.se</a></span><span style="color:black" lang="EN-US"><u></u><u></u></span></p>
<div class="MsoNormal" style="text-align:center" align="center">
<hr width="98%" size="2" align="center">
</div>
<div id="m_-4279159667496240014divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black">Från:</span></b><span style="color:black"> Tomas Cohen Arazi <<a href="mailto:tomascohen@gmail.com" target="_blank">tomascohen@gmail.com</a>><br>
<b>Skickat:</b> den 20 februari 2018 01:13:18<br>
<b>Till:</b> David Cook<br>
<b>Kopia:</b> Claes Eriksson; <a href="mailto:koha-devel@lists.koha-community.org" target="_blank">koha-devel@lists.koha-community.org</a><br>
<b>Ämne:</b> Re: [Koha-devel] Elasticsearch and facets</span> <u></u><u></u></p>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div></div></div><div link="blue" vlink="purple" lang="SV"><div class="m_-4279159667496240014WordSection1">
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-US">Facets are configurable, and goal is feature parity.<u></u><u></u></span></p>
<div>
<div>
<p class="MsoNormal">El lun., 19 de feb. de 2018 8:59 p. m., David Cook <<a href="mailto:dcook@prosentient.com.au" target="_blank">dcook@prosentient.com.au</a>> escribió:<u></u><u></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class="m_-4279159667496240014xmsonormal"><span style="color:#1f497d">Hi Claes,</span><u></u><u></u></p>
<p class="m_-4279159667496240014xmsonormal"><span style="color:#1f497d"> </span><u></u><u></u></p>
<p class="m_-4279159667496240014xmsonormal"><span style="color:#1f497d" lang="EN-AU">I think the maxRecordsForFacets system preference might be a bit legacy at this point. It was first used when we were building facets manually from retrieved records from Zebra (which was an awful
awful no good process). However, I think most installations using Zebra these days use Zebra’s native faceting which uses the entire result set. At least that’s how things were a year or two ago. It may have changed since then. I’d have to double-check, and
I have a lot on at the moment, so I’ll leave that for yourself or someone else to check. In any case, we’re all aware of the limitations around that system preference, which is why we made the move to Zebra’s native faceting. (One easy thing to check is in
your koha-conf.xml file to see if “use_zebra_facets” is set to 1. If so, then I think “maxRecordsForFacets” shouldn’t have any effect.</span><span lang="EN-AU"><u></u><u></u></span></p>
<p class="m_-4279159667496240014xmsonormal"><span style="color:#1f497d" lang="EN-AU"> </span><span lang="EN-AU"><u></u><u></u></span></p>
<p class="m_-4279159667496240014xmsonormal"><span style="color:#1f497d" lang="EN-AU">I’m not very familiar with the ElasticSearch efforts, but I think it started out as a like-for-like drop-in replacement. Making facets configurable would be great, but I’m not sure anyone has this
as a priority at the moment. I think for now the main goal of ElasticSearch may be stability?</span><span lang="EN-AU"><u></u><u></u></span></p>
<p class="m_-4279159667496240014xmsonormal"><span style="color:#1f497d" lang="EN-AU"> </span><span lang="EN-AU"><u></u><u></u></span></p>
<div>
<p class="m_-4279159667496240014xmsonormal"><span style="color:#1f497d" lang="EN-AU">David Cook</span><span lang="EN-AU"><u></u><u></u></span></p>
<p class="m_-4279159667496240014xmsonormal"><span style="color:#1f497d" lang="EN-AU">Systems Librarian</span><span lang="EN-AU"><u></u><u></u></span></p>
<p class="m_-4279159667496240014xmsonormal"><span style="color:#1f497d" lang="EN-AU">Prosentient Systems</span><span lang="EN-AU"><u></u><u></u></span></p>
<p class="m_-4279159667496240014xmsonormal"><span style="color:#1f497d" lang="EN-AU">72/330 Wattle St</span><span lang="EN-AU"><u></u><u></u></span></p>
<p class="m_-4279159667496240014xmsonormal"><span style="color:#1f497d" lang="EN-AU">Ultimo, NSW 2007</span><span lang="EN-AU"><u></u><u></u></span></p>
<p class="m_-4279159667496240014xmsonormal"><span style="color:#1f497d" lang="EN-AU">Australia</span><span lang="EN-AU"><u></u><u></u></span></p>
<p class="m_-4279159667496240014xmsonormal"><span style="color:#1f497d" lang="EN-AU"> </span><span lang="EN-AU"><u></u><u></u></span></p>
<p class="m_-4279159667496240014xmsonormal"><span style="color:#1f497d" lang="EN-AU">Office: <a href="tel:02%2092%2012%2008%2099" value="+33292120899" target="_blank">02 9212 0899</a></span><span lang="EN-AU"><u></u><u></u></span></p>
<p class="m_-4279159667496240014xmsonormal"><span style="color:#1f497d" lang="EN-AU">Direct: <a href="tel:02%2080%2005%2005%2095" value="+33280050595" target="_blank">02 8005 0595</a></span><span lang="EN-AU"><u></u><u></u></span></p>
</div>
<p class="m_-4279159667496240014xmsonormal"><span style="color:#1f497d" lang="EN-AU"> </span><span lang="EN-AU"><u></u><u></u></span></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="m_-4279159667496240014xmsonormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> <a href="mailto:koha-devel-bounces@lists.koha-community.org" target="_blank">
koha-devel-bounces@lists.koha-community.org</a> [mailto:<a href="mailto:koha-devel-bounces@lists.koha-community.org" target="_blank">koha-devel-bounces@lists.koha-community.org</a>]
<b>On Behalf Of </b>Claes Eriksson<br>
<b>Sent:</b> Monday, 19 February 2018 11:01 PM<br>
<b>To:</b> <a href="mailto:koha-devel@lists.koha-community.org" target="_blank">koha-devel@lists.koha-community.org</a><br>
<b>Subject:</b> [Koha-devel] Elasticsearch and facets</span><span lang="EN-AU"><u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="m_-4279159667496240014xmsonormal"><span lang="EN-AU"> <u></u><u></u></span></p>
<div>
<p class="m_-4279159667496240014xmsonormal"><span lang="EN-AU">First some ranting about Zebra and then a question about ElasticSearch.<u></u><u></u></span></p>
</div>
<div>
<p class="m_-4279159667496240014xmsonormal"><span lang="EN-AU"> <u></u><u></u></span></p>
</div>
<div>
<p class="m_-4279159667496240014xmsonormal"><span lang="EN-AU">Using Zebra there is a Global system pref. called maxRecordsForFacets. By default the number of records used to build the facet list is the first 20 results shown. You also get a warning in the manual to increase the
number since it will impact respons time. Building a facet list out of 20 records may be enough for some people but if you think twice about it you realise that it is quite misleading, especially since the user does not know that the facet list is built on
a very limited selection of records. Having the sort set on Author and searching for realivity theory, the facet list may not show Einstein if your library is specialised in physics and have a fairly large collection.<u></u><u></u></span></p>
</div>
<div>
<p class="m_-4279159667496240014xmsonormal"><span lang="EN-AU"> <u></u><u></u></span></p>
</div>
<div>
<p class="m_-4279159667496240014xmsonormal"><span lang="EN-AU">I have high hopes for ElasticSearch to work with facets in a better way. The best would be if all the index could be used for producing e.g. the author facet and that it would have minimal impact on system performance.
I understand that there is discussion about making facets configurable (bug 18235) but I cannot see any traces of the improvements I would like to see, but I may be wrong since I am quite new working with Koha.<u></u><u></u></span></p>
</div>
<div>
<p class="m_-4279159667496240014xmsonormal"><span lang="EN-AU"> <u></u><u></u></span></p>
</div>
<div>
<p class="m_-4279159667496240014xmsonormal"><span lang="EN-AU">Regards<u></u><u></u></span></p>
</div>
<div>
<p class="m_-4279159667496240014xmsonormal"><span lang="EN-AU">Claes Eriksson, VTI, Sweden<u></u><u></u></span></p>
</div>
<div>
<p class="m_-4279159667496240014xmsonormal"><span lang="EN-AU"> <u></u><u></u></span></p>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="EN-AU">_______________________________________________<br>
Koha-devel mailing list<br>
</span><a href="mailto:Koha-devel@lists.koha-community.org" target="_blank"><span lang="EN-AU">Koha-devel@lists.koha-community.org</span></a><span lang="EN-AU"><br>
</span><a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" target="_blank"><span lang="EN-AU">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</span></a><span lang="EN-AU"><br>
website : </span><a href="http://www.koha-community.org/" target="_blank"><span lang="EN-AU">http://www.koha-community.org/</span></a><span lang="EN-AU"><br>
git : </span><a href="http://git.koha-community.org/" target="_blank"><span lang="EN-AU">http://git.koha-community.org/</span></a><span lang="EN-AU"><br>
bugs : </span><a href="http://bugs.koha-community.org/" target="_blank"><span lang="EN-AU">http://bugs.koha-community.org/</span></a><span lang="EN-AU"><u></u><u></u></span></p>
</blockquote>
</div>
<p class="MsoNormal"><span lang="EN-US">-- <u></u><u></u></span></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt;font-family:"Helvetica",sans-serif;color:#757575" lang="EN-US">Tomás Cohen Arazi<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt;font-family:"Helvetica",sans-serif;color:#757575" lang="EN-US">Theke Solutions (</span><span style="font-size:9.5pt;font-family:"Helvetica",sans-serif;color:#757575"><a href="http://theke.io/" target="_blank"><span lang="EN-US">https://theke.io</span></a></span><span style="font-size:9.5pt;font-family:"Helvetica",sans-serif;color:#757575" lang="EN-US">)<br>
</span><span style="font-size:9.5pt;font-family:"Segoe UI Symbol",sans-serif;color:#757575" lang="EN-US">✆</span><span style="font-size:9.5pt;font-family:"Helvetica",sans-serif;color:#757575" lang="EN-US"> <a href="tel:+54%209%20351%20351-3384" value="+5493513513384" target="_blank">+54 9351 3513384</a><br>
GPG: B2F3C15F<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div></div>
_______________________________________________<br>
Koha-devel mailing list<br>
<a href="mailto:Koha-devel@lists.koha-community.org" target="_blank">Koha-devel@lists.koha-community.org</a><br>
<a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" rel="noreferrer" target="_blank">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a><br>
website : <a href="http://www.koha-community.org/" rel="noreferrer" target="_blank">http://www.koha-community.org/</a><br>
git : <a href="http://git.koha-community.org/" rel="noreferrer" target="_blank">http://git.koha-community.org/</a><br>
bugs : <a href="http://bugs.koha-community.org/" rel="noreferrer" target="_blank">http://bugs.koha-community.org/</a></blockquote></div></div></div></div></div>