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

IMPORTANT: Koha hotfix
by Tomas Cohen Arazi 11 Apr '24

11 Apr '24

Hi everyone, we just identified an error on last week's releases and are publishing a quick update. Packages are generally available with the patched versions and should be applied. Source tarballs are a bit delayed but will be published as well. Thanks to all involved -- Tomás Cohen Arazi Theke Solutions (https://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

1 0

XZ Utils backdoor for Linux
by David Cook 04 Apr '24

04 Apr '24

Hi all, This isn't related to Koha per se, but I thought I'd share it for anyone who hasn't seen it: https://en.wikipedia.org/wiki/XZ_Utils_backdoor All the more reason to have things like Kohacon so that we actually know each other. 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

Koha Mars release with security fixes
by Fridolin SOMERS 03 Apr '24

03 Apr '24

Hello everyone 🤗 The Koha community is proud to announce the release of Mars versions: 23.11.04 23.05.10 22.11.16 22.05.20 It is a bugfix/maintenance release including a lot of security fixes. It is highly recommended to upgrade. The full release notes will soon be available here: https://koha-community.org/koha-23-11-04-released/ https://koha-community.org/koha-23-05-10-released/ https://koha-community.org/koha-22-11-16-released/ https://koha-community.org/koha-22-05-20-released/ Debian packages are available. Next week is HackFest in Marseille 🌍 Best regards 🤓 -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

1 0

REMINDER: Development IRC meeting 3 April 2024
by Fischer, Katrin 02 Apr '24

02 Apr '24

Hi all, We have a Development IRC/Jitsi meeting scheduled for tomorrow: https://wiki.koha-community.org/wiki/Development_IRC_meeting_3_April_2024 Time converter: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+IR C+Meeting <https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+I RC+Meeting&iso=20240403T1200> &iso=20240403T1200 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! Katrin

1 0

Koha Community Newsletter: March 2024
by Koha Newsletter 28 Mar '24

28 Mar '24

The Koha Community Newsletter for March 2024 is here: https://koha-community.org/koha-community-newsletter-march-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

Elasticsearch sans Zebra
by David Cook 27 Mar '24

27 Mar '24

Hi all, I have started using Elasticsearch more with Koha, and we're at a point of wanting to use Elasticsearch without Zebra for Koha. I came across "Bug 21820 - Zebraqueue should not be added to when only Elasticsearch is used" and it seems like other people are interested in this too. I imagine it's just a case of getting a patch written? Overall, it's an idea that people 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

4 6

Elasticsearch indexing does not handle exceptions well
by David Cook 26 Mar '24

26 Mar '24

Hi all, I'm re-indexing Elasticsearch and I notice occasionally Elasticsearch will throw an exception when committing (e.g. Elasticsearch exception thrown: Request), and Koha just ignores it. That means that whole commit gets missed, so a default of 5000 records don't get indexed. You can probably find those inconsistencies using /usr/share/koha/bin/maintenance/compare_es_to_db.pl but that doesn't provide you a method for indexing those missed records either. Am I missing something obvious here? I'll need to look at increasing the verbosity to get more of the error message, and I'll play around with some settings to make it so that the Elasticsearch server doesn't thrown an error, but this seems weird to me. Perhaps we should have an automatic re-try, or at least a record of what records failed to be committed, so that they can be manually retried via a different mechanism? 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

REST API : PUT for partial update
by Fridolin SOMERS 21 Mar '24

21 Mar '24

Hi, I've tried to use API for a PUT on patron. Looks like I can't do a partial update, I get error on mandatory datas like if it where a POST. I found this discussion : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23285#c8 Is this a bug ? Best regards, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

2 4

The Global Bug Squashing Day just started (in Kiribati)!
by Magnus Enger 21 Mar '24

21 Mar '24

