<!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 7419 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 202, Issue 14<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: Elasticsearch not auto-updating after cataloguing<br> (Philippe Blouin)<br> 2. Re: Elasticsearch not auto-updating after cataloguing<br> (Thomas Klausner)<br> 3. Handling normalized phone number data (dcook@prosentient.com.au)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 13 Sep 2022 14:58:49 -0400<br>From: Philippe Blouin <philippe.blouin@inlibro.com><br>To: Tomas Cohen Arazi <tomascohen@gmail.com><br>Cc: koha-devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Elasticsearch not auto-updating after<br> cataloguing<br>Message-ID: <ea590f7c-17c9-e7c1-359d-b25a0041a2c8@inlibro.com><br>Content-Type: text/plain; charset="utf-8"; Format="flowed"<br><br>Hi!<br><br>Depends on the installation, but where background_jobs_worker.pl runs or <br>not makes not difference in where the cataloguing->indexing path works.<br><br>It seems to always work when Koha runs on the same machine as ES, and <br>not otherwise.<br><br>Still looking for possible clues.<br><br>Best regards,<br><br>Philippe Blouin,<br>Directeur de la technologie<br><br>Tél. : (833) 465-4276, poste 230<br>philippe.blouin@inLibro.com<br><br>inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com><br>On 2022-09-11 22:47, Tomas Cohen Arazi wrote:<br>> Is koha-worker running?<br>><br>> El vie, 9 sept 2022 12:42, Philippe Blouin <br>> <philippe.blouin@inlibro.com> escribió:<br>><br>> Hello kohaers!<br>><br>> Simply put: our production servers installation work very fine,<br>> each change into a record is immediately reindexed into ES.<br>><br>> BUT on laptop (ubuntu 20 or 22), the reindexing never occurs. We<br>> have to call rebuild_elasticsearch.pl<br>> <http://rebuild_elasticsearch.pl> manually so the search finds<br>> anything. The configuration refers to a remote ES server (instead<br>> of localhost like the prod servers), but I don't see how that<br>> would make a difference since that works once rebuilt.<br>><br>> Any clue on what I'm missing would be greatly appreciated.<br>><br>> Best regards,<br>><br>> -- <br>> Philippe Blouin,<br>> Directeur de la technologie<br>><br>> Tél. : (833) 465-4276, poste 230<br>> philippe.blouin@inLibro.com<br>><br>> inLibro | pour esprit libre | www.inLibro.com<br>> <http://www.inLibro.com><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>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220913/9b00ac59/attachment-0001.htm><br><br>------------------------------<br><br>Message: 2<br>Date: Tue, 13 Sep 2022 22:33:32 +0200<br>From: Thomas Klausner <domm@plix.at><br>To: koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Elasticsearch not auto-updating after<br> cataloguing<br>Message-ID: <20220913203332.GM490306@plix.at><br>Content-Type: text/plain; charset=us-ascii<br><br>Hi!<br><br>On Tue, Sep 13, 2022 at 02:58:49PM -0400, Philippe Blouin wrote:<br> <br>> Depends on the installation, but where background_jobs_worker.pl runs or not<br>> makes not difference in where the cataloguing->indexing path works.<br>> <br>> It seems to always work when Koha runs on the same machine as ES, and not<br>> otherwise.<br><br>Is the remote ES exposed via https? Maybe you have slightly different <br>Perls or Mozilla::CA installation? Any errors in the logs?<br><br>Which Koha Verion are you running? Are you sure both latpop and server <br>run the same version?<br><br>In the source code there is a param 'skip_record_index', which will <br>prevent the immediate indexing after an edit (if I've skimmed the code <br>correctly). Maybe that is set? Though I don't know when it would be set <br>(by whom..)<br><br>Greetings,<br>domm<br><br>-- <br>#!/usr/bin/perl https://domm.plix.at<br>for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}<br><br><br>------------------------------<br><br>Message: 3<br>Date: Wed, 14 Sep 2022 16:42:55 +1000<br>From: <dcook@prosentient.com.au><br>To: "'koha-devel'" <koha-devel@lists.koha-community.org><br>Cc: "'Kyle Hall'" <kyle@bywatersolutions.com>, "'Tomas Cohen Arazi'"<br> <tomascohen@theke.io>, "'Martin Renvoize'"<br> <martin.renvoize@ptfs-europe.com><br>Subject: [Koha-devel] Handling normalized phone number data<br>Message-ID: <19c201d8c805$48f950c0$daebf240$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi all,<br><br> <br><br>I've been working lately on<br>https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23817 in an effort<br>to let staff users easily search phone numbers in the Patrons module.<br><br> <br><br>Currently, phone number searching doesn't work if you have punctuation or<br>other formatting inconsistent with your search query. <br><br> <br><br>So I'm proposing normalizing phone numbers. Normalizing the search query is<br>easy, but normalizing the data in the database is harder. In older versions<br>of Koha, I used SQL to normalize the phone column in the WHERE clause, but<br>that's seemingly impossible now that we're using DataTables and the REST<br>API.<br><br> <br><br>So it seems to me the only way forward is to normalize the data in the<br>database. I've attached a patch which provides a Koha::Patron->phone() set<br>method which normalizes the phone number before it's saved in the database,<br>but I don't know what other Koha folk think about that. <br><br> <br><br>Thoughts?<br><br> <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> <br><br>Office: 02 9212 0899<br><br>Online: 02 8005 0595<br><br> <br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220914/cc5f2cca/attachment-0001.htm><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 202, Issue 14<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>