- Koha - lists.katipo.co.nz

Next Friday: Patch testing session to help enhancements and bug fixes to be released
by Victor Grousset/tuxayo 25 Nov '22

25 Nov '22

Hi :) To be forwarded to librarians, system librarians, educators, devs, sysadmins and other people that could be interested in contributing to Koha. Let's meet at any moment in the following timeframe: 13h-20h UTC&UK / 8h-15h US East / 5h-12h US West The place is https://visio.chapril.org/koha (the text chat can be opened with the 4th button at the bottom: 🗨️) Reminder of the modalities: The idea is to test patches to contribute to Koha. The biggest bottleneck for having more bugs fixes and enhancements is patch testing. Thus this call for getting together as Koha users. No need for particular skills, just basic Koha usage. You can come an leave at any moment, even for a short time it's possible to get simple stuff moving forward. We will use a VoIP call with chat tool to speak and eventually screenshare. It's possible to join without sound and only use chat. So if you are at the front desk and there are not much patrons you can still test patches ^^ So, whichever communication mode is the most convenient for you. No need to have a local Koha instance. Just with a web browser we can use the sandboxes [1] to have temporary Kohas to test most patches and do whatever we want without bad consequences. Here is a resource about how to test patches using sandboxes: https://wiki.koha-community.org/wiki/Sandboxes Cheers, [1] https://wiki.koha-community.org/wiki/Sandboxes -- Victor Grousset/tuxayo

1 0

how to add additional attributes in patron CSV file
by takan bhatt 25 Nov '22

25 Nov '22

Dear Sir, We are using additional attributes for patrons like student branch, course, etc. We want to upload these through patron.csv file in koha. Pls guide me Rajesh Bhatt

2 1

The Terrific Every-Other-Thursday Training Video - S3E6 - Plugin: Batch Patron Permissions Modifier
by BRANNON, CHRISTOPHER 23 Nov '22

23 Nov '22

This week's video is so spectacular, we not only had to scrap our first attempt, but we had to split it into two videos. That's right: TWO. Not only that, we're releasing it a day early, because we just know our viewers can't wait. That, and I didn't want to have to post and advertise on a holiday. Be sure to check out our outtake at the end. Happy Thanksgiving! https://youtu.be/CneHrJ4O0yk Christopher Brannon 2022 koha-US Vice President

1 0

Koha 22.05.07 is here!
by Lucas Gass 23 Nov '22

23 Nov '22

Hello, Hola, Bonjour, Guten tag, Olá! The Koha community is proud to announce the release of Koha 22.05.07! Koha 22.05.07 includes 8 enhancements, 54 bugfixes, and 1 security fix. The full release notes can be found here: https://koha-community.org/koha-22-05-07-released/ <https://koha-community.org/koha-22-05-02-release/> Debian packages should be available shortly! -- Lucas Gass Web Developer

1 0

koha-US December 2022 Events & Meetings
by Jennifer Marlatt 23 Nov '22

23 Nov '22

Hi! koha-US online meetings and events are free and open to all. See our calendar for a full list: http://koha-us.org/calendar/. For Google Calendar users, add our events calendar to your list for easy access to meeting times and links: https://calendar.google.com/calendar/u/1?cid=a29oYS11cy5vcmdfZG1xb2pkczE5Zn… *Meetings* Board Meeting - Wednesday, December 7 @ 8:30a PT / 11:30a ET / 16:30 UTC General Meeting - Wednesday, December 14 @ 8:30a PT / 11:30a ET / 16:30 UTC *Special Interest Groups* Cataloging - Thursday, December 1 @ 8:00a PT / 11:00a ET / 16:00 UTC Circulation - Tuesday, December 6 @ 10:00a PT / 1:00p ET / 18:00 UTC System Administration - Tuesday, December 13 @ 8:00a PT / 11:00p ET / 16:00 UTC Web Development - Thursday, December 15 @ 10:00a PT / 1:00p ET / 18:00 UTC Acquisitions - Cancelled for December. Demonstration Instance - Cancelled for December. Visit http://koha-us.org/special-interest-groups/ to learn more and sign up for topic-specific mailing lists. Most meetings and events are recorded and made available at https://www.youtube.com/kohaus Jennifer Marlatt koha-US Secretary secretary(a)koha-us.org

1 0

Re: [Koha] OAI-PMH harvester
by BOUIS Sonia 22 Nov '22

22 Nov '22