Kia ora, dear Community! If you are in Kiribati (or if you choose Kiribati as your time zone) you are in luck, because the Global Bug Squasing Day just started for you! More information and resources here: https://wiki.koha-community.org/wiki/2024-03-22_Global_bug_squashing_day I just copied some numbers related to different bug statuses into the wiki page, so we can try and see how much progress we made at the end. For more individual stats, you can try and see how far you can get your name up the lists for "March" (and "2024") on the dashboard: https://dashboard.koha-community.org/ But don't get too hung up on those numbers either, *everything* helps and *everything* counts: - Answer a question on IRC or the mail lists - Add a comment in Bugzilla - Tall a friend about Koha :-) And most important: Have fun! Best regards, Magnus Libriotech/imCode

1 0

Ponderings on locations
by Wagner, Alexander 21 Mar '24

21 Mar '24

Hi! While migrating our catalogue to Koha I get quite confused with the location handling. Location for me is "the place where I have to go to fetch the item". So an item could be in the general collection `main reading room`, but I may have a special area there like an exhibition or a new items shelf. And it can be at it's usual location or at some temporary place. AFAIS Koha items have internally a `location` and a `permanent_location`. (In my still current world they'd be named `temporary location` (876__l) and `location` (aka `852__a`), respectively, so slightly the other way round.) Now, in item cataloguing the location I get exposed to the editor seems to be a mixture of `permanent_location` and `location`, in the sense that the editor always sets both. Using mappings for `UpdateItemLocationOnCheckin` however, some values are magic. If `CART` and `PROC` get mapped they only change the `location`, while all others change both. (I do understand that the magic value is used by some cron-job.) However, I wonder if the procedures were not more flexible and easier to understand if "any mapped location" juggles the `location` and leaves the `permanent_location`, while I do get both values in the item editor and the actual place where an item is is defined as `permanet_location` if there is no `location` set. There is already `_PERM_` to access the permanent location in mappings, but with the current logic it's value is gone once a non-magical location enters the game. IMHO one could achieve the same functionality like now by just clearing `location` once an item is back at it's permanent location. (At least this is how our old system does it right now.) Example: - We order an item and set it's location to `On Order`. ORD is non-magical. - The item arrives, I check it in, `ORD: PROC` "moves" it to cataloguing. Cataloguing wants to change the permanent location. - After cataloguing it should go to the new items shelf. Check in, `PROC: NEW`. Everything fine in the OPAC display. - After a week or so on the new items shelf, check in, `NEW: _PERM_` moves it back to `on order`. To work around my trouble with the location, I played with a similar juggling for `UpdateNotForLoanStatusOnCheckin`. (Sidenote: it seems that I am required to use numbers for the values to juggle there, e.g. `-1: -3`, while the editor allows for text. If this is a bug I'd add one to bz.) This propagates as expected and from a display perspective it would also be ok. Unfortunately, the strict `not for loan` doesn't work well for us. We are open 24/7, but not staffed 24/7. IOW whatever hits the shelf can be taken. If someone checks out an item that is in principle not for loan, I'd really like to check it out, just to know who has it ;) I did not yet find a way to soften `not for loan` to something like `2 days and immediately send a recall letter`. (Current procedure.) Additionally, we check in _all items_ from the CART all the time as we have a lot of patrons that just drop them into the box and they need to be returned to get the RFID into the proper state. (So in our case the cron wouldn't help.) BTW: what proved pretty flexible in our current system are what I called back then "special patrons". If I check out an item to those the item is not actually checked out, but they manipulate some Marc fields. We used them a lot to set the temporary locations to values like `repair`, `cataloguing`, `on display` or `library desk` (for items ready for the patron to fetch; Koha does this differently). Unlike checking in, where I have to rely on automatic propagation, checking out allows to select what I want to do by means of the cardnumber I get as a second parameter on the SIP-terminal. For configuration I used something like 788 _7 |2 P:(DE-HGF) |a {"j": "available", "l": "Cataloguing"} |i 8767_ which would set `876 7_ |javailable |lCataloguing`, ie the item is available, but in cataloguing. (Our patrons are currently just authority records, so I have full Marc at my disposal.) -- Kind regards, Alexander Wagner Deutsches Elektronen-Synchrotron DESY Library and Documentation Building 01d Room OG1.444 Notkestr. 85 22607 Hamburg phone: +49-40-8998-1758 e-mail: alexander.wagner(a)desy.de

4 8