- Koha - lists.katipo.co.nz

Koha Community Newsletter: February 2023
by Koha Newsletter 27 Feb '23

27 Feb '23

The Koha Community Newsletter for February 2023 is here: https://koha-community.org/koha-community-newsletter-february-2023/ 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

Re: [Koha] Creating a database
by Thomas Daly 27 Feb '23

27 Feb '23

Thank you for your help. I was actually using MySQL, not MariaDB. I tried setting the MySQL root password to null, but then ran into a different error. So I've now replaced MySQL with MariaDB. Since the 'Koha on Debian' guide says that you can use either MariaDB or MySQL, I think it ought to make clear any differences in configuration that are needed when using MySQL, such as the need for a null password. -----Original Message----- From: René Seindal <rene(a)seindal.it> Sent: 26 February 2023 17:59 To: Thomas Daly <letterbox(a)daladi.com> Cc: koha(a)lists.katipo.co.nz Subject: Re: [Koha] Creating a database On Debian you don't need to do anything. The superuser has access to the database without a password. It is described in the package documentation: /usr/share/doc/mariadb-server-10.5/README.Debian.gz * ROOT USER AUTHENTICATION VIA UNIX SOCKET ========================================== On new installs no root password is set and no debian-sys-maint user is created anymore. Instead the MariaDB root account is set to be authenticated using the Unix socket, e.g. any mysqld invocation by root or via sudo will let the user see the mysqld prompt. You may never ever delete the mysql user "root". Although it has no password is set, the unix_auth plugin ensure that it can only be run locally as the root user. The credentials in /etc/mysql/debian.cnf specify the user which is used by the init scripts to stop the server and perform log rotation. This used to be the debian-sys-maint user which is no longer used as root can run directly. If you have start/stop problems make sure that the /etc/mysql/debian.cnf file specifies the root user and no password. In the long run please stop using that file as is has been obsoleted. On 2023-02-26 15:16, Thomas Daly wrote: > Hello, > > > > I'm following the 'Koha on Debian > <https://wiki.koha-community.org/wiki/Koha_on_Debian> ' guide but have > got stuck at the 'Create a Koha instance' part. This section doesn't > say anything about supplying the 'koha-create' command with a MySQL > username and password. I don't see how 'koha-create' can create the > database if it doesn't know the MySQL root password. > > > > I tried putting the MySQL root login details in both /etc/koha/passwd > and /etc/mysql/koha-common.cnf, but I get this error: > > > > # koha-create --create-db --passwdfile /etc/koha/passwd zilib > > WARNING: The koha-common.cnf file is a dead soft link! > > ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using > password: NO) > > > > koha-common.cnf is not actually a dead link but a text file.

1 0

Koha 22.11 Upgrade - Bug 31162 - Add primary key to erm_eholdings_packages_agreements
by Craig Butosi 26 Feb '23

26 Feb '23

Hi there, Just updated to Koha 22.11 (ubuntu 18.04.06) and received an error after database schema upgrade: Bug 31162 - Add primary key to erm_eholdings_packages_agreements Upgrade to 22.06.00.084 [10:30:33]: Bug 31162 - Add primary key to erm_eholdings_packages_agreements ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'CONSTRAINT erm_eholdings_packages_agreements_uniq, ADD PRIMARY K' at line 3 at /usr/share/koha/lib/C4/Installer.pm line 739 I don't quite understand this error. Could someone advise? Many thanks, Craig Butosi, MA, MLIS, B Mus (Hons) Library: library.craigbutosi.ca

1 0

Creating a database
by Thomas Daly 26 Feb '23

26 Feb '23

Hello, I'm following the 'Koha on Debian <https://wiki.koha-community.org/wiki/Koha_on_Debian> ' guide but have got stuck at the 'Create a Koha instance' part. This section doesn't say anything about supplying the 'koha-create' command with a MySQL username and password. I don't see how 'koha-create' can create the database if it doesn't know the MySQL root password. I tried putting the MySQL root login details in both /etc/koha/passwd and /etc/mysql/koha-common.cnf, but I get this error: # koha-create --create-db --passwdfile /etc/koha/passwd zilib WARNING: The koha-common.cnf file is a dead soft link! ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO) koha-common.cnf is not actually a dead link but a text file. Can anyone help please?

1 0

2023 koha-US Annual Conference Location
by BRANNON, CHRISTOPHER 24 Feb '23

24 Feb '23

Happy Friday to all! I am pleased to announce that the votes are in and the location for the 2023 koha-US Annual Conference has been selected. This year we will be meeting at the Portsmouth Public Library, in Portsmouth, NH, which is scheduled for September 20th-23rd. Be sure to follow our 2023 Conference updates at https://koha-us.org/events/conferences/2023-koha-us-annual-conference-ports…. We will be updating the site this next month with more details. Sincerely, Christopher Brannon 2023 koha-US President

1 0

Request for proposals to host KohaCon 2024
by Caroline Cyr La Rose 24 Feb '23

24 Feb '23

