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

Bug 33092 - Add ability to search within a list
by David Cook 29 Apr '24

29 Apr '24

Hi all, Has anyone looked at this one? My first thought is that the list ID would need to be added to a repeatable subfield (e.g. 999$l) and indexed. That way it would be easy to allow any search engine query and then just wrap it like "(<query>) and (list_id=X)". But. it would mean that we'd have to re-index records for list operations, and I don't love that. Does anyone have any other ideas? Or happy to support this one? It would be a fairly significant change to lists, so I think it would need to be well thought out. 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

Koha Community Newsletter: April 2024
by Koha Newsletter 28 Apr '24

28 Apr '24

The Koha Community Newsletter for April 2024 is here: https://koha-community.org/koha-community-newsletter-april-2024/ Many thanks to everyone who submitted articles and news to this newsletter! Please feel free to email me with any corrections or suggestions. -- Michael Kuhn Editor, Koha Community Newsletter

1 0

IMPORTANT: Git branch master is now main
by Fischer, Katrin 22 Apr '24

22 Apr '24

Hi all, we have made a lot of changes today to make sure that our git repositories are no longer using 'master', but 'main' as their main and development branch. Some small changes are required to make things work again: Translators If you have any bookmarks for translating, you might need to adapt them to the new branch name: https://translate.koha-community.org/projects/koha/main/ git repositories Please note that this change doesn't only affect the Koha repository, but also our side project and tool repositories. In your local repositories you will want to rename the local branch to main and then set it to track main in the upstream repository: git config --global init.defaultBranch main git branch --move master main git branch -u origin/main git pull koha-testing-docker Switch the repository over to use main as detailed above. Edit your .env file and replace every occurrence of master with main, especially within the KOHA_IMAGE line. Run ktd pull to pull the new images. RMaints and RM release-tools: Edit etc/user.yaml and replace 'master' with 'main' in line 4. If you encounter any issues, please let us know! Many many thanks to everyone who has helped today to make this possible on short notice! Katrin

3 2

Google OpenID Connect
by long_sam.tw 22 Apr '24

22 Apr '24

Hi, all Google OpenID Connect is used in koha. Why does opac have this identity authentication login, but staff does not have this function? What is the main reason? With respect, long_sam

2 1

Community positions for the 24.11 cycle
by Renvoize, Martin 18 Apr '24

18 Apr '24

Hi everyone, We need your help! I'd like to advertise that we have a vote upcoming in the community for the roles for the next release cycle, 24.11. Please see the roles page at https://wiki.koha-community.org/wiki/Roles_for_24.11 and add your name to a role if you would like to propose volunteering for it. The team vote will take place on May 2nd at the next community general meeting <https://wiki.koha-community.org/wiki/General_IRC_meeting_2_May_2024>. We'd love to see some new faces on the team, and we value contributions from developers to help drive the project forward. Some roles I'd like to draw your attention to: * Bug Wranglers <https://wiki.koha-community.org/wiki/Project_roles#Bug_wrangler> - We can always do with more bug wranglers! These people love to keep things tidy and Bugzilla is always in need of your help. We need people to help manage 'the list', identify the duplicates, promote bugs to specialists and find people to do signoffs and testing. Everyone is invited to this party, we need you! This is a great first-time role to take on and it makes a real difference to active community contributors' lives! * Topic experts <https://wiki.koha-community.org/wiki/Project_roles#Topic_expert> - Do you know a particular topic or area in Koha well? Then why not let people know and put your name forward as a Topic expert! These people can help drive an area forward, adding detailed information to bugs in their respective fields, and adding highly respected signoff that may be treated as a quality assurance pass as well. * Quality assurance <https://wiki.koha-community.org/wiki/Project_roles#QA_team_member> - The testing and quality assurance queues are always overflowing and we need more people to take on this role. There's plenty of work to go around and not all of it is as difficult as it sounds; We encourage you to step up and contribute your expertise to these critical areas of the project. I would be more than happy to personally mentor anyone who wants to join this team, guiding them on how to pick bugs and then work through them. Don't be scared, this role is vital to keep the project progressing, but it really isn't as scary as it sounds and the team around you are all lovely, friendly and knowledgeable. * Release maintainer <https://wiki.koha-community.org/wiki/Project_roles#Release_maintainer> - Koha strives to support 4 versions of Koha concurrently, including one Long Term Support version. To do this, we need people committed to maintaining those versions. There's a clearly defined process to this and a group of people willing to guide and help out. You'll need to be comfortable in git and happy to work closely with the other maintainers and release team members to keep your queues in check and make regular monthly releases. This role looks great on your CV and your sponsoring company's profile too 😉. There are lots of other roles and I'm more than happy to try and mentor anyone interested in taking any of them on. If it's not something I've personally taken on in the past, I'm confident I can find the right person to help you out. Looking forward to seeing some new names on the list and your active engagement. Martin Renvoize, MPhys (Hons) Head of Development & Community Engagement PTFS Europe [image: Phone icon] M: +44 7725985636 <+447725985636> | T: +44 1483 378728 <+441483378728> [image: Email icon] martin.renvoize(a)ptfs-europe.com [image: Link icon] www.ptfs-europe.com Sign up for our Newsletter. <http://eepurl.com/dPjjkn> <http://www.linkedin.com/company/ptfs-europe-limited> <http://youtube.com/@PTFSEurope> [image: Click to open PTFS Europe webpage] <https://www.ptfs-europe.com>

1 0

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