- Koha-devel - lists.koha-community.org

Call to Koha Community presence on The Perl and Raku Conference 2024 in Las Vegas (US) on June 24-28
by Andrii 18 Apr '24

18 Apr '24

At the past "Perl and Koha conferences in Helsinki" we made an efficient effort to interconnect the communities, Per and Koha. Here is another step to take to improve this: this summer in Las Vegas (US), June 24-28: there will be the *most important Perl event in 2024*: "The Perl and Raku Conference". I will be representing us there, but that's not enough ;-). To increase our Koha presence, interconnection, and respect in the Perl community, we need to be represented on this TPRC.us not just by the stand and a few talks of mine, but by a bigger Koha track, if possible, at least for a day. To make this happen, I can't do it alone. This needs more talkers, Perl-oriented. If you can come with a talk, even if not sure, but possible - let's coordinate and combine our efforts. *I will be glad to help in talk preparation if needed (or just be glad to be aware that you are coming)*, – just let me know, Andrii <nugged(a)gmail.com> <nugged(a)gmail.com>, Knowing whom from Koha people want to come and in which role will help us plan our presence. !!! IMPORTANT: I/we will be collecting talks ideas/topics for the next week (!!!), and then we can improve later, but we need to declare what we can present during this time for The Perl Community, so please communicate ASAP 🙏. We will then post drafts on the "Call for talks" TPRC.us page section this/next week – I will support you. Don't be too demanding. If you already had some previous Perl-related talks at Koha workshops or conferences, it's also good to re-make some of those for the Perl community. Simpler topics are good, too, just to show and explain how we solved some things in Koha Perl/Linux-wise, such as what you or your team did. Or just regular clean "Perl experience/development talk". What I can promise you back: you will return from this conference knowing all core Perl people, as Perl _and_ Koha community members, insights, and all those things and Perl community will add to their trust in Koha as the current uprising trend Modern Perl product (and actually sub-Perl community behind!). I will post some updates to these mailing lists I am currently posting, and also on this page through the upcoming weeks here: https://perlkohacon.fi/The-Perl-and-Raku-Conference-Las-Vegas-2024.html I have a bigger "Koha Open Source Ambassadors Initiative," which I will be presenting and calling the Perl community to join, so I will announce that separately soon. We are also working on expanding our support for Ukrainian Libraries (ULRI <https://perlkohacon.fi/ULRI.html>). Also, for any other topics, you're welcome to contact me on LinkedIn: linkedin.com/in/nugged chat or email. -- 🇺🇦 🇫🇮 , 📚 🐪 With respect, Andrii Nugged, nugged(a)gmail.com

1 1

SelfCheckoutByLogin
by long_sam.tw 17 Apr '24

17 Apr '24

Hi, all Koha SelfCheckoutByLogin https://koha-community.org/manual/latest/en/html/circulationpreferences.htm… I found that only local account authentication and cardnumber are supported, but other authentication methods are not supported, such as google openid Oauth2, are not supported. Can anyone explain the reason? With respect, long_sam

4 8

Rename git branch master to main
by Fischer, Katrin 17 Apr '24

17 Apr '24

Hi all, we decided a long time ago to switch the name of the branch 'master' in our git repositories to 'main'. The name change is now planned for this Friday, 19 April 2024. We will try to adjust the branch name in all tools we use to make the change as trouble-free as possible. But It might take us a little bit to find all spots and fix all documentation. If you want to help, please let us know and join us in the Mattermost chat at https://chat.koha-community.org on Friday! Katrin

1 0

24.05 Release dates
by Fischer, Katrin 16 Apr '24

16 Apr '24

Hi all, you've probably already been waiting for this, so here it is: . 30 April: Soft feature freeze o Nothing big or with high risk of side-effects will be pushed after this date. o Everything Passed QA will be reviewed by RM for this release and pushed if no further work is required. . 10 May: Hard feature freeze and String warning o Nothing categorized as 'enhancement' or 'new feature' will be pushed after this date if not already marked as Passed QA. . 13 May: String warning - Start your translations! o With the new translation system the translation files are continuously updated, so you can start on translations anytime. We assume that by this date most string changes should have been pushed as we will have entered hard feature freeze. o If you haven't entered release notes for your features and enhancements on Bugzilla yet, now is the time to help pretty up the release notes! . 17 May: Bug freeze / String freeze o Only bug fixes considered major, critical or blocker will be pushed after this. o We will avoid pushing any more string changes to let translators finish. o Last release preparations will take place. . 28 May: 24.05 Release Dates are to be read as 'until the end of this day' in your own timezone. ;) Close to the finish line - let's make 24.05 shine! Katrin PS: Please consider putting your name down for one of the many roles in the release team for 24.11! https://wiki.koha-community.org/wiki/Roles_for_24.11

1 0

Signoff request
by Marcel de Rooy 16 Apr '24

