- Koha - lists.katipo.co.nz

OPAC Ask for a discharge
by Kazım ŞENTÜRK 24 Jan '24

24 Jan '24

Hello, When our patrons apply to discharge, if they hold a material there is a warning message about returning the items. We fine our patrons if they do not return the items timely, and in OPAC we would like to generate a warning message for the applicants who have to pay the fines before the discharge. Is it possible to set up a message for those users? Best regards Kazım ŞENTÜRK Kütüphane Müdür V. Bursa Uludağ Üniversitesi Kütüphane ve Dokümantasyon Daire Başkanlığı Prof. Dr. Fuat Sezgin Merkez Kütüphanesi Görükle Yerleşkesi Nilüfer / Bursa

1 0

Security configuration changes for Elasticsearch 7 and Koha
by Aleisha Amohia 23 Jan '24

23 Jan '24

Hello everybody We encountered a few issues with the security configuration required for Elasticsearch 7.17 since upgrading from ES6. We started with the minimal security setup documentation https://www.elastic.co/guide/en/elasticsearch/reference/7.17/security-minim… and we have a cluster with multiple nodes, so moved on to the basic security setup documentation https://www.elastic.co/guide/en/elasticsearch/reference/7.17/security-basic… but found we were getting all kinds of errors that we didn't know how to handle. Has anyone else implemented security for a multi-node Elasticsearch 7 cluster that could provide some insights? -- *Aleisha Amohia (she/her)* Technical Lead | Rōpū kohinga *Catalyst.Net Limited - Expert Open Source Solutions* *Catalyst.Net Ltd - a Catalyst IT group company* Tel: +64 4 803 2259 or +61 3 9116 2642 | www.catalyst.net.nz <http://www.catalyst.net.nz> Follow Catalyst Koha on Twitter <https://twitter.com/catalystkoha> | Subscribe to the Catalyst Koha newsletter <https://catalyst.us4.list-manage.com/subscribe?u=62457ff5060d15ee3c07d3fc4&…> Catalyst Logo CONFIDENTIALITY NOTICE: This email is intended for the named recipients only. It may contain privileged, confidential or copyright information. If you are not the named recipient, any use, reliance upon, disclosure or copying of this email or its attachments is unauthorised. If you have received this email in error, please reply via email or call +64 4 499 2267.

1 0

Re: [Koha] How to copy patron permissions?
by BRANNON, CHRISTOPHER 22 Jan '24

22 Jan '24

Michael, I've had some jQuery in the Koha library for quite a while. You should take a look at https://wiki.koha-community.org/wiki/JQuery_Library#Add_clear_and_preset_pe… There are 3 versions of this for different versions of Koha, but this latest one includes a clear permissions button, a couple of preset permission buttons, and a copy permissions button. Please check it out. We also did a video tutorial on this enhancement in season one of The Terrific Every-Other-Thursday Training Videos. You can find that here: https://youtu.be/M6aQITCJY0U. ___________________________ Christopher Brannon IT Coordinator 702 E Front Ave Coeur d'Alene, ID 83814 (208)769-2315 Ext. 456 cbrannon(a)cdalibrary.org www.cdalibrary.org Keep tabs on us at: Date: Tue, 26 Apr 2022 10:39:58 +0200 From: Michael Kuhn <mik(a)adminkuhn.ch> To: Koha <koha(a)lists.katipo.co.nz> Subject: [Koha] How to copy patron permissions? Message-ID: <abc69231-a587-77d5-01d2-7f98e5b16174(a)adminkuhn.ch> Content-Type: text/plain; charset=UTF-8; format=flowed Hi Is it possible to copy the permissions of another patron when creating a new one? I always thought this would happen when copying/duplicating an existing patron. But when I actually tried it today the permissions were not there with the new patron and I had to set them manually. Best wishes: Michael Kuhn

4 3

Next Koha Documentation meeting
by Charillon, Aude 22 Jan '24

22 Jan '24

