- Koha - lists.katipo.co.nz

Marc Overlay rules
by Hugo Agud Andreu 14 May '23

14 May '23

Good morning We 're testing the 21.11 feature 'Manage MARC overlay rules' we have enabled the syspref and I do not know if it is not working of perhaps we are not understanding propertly the workflow.. We are updating existing records from external z39.50 source We have defined source Z39.50 tag 650 and protect Whem replaceing a record via z39.50 from external source, the rule doesn't apply and overwritte Are we missing soomething? any hep will be great! Hugo Agud - Orex Digital www.orex.es<http://www.orex.es> - Linkedin<https://www.linkedin.com/company/orex-digital/> Innovando para ayudar a las bibliotecas a alcanzar el siguiente nivel <https://orex.es/productos/orex-analytics/> Director Passeig Comte Vilardaga, 118 3-3 08980 -Sant Feliu de Llobregat - Tel: 933 856 138 hagud(a)orex.es<mailto:hagud@orex.es> · http://www.orex.es/ No imprima este mensaje a no ser que sea necesario. Una tonelada de papel implica la tala de 15 árboles y el consumo de 250.000 litros de agua. Aviso de confidencialidad Este mensaje y sus archivos adjuntos van dirigidos exclusivamente a su destinatario, pudiendo contener información confidencial sometida a secreto profesional. No está permitida su reproducción o distribución sin la autorización expresa de Orex Digital, S.L. Si usted no es el destinatario final por favor elimínelo e infórmenos por esta vía. En cumplimiento de lo establecido en el Reglamento General de Protección de Datos (RGPD) (UE) 2016/679 y a la Ley Orgánica 3/2018, de 5 de diciembre, de Protección de Datos de Carácter Personal y Garantía de los Derechos Digitales (LOPD-GDD), le informamos que tratamos sus datos personales con la finalidad de responder a su solicitud de información, realizar la gestión administrativa derivada de nuestra relación comercial o contractual, así como enviarle comunicaciones comerciales sobre nuestros productos y servicios. La legitimación será en base a un interés legítimo, por ejecución de un contrato y/o por consentimiento, en algunos casos. Los datos proporcionados se conservarán mientras se mantenga la relación contractual o durante los años necesarios para cumplir con las obligaciones legales. Los datos no se cederán a terceros salvo en los casos en que exista una obligación legal o sea necesario para la ejecución de un contrato. No se tomarán decisiones automatizadas que puedan causar un efecto jurídico significativo, salvo que se haya recabado previamente el consentimiento. Asimismo, le informamos de la posibilidad de ejercer los siguientes derechos sobre sus datos personales: derecho de acceso, rectificación, supresión u olvido, limitación, oposición, portabilidad y a retirar el consentimiento prestado. Para ello podrá enviar un email a: info(a)orex.es, adjuntando copia de su DNI. Además, el interesado puede dirigirse a la Autoridad de Control en materia de Protección de Datos competente (AEPD, en España) para obtener información adicional o presentar una reclamación. Datos identificativos: Orex Digital, S.L., B64500945, Paseo Conde de Vilardaga 118, 3-3 - 08980 - Sant Feliu de Llobregat - BARCELONA, 933856138

2 1

Barcode Font
by Himanshu Aggarwal 14 May '23

14 May '23

I am able to generate the barcodes using the Bywater plugins but how to change the barcode font size as the size of the barcode text is coming very small. Can someone guide me please. -- Assistant Librarian, Confucius Institute Scholar 13-14, R.D. National College, Bandra (W.)

2 1

Call for news - Newsletter May 2023
by Koha Newsletter 14 May '23

14 May '23

Hi I'm collecting news for the May 2023 Koha Community Newsletter. Please send anything noteworthy to: kohanews (at) gmail (dot) com News criteria: * News items can be of any length. * Images are fine. * Anything and everything Koha. * Submit by the 26th of the month. Text format criteria: * Just structured plain text, or * HTML text to include tables or similar For events: * Consider adding your event to the Koha Community calendar at https://koha-community.org/calendar/ Thank you! Michael Kuhn Editor, Koha Community Newsletter

