- Koha - lists.katipo.co.nz

Koha May release with security fixes
by Fridolin SOMERS 19 Jun '24

19 Jun '24

Hello everyone 🤗 The Koha community is proud to announce the release of May versions: 24.05.01 23.11.06 23.05.12 22.11.18 22.05.22 It is a bugfix/maintenance release including some security fixes. It is highly recommended to upgrade. The full release notes will soon be available here: https://koha-community.org/koha-24-05-01-released/ https://koha-community.org/koha-23-11-06-released/ https://koha-community.org/koha-23-05-12-released/ https://koha-community.org/koha-22-11-18-released/ https://koha-community.org/koha-22-05-22-released/ Debian packages are available. We now start 24.11 cycle, lets go. Best regards 🤓 -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

1 1

Batch record modification
by Сычев Игорь Алексеевич 18 Jun '24

18 Jun '24

Hello! I have a list of records that need to change the value "2" to "1" in the 8th position of the leader. How do I make a batch modification at the leader position? Good Luck! Igor A. Sychev Tomsk Polytechnic University https://lib.tpu.ru

3 2

Issues with persistent TCP connections in Microsoft Azure cloud
by David Cook 18 Jun '24

18 Jun '24

Hi all, We recently migrated a busy Koha instance from an on-premises server to an Azure cloud server. During that move, we also took the opportunity to switch to using Elasticsearch (not located on the same virtual machine). Over time, we noticed that we were getting issues with SIP2 connections and with Koha's Elasticsearch indexer worker timing out. Especially during the least busy parts of the day. After some investigation, we learned that Azure allows TCP connections to only be idle for a maximum of 4 minutes (https://learn.microsoft.com/en-us/azure/firewall/long-running-sessions) One solution is to implement application-level keepalives, but that wasn't practical with Koha's Elasticsearch client library or the SIP2 server. Instead, I opted to utilize Linux's TCP keepalive implementation, which operates at a lower level of the technology stack. Fortunately, Koha's Elasticsearch client library is already compatible with TCP keepalives, so I just needed to tweak the "net.ipv4.tcp_keepalive_time" kernel parameter via "sysctl". I dropped the keepalive to under the 4 minute threshold (from the default of 2 hours), and now no more timeouts with Koha's Elasticsearch indexer worker! Unfortunately, Koha's SIP2 server doesn't support the TCP keepalives out of the box. However, I've written a patch at "Bug 37087 - Add support for TCP keepalive to SIP server" which adds granular TCP keepalive support which can actually be configured via the SIPconfig.xml configuration file (without needing to change any kernel parameters at all). I've written up a bit about it on the wiki: https://wiki.koha-community.org/wiki/Koha_SIP2_server_setup#Microsoft_Azure_ cloud_platform https://wiki.koha-community.org/wiki/Elasticsearch#Microsoft_Azure_cloud_pla tform I hope that this information is useful to other people out in the world implementing Koha. It was a very annoying problem with a surprisingly simple solution in the end. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

Re: [Koha] Library Membership Agreement
by BRANNON, CHRISTOPHER 17 Jun '24

17 Jun '24

I agree, you could probably achieve this with the patron attributes. Upload the agreement in Koha and make available publicly, and put the link to that agreement next to the attribute. Probably the easiest solution. ___________________________ 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: I don't think that is possible to do exactly what you want at the moment. A workaround could be to use the "Patron attribute types" (Koha administration > Patrons and circulation). Create some fields to record whether this was completed or not. You may be able to use the uploads tool (Tools > Additional tools > Uploads) to upload a scanned version of your membership agreement. However, I haven't used this tool to any great extent, and I'm not sure how you could link it to the patron. More tricky, and would require developing a plugin, would be to create a plugin with a custom consent - see Bug 31503 - Allow several consent types on the consents tab of OPAC account page (23.11). I image this could work similar to the privacy policy consent (see the PrivacyPolicyConsent system preference) that requires patrons to agree to the privacy policy consent in the OPAC. However, this isn't something I have any knowledge or expertise with. I think your best bet, unless anyone else has some other ideas, is to use patron attributes. David Nind New Zealand On Fri, 7 Jun 2024 at 19:49, Kazım ŞENTÜRK <ksenturk(a)uludag.edu.tr> wrote: > Hello, > > In order to become a member of the Library, our users are required to > fill in and sign the printed Library Membership Agreement. > > Can we have new users approve the Library Membership Agreement in > Koha? Can we keep this agreement in a format for future reference? > > 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

Library Membership Agreement
by Kazım ŞENTÜRK 17 Jun '24

17 Jun '24

Hello, In order to become a member of the Library, our users are required to fill in and sign the printed Library Membership Agreement. Can we have new users approve the Library Membership Agreement in Koha? Can we keep this agreement in a format for future reference? 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 0224 294 04 75 0224 294 04 99 ksenturk(a)uludag.edu.tr Bu mesajı yazdırmadan önce çevreye verebileceğiniz zararları bir kez daha düşününüz. Think of the environment once more before printing out this message.

3 2

Extending loan times for a subset of users
by City & Guilds of London Art School Admin 17 Jun '24

17 Jun '24

Hello, I have read through the db schema and documentation and suspect what I'd like to do isn't possible, but thought I would cover all bases by asking here: Suppose we have a 1st year BA student on course X, they belong to category BAX1, along with all other 1st year BA's on that course. Now suppose that same student has registered as dyslexic, which means we want to give them a longer loan period for all items as the default. Is there a way of doing that *without* moving them into a different category? Thanks, all the best, Chris

2 1

Re: [Koha] Database increment error returned 23.11
by Christina Fairlamb 17 Jun '24

17 Jun '24