Hi, Thanks to David, Tomas, Michal and Michael for your replies. So we have decided to evaluate several external OAI-PMH client that could be used by Koha and to choose one in the end of January There a lot to do after that and we discussed about the background jobs and cronjobs seems to be appropriate. We thought that the settings in the koha intranet should be only to define URLs, SETs, or XSLT sheets (for example, to transform DC XML in MARCXML). We are only at the begining of the process 😊 Kind regards, Sonia ------------------------------ Message: 2 Date: Wed, 26 Oct 2022 10:37:49 +1100 From: "David Cook" <dcook(a)prosentient.com.au> To: "'Tomas Cohen Arazi'" <tomascohen(a)gmail.com>, "'BOUIS Sonia'" <sonia.bouis(a)univ-lyon3.fr> Cc: "'koha'" <koha(a)lists.katipo.co.nz>, "'koha-devel'" <koha-devel(a)lists.koha-community.org> Subject: Re: [Koha-devel] [Koha] OAI-PMH harvester Message-ID: <07af01d8e8ca$dfbddef0$9f399cd0$(a)prosentient.com.au> Content-Type: text/plain; charset="utf-8" Hi Sonia, I’m excited to hear that KohaLA would like to finance an OAI-PMH client in Koha! This functionality is always brewing in the back of my mind, since I first raised 10662 back in 2013. As Tomas says, I think that the background jobs are a key component for processing incoming OAI-PMH records. However, the ***missing component right now is the scheduling of the OAI-PMH harvesting tasks***, and I think this is where opinions get divided. Below, I’ll provide some history and opinions on Koha OAI-PMH. -- With 10662, the sponsored goal was for Koha library staff to schedule OAI-PMH harvests through the Web UI. However, Fridolin from BibLibre raised a point with me at Kohacon18 about how letting library staff control the timing of harvesting tasks could be a problem for support vendors. If too many libraries using the same public IP address tried to harvest from the same OAI-PMH repository, they could be rate limited or blocked. There could also be server load concerns. So there probably needs to be a balance between user configuration and system configuration. If I recall correctly, this is how DSpace’s OAI-PMH harvester works. Users set up targets and can start/stop harvests, but things like frequency and concurrency are handled by the system configuration. Based on my experience working on OAI-PMH on and off for nearly 10 years and as a Koha support vendor, I think my preference would be for sysadmins to handle most of the OAI-PMH harvesting details. The sponsorship for 10662 had certain requirements that many other libraries might not have, which is what made me think that it might be better to have an external client that connects to Koha. I thought maybe I could get the ordinary requirements pushed into Koha, and then handle extraordinary requirements externally. However, an external harvester won’t perform as fast as an internal harvester. (The compromise would be to write the harvester in such a way that people could provide different OAI-PMH harvester Perl modules that all stage records using the same core Koha modules.) Even then… the scheduling would depend on a library’s needs. Back in 2013, I had a Koha OAI-PMH harvester which worked as a cronjob. It would run each night. However, some libraries want to run OAI-PMH harvests as frequently as every 3 seconds. A cronjob’s smallest frequency is 60 seconds, so that wouldn’t work for that requirement. If a cronjob isn’t suitable, then I think you’d need a daemon created by a new command like “koha-oai --start <instance_name>”. It could read a configuration file and handle scheduling accordingly. With 10662, I used the POE module, because I knew it well and it has some timer tools for scheduling tasks. If I were to work on it again, I’d probably use Mojo::IOLoop instead these days, since Mojolicious is already part of Koha while POE is not. (That said, using modules like Mojo and POE are difficult, because they’re difficult to test using automation. That was one of the stumbling blocks with 10662. While the 10662 harvester worked very well, it was difficult to unit test. In hindsight, I should’ve written it in a way that was easier to unit test, but it had a lot of event-driven code which made things more difficult.) Another option would be to create a generic daemon for task scheduling in general (e.g. “koha-schedule”). Koha could use this for many things, but it’s a project in itself. -- The process of downloading OAI-PMH records and importing MARCXML into Koha is actually a fairly straightforward process. The difficulty is the task scheduling and management of tasks (and unit testing). I don’t know the answer that will make everyone happy. There’s lots of different ways of managing and scheduling the tasks. Based on my experience, I’d suggest targeting the simplest approach first, because complexity will make it less likely for the project to succeed. On that note, I’d be happy to test/QA any OAI-PMH harvester put forward. When I was writing OAI-PMH harvester patches, I found it really hard to get QA, so I’m happy to be that resource for someone else. I’ve spent a lot of time thinking about this topic, so happy to provide advice, warnings, emotional support 😉. 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 From: Koha-devel <koha-devel-bounces(a)lists.koha-community.org> On Behalf Of Tomas Cohen Arazi Sent: Wednesday, 26 October 2022 3:46 AM To: BOUIS Sonia <sonia.bouis(a)univ-lyon3.fr> Cc: koha <koha(a)lists.katipo.co.nz>; koha-devel <koha-devel(a)lists.koha-community.org> Subject: Re: [Koha-devel] [Koha] OAI-PMH harvester I think with background jobs we have most of the framework that is needed to deal with this within Koha. Best regards El mar, 25 oct 2022 7:08, BOUIS Sonia <sonia.bouis(a)univ-lyon3.fr <mailto:sonia.bouis@univ-lyon3.fr> > escribió: Hi, KohaLA would like to finance an OAI-PMH client in Koha but, we have questions that we want to raise to the community. There was already tries to propose an OAI-PMH client : - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10662 : it's an old project that doesnt seem compatible with the current version of Koha - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25905 : the scope is more to use an external OAI-PMH client and to connect it to Koha Our main question is about the way to handle this. Do you think that it's a better idea to use an external software or PERL routine and to find a way to connect it to Koha. Or would it be better to a new module in Koha from scratch and that Koha have his own OAI-PMH client. Please, let us hear your toughts about this projet. Kind regards Sonia Sonia BOUIS ------------------------------------------------------ Responsable du Service informatique documentaire Département d'Appui à la Recherche et aux Projets (DARP) Bibliothèques universitaires Université Jean Moulin Lyon 3 ADRESSE GÉOGRAPHIQUE > Manufacture des Tabacs | 6 cours Albert Thomas | LYON 8e ADRESSE POSTALE > Bibliothèque de la Manufacture | 1C avenue des Frères Lumière | CS 78242 - 69372 LYON CEDEX 08 Ligne directe : 33 (0)4 78 78 79 03 http://bu.univ-lyon3.fr<http://bu.univ-lyon3.fr/>| Suivez-nous > Facebook<https://www.facebook.com/bulyon3/> | Twitter<https://twitter.com/bulyon3>| Instagram<https://www.instagram.com/bu.lyon3/?hl=fr> _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20221026/d…> ------------------------------ Subject: Digest Footer _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/ ------------------------------ End of Koha-devel Digest, Vol 203, Issue 15 *******************************************