2 1

koha-US General Meeting Minutes for May 10, 2023
by Jennifer Marlatt 12 May '23

12 May '23

Hello, Here's a link to the minutes from the koha-US General Meeting held on Wednesday, May 10, 2023 - https://docs.google.com/document/d/1BAbF4wgxkBcJheOGMh-57LAt_lHsjDVNy29HVaz… . The recording for the general meeting has been posted, there's a link to the recording in the minutes. koha-US meetings are open to all! The next board meeting will be on June 7, 2023 at 8:30 am PT / 9:30 am MT / 10:30 am CT / 11:30 am ET. The next general meeting will be on June 14, 2023 at 8:30 am PT / 9:30 am MT / 10:30 am CT / 11:30 am ET. Jennifer Marlatt koha-US Secretary <secretary(a)koha-us.org>secretary(a)koha-us.org

1 0

All About Passwords | S3E18
by BRANNON, CHRISTOPHER 12 May '23

12 May '23

It's no secret! We're sharing our passwords. Er...we're sharing everything we know about how passwords work in Koha, that is. So, if you are looking for ways to tighten up security, and help your forgetful patrons, this video is a must-see. https://youtu.be/66Ld3jb71mk Christopher Brannon 2023 koha-US President

1 0

Koha 21.11.09 released
by Arthur 11 May '23

11 May '23

The Koha community is pleased to announce the release of version 21.11.09. For full release notes, please visit https://koha-community.org/koha-version-21-11-09-released/ <https://koha-community.org/koha-21-11-09-released/> Thanks! 🚀

3 4

Starting rabbitmq-server fails with Koha 22.11.05-2
by Michael Kuhn 11 May '23

11 May '23

Hi When trying to install Koha 22.11.05-2 via package installation on a completely new machine with 4 virtual CPUs, 4 GB RAM and Debian GNU/Linux 11 the following error appears: rabbitmq-server (3.8.9-3) wird eingerichtet ... Job for rabbitmq-server.service failed because the control process exited with error code. See "systemctl status rabbitmq-server.service" and "journalctl -xe" for details. invoke-rc.d: initscript rabbitmq-server, action "start" failed. ● rabbitmq-server.service - RabbitMQ Messaging Server Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Thu 2023-05-11 15:14:44 CEST; 4ms ago Process: 38141 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server (code=exited, status=1/FAILURE) Main PID: 38141 (code=exited, status=1/FAILURE) CPU: 1.071s Mai 11 15:14:44 koha systemd[1]: Failed to start RabbitMQ Messaging Server. Mai 11 15:14:44 koha systemd[1]: rabbitmq-server.service: Consumed 1.071s CPU time. Can someone please tell me how to solve this problem? You can see the output of "systemctl status rabbitmq-server.service" resp. "journalctl -xe" just below. 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 koha@koha:~$ sudo systemctl status rabbitmq-server.service ● rabbitmq-server.service - RabbitMQ Messaging Server Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Thu 2023-05-11 15:19:57 CEST; 3s ago Process: 41298 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server (code=exited, status=1/FAILURE) Main PID: 41298 (code=exited, status=1/FAILURE) CPU: 1.066s koha@koha:~$ sudo journalctl -xe ░░ An ExecStart= process belonging to unit rabbitmq-server.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Mai 11 15:20:47 koha systemd[1]: rabbitmq-server.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit rabbitmq-server.service has entered the 'failed' state with result 'exit-code'. Mai 11 15:20:47 koha systemd[1]: Failed to start RabbitMQ Messaging Server. ░░ Subject: A start job for unit rabbitmq-server.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit rabbitmq-server.service has finished with a failure. ░░ ░░ The job identifier is 3262 and the job result is failed. Mai 11 15:20:47 koha systemd[1]: rabbitmq-server.service: Consumed 1.127s CPU time. ░░ Subject: Resources consumed by unit runtime ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit rabbitmq-server.service completed and consumed the indicated resources. Mai 11 15:20:48 koha sudo[41974]: koha : TTY=pts/0 ; PWD=/home/koha ; USER=root ; COMMAND=/usr/bin/journalctl -xe Mai 11 15:20:48 koha sudo[41974]: pam_unix(sudo:session): session opened for user root(uid=0) by koha(uid=1000)

