- Koha - lists.katipo.co.nz

Problem Sharing Lists on Koha
by Ms. Naveen Ali 18 May '23

18 May '23

Dear All, I am using Koha 22.05.06.000 I was trying to share Koha Lists created on OPAC using the "Share list" Option. The following URL is used: https://myServer/cgi-bin/koha/opac-shareshelf.pl?op=invite&shelfnumber=13 And email send failure is reported in the "message_queue" table with "failure_code" as SENDMAIL Then I tried the using the "Send List" Option The following URL is used: https://eakl.neduet.edu.pk/cgi-bin/koha/opac-sendshelf.pl?shelfid=13 And email is sent successfully. First of all I would like to know what are the requirements of "Share list" option so that I do not get the SENDMAIL failure. I want to use this option as it allows me to customize the "SHARE_INVITE" and "ACCEPT_INVITE" notice. Also I have not been able to find any information about this option in the manual https://koha-community.org/manual//22.05/en/html/lists.html#viewing-lists . The "Share List" option is not shown there. Secondly, if the option is no longer available, how can I customize the message being sent in the email using the "Send List" Option. Thank you very much for your time. With best regards, Naveen Ali ITM-JE (EAKL) Inst Representative for HEC Digital Library Resources. NEDUET, Karachi.

1 0

Error while editing item on migrated instance
by DHIM IT 18 May '23

18 May '23

Dear colleagues, I migrated koha db to a new server with fresh installed instance. Everything working fine. I have only one error while editing items: [WARN] DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: The user specified as a definer ('root'@'%') does not exist at /usr/share/koha/lib/Koha/Object.pm line 170 Does anybody know what can I do to solve it? KOHA 22.05 Debian 11 Mit besten Grüßen IT-Manager Eugen Bastron

2 1

Re: [Koha] Fwd: Dead Koha Resuscitation
by Bruce A. Metcalf 17 May '23

17 May '23

On 5/15/23 12:12, David Liddle wrote: > I see now that I overlooked your statement that commands such as > 'koha-dump' are not recognized. Do they appear in the directory > /usr/sbin/? No. Not a single koha- command present in that directory. > Do you have automated Koha backups configured that are available in > /var/spool/koha/{instance}? No, though that would have been smart of me. I don't even have a directory /var/spool/koha, much less /var/spool/koha/instance. Appreciate the effort. Respectfully, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library

2 8

Re: [Koha] Background job / Staging MARC import stuck at 0%
by Michael Brown 16 May '23

16 May '23

