<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 15765 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 190, Issue 8<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. Re: Security releases for all stable branches - UPGRADE! (Paul A)<br> 2. Re: Immediate logout in Koha 21.05.02 (03?) (Michael Kuhn)<br> 3. Re: Security releases for all stable branches - UPGRADE!<br> (Fridolin SOMERS)<br> 4. Re: Listing Zebra (and Elasticsearch) indexes for end-users'<br> benefit (Fridolin SOMERS)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 7 Sep 2021 10:15:01 -0400<br>From: Paul A <paul.a@navalmarinearchive.com><br>To: koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Security releases for all stable branches -<br> UPGRADE!<br>Message-ID:<br> <26a4ad59-1bc3-29d2-6229-bbe556ece4e2@navalmarinearchive.com><br>Content-Type: text/plain; charset=utf-8; format=flowed<br><br>On 2021-09-06 8:00 a.m., Jonathan Druart wrote:<br>> Don't ignore this email!<br>[snip]> If you are using an older version of Koha (<19.11) you should either<br>> upgrade to a newer version, or apply those two patches (they should<br>> apply on older versions as well):<br><br>Jonathan -- many thanks. As for older versions, for 3.8.24 (I know ;=} <br>but it still works perfectly for a non-lending library, so we still <br>consider it as a "stable" branch):<br><br>First patch works apparently perfectly, but starts around line 179<br>Second patch, gdpr_proc_consent does not exist (compliance for us taken <br>care of at system level)<br>Third patch, PatronSelfRegistration does not exist.<br><br>Best regards all round and please stay safe,<br>Paul<br><br><br>------------------------------<br><br>Message: 2<br>Date: Tue, 7 Sep 2021 23:02:41 +0200<br>From: Michael Kuhn <mik@adminkuhn.ch><br>To: koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Immediate logout in Koha 21.05.02 (03?)<br>Message-ID: <8d53e163-0473-45f2-e589-bdf696c2a9a8@adminkuhn.ch><br>Content-Type: text/plain; charset=utf-8; format=flowed<br><br>Hi Katrin<br><br>Yo wrote:<br><br> > have you tried if setting them makes a difference?<br><br>I have now set both "OPACBaseURL" and "staffClientBaseURL" but it <br>doesn't make a difference.<br><br> > Another pref that comes to mind is "timeout".<br><br>This was already set to 1500000<br><br><br>So still opening an SSH tunnel with<br><br>ssh -p 33 -t root@host1 ssh -C -g -L 10080:kohahost:80 -L <br>18080:kohahost:8080 -J root@host2 koha@kohahost<br><br>first worked but after loading and updateing the Koha database leads to <br>an immediate logout after the first click when accesssing via <br>http://host1:18080<br><br>However, as said the system administrator now opened the firewall and <br>gave me direct access to the staff client so direct access via <br>http://kohahost:8080 works as expected and I consider this matter as <br>"solved".<br><br>Thanks for your time!<br><br>Best wishes: Michael<br>-- <br>Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis<br>Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz<br>T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch<br><br><br>------------------------------<br><br>Message: 3<br>Date: Tue, 7 Sep 2021 21:34:26 -1000<br>From: Fridolin SOMERS <fridolin.somers@biblibre.com><br>To: koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Security releases for all stable branches -<br> UPGRADE!<br>Message-ID: <e3ad353a-f1ab-07fc-2fe8-603dec347519@biblibre.com><br>Content-Type: text/plain; charset=utf-8; format=flowed<br><br>Hi,<br><br>If anyone needs it we have patches for 17.11 and 16.11 (conflicts are <br>trivial).<br><br>Look at the 2 top commits in :<br>https://git.biblibre.com/biblibre/kohac/commits/branch/17.11/MT33996<br>https://git.biblibre.com/biblibre/kohac/commits/branch/16.11/MT33996<br><br>Best regards,<br><br>Le 07/09/2021 à 04:15, Paul A a écrit :<br>> On 2021-09-06 8:00 a.m., Jonathan Druart wrote:<br>>> Don't ignore this email!<br>> [snip]> If you are using an older version of Koha (<19.11) you should <br>> either<br>>> upgrade to a newer version, or apply those two patches (they should<br>>> apply on older versions as well):<br>> <br>> Jonathan -- many thanks. As for older versions, for 3.8.24 (I know ;=} <br>> but it still works perfectly for a non-lending library, so we still <br>> consider it as a "stable" branch):<br>> <br>> First patch works apparently perfectly, but starts around line 179<br>> Second patch, gdpr_proc_consent does not exist (compliance for us taken <br>> care of at system level)<br>> Third patch, PatronSelfRegistration does not exist.<br>> <br>> Best regards all round and please stay safe,<br>> Paul<br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website : https://www.koha-community.org/<br>> git : https://git.koha-community.org/<br>> bugs : https://bugs.koha-community.org/<br><br>-- <br>Fridolin SOMERS <fridolin.somers@biblibre.com><br>Software and system maintainer 🦄<br>BibLibre, France<br><br><br>------------------------------<br><br>Message: 4<br>Date: Tue, 7 Sep 2021 22:49:48 -1000<br>From: Fridolin SOMERS <fridolin.somers@biblibre.com><br>To: 'koha-devel' <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Listing Zebra (and Elasticsearch) indexes<br> for end-users' benefit<br>Message-ID: <146d7484-dda7-f4df-93f3-66e9a62dc86d@biblibre.com><br>Content-Type: text/plain; charset=UTF-8; format=flowed<br><br>Hi, sounds nice.<br><br>FIY I am actually using a transformation of Zebra config in order to <br>present it in CSV:<br>https://git.biblibre.com/biblibre/tools/src/branch/master/zebra/list_indexes.xsl<br><br>We may use this to display in HTML.<br><br>Best regards,<br><br>Le 18/08/2021 à 17:12, dcook@prosentient.com.au a écrit :<br>> Hi all,<br>> <br>> As always, a new day brings a new Zebra idea.<br>> <br>> One of my librarians asked me if there was any way to get a list of <br>> Zebra indexes (particularly for Record Matching Rules), and I was all <br>> prepared to say no… when I remembered something I read the other day.<br>> <br>> It turns out you can send the query "@attr exp1 1=1 attributedetails" to <br>> the magical database “IR-explain-1”, and it will give you a list of all <br>> the indexes in that database along with the type of index and how many <br>> documents are indexed against that index in the database. I think this <br>> is something that we should add to Koha!<br>> <br>> I’m not familiar with Koha’s use of Elasticsearch, but I imagine there <br>> is an easy way of getting a list of Elasticsearch indexes?<br>> <br>> --<br>> <br>> Of course, while having a list of indexes is good, it would be nice to <br>> know what MARC data is in each of those indexes. I’m thinking about <br>> creating a Koha Plugin that parses "biblio-koha-indexdefs.xml" and shows <br>> a user-friendly view of what parts of the MARC record are put into which <br>> indexes.<br>> <br>> --<br>> <br>> What do folk think about that? I think having a list of Zebra indexes <br>> would be very useful for Record Matching Rules, but also for a “Search <br>> tips” guide for the Staff Interface and OPAC.<br>> <br>> While we could provide a static list of indexes, but I think that would <br>> be too much of a maintenance burden. I think having a list from Zebra <br>> (or Elasticsearch), which we could cache in Memcached, would be the way <br>> to go.<br>> <br>> Ideally, we could have an API route that surfaces this information, so <br>> that we could just do an AJAX lookup from a web interface.<br>> <br>> --<br>> <br>> I’m hoping my librarian will sponsor development of a plugin, but I <br>> think this would be useful in the core Koha code.<br>> <br>> David Cook<br>> <br>> Senior Software Engineer<br>> <br>> Prosentient Systems<br>> <br>> Suite 7.03<br>> <br>> 6a Glen St<br>> <br>> Milsons Point NSW 2061<br>> <br>> Australia<br>> <br>> Office: 02 9212 0899<br>> <br>> Online: 02 8005 0595<br>> <br><br>-- <br>Fridolin SOMERS <fridolin.somers@biblibre.com><br>Software and system maintainer 🦄<br>BibLibre, France<br><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 190, Issue 8<br>******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>