2 1

Koha 21.11.14 released
by Arthur Suzuki 22 Nov '22

22 Nov '22

Hello, I'm very proud to announce the release of Koha 21.11.14. It includes 1 security fixes, 4 enhancements, 46 bugfixes. More information can be found here : https://koha-community.org/koha-21-11-14-released/ Enjoy! 🌅🚀 Arthur Suzuki, 🌈🏔️ Développeur @BibLibre

1 0

Some very sad news.
by Chris Cormack 22 Nov '22

22 Nov '22

Tēnā koutou It is with great sadness that I pass on to you all the news that Rosalie Blake has passed away. Rosalie was the Head Librarian at Horowhenua Library Trust when Koha was started and without her Koha would not exist. But more than this Rosalie was an amazing person, a librarian who always thought outside the box, a gifted potter, a friend to many and a beloved mother and grandmother. Details around the funeral and memorial note should be available tomorrow. But I am sure you will all join me holding Rosalie's family and friends in your thoughts. Tiwhatiwha te pō, tiwhatiwha te ao. Chris

9 9

Time to translate: string freeze to prepare Koha 21.05.21 has begun
by Victor Grousset/tuxayo 22 Nov '22

22 Nov '22

Hi, String freeze is into effect as of now for the 21.05.x maintenance branch. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 21.05, then you must also copy it to 21.11, 22.05 and 22.11. Otherwise your work will be lost for future versions. Happy translating :) -- Victor Grousset/tuxayo

1 0

koha on debian 11 / apache 2 and varnish cache
by Manos PETRIDIS 21 Nov '22

21 Nov '22

Has anyone tried using varnish cache with koha on debian 11? As my original configration had koha listen on ports 81 (OPAC) and 8081 (administrative), I've amended the apache virtual hosts file to listen on ports 80 and 8080, and set up varnish to respond to ports 81/8081 and forward to ports 80/8080 any requests not in cache. It seems to work, i.e. koha responds on all four ports, when however one tries a Z39.50 query, instead of search results results z3950_search.pl produces the following error message: Error 503 Backend fetch failed Backend fetch failed Guru Meditation: XID: 196655 Varnish cache server Any tips on how to resolve this?

1 0