- Koha - lists.katipo.co.nz

The "one manual" idea
by Charillon, Aude 06 Oct '23

06 Oct '23

Hello, In the Koha Documentation team, we have been discussing whether we still need one version of the manual per Koha version. The idea being mooted is that having only one manual for all versions in the future may be better. It's an idea that is still at the exploration stage; at this point we would like to get feedback from a wider group of people, hence this message! I included further down a summary of what has been raised so far. We are particularly interested in your thoughts on the following: - What would be impacted if we decided to move to one manual - that we haven't considered yet (see summary)? What issues may arise, who would they affect, what are your suggestions to solve them? - Are there any specific considerations for translated versions of the manual? - Are there any technical considerations that us non-developers haven't thought of? If you have questions, concerns or just think it's a good idea, it would also be nice to hear from you :-) Thanks, Aude [aude_c on Koha IRC] Documentation Manager for the 23.11 cycle Issues with the current situation - The documentation cycle doesn't match the Koha development cycle. It is near impossible for the Documentation team to document all the new features before the new Koha version is released. The manual published alongside the new Koha version is always behind. - When the manual is updated, the update is made to the master branch - the one that matches the numbering of the Koha version currently in development. This master branch isn't visible (unless you know where to find it). It is possible to "backport" updates to older versions of the manual but this is not straightforward. Because we are behind with documenting features, some updates would have to go back through several older versions of the manual, making the process even less straightforward. I'll be honest: it's rare these days when we backport to older versions. - For library teams, that means the explanation of a feature in their Koha version is more likely to be in a newer version of the manual (than in the one they'll land on when clicking the Help button). One manual - why it would be beneficial - Everything in one place: all the latest additions and improvements to the manual available straight away to everyone everywhere. - Translated manuals: only one version to keep on top of. - Easier to manage by the community. How it could work; questions and concerns identified - What if something changes in a newer version of Koha / only exists in some versions but not others? Wouldn't that be confusing in one manual? We would need to clearly mark sections with the Koha versions it applies to, e.g. "until 22.11", "from 23.05". Aude Charillon Customer Services Consultant PTFS Europe aude.charillon(a)ptfs-europe.com

4 4

bulkmarcimport.pl with Record Matching Rules?
by Thomas Klausner 06 Oct '23

06 Oct '23

Hi! Is there a way to run bulkmarcimport.pl together with some Record Matching Rules (like they are available in the Staff interface via "Stage MARC records for import") ? The param "-match" seems related, but from --help I cannot figure out what this actually does.. Background: We want to import authorities from the GND/DNB (German National Libray) but do not want to create duplicate auths for those we already have in the DB. We can match the auths via 024$a (so if we have a local record with the same value in 024$a as the one we're currently importing, it's a match and should update the old record instead of creating a new one) Greetings, domm -- Thomas Klausner domm https://domm.plix.at Just another ( Perl | Postgres | Bicycle | Food | Photo | Vinyl ) Hacker A not-so-short list of things I learned at PerlKohaCon #Perl #Koha [ 2023-08-19 10:00 > https://domm.plix.at/perl/2023_08_things_i_learned_at_perlkohacon.html ] Long and good read: http://bit-player.org/2023/ai-and-the-end-of-programming [ 2023-09-14 12:01 > https://domm.plix.at/microblog.html ]

2 2

koha-US Board Meeting Minutes - Wednesday, October 4, 2023
by Jennifer Marlatt 05 Oct '23

05 Oct '23

Hello, Here's a link to the minutes from the koha-US board meeting on Wednesday, October 4, 2023 - https://docs.google.com/document/d/14zm9RcrYWOjiLvmzZ9QGwa92NiOBweBoXf254lL… koha-US meetings are open to all! Board meetings are held on the first Wednesday of each month at 8:30 PT / 9:30 MT / 10:30 CT / 11:30 ET. The next koha-US general meeting will be on Wednesday, October 11 @ 8:30 PT / 9:30 MT / 10:30 CT / 11:30 ET (time converter <https://www.timeanddate.com/worldclock/fixedtime.html?msg=koha-US+October+G…> ). The agenda for the next general meeting is available here - https://docs.google.com/document/d/1mU8nt9PG7FvvWZBuzxuvKCSpRTZ02qADYbwHAC6… If you have additional topics for the agenda, please send them to secretary(a)koha-us.org. Jennifer Marlatt koha-US Secretary <secretary(a)koha-us.org>secretary(a)koha-us.org

1 0

problem in opac error 500
by Asif Iqbal 05 Oct '23

05 Oct '23

Dear, I am facing a problem using koha for my university in opac i am facing the error when i search a book but in staff environment its giveing me proper book details but in OPAC giving me error 500. i uploaded book record using mark record and following fields are included only not i have converted above files xls to mrc file using mark editor and staged and uploaded successfully. Regards, Asif Iqbal Additional Director IT (Operations) BUITEMS, Takatu Campus, Quetta Phone: +92 81-2880511 (Ext: 555) Mobile: +92 3083999909 E-mail: asif.iqbal(a)buitms.edu.pk<mailto:asif.iqbal@buitms.edu.pk>

1 0

Koha not compatible with Plesk Control Panel?
by Alessandro Tedesco 04 Oct '23

04 Oct '23

Hello everyone, I am trying to install the current stable release of Koha on a VPS (OS Ubuntu 22.04.1) managed with the Plesk Control Panel. However, it seems that Koha is not compatible with Plesk. Below the error generated after launching the installation ------------------- # sudo apt-get install koha-common Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: psa : Conflicts: javascript-common but 11+nmu1 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. ------------------- I have found that Plesk is not compatible with the javascript-common package required by Koha (https:// talk.plesk.com/threads/cant-install-prometheus-together-with-plesk-on-debia… ). However, it's strange because last year I installed Koha without problems on a VPS with Plesk...maybe the javascript-common package in the latest versions of Koha? Does anyone experience the same issues? Thanks and Kind Regards Alex

3 11

search_for_data_inconsistencies.pl: Bibliographic records have invalid MARCXML
by Michael Kuhn 04 Oct '23

04 Oct '23

Hi We are using Koha 21.11.09 with MariaDB 10.3.38, running on Debian GNU/Linux 10. When running script "search_for_data_inconsistencies.pl" we are getting the following output: == Bibliographic records have invalid MARCXML == * DBIC result _type isn't of the _type BiblioMetadata at /usr/share/koha/bin/maintenance/search_for_data_inconsistencies.pl line 124. * DBIC result _type isn't of the _type BiblioMetadata at /usr/share/koha/bin/maintenance/search_for_data_inconsistencies.pl line 124. * DBIC result _type isn't of the _type BiblioMetadata at /usr/share/koha/bin/maintenance/search_for_data_inconsistencies.pl line 124. => The bibliographic records must have a valid MARCXML or you will face encoding issues or wrong displays Does anyone know how to obtain further information (biblionumbers?) for these cases? Best wishes: Michael -- 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

2 3

Add a Usage Statistics module to ERM
by Field, Jonathan 03 Oct '23

03 Oct '23

Hi all, I just wanted to bring your attention to Bug 34587 which is another enhancement to the ERM module to introduce Data Providers, COUNTER and SUSHI to Koha. There is no formal test plan to this (as it is a big feature) but you can watch my video at KohaCon 23 this year which shows how all of the features work (and the workflow). It's about 30 minutes long. We have provided a permanent sandbox here - http://staff-usagestats.sandboxes.ptfs-europe.co.uk/cgi-bin/koha/erm/eusage… which we will leave live and it would be great if anyone who has an interest in this topic/feature could do some testing and feedback any comments/issues on the bug. We'd love to add it to the next version as it is of interest to many libraries. Credentials will be required for testing, please check if your organisation has access to any valid SUSHI credentials in order to test. Other details can be found at the Project Counter registry - https://registry.projectcounter.org/ All credentials are redacted in the sandbox and will not be visible to other users. In the released version, credentials will be visible in the ERM module. I'm also happy to answer any specific questions about this feature directly if anyone has any. Many thanks Jonathan -- Jonathan Field Managing Director PTFS Europe [image: Phone icon] M: +44 7919 372002 | T: +44 1483 378728 ext. 1000 [image: Email icon] jonathan.field(a)ptfs-europe.com [image: Link icon] www.ptfs-europe.com [image: Click to open Twitter] <https://twitter.com/PTFSEurope> [image: Click to open YouTube] <https://www.youtube.com/@PTFSEurope> [image: Click to open PTFS Europe webpage] <https://www.ptfs-europe.com>

1 0

search_for_data_inconsistencies.pl: Can't call method "get_column"
by Michael Kuhn 03 Oct '23

03 Oct '23

Hi We are using Koha 20.11.02 with MariaDB 10.3.39, running on Debian GNU/Linux 10. When calling the script "search_for_data_inconsistencies.pl" the only output is the following: $ sudo koha-shell -c "perl /usr/share/koha/bin/maintenance/search_for_data_inconsistencies.pl" instancename Can't call method "get_column" on an undefined value at /usr/share/koha/bin/maintenance/search_for_data_inconsistencies.pl line 157. Does anyone know how to solve this problem? Best wishes: Michael -- 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

2 2

Koha versions 23.05.04, 22.11.10, 22.05.16 and 21.11.24 released
by Tomas Cohen Arazi 03 Oct '23

03 Oct '23

The Koha community is proud to announce the latest releases of the current stable, oldstable, oldoldstable and lts versions of the software. This is a security and maintenance release on all branches, so please update at the earliest opportunity. As always, you can update using the already available packages, or download the release from https://download.koha-community.org Thank you very much to all release maintainers and the whole team involved in this release. Release notes for respective branches are available online now at: * https://koha-community.org/koha-23-05-04-released/ * https://koha-community.org/koha-22-11-10-released/ * https://koha-community.org/koha-22-05-16-released/ * https://koha-community.org/koha-21-11-24-released/ -- Tomás Cohen Arazi Theke Solutions (https://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

2 1

link_bibs_to_authorities
by Сычев Игорь Алексеевич 02 Oct '23

02 Oct '23

Hello! Using the script "link_bibs_to_authorities.pl ". Binds only one Unimarc field? Only 700? How do I make multiple fields linked? For example, there are 600, 700, 701 in the bibliographic record. These fields were linked in another ILS. Good Luck! Igor A. Sychev Tomsk Polytechnic University https://lib.tpu.ru

2 1