Hello, The next Koha Documentation team meeting will take place on Wednesday 31 January at 15:00 UTC (check the date and time in your timezone: https://greenwichmeantime.com/time-gadgets/event-time/share/?name=Koha%2520… ) All details on how to join and what we're planning to discuss are on the meeting agenda https://wiki.koha-community.org/wiki/Documentation_meeting_31_January_2024 As for previous meetings, we will be using a Jitsi meeting link for the discussions. Here's a preview of what's on the agenda this month: - finally starting our overall review of what we want the manual to contain (use cases? workflows?) and how it should appear; - getting updates on what everybody has been working on; - deciding whether we want to plan more online documentation workshops (note: the next one is taking place on Tuesday 23 January - see https://wiki.koha-community.org/wiki/Documentation_Team_-_Drop-in_sessions See you there?) If you are curious about how the Koha manual gets made (and what we're doing to improve it), please join us! Thanks, Aude [aude_c on Koha IRC] Documentation Manager for the 24.05 cycle Aude Charillon Librarian | Customer Services Consultant PTFS Europe aude.charillon(a)ptfs-europe.com

1 0

The Terrific Every-Other-Thursday Training Video | 410 | Bug 26520 and the Messaging Preference Bug
by BRANNON, CHRISTOPHER 18 Jan '24

18 Jan '24

This week George will inform everyone about a messaging preference bug - but don't worry! His ability to notify you of this dastardly outcome is completely unaffected by this bug. This issue will not affect most workflows, but it is important to know about. It also never hurts to add your comments to the bug. https://youtu.be/vtjWbfQhHCU Sincerely, Christopher Brannon koha-US Admin

1 0

Zebra Index not working
by Bruns, Anke 18 Jan '24

18 Jan '24

Hi, we are facing a similar problem to https://stackoverflow.com/questions/26925152/reindexing-zebra-because-there- are-no-results-found-in-opac-and-intranet-search. I tried rebuilding the Zebra index, also checked the directories' permissions according to https://koha.katipo.co.narkive.com/cc099Nwf/reindexing-zebra-because-there-a re-no-results-found-in-opac-and-intranet-search and tried to reset the Zebra Index, as proposed in https://koha-community.org/manual/16.11/html/apis02.html . None of this shows any effect. According to screen output, the 6 biblios (it's a very new testing instance) are exported and the index is rebuilt as expected. Yet, there are no search results at all. Curiously, the Koha instance where this problem occurs is one of six instances on one and the same server, all other five having fully functional Zebra indexes, and a rebuild on another instance on that server works without any problems. Does anybody have an idea what might be the reason for this? Cheers in advance, Anke -- Anke Bruns M.A. (LIS) Arbeitsgruppe "Anwendungs- und Informationssysteme" E-Mail: anke.bruns(a)gwdg.de ------------------------------------------------- Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen (GWDG) Burckhardtweg 4, 37077 Göttingen, URL: https://gwdg.de Support: Tel.: +49 551 39-30000, URL: https://gwdg.de/support Sekretariat: Tel.: +49 551 39-30001, E-Mail: gwdg(a)gwdg.de Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen, Handelsregister-Nr. B 598 ------------------------------------------------- Zertifiziert nach ISO 9001 und ISO 27001 -------------------------------------------------

2 2

KOHA Upgraded - Configuration - HTML Customization
by Dr. Yesan S (DLIS) 17 Jan '24

17 Jan '24

Hello All, Recently we migrated Koha 21.05 to a new server and upgraded to Koha 23.05. We found that files in HTML customization are empty in the current installation. HMTL Source codes are not found. We want to modify them. Do we have to import the Koha configuration backup from the old server? Kindly advise. Is there any way to locate them in the current installation? thanks *Dr. Yesan Sellan, * *MLISc., PGDLAN, BCS., UGC-NET., PhD* *(Strategic | Learner | Achiever | Responsibility | Intellection)* Assistant Professor, PG and Research Department of Library and Information Science Bishop Heber College, Puthur PO, Trichy - 620017, INDIA Mobile: 91-9972348251 https://orcid.org/0000-0002-0501-5661 https://www.linkedin.com/in/dr-yesan-sellan-01230336/ -----------------------------------------------IMPORTANT------------------------------------------------------------------------- This message is intended only for the addressee. It may contain confidential information. Any unauthorized disclosure is strictly prohibited. If you have received this message in error, please notify us immediately so that we may correct our internal records. Please then delete the original message. Thank you

1 0

Call for news - Newsletter January 2024
by Koha Newsletter 16 Jan '24

16 Jan '24

Hi I'm collecting news for the January 2024 Koha Community Newsletter. Please send anything noteworthy to: kohanews (at) gmail (dot) com News criteria: * News items can be of any length. * Images are fine. * Anything and everything Koha. * Submit by the 26th of the month. Text format criteria: * Just structured plain text, or * HTML text to include tables or similar For events: * Consider adding your event to the Koha Community calendar at https://koha-community.org/calendar/ Thank you! Michael Kuhn Editor, Koha Community Newsletter

3 3

Reminder: General IRC meeting 17 January 2024
by Fischer, Katrin 16 Jan '24

16 Jan '24

Hi all, just a quick reminder that we have scheduled a General IRC meeting for tomorrow: https://wiki.koha-community.org/wiki/General_IRC_meeting_17_January_2024 Time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+General+IRC+M eeting <https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+General+IRC+ Meeting&iso=20240117T1400> &iso=20240117T1400 Katrin

1 0

Argument "0, 00" isn't numeric in numeric gt (>) at /usr/share/koha/lib/C4/Overdues.pm line 292.
by Michael Kuhn 15 Jan '24

15 Jan '24

Hi Our library is working with Koha 22.05.17. Since some days the anacron job "cron.daily" sends us an e-mail with hundreds of lines like the following every day: Argument "0,00" isn't numeric in numeric gt (>) at /usr/share/koha/lib/C4/Overdues.pm line 292. I see in the circulation and fine rules the "Overdue fines cap (amount)" shows as "0,00" instead of "0.00" as usual. However, this can't be changed at this place. Changing lines in script "Overdues.pm" according to https://gomezcardozo.com/error-en-fines-koha/ didn't help. How can this output be prevented? Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch

3 5