Hello everyone! The request for proposals to host KohaCon 2024 is now open! If you or your organization would like to *organize KohaCon24*, please enter all the required information on the KohaCon 2024 proposal wiki page [1]: https://wiki.koha-community.org/wiki/KohaCon24_Proposals The closing date for bids is *4 April 2023 23:59 UTC*. Proposals received will be discussed at the *5 April 2023 General IRC Meeting* (https://wiki.koha-community.org/wiki/General_IRC_meeting_5_April_2023) Information about hosting KohaCon -------------------------------------------------- The community has agreed that KohaCon conferences must be either: - hybrid with an in-person conference streamed online, or - entirely online. This allows for greater accessibility, so that everyone can attend and learn from each other no matter their availability, ability to travel, or budget. For hybrid conferences, the rules for continent rotation apply. Therefore, for 2024, the following continents are eligible: - Africa - Asia - South America - Oceania For more information about the generally agreed rules established for KohaCons, see https://wiki.koha-community.org/wiki/Processes_for_KohaCons This covers the timetable, continent rotation, and information to help with planning a successful KohaCon. Deadline for proposals -------------------------------------------------- The closing date for proposals is *4 April 2023 at 23:59 UTC*. If there is more than one proposal, we will organize a vote - this will be announced on the mailing list. Help with your proposal -------------------------------------------------- The community stands behind anyone who volunteers to organize a KohaCon, and help is always available if you're unsure how to proceed. Send an email to the mailing list if you need help, or ask on IRC. There is a wealth of experience in the community from those who have attended and organized previous KohaCons (and other conferences). [1] If you do not have an account to edit the wiki, you can request one. It is usually pretty fast to get access. <https://inLibro.com/en> Caroline Cyr-La-Rose, M.L.I.S. Librarian | Product Manager P 833-INLIBRO (465-4276) <tel:833-465-4276>, poste 221 E caroline.cyr-la-rose(a)inlibro.com www.inLibro.com <https://inLibro.com/en>

1 0

Question on path for custom xsl files (OPAC and Staff client)
by Bruns, Anke 24 Feb '23

24 Feb '23

Hi, we have some settings of our own in some XSL files, e.g. /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/{langcode}/xslt/MARC21slim2O PACResults.xsl as well as for the staff client in e.g. /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/{langcode}/xslt/MARC21sli m2intranetResults.xsl All works fine when we copy and rename these files, keeping our own versions in /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/{langcode}/xslt/ resp. /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/{langcode}/xslt/ For us, however, it would be easier to store them in another place, e.g. (for the OPAC): /usr/share/koha/opac/htdocs/<our_directory>/<instancename>/{langcode}/xslt/ so we could hold all our files in one place (<our_directory), together with e.g. logos and other pictures etc, which we could easily tar and transport to another server when migrating an instance. But, alas, this doesn't seem to work - obviously the parameters XSLTDetailsDisplay, XSLTResultsDisplay, OPACXSLTDetailsDisplay and OPACXSLTResultsDisplay expect the files in the same directories as the standard versions. Is there any rule what paths are possible for our own xsl files/settings? Thanks in advance and best regards, Anke -- Anke Bruns M.A. (LIS) Arbeitsgruppe "Anwendungs- und Informationssysteme" E-Mail: anke.bruns(a)gwdg.de --------------------------------------- Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen (GWDG) Burckhardtweg 4, 37077 Göttingen, URL: https://gwdg.de Support: Tel.: +49 551 39-30000, URL: https://gwdg.de/support Sekretariat: Tel.: +49 551 39-30001, E-Mail: gwdg(a)gwdg.de Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Norbert Lossau Sitz der Gesellschaft: Göttingen Registergericht: Göttingen, Handelsregister-Nr. B 598 --------------------------------------- Zertifiziert nach ISO 9001 ---------------------------------------

4 9

Koha 22.11.03 release
by Renvoize, Martin 23 Feb '23

23 Feb '23

Hello, Bonjour, Ola, Kia ora, 今日は, The Koha community is pleased to announce the release of version 22.11.03. This release is a bugfix/maintenance release with a small number of minor architectural enhancements to aid in the continued maintenance of this version. It includes 40 enhancements and 87 bugfixes. For full release notes, please visit https://koha-community.org/koha-22-11-03-released/ Thanks for anybody involved! 🚀 Martin Renvoize, MPhys (Hons) Head of Development and Community Engagement E: martin.renvoize(a)ptfs-europe.com P: +44 (0) 1483 378728 M: +44 (0) 7725 985636 www.ptfs-europe.com

1 0

Errors in the MARC bibliographic framework test: itemtype NOT mapped and subfields not in same tabs (UNIMARC)
by library＠ssst.edu.ba 23 Feb '23

23 Feb '23

Hello all, I am new to both Koha and Linux, and I have been trying to learn how to use both as I want our library to move from an in-house developed system to Koha. I am in Bosnia, and we use UNIMARC, so I chose that as my MARC flavor during the installation. When doing the MARC bibliographic framework test, I got two errors: itemtype NOT mapped the biblioitems.itemtype field MUST : - be mapped to a MARC subfield, - the corresponding subfield MUST have "Authorized value" set to "itemtype" subfields not in same tabs Not all subfields for the following tags are in the same tab (or marked 'ignored'). Code Description Tag Tabs in use Default framework 410 3,4 The tabs in use for all tags are tabs 3,4 and the tags are: 410 to 413 421 to 425 430 to 437 440 to 448 451 to 456 461 to 464 470 481 to 482 488 I'm not sure how to fix this error? What do I need to do? Best regards Aida Đikić

2 3

Volunteer needed to open the bidding for KohaCon24 & need confirmation of task list
by tuxayo 22 Feb '23

22 Feb '23

Hi :) The things to do are: - making the wikipage using the template - make an announcement email using past ones - send reminders - @all: anything else? The aim is to start the bid in the next weeks so proposals that start early 2024 have time to plan. And let the bid run until the next general meeting in april I can help with proofreading and finding past resources. (wikipage template, emails) Cheers, -- tuxayo

2 1