Hi Cindy, apologies for the double-response: I had unsubscribed from the koha list so my response didn't get added to the thread. I wanted to remedy that, and also say that, because I had unsubscribed, I missed Mengü's suggestion of updating manage-marc-import.pl. I am eager to try that fix and will report back later today or tomorrow with my findings. Here's my original response to Cindy before re-subscribing to to the koha list: Yes, my koha-conf.xml does contain that block because I added it during the initial setup. (You're right, it wasn't there originally.) However, it doesn't help; I still cannot import batch bib records in Koha 22.11 the way I could in Koha 22.05. The enqueuement hangs and sends my cpu through the roof until I navigate away from that page. I've gotten one off-list suggestion that upgrading to the newest Koha fixes the problem. Unfortunately for me, I don't really have time for that right now, so I have (at least temporarily) abandoned my efforts with Koha. Thanks for your suggestion! Bests, Michael On Tue, May 9, 2023 at 4:40 PM Michael Brown <michael8rown(a)gmail.com> wrote: > Hi Cindy, > > Yes, my koha-conf.xml does contain that block because I added it during > the initial setup. (You're right, it wasn't there originally.) > > However, it doesn't help; I still cannot import batch bib records in Koha > 22.11 the way I could in Koha 22.05. The enqueuement hangs and sends my cpu > through the roof until I navigate away from that page. I've gotten one > off-list suggestion that upgrading to the newest Koha fixes the problem. > Unfortunately for me, I don't really have time for that right now, so I > have (at least temporarily) abandoned my efforts with Koha. > > Thanks for your suggestion! > > Bests, > Michael > > On Tue, May 9, 2023 at 1:37 PM Cindy Murdock Ames <cmurdock(a)ccfls.org> > wrote: > >> Hi Michael, >> >> Can you confirm your koha-conf.xml contains a message broker section, >> like this? >> >> <message_broker> >> <hostname>localhost</hostname> >> <port>61613</port> >> <username>guest</username> >> <password>guest</password> >> <vhost></vhost> >> </message_broker> >> >> I had the same problem after upgrading from 22.05 to 22.11; I'm guessing >> 22.05 must have had some defaults set in the code that allowed the message >> broker to start automatically without this section whereas 22.11 must not. >> I was missing this section and added it and was able to complete imports >> after restarting Koha. >> >> I'm still having the issue with zombie background jobs (I'm afraid to >> test rolling back the code on a production server) but I made a hacky bash >> script to run as a cron job to check for them and kill them off so at least >> our staff can do batch imports without issue, but that's another matter. >> >> HTH! >> Cindy >> >> >> ----------------------------------------------------------- >> Cindy Murdock Ames >> IT Services Director >> Meadville Public Library | CCFLS >> https://meadvillelibrary.org | https://ccfls.org >> >> Please report tech support issues in Mantis: https://mantis.ccfls.org >> >> >> On Thu, Mar 2, 2023 at 8:51 AM Michael Brown <michael8rown(a)gmail.com> >> wrote: >> >>> Greetings: >>> >>> My name is Michael Brown and I am a professional cataloger and SirsiDynix >>> System Admin at the Texas State Library & Archives in Austin (20+ years >>> now). I have been using Koha on Arch Linux in my home library for about a >>> year now. I am migrating my home server to AlmaLinux and I'm having a >>> problem. >>> >>> I am running Koha 22.11.03.000 Rosalie on AlmaLinux 9.1. Staging a MARC >>> file for import gets stuck at 0%. On screen, I am able to select the file >>> for import (bib.mrc), review the profile options (but I don't change any >>> defaults), and then click on "Stage for import" at the bottom. Next >>> screen >>> reads: >>> >>> The job has been enqueued! It will be processed as soon as possible. >>> 0% >>> View detail of the enqueued job >>> >>> After a few seconds, it changes to (and then hangs at): >>> >>> The job has been enqueued! It will be processed as soon as possible. >>> 0% Not started >>> View detail of the enqueued job >>> >>> Clicking on "View detail of the enqueued job" I see: >>> >>> Details of job #22 >>> >>> Job ID: 22 >>> Status: New >>> Progress: 0 / 0 >>> Type: Staged MARC records for import >>> Queued: 03/02/2023 05:42 >>> Started: >>> Ended: >>> >>> Report >>> Detailed messages >>> Return to the job list >>> >>> The corresponding entry in mariadb is: >>> >>> id 22 >>> status new >>> progress NULL >>> size 0 >>> borrowernumber 1 >>> type stage_marc_for_import >>> queue Name of the queue the job is sent to long_tasks >>> data {"encoding":"UTF-8","comments":"","basket_id":null... >>> context JSON-serialized context information for the job >>> {"flags":1,"branch":"ALMA","interface":"intranet",... >>> enqueued_on 2023-03-02 05:42:33 >>> started_on NULL >>> ended_on NULL >>> >>> (If you need to see the full entries for "data" and "context", please let >>> me know.) >>> >>> tmp, koha_upload, and lock directories have been tweaked and fine tuned. >>> I >>> was getting early warnings about them not being set in koha-conf.xml so I >>> created them (and set correct permissions) and I can see the uploaded >>> file >>> (for job 22 the name is 2287629673fb980ad4102f62ebeaa1b9_bib.mrc), so the >>> actual upload function appears to be working. >>> >>> I am getting no apache errors and no other on-screen diagnostics. >>> >>> I have Koha 22.05.02.000 running on Arch Linux that imports this file >>> just >>> fine. Similarly, I have Koha latest running on a Debian VM that can >>> import >>> this file just fine, too. >>> >>> What am I missing? >>> >>> Details of my system: >>> >>> Koha version: 22.11.03.000 Rosalie >>> OS version ('uname -a'): Linux alma 5.14.0-162.12.1.el9_1.x86_64 #1 SMP >>> PREEMPT_DYNAMIC Mon Jan 23 14:51:52 EST 2023 x86_64 >>> Perl interpreter: /usr/bin/perl >>> Perl version: 5.032001 >>> Perl @INC: /usr/share/koha/lib >>> /usr/local/lib64/perl5/5.32 >>> /usr/local/share/perl5/5.32 >>> /usr/lib64/perl5/vendor_perl >>> /usr/share/perl5/vendor_perl >>> /usr/lib64/perl5 >>> /usr/share/perl5 >>> /var/lib/koha/plugins >>> MySQL version: mysql Ver 15.1 Distrib 10.5.16-MariaDB, for Linux (x86_64) >>> using EditLine wrapper >>> Apache version: Server version: Apache/2.4.53 (AlmaLinux) Server built: >>> Jul >>> 20 2022 00:00:00 >>> Memcached: Servers: 127.0.0.1:11211 | Namespace: KOHA | Status: >>> running. | >>> Config read from: koha-conf.xml >>> Zebra version: Zebra 2.2.7 (C) 1994-2023, Index Data Zebra is free >>> software, covered by the GNU General Public License, and you are welcome >>> to >>> change it and/or distribute copies of it under certain conditions. SHA1 >>> ID: >>> ac40f289672405a299436d73c1532f9906774cc6 Using ICU >>> Zebra status: Running >>> Message broker: Using RabbitMQ >>> Date and time: 03/01/2023 16:20 >>> Time zone: Used: America/Chicago | Config: Undefined | Environment (TZ): >>> Undefined >>> >>> Thanks, >>> Michael >>> _______________________________________________ >>> >>> Koha mailing list http://koha-community.org >>> Koha(a)lists.katipo.co.nz >>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >>> >>

3 4

22.11.x String Freeze
by Renvoize, Martin 16 May '23

16 May '23

I can happily report that we are now in string freeze for 22.11.06. Happy translating. 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

Not Indexed Records
by Mohamad F Barham 15 May '23

15 May '23

Dears, I am using Elasticsearch but having Records are not indexed in Elasticsearch Warning7010 record(s) missing on a total of 306407 in index koha_koha_biblios. how to find unindexed records? Regards Mohamad Barham System Engineer | Information Technology Department Birzeit University P.O.Box. 14, Birzeit, Palestine Tel: + 970 22982012 | Mob: +970 597 861929 | Ext: 5616 mbarham(a)birzeit.edu | www.birzeit.edu<http://www.birzeit.edu/> ~~~~~~~~~~~~~~~~~~~~~~~~~~ The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. The University is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt. ~~~~~~~~~~~~~~~~~~~~~~~~~~

2 1

The Koha Community Wiki and SPAM registrations/SPAM pages and edits
by David Nind 14 May '23

14 May '23

In the last week, a configuration issue was identified with account creation on the Wiki. This issue meant that some Wiki accounts were created without going through the account approval process. This has occurred since the Wiki upgrade in late October 2022. We are fortunate that this resulted in very little SPAM, and most of this was in early May (and mainly on the newly created account user pages). Action taken ----------------- 1. The configuration issue was fixed. 2. Any SPAM pages created were deleted, and any edits were reverted (with the accounts responsible blocked). 3. We've also blocked all Wiki accounts created since the October upgrade, where the account has: - not created a user page, and - not edited or created any pages. Do I need to do anything? ---------------------------------- You only need to do something if you requested an account after the October 2022 upgrade, or are having issues logging in to the Wiki. If **you have created a Wiki account since October 2022**, and find that you can't log in or are blocked, please let me know and I will get it fixed. If **you find you are blocked from logging in**, please let me know and I will get it fixed. More information ----------------------- For more information, see: - Bug 23073: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23073 - Message thread on the development mailing list: https://lists.koha-community.org/pipermail/koha-devel/2023-May/048145.html David Nind | david(a)davidnind.com m. +64 21 0537 847

1 0

How to limit entry of the number of copies in Koha?
by Victor Barroso Oliveira 14 May '23

14 May '23

Hello friends, How to limit entry of the number of copies in Koha? Thanks, Victor

2 1

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