2 2

Re: [Koha] [Koha-devel] Starting rabbitmq-server fails with Koha 22.11.05-2
by Michael Kuhn 11 May '23

11 May '23

Hi Jonathan You wrote: > Well, it's pretty obvious, everything is in the log: > """ > The process' exit code is 'exited' and its exit status is 1. > """ > > Heh :D > > I don't know! Did you try to stop and start it again? > systemctl rabbitmq-server stop > systemctl rabbitmq-server start It's not possible: koha@koha:~$ sudo systemctl rabbitmq-server stop Unknown command verb rabbitmq-server. koha@koha:~$ sudo systemctl rabbitmq-server start Unknown command verb rabbitmq-server. > Looks like it's not started so it won't certainly help. > Rebooted the VM? I did reboot the machine, it didn't change a thing. > Do you have elastic running as well (in such case 4G > of RAM won't be enough) No I'm not running Elasticsearch. At the moment it seems to me like there is a fundamental problem with package "koha-common" 22.11.05-2 when it cannot properly configure rabbitmq-server on a completely new machine. The problem didn't exist with version 22.11.03-1 but I don't know how to obtain this older version via APT. 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 Am 11.05.23 um 16:08 schrieb Jonathan Druart: > Well, it's pretty obvious, everything is in the log: > """ > The process' exit code is 'exited' and its exit status is 1. > """ > > Heh :D > > I don't know! Did you try to stop and start it again? > systemctl rabbitmq-server stop > systemctl rabbitmq-server start > Looks like it's not started so it won't certainly help. > Rebooted the VM? Do you have elastic running as well (in such case 4G > of RAM won't be enough) > > Le jeu. 11 mai 2023 à 15:27, Michael Kuhn <mik(a)adminkuhn.ch> a écrit : >> >> Hi >> >> When trying to install Koha 22.11.05-2 via package installation on a >> completely new machine with 4 virtual CPUs, 4 GB RAM and Debian >> GNU/Linux 11 the following error appears: >> >> >> rabbitmq-server (3.8.9-3) wird eingerichtet ... >> Job for rabbitmq-server.service failed because the control process >> exited with error code. >> See "systemctl status rabbitmq-server.service" and "journalctl -xe" for >> details. >> invoke-rc.d: initscript rabbitmq-server, action "start" failed. >> ● rabbitmq-server.service - RabbitMQ Messaging Server >> Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; >> enabled; vendor preset: enabled) >> Active: activating (auto-restart) (Result: exit-code) since Thu >> 2023-05-11 15:14:44 CEST; 4ms ago >> Process: 38141 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server >> (code=exited, status=1/FAILURE) >> Main PID: 38141 (code=exited, status=1/FAILURE) >> CPU: 1.071s >> >> Mai 11 15:14:44 koha systemd[1]: Failed to start RabbitMQ Messaging Server. >> Mai 11 15:14:44 koha systemd[1]: rabbitmq-server.service: Consumed >> 1.071s CPU time. >> >> >> Can someone please tell me how to solve this problem? >> >> You can see the output of "systemctl status rabbitmq-server.service" >> resp. "journalctl -xe" just below. >> >> 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 >> >> >> >> >> koha@koha:~$ sudo systemctl status rabbitmq-server.service >> ● rabbitmq-server.service - RabbitMQ Messaging Server >> Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; >> enabled; vendor preset: enabled) >> Active: activating (auto-restart) (Result: exit-code) since Thu >> 2023-05-11 15:19:57 CEST; 3s ago >> Process: 41298 ExecStart=/usr/lib/rabbitmq/bin/rabbitmq-server >> (code=exited, status=1/FAILURE) >> Main PID: 41298 (code=exited, status=1/FAILURE) >> CPU: 1.066s >> >> koha@koha:~$ sudo journalctl -xe >> ░░ An ExecStart= process belonging to unit rabbitmq-server.service has >> exited. >> ░░ >> ░░ The process' exit code is 'exited' and its exit status is 1. >> Mai 11 15:20:47 koha systemd[1]: rabbitmq-server.service: Failed with >> result 'exit-code'. >> ░░ Subject: Unit failed >> ░░ Defined-By: systemd >> ░░ Support: https://www.debian.org/support >> ░░ >> ░░ The unit rabbitmq-server.service has entered the 'failed' state with >> result 'exit-code'. >> Mai 11 15:20:47 koha systemd[1]: Failed to start RabbitMQ Messaging Server. >> ░░ Subject: A start job for unit rabbitmq-server.service has failed >> ░░ Defined-By: systemd >> ░░ Support: https://www.debian.org/support >> ░░ >> ░░ A start job for unit rabbitmq-server.service has finished with a failure. >> ░░ >> ░░ The job identifier is 3262 and the job result is failed. >> Mai 11 15:20:47 koha systemd[1]: rabbitmq-server.service: Consumed >> 1.127s CPU time. >> ░░ Subject: Resources consumed by unit runtime >> ░░ Defined-By: systemd >> ░░ Support: https://www.debian.org/support >> ░░ >> ░░ The unit rabbitmq-server.service completed and consumed the indicated >> resources. >> Mai 11 15:20:48 koha sudo[41974]: koha : TTY=pts/0 ; PWD=/home/koha >> ; USER=root ; COMMAND=/usr/bin/journalctl -xe >> Mai 11 15:20:48 koha sudo[41974]: pam_unix(sudo:session): session opened >> for user root(uid=0) by koha(uid=1000) >> >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel(a)lists.koha-community.org >> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : https://www.koha-community.org/ >> git : https://git.koha-community.org/ >> bugs : https://bugs.koha-community.org/

1 0

Elasticsearch authority sorting giving unexpected results
by Aleisha Amohia 09 May '23

09 May '23

Hi all, We have some unexpected sorting results happening when we search authority records. We are using Elasticsearch. Wondering if anyone has seen this before and knows a code fix or some Elasticsearch configuration required to fix it. I've noticed this happens in upstream Koha too so might be a real bug, with Koha or Elasticsearch, I'm not sure which. As an example, when we search for "political science" authorities with the 'heading ascending' sort order, these are the results: 1. Political science Philosophy 2. Political science Poetry 3. Political science 4. Political science Problems 5. Political science Quotations We would expect Political science (#3 in the above results list) to show first, before the others. Any ideas? -- *Aleisha Amohia (she/her)* Koha Technical Lead *Catalyst.Net Limited - Expert Open Source Solutions* *Catalyst.Net Ltd - a Catalyst IT group company* Tel: +64 4 499 2267 | www.catalyst.net.nz <http://www.catalyst.net.nz> Catalyst Logo CONFIDENTIALITY NOTICE: This email is intended for the named recipients only. It may contain privileged, confidential or copyright information. If you are not the named recipient, any use, reliance upon, disclosure or copying of this email or its attachments is unauthorised. If you have received this email in error, please reply via email or call +64 4 499 2267.

3 2

koha-US General Meeting reminder: Wednesday, May 10, 2023
by Jennifer Marlatt 09 May '23

09 May '23

The next koha-US General Meeting is Wednesday, May 10, 2023. When: 8:30a PT / 11:30a ET (time converter <https://www.timeanddate.com/worldclock/fixedtime.html?msg=koha-US+general+m…> ) Where: https://us02web.zoom.us/j/293750042?pwd=SGQzS2pmU3prNFhYRHNaeTFhOHN4QT09 Agenda: https://docs.google.com/document/d/1Gck0YOXJeZmzcTobPmmypYHlFslnfRVhKpxjrnj… If you have additional topics for the agenda, please send them to secretary(a)koha-us.org Meetings are held via Zoom video conferencing. A microphone and webcam are recommended but not required. Zoom is available for Windows, Mac, and Linux on desktops, and Android and iOS on mobile devices. For help getting started, visit: https://support.zoom.us/hc/en-us/categories/200101697 These meetings are always free and open to any and all. Jennifer Marlatt koha-US Secretary secretary(a)koha-us.org

1 0