Thanks Katrin, We are two different libraries, I added my voice to the ring for if more than one user is facing the same problem it might become a bigger issue affecting many. My versions: 10.5.23-MariaDB Koha 23.11.05 I ran through the whole process again anyhow. I implemented the script and tested it all out as advised, the new items are getting new numbers. The solution works just as it did way back when. Most concerning to me is that this reoccurred despite implementing the fix a long time ago (I can't remember which version at this point) and having a later version of MariaDB. The error only flagged after a major upgrade, no issues were raised in the normal cataloguing activities of the library nor caught in the corrupted data report that gets run occasionally. Christina

2 1

Call for news - Newsletter June 2024
by Koha Newsletter 16 Jun '24

16 Jun '24

Hi I'm collecting news for the June 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

1 0

Re: [Koha] 500 internal server error - only in one category (Caroline Cyr La Rose)
by rudy.hinojosa＠lightwavelibrary.com 14 Jun '24

14 Jun '24

I've seen this error appear when you have a malformed xml meta structure in the biblio meta data. If you are adept, or someone in your department is adept with sql, find the offending biblionumber and extract the xml, paste it into any online free xml validator. You'll find out real quick if it's the xml or not. Rudy Hinojosa ________________________________ From: Koha <koha-bounces(a)lists.katipo.co.nz> on behalf of koha-request(a)lists.katipo.co.nz <koha-request(a)lists.katipo.co.nz> Sent: Thursday, June 13, 2024 5:00 PM To: koha(a)lists.katipo.co.nz <koha(a)lists.katipo.co.nz> Subject: Koha Digest, Vol 224, Issue 8 Send Koha mailing list submissions to koha(a)lists.katipo.co.nz To subscribe or unsubscribe via the World Wide Web, visit https://lists.katipo.co.nz/mailman/listinfo/koha or, via email, send a message with subject or body 'help' to koha-request(a)lists.katipo.co.nz You can reach the person managing the list at koha-owner(a)lists.katipo.co.nz When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha digest..." Today's Topics: 1. Re: 500 internal server error - only in one category (Caroline Cyr La Rose) 2. Foundation vote closing soon (Auld, Andrew) ---------------------------------------------------------------------- Message: 1 Date: Thu, 13 Jun 2024 10:14:41 -0400 From: Caroline Cyr La Rose <caroline.cyr-la-rose(a)inlibro.com> To: koha(a)lists.katipo.co.nz Subject: Re: [Koha] 500 internal server error - only in one category Message-ID: <4301ea59-09c6-4816-a9cf-e97377d096bf(a)inlibro.com> Content-Type: text/plain; charset=UTF-8; format=flowed Hi Scott, When I've seen this, it's usually a problem with one or more patron files in the category, and not with the category itself. Our upgrades to 22.05 are a bit far in my memory, but I remember at one point there was a problem with dates in the patron file being 0000-00-00. This resulted in error 500 during a patron search. You can try select date_renewed,dateofbirth,dateenrolled,dateexpiry,lastseen,updated_on,debarred from borrowers where date_renewed = '0000-00-00' or dateexpiry = '0000-00-00' or dateenrolled = '0000-00-00' or dateofbirth = '0000-00-00' or lastseen = '0000-00-00' or updated_on = '0000-00-00' or debarred = '0000-00-00'; Regards, Caroline On 2024-06-11 13:40, Scott Owen wrote: > Hi All, > > I just upgraded to Koha > Koha version: 22.05.21.000 > and imported sql data from a older system ( 20.05.15.001 ) > > The catalog looks fine, as well as my "Board" "Staff" and "Teacher" > categories. > > However, whenever I select my "Student" category, and try a search in the > left leaving the "search" blank and just searching for the Student Category > , I get a "Something went wrong loading the table 500 internal Server > error" > > Trying to browse by last names gives the same "500 internal Server error" > error. > > If I try typing in a last name, it seems to work, and will bring up a list > of names. > > I already tried exporting a 2nd DB dump and importing it clean...same issue. > > Any idea where to start ?? It seems like the data is good, it seems like > it's all there. but it's not being sorted / indexed correctly ? > I tried looking in log files, but I really didn't see much . > > -S > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha Caroline Cyr-La-Rose, M.L.I.S. (she/her) Librarian | Product Manager 1-833-INLIBRO (465-4276), ext. 221 caroline.cyr-la-rose(a)inlibro.com https://www.inLibro.com ------------------------------ Message: 2 Date: Thu, 13 Jun 2024 22:06:24 +0100 From: "Auld, Andrew" <andrew.auld(a)ptfs-europe.com> To: koha(a)lists.katipo.co.nz Subject: [Koha] Foundation vote closing soon Message-ID: <CAFAdoMWyhmubRP8D11zibeSZOiBirknJ-_=FDDdgrMeRhCKtdQ(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Less than 24 hours for you to cast your vote on whether the Koha project should join an open source foundation and specifically the Open Library Foundation. Read the proposal and have your say here: https://chat.koha-community.org/koha-community/pl/d3161rfwe7goxc6xmhyrmoi93c Voting closes at 17:00 UTC on Friday 14 June. Andrew Auld PTFS Europe ------------------------------ Subject: Digest Footer _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha ------------------------------ End of Koha Digest, Vol 224, Issue 8 ************************************

1 0

Foundation vote closing soon
by Auld, Andrew 13 Jun '24

13 Jun '24

Less than 24 hours for you to cast your vote on whether the Koha project should join an open source foundation and specifically the Open Library Foundation. Read the proposal and have your say here: https://chat.koha-community.org/koha-community/pl/d3161rfwe7goxc6xmhyrmoi93c Voting closes at 17:00 UTC on Friday 14 June. Andrew Auld PTFS Europe

1 0