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

REST API should not advertise required permissions
by David Cook 04 Jan '23

04 Jan '23

Hi all, I just noticed the following error while testing the REST API: {"error":"Authorization failure. Missing required permission(s).","required_permissions":{"borrowers":"1"}} It seems to me that we should just stop at "Authorization failure". While it might be helpful for a dev to know what the required permissions are, I think it would also be overly helpful for an attacker to know what permissions are required too, no? I suppose Koha is open source, so it wouldn't be hard for them to look them up anyway, but it just seems odd? 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

3 2

Roadmap for v23.05
by Tomas Cohen Arazi 03 Jan '23

03 Jan '23

Hi all, last cycle we worked through a roadmap which was not 100% finished, but we made good progress in many of the main milestones: - Task queue streamlining (several improvements, progress bars, etc) - ERM (done) - Introduction of Vue (done) - Dates handling (partially done) - Circ, holds, biblios and items refactoring (partially done) - New staff interface (done) - API refinements (partially done) - Wiki migration (done) Now, it is time for us to build a new one ofr this cycle. Please fill with the things you plan to work on this cycle, and put your name so we all know and can help each other. https://annuel.framapad.org/p/Roadmap_for_Koha_v23.05 Thanks in advance! -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

2 1

Hackfest in Marseille
by Paul Poulain 02 Jan '23

02 Jan '23

<TL:DR>The hackfest will take place in March, 27th - 31th, drop me an email if you want to join Hello ladies and gentlemen, After 3 years of pandemic where everything was messy, the hackfest in Marseille is back ! Join us for coding/testing/translating/documenting/dreaming about the future of your preferred ILS, in Marseille, 108 rue Breteuil, 13006 Marseille. We'll start on monday, March, 27th, and end on Friday, March, 31th. * *How to register ?* Just drop me an email ! * *How much does it cost ?* Nothing. We just ask some fees for the lunch [special information: cheese lunch on Tuesday] * *What is the agenda ?* there's none, come with your ideas, your wish, your goodwill, and we'll do a lot of things in smaller or larger groups. * *5 days, wow, that's a lot !* yes, but as it's an "un-conference", you can come just for a part of the week. I suggest not less than 3 days, but no obligation here. * *I'm not a developer !* That's not a problem. MANY librarians come to the hackfest, they meet other librarians, they talk about Koha, they help testing, documenting, translating... There's always a lot of things to do Also note: it will be the very last hackfest in our current office, we'll move to another office in May (but don't worry, I plan to continue hackfesting in your new office) -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

1 0

How best to support MARC21 880?
by David Cook 01 Jan '23

01 Jan '23

Hi all, The MARC21 880 field allows you to provide alternative graphical representations for pretty much any other MARC field. Typically, in Koha (and perhaps other library systems), we display these alternative graphical representations on the "detail page". You can see the roman script, the Arabic script, the Chinese script, etc. In Koha, we also show some data in the search results, and that's more problematic. because the search results should take up a limited amount of space on the screen, but hypothetically you can include many different scripts via the 880. I used to work in a government library in Canada where many of our bibliographic records contained quite a few different 880s. So it does happen. I have a library that has catalogued records using the roman alphabet (ie using Pinyin) and provided Chinese versions via the 880. They'd like to show both the romanized and Chinese versions throughout Koha (e.g. in the cart, checkout screens, course reserves, etc.) I've coded some of those customizations, since they only have 880s in Chinese, but I'm increasingly reluctant to make these changes. I don't want to carry these customizations locally, but I don't know that the Koha community would accept these changes. What do you all think about this? Should we include every 880 title and author in every screen? Should we maybe include them but hide them by default using CSS and then allow certain libraries to just show particular languages used by their patrons or by checking the current language? I know I can go faster on my own, but I rather go farther with all of you, so please let me know your thoughts : ) 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

2 1