16 Apr '24

Hello all, I need help on the following bugs (signoffs), all related to acquisition, although some marked as architectural: 36002 Koha Acquisit m.de.rooy(a)rijksmuseum.nl Need --- enh Get rid of aqorders.purchaseordernumber 2024-02-06 36018 Koha Architec m.de.rooy(a)rijksmuseum.nl Need --- enh Improve consistency in Acquisition/Order(s) regarding active/current orders 2024-03-25 (rebased) 35994 Koha Architec m.de.rooy(a)rijksmuseum.nl Need --- enh New acquisition status method to see if biblio record is still in acquisition 13:04:46 (changed title) Still apply on master today. Would be nice to see them getting further. 35994 has dependencies. Thanks, Marcel

1 0

REMINDER: Development IRC meeting on the 17th of April 2024
by Paul Derscheid 16 Apr '24

16 Apr '24

Hi all, We have a Development IRC/Jitsi meeting scheduled for tomorrow: https://wiki.koha-community.org/wiki/Development_IRC_meeting_17_April_2024 Time converter: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+I… <https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+I…> Please feel free to add any topics you’d like to discuss to the agenda or let me know and I am happy to add them for you. If you are lead or supporter of a roadmap project, we will be happy to get an update on progress. See you there! Paul

1 0

Error 500 when searching in Koha 23.11.0
by Michael Kuhn 15 Apr '24

15 Apr '24

Hi I have updated our database from koha 21.11.10 to the current Koha 23.11.04. When searching the catalogue I get a result list, but when clicking a single hit I get an error 500. In file "plack-error.log" I have found the following line which could be the reason: DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Unknown column 'issue.renewals_count' in 'field list' at /usr/share/koha/lib/Koha/Objects.pm line 317 In fact there is no table "issue" in Koha 23.11, the correct name of this table is "issues" (see https://schema.koha-community.org/23_11/tables/issues.html) I have searched in Bugzilla but couldn't find a respective bug. But I found the sequence "issue.renewals_count" in https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=137152 so there may be some relation to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30275 Does anyone know how I can solve this problem with the 500 error? Best wishes: Michael Kuhn -- 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 6

Re: [Koha-devel] Finding invalid XML characters in Koha data via SQL
by David Cook 15 Apr '24

15 Apr '24

I’m just finishing up the next version of the plugin which finds problem bib records, problem item records, and lets you fix 1 bib record and its X problem item records at a time. I’ll be putting it up online sometime in the next couple weeks. (I’m away a lot these couple of weeks, so tough to give a firm time.) But I’m about to use it to find problem item records in one of my systems… 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: Tomas Cohen Arazi <tomascohen(a)theke.io> Sent: Sunday, 14 April 2024 2:49 AM To: Magnus Enger <magnus(a)libriotech.no> Cc: David Cook <dcook(a)prosentient.com.au>; koha-devel(a)lists.koha-community.org Subject: Re: [Koha-devel] Finding invalid XML characters in Koha data via SQL Yeah, dump it somewhere and we send pull requests to add missing bits El El vie, 12 abr 2024 a la(s) 9:50 a. m., Magnus Enger via Koha-devel <koha-devel(a)lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> > escribió: Den 12.04.2024 08:24, skrev David Cook: > Not yet. At some point I need to get better at sharing Koha plugins more widely. Just dump it to Github or similar, and set the version to 0.0.1. ;-) Release early, release often. Best regards, Magnus _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha-community.org <mailto:Koha-devel@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/

1 0

Koha CSRF protection
by Nick Clemens 13 Apr '24

13 Apr '24

Hello all! We have pushed the CSRF work from 34478 and related bugs today. We know there are more follow-ups needed, and have filed a series of bugs under an omnibus: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36192 We have a framapad where issues can be reported/found: https://annuel.framapad.org/p/koha_34478_remaining And we have bugs for each of the sections of the document. We need all developers to submit patches when they encounter issues, and for other users testing master to report found issues on the pad. Testers can report issues on the pad as well. There is a new coding guideline - all POSTs to forms in Koha will need to include a csrf token: https://wiki.koha-community.org/wiki/Coding_Guidelines#Security This has been a big work, many thanks to all involved, and there is still work to be done, but this is an important fix that we must do. You can reach out to me on IRC (kidclamp) or via email and I will do my best to help anyone contribute. Thanks, Nick -- Nick Clemens ByWater Solutions bywatersolutions.com Phone: (888) 900-8944 Pronouns: (he/him/his) Timezone: Eastern Follow us: <https://www.facebook.com/ByWaterSolutions/> <https://www.instagram.com/bywatersolutions/> <https://www.youtube.com/user/bywatersolutions> <https://twitter.com/ByWaterSolution>

5 7

Call for news - Newsletter April 2024
by Koha Newsletter 13 Apr '24

13 Apr '24

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