From kohanews at gmail.com Fri Jul 1 06:16:55 2022 From: kohanews at gmail.com (Koha Newsletter) Date: Thu, 30 Jun 2022 20:16:55 +0200 Subject: [Koha] Koha Community Newsletter: June 2022 Message-ID: The Koha Community Newsletter for June 2022 is here: https://koha-community.org/koha-community-newsletter-june-2022/ 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 From keith at thesorbos.com Fri Jul 1 14:03:56 2022 From: keith at thesorbos.com (Keith Sorbo) Date: Thu, 30 Jun 2022 21:03:56 -0500 Subject: [Koha] How to update database from command line Message-ID: What is the proper way to update my database from the command line? When I run from the web interface, it times out and leaves me with an error in my database. Thanks. From mtj at kohaaloha.com Fri Jul 1 19:40:49 2022 From: mtj at kohaaloha.com (Mason James) Date: Fri, 1 Jul 2022 19:40:49 +1200 Subject: [Koha] How to update database from command line In-Reply-To: References: Message-ID: <0f31e837-f633-2809-5be3-22a5860ff7c5@kohaaloha.com> hi Keith try the following command...  $ sudo koha-upgrade-schema mykoha On 1/07/22 2:03 pm, Keith Sorbo wrote: > What is the proper way to update my database from the command line? > > When I run from the web interface, it times out and leaves me with an error > in my database. > > Thanks. > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From tadas.kaupa at gmail.com Fri Jul 1 22:49:28 2022 From: tadas.kaupa at gmail.com (Tadas G) Date: Fri, 1 Jul 2022 13:49:28 +0300 Subject: [Koha] Koha SQL report with MARC field Message-ID: Hello, My Koha 21.05.11 version. I use this report to view the inventory. It works well. The question would be how would I go about adding a MARC field from Record e.g 675$3 Maybe someone has an idea how to add it? SELECT items.dateaccessioned AS Pridėjimas,items.barcode AS Barkodas,biblio.author AS Autorius,biblio.title AS Pavadinimas,biblioitems.publishercode AS Leidykla,items.copynumber AS Inventorinis,biblioitems.isbn AS ISBN,items.itemnotes AS Uzrasai,items.itype AS Išteklis,items.homebranch AS Lokacija FROM items LEFT JOIN biblioitems ON (items.biblioitemnumber=biblioitems.biblioitemnumber) LEFT JOIN biblio ON (biblioitems.biblionumber=biblio.biblionumber) WHERE items.dateaccessioned BETWEEN <> and <> ORDER BY items.barcode DESC I think you need to add lines: CONCAT('', b.title, '' ) AS Title, ExtractValue(bi.metadata, '//datafield[@tag="675"]/subfield[@code="3"]') AS "Informacija", But I don't know how to add them to work Thanks for the help From Holger.Meissner at hs-gesundheit.de Fri Jul 1 23:34:26 2022 From: Holger.Meissner at hs-gesundheit.de (Holger Meissner) Date: Fri, 1 Jul 2022 11:34:26 +0000 Subject: [Koha] Koha SQL report with MARC field Message-ID: Hello Tadas, does this work? SELECT i.dateaccessioned AS "Pridejimas", i.barcode AS "Barkodas", b.author AS "Autorius", b.title AS "Pavadinimas", bi.publishercode AS "Leidykla", i.copynumber AS "Inventorinis", bi.isbn AS "ISBN", i.itemnotes AS "Uzrasai", i.itype AS "Išteklis", i.homebranch AS "Lokacija", ExtractValue(m.metadata, '//datafield[@tag="675"]/subfield[@code="3"]') AS "Informacija" FROM items i LEFT JOIN biblioitems bi ON i.biblioitemnumber = bi.biblioitemnumber LEFT JOIN biblio b ON bi.biblionumber = b.biblionumber LEFT JOIN biblio_metadata m ON m.biblionumber = b.biblionumber WHERE i.dateaccessioned BETWEEN <> AND <> ORDER BY i.barcode DESC Regards, Holger From tadas.kaupa at gmail.com Sat Jul 2 00:38:20 2022 From: tadas.kaupa at gmail.com (Tadas G) Date: Fri, 1 Jul 2022 15:38:20 +0300 Subject: [Koha] Koha SQL report with MARC field Message-ID: The report starts but does not show all the information. The column is empty Thanks for the help From isabel.pineda at ds.edu.sv Sat Jul 2 01:29:05 2022 From: isabel.pineda at ds.edu.sv (Isabel Pineda) Date: Fri, 1 Jul 2022 13:29:05 +0000 Subject: [Koha] Koha 22.05 on Ubuntu 22.04? In-Reply-To: References: <11334004-8625-b668-0f11-4113fdac67c8@adminkuhn.ch> Message-ID: Hi. I have just revisited the page of the system requirements (https://wiki.koha-community.org/wiki/System_requirements_and_recommendations), and now I see that Ubuntu 22.04 is supported, in Koha 22.05 and even in the Koha 21 versions. Can you confirm that? Thank you Isabel Pineda -----Mensaje original----- De: Isabel Pineda Enviado el: viernes, 10 de junio de 2022 09:15 Para: koha at lists.katipo.co.nz Asunto: RE: [Koha] Koha 22.05 on Ubuntu 22.04? Thank you, Fridolin and Michael. Best regards Isabel -----Mensaje original----- De: Koha En nombre de Fridolin SOMERS Enviado el: jueves, 9 de junio de 2022 15:04 Para: koha at lists.katipo.co.nz Asunto: Re: [Koha] Koha 22.05 on Ubuntu 22.04? Hi, We have build a CI for Ubuntu 22.04 that works well : https://jenkins.koha-community.org/view/22.05/ So you can give it a try. But its quite fresh to we decided to support officially only in next release 22.11. Best regards, Le 09/06/2022 à 06:31, Michael Kuhn a écrit : > Hi Isabel > > You wrote: > > > Does Koha 22.05 support Ubuntu 22.04? In the system requirements I > can > see that it goes only from Ubuntu version 18.04 to 21.10. > > According to > https://wiki.koha-community.org/wiki/System_requirements_and_recommend > ations#Koha_22.05 Ubuntu 22.04 is not one of officially supported > operating systems yet. > > Hope this helps. > > Best wishes: Michael -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France _______________________________________________ Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From Holger.Meissner at hs-gesundheit.de Sat Jul 2 02:04:57 2022 From: Holger.Meissner at hs-gesundheit.de (Holger Meissner) Date: Fri, 1 Jul 2022 14:04:57 +0000 Subject: [Koha] Koha SQL report with MARC field Message-ID: <7834243cf69b41ea90f6e1c9212f8a14@nExchange1.hsg.intra> Hello Tadas, I suppose your MARC field is empty, then. As far as I can tell, field 675 is not used in MARC 21 bibliographic records. https://www.loc.gov/marc/bibliographic/bd6xx.html Maybe try field 657? Or rather take a look at your MARC records and check which field contains the information you need. Regards, Holger Tadas G wrote: > The report starts but does not show all the information. The column is empty From c.s.hayward at protonmail.com Sat Jul 2 03:17:38 2022 From: c.s.hayward at protonmail.com (C.S. Hayward) Date: Fri, 01 Jul 2022 15:17:38 +0000 Subject: [Koha] Migrating from one server to another Message-ID: (Note: I am not using "migrate" as it is usually used today, meaning switching from ABC software to DEF. I'm referring to relocating an installation's data.) I would like to migrate my data from one Koha installation on one server to another installation on another server. Both use MariaDB. Where are instructions suitable to migrating data between two different servers? Thanks, Br. C.S. Hayward From c.s.hayward at protonmail.com Sat Jul 2 03:27:59 2022 From: c.s.hayward at protonmail.com (C.S. Hayward) Date: Fri, 01 Jul 2022 15:27:59 +0000 Subject: [Koha] Migrating from one server to another In-Reply-To: References: Message-ID: One minor clarification: Earlier I was trying to install Koha on an existing Debian server. Now I have left that server and am working on installing to a clean Ubuntu server. I've had an uneventful run-through of getting to the web installer, and getting through most of using the web installer on the new machine. I suspect further data may be clobbered by the data from the migration. Br. C.S. Hayward, https://c-s-hayward.com. ------- Original Message ------- On Friday, July 1st, 2022 at 11:17 AM, C.S. Hayward wrote: > (Note: I am not using "migrate" as it is usually used today, meaning switching from ABC software to DEF. I'm referring to relocating an installation's data.) > > I would like to migrate my data from one Koha installation on one server to another installation on another server. Both use MariaDB. > > Where are instructions suitable to migrating data between two different servers? > > > Thanks, > Br. C.S. Hayward From libsitali at gmail.com Sat Jul 2 04:45:53 2022 From: libsitali at gmail.com (Mr. Sitali C. S.) Date: Fri, 1 Jul 2022 18:45:53 +0200 Subject: [Koha] Migrating from one server to another In-Reply-To: References: Message-ID: Try the following: http://kohageek.pbworks.com/w/page/60452540/How%20to%20move%20your%20koha%20database%20to%20newly%20installed%20Koha On Fri, Jul 1, 2022, 17:28 C.S. Hayward wrote: > One minor clarification: > > Earlier I was trying to install Koha on an existing Debian server. Now I > have left that server and am working on installing to a clean Ubuntu server. > > I've had an uneventful run-through of getting to the web installer, and > getting through most of using the web installer on the new machine. I > suspect further data may be clobbered by the data from the migration. > > Br. C.S. Hayward, https://c-s-hayward.com. > > > ------- Original Message ------- > On Friday, July 1st, 2022 at 11:17 AM, C.S. Hayward < > c.s.hayward at protonmail.com> wrote: > > > > (Note: I am not using "migrate" as it is usually used today, meaning > switching from ABC software to DEF. I'm referring to relocating an > installation's data.) > > > > I would like to migrate my data from one Koha installation on one server > to another installation on another server. Both use MariaDB. > > > > Where are instructions suitable to migrating data between two different > servers? > > > > > > Thanks, > > Br. C.S. Hayward > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From rtr.himanshu at gmail.com Sat Jul 2 04:50:27 2022 From: rtr.himanshu at gmail.com (Himanshu Aggarwal) Date: Fri, 1 Jul 2022 22:20:27 +0530 Subject: [Koha] Koha 22.05 on Ubuntu 22.04? In-Reply-To: References: <11334004-8625-b668-0f11-4113fdac67c8@adminkuhn.ch> Message-ID: Yes Koha 22.05 works smoothly on Ubuntu 22.04 On Fri, Jul 1, 2022 at 6:59 PM Isabel Pineda wrote: > Hi. > > I have just revisited the page of the system requirements ( > https://wiki.koha-community.org/wiki/System_requirements_and_recommendations), > and now I see that Ubuntu 22.04 is supported, in Koha 22.05 and even in the > Koha 21 versions. Can you confirm that? > > Thank you > Isabel Pineda > > > > -----Mensaje original----- > De: Isabel Pineda > Enviado el: viernes, 10 de junio de 2022 09:15 > Para: koha at lists.katipo.co.nz > Asunto: RE: [Koha] Koha 22.05 on Ubuntu 22.04? > > Thank you, Fridolin and Michael. > > Best regards > > Isabel > > > > -----Mensaje original----- > De: Koha En nombre de Fridolin SOMERS > Enviado el: jueves, 9 de junio de 2022 15:04 > Para: koha at lists.katipo.co.nz > Asunto: Re: [Koha] Koha 22.05 on Ubuntu 22.04? > > Hi, > > We have build a CI for Ubuntu 22.04 that works well : > https://jenkins.koha-community.org/view/22.05/ > > So you can give it a try. > > But its quite fresh to we decided to support officially only in next > release 22.11. > > Best regards, > > Le 09/06/2022 à 06:31, Michael Kuhn a écrit : > > Hi Isabel > > > > You wrote: > > > > > Does Koha 22.05 support Ubuntu 22.04? In the system requirements I > > can > see that it goes only from Ubuntu version 18.04 to 21.10. > > > > According to > > https://wiki.koha-community.org/wiki/System_requirements_and_recommend > > ations#Koha_22.05 Ubuntu 22.04 is not one of officially supported > > operating systems yet. > > > > Hope this helps. > > > > Best wishes: Michael > > -- > Fridolin SOMERS Software and system > maintainer 🦄 > BibLibre, France > _______________________________________________ > > Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > -- Assistant Librarian, Confucius Institute Scholar 13-14, R.D. National College, Bandra (W.) From isabel.pineda at ds.edu.sv Sat Jul 2 04:56:23 2022 From: isabel.pineda at ds.edu.sv (Isabel Pineda) Date: Fri, 1 Jul 2022 16:56:23 +0000 Subject: [Koha] Koha 22.05 on Ubuntu 22.04? In-Reply-To: References: <11334004-8625-b668-0f11-4113fdac67c8@adminkuhn.ch> Message-ID: Thank you. This is really important information for me. De: Himanshu Aggarwal Enviado el: viernes, 1 de julio de 2022 10:50 Para: Isabel Pineda CC: koha at lists.katipo.co.nz Asunto: Re: [Koha] Koha 22.05 on Ubuntu 22.04? Yes Koha 22.05 works smoothly on Ubuntu 22.04 On Fri, Jul 1, 2022 at 6:59 PM Isabel Pineda > wrote: Hi. I have just revisited the page of the system requirements (https://wiki.koha-community.org/wiki/System_requirements_and_recommendations), and now I see that Ubuntu 22.04 is supported, in Koha 22.05 and even in the Koha 21 versions. Can you confirm that? Thank you Isabel Pineda -----Mensaje original----- De: Isabel Pineda Enviado el: viernes, 10 de junio de 2022 09:15 Para: koha at lists.katipo.co.nz Asunto: RE: [Koha] Koha 22.05 on Ubuntu 22.04? Thank you, Fridolin and Michael. Best regards Isabel -----Mensaje original----- De: Koha > En nombre de Fridolin SOMERS Enviado el: jueves, 9 de junio de 2022 15:04 Para: koha at lists.katipo.co.nz Asunto: Re: [Koha] Koha 22.05 on Ubuntu 22.04? Hi, We have build a CI for Ubuntu 22.04 that works well : https://jenkins.koha-community.org/view/22.05/ So you can give it a try. But its quite fresh to we decided to support officially only in next release 22.11. Best regards, Le 09/06/2022 à 06:31, Michael Kuhn a écrit : > Hi Isabel > > You wrote: > > > Does Koha 22.05 support Ubuntu 22.04? In the system requirements I > can > see that it goes only from Ubuntu version 18.04 to 21.10. > > According to > https://wiki.koha-community.org/wiki/System_requirements_and_recommend > ations#Koha_22.05 Ubuntu 22.04 is not one of officially supported > operating systems yet. > > Hope this helps. > > Best wishes: Michael -- Fridolin SOMERS > Software and system maintainer 🦄 BibLibre, France _______________________________________________ Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha _______________________________________________ Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha -- Assistant Librarian, Confucius Institute Scholar 13-14, R.D. National College, Bandra (W.) From tomascohen at gmail.com Sat Jul 2 06:45:04 2022 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Fri, 1 Jul 2022 15:45:04 -0300 Subject: [Koha] Koha 22.05 on Ubuntu 22.04? In-Reply-To: References: <11334004-8625-b668-0f11-4113fdac67c8@adminkuhn.ch> Message-ID: Our test suite covers several distros. It is not perfect, though. But generally speaking, it is supported, the best we can :-D El vie, 1 jul 2022 a las 13:57, Isabel Pineda () escribió: > Thank you. This is really important information for me. > > > > De: Himanshu Aggarwal > Enviado el: viernes, 1 de julio de 2022 10:50 > Para: Isabel Pineda > CC: koha at lists.katipo.co.nz > Asunto: Re: [Koha] Koha 22.05 on Ubuntu 22.04? > > Yes Koha 22.05 works smoothly on Ubuntu 22.04 > > On Fri, Jul 1, 2022 at 6:59 PM Isabel Pineda > wrote: > Hi. > > I have just revisited the page of the system requirements ( > https://wiki.koha-community.org/wiki/System_requirements_and_recommendations), > and now I see that Ubuntu 22.04 is supported, in Koha 22.05 and even in the > Koha 21 versions. Can you confirm that? > > Thank you > Isabel Pineda > > > > -----Mensaje original----- > De: Isabel Pineda > Enviado el: viernes, 10 de junio de 2022 09:15 > Para: koha at lists.katipo.co.nz > Asunto: RE: [Koha] Koha 22.05 on Ubuntu 22.04? > > Thank you, Fridolin and Michael. > > Best regards > > Isabel > > > > -----Mensaje original----- > De: Koha koha-bounces at lists.katipo.co.nz>> En nombre de Fridolin SOMERS Enviado > el: jueves, 9 de junio de 2022 15:04 > Para: koha at lists.katipo.co.nz > Asunto: Re: [Koha] Koha 22.05 on Ubuntu 22.04? > > Hi, > > We have build a CI for Ubuntu 22.04 that works well : > https://jenkins.koha-community.org/view/22.05/ > > So you can give it a try. > > But its quite fresh to we decided to support officially only in next > release 22.11. > > Best regards, > > Le 09/06/2022 à 06:31, Michael Kuhn a écrit : > > Hi Isabel > > > > You wrote: > > > > > Does Koha 22.05 support Ubuntu 22.04? In the system requirements I > > can > see that it goes only from Ubuntu version 18.04 to 21.10. > > > > According to > > https://wiki.koha-community.org/wiki/System_requirements_and_recommend > > ations#Koha_22.05 Ubuntu 22.04 is not one of officially supported > > operating systems yet. > > > > Hope this helps. > > > > Best wishes: Michael > > -- > Fridolin SOMERS fridolin.somers at biblibre.com>> Software and system maintainer 🦄 > BibLibre, France > _______________________________________________ > > Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > -- > Assistant Librarian, > Confucius Institute Scholar 13-14, > R.D. National College, > Bandra (W.) > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F From evanstewart406 at gmail.com Sat Jul 2 15:58:04 2022 From: evanstewart406 at gmail.com (Evan Stewart) Date: Fri, 1 Jul 2022 21:58:04 -0600 Subject: [Koha] Migrating from one server to another In-Reply-To: References: Message-ID: Hi CS, What version of Koha is running on the old server and what version is running on the new server? I've relocated my data from a server running Koha 20 to one running Koha 21 without issue. Both servers were Debian 10. It is fairly simple using the koha-dump and koha-restore commands from the Linux terminal. You run koha-dump on the old server, copy the files created to the new server, and then run koha-restore on the new server. The koha-dump command creates a .tar file of the application config files and the database dump file. You can install Koha on the new server but instead of creating a new instance (like you would if you were installing a new library setup) you can use the koha-restore command to restore the previous Koha installation to the new server. A brief summary of the koha-dump and koha-restore commands can be found here: https://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_packages#koha-dump After the older install is restored to the new server (using koha-restore) you must edit the Apache config file used for the Koha instance to match the new server environment (assuming you're using Apache for the server). On my Debian server the site config file is located at /etc/apache2/sites-enabled/instanceName.conf If it would help, I will look for my notes I made the last time I did this earlier this year. -Evan On Fri, Jul 1, 2022 at 9:28 AM C.S. Hayward wrote: > One minor clarification: > > Earlier I was trying to install Koha on an existing Debian server. Now I > have left that server and am working on installing to a clean Ubuntu server. > > I've had an uneventful run-through of getting to the web installer, and > getting through most of using the web installer on the new machine. I > suspect further data may be clobbered by the data from the migration. > > Br. C.S. Hayward, https://c-s-hayward.com. > > > ------- Original Message ------- > On Friday, July 1st, 2022 at 11:17 AM, C.S. Hayward < > c.s.hayward at protonmail.com> wrote: > > > > (Note: I am not using "migrate" as it is usually used today, meaning > switching from ABC software to DEF. I'm referring to relocating an > installation's data.) > > > > I would like to migrate my data from one Koha installation on one server > to another installation on another server. Both use MariaDB. > > > > Where are instructions suitable to migrating data between two different > servers? > > > > > > Thanks, > > Br. C.S. Hayward > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From keith at thesorbos.com Sun Jul 3 06:50:00 2022 From: keith at thesorbos.com (Keith Sorbo) Date: Sat, 2 Jul 2022 13:50:00 -0500 Subject: [Koha] DB Upgrade error saga Message-ID: I am still struggling to get my koha library database to upgrade properly. My saga: 1. I attempted an update which timed out and errored. 2. I restored from a mysql database prior to my update attempt 3. I ran the koha-upgrade-schema library update. It ran through quite few upgrades but errored with the following: Upgrading database schema for sati Upgrade to 21.12.00.057 [18:44:54]: Bug 30852 - Add index to article_requests.debit_id ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Key column 'debit_id' doesn't exist in table at /usr/share/koha/lib/C4/Installer.pm line 739 DEV atomic update /usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/ bug_30899.pl [18:44:54]: Bug 30899 - Check borrower_attribute_types FK constraint (30449 follow-up) What do I need to do to get my koha library back up and functional? (We have been offline for over 2 weeks because of the database upgrade problems!) From cornejo.alvaro at gmail.com Sun Jul 3 07:41:09 2022 From: cornejo.alvaro at gmail.com (Alvaro Cornejo) Date: Sat, 2 Jul 2022 14:41:09 -0500 Subject: [Koha] DB Upgrade error saga In-Reply-To: References: Message-ID: Hi Keith For the 1st error, it seems debit_id was not created during upgrade so you can try to manually add the missing column 'debit_id' accessing directly to the db and then run schema-upgrade again. On koha 21.11 as per https://schema.koha-community.org/21_11/tables/article_requests.html 'debit_id' does not exist but on 22.05 it does ( https://schema.koha-community.org/22_05/tables/article_requests.html) As per the DB definition debit_id is a column INT 10 so you can do something like: ALTER TABLE article_requests ADD debit_id INT AFTER cancellation_reason For the 2nd error, I have no idea. As always, backup your database before trying this manual modification. Regards, Alvaro |----------------------------------------------------------------------------------------| Stay safe / Cuídate/ Reste sécurisé *7* Switch off as you go / Apaga lo que no usas / Débranchez au fur et à mesure. *q *Recycle always / Recicla siempre / Recyclez toujours P Print only if absolutely necessary / Imprime solo si es necesario / Imprimez seulement si nécessaire Le sam. 2 juil. 2022 à 13:50, Keith Sorbo a écrit : > I am still struggling to get my koha library database to upgrade properly. > > My saga: > 1. I attempted an update which timed out and errored. > 2. I restored from a mysql database prior to my update attempt > 3. I ran the koha-upgrade-schema library update. It ran through quite few > upgrades but errored with the following: > > Upgrading database schema for sati > Upgrade to 21.12.00.057 [18:44:54]: Bug 30852 - Add index to > article_requests.debit_id > ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Key column > 'debit_id' doesn't exist in table at /usr/share/koha/lib/C4/Installer.pm > line 739 > > DEV atomic update > /usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/ > bug_30899.pl [18:44:54]: Bug 30899 - Check borrower_attribute_types FK > constraint (30449 follow-up) > > What do I need to do to get my koha library back up and functional? (We > have been offline for over 2 weeks because of the database upgrade > problems!) > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From katrin.fischer.83 at web.de Mon Jul 4 04:01:28 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sun, 3 Jul 2022 18:01:28 +0200 Subject: [Koha] Sort 1 and 2 In-Reply-To: References: Message-ID: Hi, at the moment this is not possible, but there already is a bug for this: *Bug 13901* - sort1 and sort2 not on self registration form Hope this helps, Katrin at the moment it's not possible On 24.06.22 09:49, Himanshu Aggarwal wrote: > Is there any way one can enable Sort 1 and 2 in Self Registration? > From katrin.fischer.83 at web.de Mon Jul 4 04:04:16 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sun, 3 Jul 2022 18:04:16 +0200 Subject: [Koha] BULKMARC IMPORT RECORDS VIA TERMINAL In-Reply-To: References: Message-ID: Hi James, I am not sure if this is possible with bulkmarcimport, but it's possible with the stage_file.pl and commit_file.pl scripts. They work like the staged import tool. Hope this helps, Katrin On 24.06.22 09:29, muiru james wrote: > Hello, > > I want to bulk import records with items via terminal and I want to match > records using title(245a) where if it exists to skip the incoming record > but add items. > > How can I modify this script not to replace existing record with incoming > one? > > perl bulkmarcimport.pl -framework BKS -b -file newbooks.mrc -match -Title:p > > Warm regards > James > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From rtr.himanshu at gmail.com Mon Jul 4 04:29:53 2022 From: rtr.himanshu at gmail.com (Himanshu Aggarwal) Date: Sun, 3 Jul 2022 21:59:53 +0530 Subject: [Koha] Sort 1 and 2 In-Reply-To: References: Message-ID: But No solution on this yet On Sun, Jul 3, 2022 at 9:32 PM Katrin Fischer wrote: > Hi, > > at the moment this is not possible, but there already is a bug for this: > > *Bug 13901* > - > sort1 and sort2 not on self registration form > > Hope this helps, > > Katrin > > at the moment it's not possible > > On 24.06.22 09:49, Himanshu Aggarwal wrote: > > Is there any way one can enable Sort 1 and 2 in Self Registration? > > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > -- Assistant Librarian, Confucius Institute Scholar 13-14, R.D. National College, Bandra (W.) From lennon at kohasupport.com Mon Jul 4 22:11:04 2022 From: lennon at kohasupport.com (=?UTF-8?Q?Lennon_Mazonde?=) Date: Mon, 4 Jul 2022 10:11:04 +0000 Subject: [Koha] Migrating from one server to another In-Reply-To: References: <7e5265ff-7f93-910a-8774-d2a07e0e5d15@kohasupport.com> Message-ID: <01000181c8b13147-6bd33035-915f-44df-8da3-c7cf945aadc6-000000@email.amazonses.com> Hi, I have a repo on GitHub with scripts that might be able to help you. Have a look at the 'koha-migrate' script - I originally wrote it to migrate several Koha MariaDB databases running on a Ubuntu (20.04LTS) server to Amazon Aurora MySQL on AWS but it should work for other use-cases. There are several other scripts there you might find useful as well. As always, test them in a dev environment before running them on your production server :) If anyone else is interested and would like to contribute to the project, please let me know! Best regards, Lennon Mazonde KohaSupport lennon at kohasupport.com www.kohasupport.com 651 North Broad Street, Middletown, DE 19709, USA The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. On 7/1/22 5:17 PM, C.S. Hayward wrote: (Note: I am not using "migrate" as it is usually used today, meaning switching from ABC software to DEF. I'm referring to relocating an installation's data.) I would like to migrate my data from one Koha installation on one server to another installation on another server. Both use MariaDB. Where are instructions suitable to migrating data between two different servers? Thanks, Br. C.S. Hayward _______________________________________________ Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From lennon at kohasupport.com Mon Jul 4 22:14:42 2022 From: lennon at kohasupport.com (=?UTF-8?Q?Lennon_Mazonde?=) Date: Mon, 4 Jul 2022 10:14:42 +0000 Subject: [Koha] Migrating from one server to another In-Reply-To: <01000181c8b13147-6bd33035-915f-44df-8da3-c7cf945aadc6-000000@email.amazonses.com> References: <7e5265ff-7f93-910a-8774-d2a07e0e5d15@kohasupport.com> <01000181c8b13147-6bd33035-915f-44df-8da3-c7cf945aadc6-000000@email.amazonses.com> <6ddbbc0d-bfa8-3d69-8eb5-1de889d6209a@kohasupport.com> Message-ID: <01000181c8b482ca-9bef45b4-aaf6-4953-bc28-60a38a5eae55-000000@email.amazonses.com> Forgot to add the link to the GitHub repo, here it is - https://github.com/grandmaestr/koha-scripts. Best regards, Lennon Mazonde KohaSupport lennon at kohasupport.com www.kohasupport.com 651 North Broad Street, Middletown, DE 19709, USA The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. On 7/4/22 12:11 PM, Lennon Mazonde wrote: Hi, I have a repo on GitHub with scripts that might be able to help you. Have a look at the 'koha-migrate' script - I originally wrote it to migrate several Koha MariaDB databases running on a Ubuntu (20.04LTS) server to Amazon Aurora MySQL on AWS but it should work for other use-cases. There are several other scripts there you might find useful as well. As always, test them in a dev environment before running them on your production server :) If anyone else is interested and would like to contribute to the project, please let me know! Best regards, Lennon Mazonde KohaSupport lennon at kohasupport.com www.kohasupport.com 651 North Broad Street, Middletown, DE 19709, USA The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. On 7/1/22 5:17 PM, C.S. Hayward wrote: (Note: I am not using "migrate" as it is usually used today, meaning switching from ABC software to DEF. I'm referring to relocating an installation's data.) I would like to migrate my data from one Koha installation on one server to another installation on another server. Both use MariaDB. Where are instructions suitable to migrating data between two different servers? Thanks, Br. C.S. Hayward _______________________________________________ Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha _______________________________________________ Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From caroline.cyr-la-rose at inlibro.com Tue Jul 5 00:46:18 2022 From: caroline.cyr-la-rose at inlibro.com (Caroline Cyr La Rose) Date: Mon, 4 Jul 2022 08:46:18 -0400 Subject: [Koha] Koha SQL report with MARC field In-Reply-To: References: Message-ID: Hi, The metadata was moved to it's own table some time ago. You will need to add this line somewhere in the SELECT ExtractValue(biblio_metadata.metadata, '//datafield[@tag="675"]/subfield[@code="3"]') AS "Informacija" And this line between the last LEFT JOIN and the WHERE LEFT JOIN biblio_metadata USING (biblionumber) Like this (I added some carriage returns for legibility) SELECT items.dateaccessioned AS Pridėjimas, items.barcode AS Barkodas, biblio.author AS Autorius, biblio.title AS Pavadinimas, biblioitems.publishercode AS Leidykla, items.copynumber AS Inventorinis, biblioitems.isbn AS ISBN, items.itemnotes AS Uzrasai, items.itype AS Išteklis, items.homebranch AS Lokacija, ExtractValue(biblio_metadata.metadata, '//datafield[@tag="675"]/subfield[@code="3"]') AS "Informacija" FROM items LEFT JOIN biblioitems ON (items.biblioitemnumber=biblioitems.biblioitemnumber) LEFT JOIN biblio ON (biblioitems.biblionumber=biblio.biblionumber) LEFT JOIN biblio_metadata USING (biblionumber) WHERE items.dateaccessioned BETWEEN <> AND <> ORDER BY items.barcode DESC (Note: I haven't tested it...) Good luck! Caroline On 2022-07-01 06:49, Tadas G wrote: > Hello, My Koha 21.05.11 version. > I use this report to view the inventory. It works well. The question would > be how would I go about adding a MARC field from Record e.g 675$3 > Maybe someone has an idea how to add it? > > SELECT items.dateaccessioned AS Pridėjimas,items.barcode AS > Barkodas,biblio.author AS Autorius,biblio.title AS > Pavadinimas,biblioitems.publishercode AS Leidykla,items.copynumber AS > Inventorinis,biblioitems.isbn AS ISBN,items.itemnotes AS > Uzrasai,items.itype AS Išteklis,items.homebranch AS Lokacija FROM items > LEFT JOIN biblioitems ON > (items.biblioitemnumber=biblioitems.biblioitemnumber) > LEFT JOIN biblio ON (biblioitems.biblionumber=biblio.biblionumber) WHERE > items.dateaccessioned BETWEEN > <> and <> > ORDER BY items.barcode DESC > > I think you need to add lines: > CONCAT(' '\">', b.title, '' ) AS Title, > ExtractValue(bi.metadata, > '//datafield[@tag="675"]/subfield[@code="3"]') AS "Informacija", > > But I don't know how to add them to work > > > Thanks for the help > _______________________________________________ > > Koha mailing listhttp://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha -- Caroline Cyr La Rose, M.S.I. Bibliothécaire | Responsable de produit Tél. : 1-833-465-4276, poste 221 Caroline.Cyr-La-Rose at inLibro.com INLiBRO | Spécialistes en technologies documentaires | www.inLibro.com From itmanager at dhi-moskau.org Tue Jul 5 01:05:51 2022 From: itmanager at dhi-moskau.org (DHIM IT) Date: Mon, 4 Jul 2022 13:05:51 +0000 Subject: [Koha] Translation mistakes ru-RU In-Reply-To: References: Message-ID: <09B05801-6305-4A17-A362-77ED055440B8@dhi-moskau.org> Dear Colleagues, I found some mistakes in the translation ru-RU. How can I provide to all KOHA users right translation? Mit besten Grüßen, Eugen Bastron IT-Manager Deutsches Historisches Institut Moskau From toni.afandi at gmail.com Tue Jul 5 02:40:53 2022 From: toni.afandi at gmail.com (Toni Afandi) Date: Mon, 4 Jul 2022 21:40:53 +0700 Subject: [Koha] Non letter character in searching Message-ID: Dear all, I vobe Koha, but there is an annoying matter that I've experienced when do searching in Koha. If I included a non-letter character, for example a colon, I got no results. But if I remove it, then the results show up. Anyone can help? I use Koha 20.11.18.000 with Zebra. I have not tried using ElasticSearch yet, due to failed installation in the first attempts, two years ago. Thank you in advance. Regards, *Toni Afandi* *Librarian* *STT SAAT* *(Southeast Asia Bible Seminary)* From cmkelleymls at gmail.com Tue Jul 5 11:20:31 2022 From: cmkelleymls at gmail.com (Charles Kelley) Date: Tue, 5 Jul 2022 08:20:31 +0900 Subject: [Koha] Rotating IP Address and Koha Logout Message-ID: Hi, all! My library is moving its Koha ILS to an AWS-based server. In development, it was on a standalone laptop. In the testing phase on the AWS server, we have noted that the IP address for logins changes every thirty seconds and staff are signed out from Koha. The staff have to sign in anew and refresh. Whatever the staff were working on -- search, record editing, uploading new records, etc. -- may or may not survive intact. We don't know what causes this, but it's like IP 42.0.2.35 Staff types a search query. IP 42.0.2.35 Staff selects Edit Record from dropdown menu. Sudden change to IP 42.0.2.29 Record vanishes. Login screen appears. New IP 42.0.2.34 Staff logs in anew Staff backs up two tabs (or windows) and continues. New IP 42.02.31 Repeat of what staff intervention at New IP 42.0.2.34 Eventually whatever the staff were working on is accomplished, but logging in anew and reentering the previous steps so often are a bit inconvenient, to state the least. My IT staff doesn't understand this phenomenon. We checked the system preferences, but we haven't changed the timeouts since Koha was initially installed. Has this been reported to the Koha development teams or on this discussion group before? Does anyone have an idea what would be causing this? -- よろしくお願いします。 -- Charles. Until 2022-07-15: Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 +81-80-4356-2178 [JPN cell] From 2022-07-18: Charles Kelley c/o Bob and Ronni DiGioia 147 Mitchel Drive Oakland, MD 21550 USA +1-301-741-7122 [US cell] mnogojazyk at aol.com [h] cmkelleymls at gmail.com [p] linkedin.com/in/cmkelleymls Meeting Your Information Needs. Virtually. From vbovictor at gmail.com Tue Jul 5 11:41:49 2022 From: vbovictor at gmail.com (Victor Barroso Oliveira) Date: Mon, 4 Jul 2022 20:41:49 -0300 Subject: [Koha] Options of "export database" and "export settings" are not available Message-ID: In Ubuntu 20.5 and Koha 22.05.02.000 I enabled in instance-conf.xml 1 1 In Tools --> Export Data The option tohe option of "export database" and "export settings" are not available. Here's the information that appears: "Note: This generated file will be very large, and will be generated daily." "Unfortunately, there are no backups available." From dcook at prosentient.com.au Tue Jul 5 12:06:26 2022 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Tue, 5 Jul 2022 10:06:26 +1000 Subject: [Koha] Fonts for "Label creator" Message-ID: <008901d89003$11fa5630$35ef0290$@prosentient.com.au> Hi all, Do folk ever need to print labels in multiple languages with different scripts and find that the “Label creator” doesn’t work? European scripts will print but Chinese, Japanese, Korean and others don’t? Well I have a story about how to make it work... -- Recently, I needed to print labels that had both English and Chinese, but the Chinese was showing up as an empty box like ▯ while the English appeared correctly. Initially I turned to the Koha plugin https://github.com/bywatersolutions/koha-plugin-label-maker which worked great, because it leverages the browser's ability to detect different scripts and dynamically choses appropriate fonts to match them (on Chrome on Windows 10 the browser would use Times New Roman for the English and use "Microsoft YaHei" for the Chinese). However, the problem itched my brain, so I kept looking for answers in core Koha. In the "koha-conf.xml" file, there is a "ttf" element. Within that XML, there are font elements where font codes get mapped to "ttf" TrueType font files. While it's not the most elegant solution, you can choose to replace these font files, so that "Courier Bold" can actually be something else. Unfortunately, I still had a problem. While the browser could switch fonts, Koha can only use 1 font. Currently, it can't dynamically switch between different fonts. Adding that support would require time and money which I didn't have. Fortunately, Chinese fonts like Noto Sans CJK TC contain not only Chinese but also English! I didn't need Koha to change fonts; I could just use one font! However, the Noto fonts on Debian/Ubuntu come as large "ttc" files which are collections of font files and not as individual "ttf" files. Even downloading particular fonts like Noto Sans CJK TC Bold from Google, they came as "otf" files, which aren't compatible with Koha. After a lot of reading, I downloaded a tool called "FontForge". I could open the "otf" file, "flatten" it, re-encode it using a Unicode option, and then export as a "ttf" file. I replaced the "Courier Bold" file of /usr/share/fonts/truetype/dejavu/DejaVuSansMono-Bold.ttf in Koha with my newly generated Noto ttf file. It printed out the Chinese text, but I noticed instead of spaces in English it was now showing the empty box ▯ again. Ubuntu had a package called "fonts-wqy-zenhei" which provides another Chinese font, so I ran that through the same process and that worked perfectly. Since Noto is a very popular font and I am very stubborn, I decided to keep trying with the Noto. Using FontForge, I was able to manually add in the missing space definition in the font file, so I was able to export a Noto Sans CJK TC Bold "ttf" file, which also worked perfectly. I got Koha to print barcode labels with English and Chinese text! -- If people want to know more specifics, I'm happy to provide more technical/specific information. I figured I'd share this story though, as I imagine that other people must bump into this same problem. I'm personally familiar with the English, French, Chinese, and Korean languages so those are the languages I'm best capable to help with, but I imagine I could still help with any language. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia From cornejo.alvaro at gmail.com Tue Jul 5 13:39:39 2022 From: cornejo.alvaro at gmail.com (Alvaro Cornejo) Date: Mon, 4 Jul 2022 20:39:39 -0500 Subject: [Koha] Rotating IP Address and Koha Logout In-Reply-To: References: Message-ID: Hi Charles IP is assigned by the OS system. In your case, AWS. I assume you will need to ask AWS to assign/configure you a fixed public IP address Regards, Alvaro |----------------------------------------------------------------------------------------| Stay safe / Cuídate/ Reste sécurisé *7* Switch off as you go / Apaga lo que no usas / Débranchez au fur et à mesure. *q *Recycle always / Recicla siempre / Recyclez toujours P Print only if absolutely necessary / Imprime solo si es necesario / Imprimez seulement si nécessaire Le lun. 4 juil. 2022 à 18:21, Charles Kelley a écrit : > Hi, all! > > My library is moving its Koha ILS to an AWS-based server. In > development, it was on a standalone laptop. > > In the testing phase on the AWS server, we have noted that the IP > address for logins changes every thirty seconds and staff are signed out > from Koha. The staff have to sign in anew and refresh. Whatever the staff > were working on -- search, record editing, uploading new records, etc. -- > may or may not survive intact. > > We don't know what causes this, but it's like > > IP 42.0.2.35 > Staff types a search query. > IP 42.0.2.35 > Staff selects Edit Record from dropdown menu. > Sudden change to IP 42.0.2.29 > Record vanishes. > Login screen appears. > New IP 42.0.2.34 > Staff logs in anew > Staff backs up two tabs (or windows) and continues. > New IP 42.02.31 > Repeat of what staff intervention at New IP 42.0.2.34 > > Eventually whatever the staff were working on is accomplished, but > logging in anew and reentering the previous steps so often are a bit > inconvenient, to state the least. > > My IT staff doesn't understand this phenomenon. We checked the system > preferences, but we haven't changed the timeouts since Koha was initially > installed. Has this been reported to the Koha development teams or on this > discussion group before? > > Does anyone have an idea what would be causing this? > > -- > よろしくお願いします。 > > -- Charles. > > Until 2022-07-15: > Charles Kelley, MLS > PSC 704 Box 1029 > APO AP 96338 > +81-80-4356-2178 [JPN cell] > > From 2022-07-18: > Charles Kelley > c/o Bob and Ronni DiGioia > 147 Mitchel Drive > Oakland, MD 21550 USA > +1-301-741-7122 [US cell] > > mnogojazyk at aol.com [h] > cmkelleymls at gmail.com [p] > > linkedin.com/in/cmkelleymls > Meeting Your Information Needs. Virtually. > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From cornejo.alvaro at gmail.com Tue Jul 5 13:44:12 2022 From: cornejo.alvaro at gmail.com (Alvaro Cornejo) Date: Mon, 4 Jul 2022 20:44:12 -0500 Subject: [Koha] Options of "export database" and "export settings" are not available In-Reply-To: References: Message-ID: Hi Victor, You might need to wait 24hrs before the system generates a set if backup files. Regards, Alvaro |----------------------------------------------------------------------------------------| Stay safe / Cuídate/ Reste sécurisé *7* Switch off as you go / Apaga lo que no usas / Débranchez au fur et à mesure. *q *Recycle always / Recicla siempre / Recyclez toujours P Print only if absolutely necessary / Imprime solo si es necesario / Imprimez seulement si nécessaire Le lun. 4 juil. 2022 à 18:42, Victor Barroso Oliveira a écrit : > In Ubuntu 20.5 and Koha 22.05.02.000 > > I enabled in instance-conf.xml > > 1 > 1 > > In Tools --> Export Data > The option tohe option of "export database" and "export settings" are > not available. > > Here's the information that appears: > "Note: This generated file will be very large, and will be generated > daily." > "Unfortunately, there are no backups available." > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From mtj at kohaaloha.com Tue Jul 5 18:22:12 2022 From: mtj at kohaaloha.com (Mason James) Date: Tue, 5 Jul 2022 18:22:12 +1200 Subject: [Koha] =?utf-8?q?Koha_packages_are_available_=F0=9F=8E=81?= Message-ID: <0ccf7d74-fb36-74d1-3d30-40d916126899@kohaaloha.com> kia ora community, the latest Koha packages are available (sorry for the late email) an installation guide is below...   https://wiki.koha-community.org/wiki/Koha_on_Debian cheers, Mason From bc at interleaf.ie Tue Jul 5 18:33:25 2022 From: bc at interleaf.ie (Barry Cannon) Date: Tue, 5 Jul 2022 07:33:25 +0100 Subject: [Koha] Rotating IP Address and Koha Logout In-Reply-To: References: Message-ID: Hi Charles, To temporarily get around this problem you can disable the SessionRestrictionByIP system preference in Koha. This binds the user's session ID to their public IP address. If it changes, the session becomes invalid and Koha will prompt for a new login. The changing IP seems to be unrelated to AWS as they appear to be your ISP addresses. Does the same problem exist outside of your organisation? For example, at home or on a mobile device. If not then the problem is most likely related to an outbound proxy at your end - your IT might look into this. If it still happens elsewhere then perhaps your ISP is doing something with transparent proxying that they might be able to help you with. Regards Barry *Barry Cannon* Technical Director bc at interleaf.ie +353-1-286-5855 <+353%201%20286%205855> Ext: 102 A98 YD30 www.interleaf.ie On Tue, 5 Jul 2022 at 00:21, Charles Kelley wrote: > Hi, all! > > My library is moving its Koha ILS to an AWS-based server. In > development, it was on a standalone laptop. > > In the testing phase on the AWS server, we have noted that the IP > address for logins changes every thirty seconds and staff are signed out > from Koha. The staff have to sign in anew and refresh. Whatever the staff > were working on -- search, record editing, uploading new records, etc. -- > may or may not survive intact. > > We don't know what causes this, but it's like > > IP 42.0.2.35 > Staff types a search query. > IP 42.0.2.35 > Staff selects Edit Record from dropdown menu. > Sudden change to IP 42.0.2.29 > Record vanishes. > Login screen appears. > New IP 42.0.2.34 > Staff logs in anew > Staff backs up two tabs (or windows) and continues. > New IP 42.02.31 > Repeat of what staff intervention at New IP 42.0.2.34 > > Eventually whatever the staff were working on is accomplished, but > logging in anew and reentering the previous steps so often are a bit > inconvenient, to state the least. > > My IT staff doesn't understand this phenomenon. We checked the system > preferences, but we haven't changed the timeouts since Koha was initially > installed. Has this been reported to the Koha development teams or on this > discussion group before? > > Does anyone have an idea what would be causing this? > > -- > よろしくお願いします。 > > -- Charles. > > Until 2022-07-15: > Charles Kelley, MLS > PSC 704 Box 1029 > APO AP 96338 > +81-80-4356-2178 [JPN cell] > > From 2022-07-18: > Charles Kelley > c/o Bob and Ronni DiGioia > 147 Mitchel Drive > Oakland, MD 21550 USA > +1-301-741-7122 [US cell] > > mnogojazyk at aol.com [h] > cmkelleymls at gmail.com [p] > > linkedin.com/in/cmkelleymls > Meeting Your Information Needs. Virtually. > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From eberhard at pietzsch.org Tue Jul 5 19:35:53 2022 From: eberhard at pietzsch.org (Dr. Eberhard Pietzsch) Date: Tue, 5 Jul 2022 09:35:53 +0200 (CEST) Subject: [Koha] Error in Koha 22.05? Message-ID: <542482724.267230.1657006553609@office.mailbox.org> Hello, I would like to point out a bug in Koha after the update to 22.05. Koha is also included in the package management of Ubuntu 22.04 LTS and can be updated together with Ubuntu. I had skipped the short time preceding Koha update because of errors. However, the current update to 22.05 apparently also contains bugs: The structure of the borrowers table seems to have been changed compared to previous versions. Existing user data are not correctly loaded into the new structured table with the update, so that no login, e.g. as superlibrarian, is possible anymore. Possibly this phenomenon is caused by the skipped update to the previous version? Many greetings Eberhard Pietzsch From fmartinez at uns.edu.ar Tue Jul 5 22:21:05 2022 From: fmartinez at uns.edu.ar (Fernando A. Martinez) Date: Tue, 5 Jul 2022 07:21:05 -0300 Subject: [Koha] Error in Koha 22.05? In-Reply-To: <542482724.267230.1657006553609@office.mailbox.org> References: <542482724.267230.1657006553609@office.mailbox.org> Message-ID: <48f68a85-5c1f-58a7-f37b-a608135b3c3c@uns.edu.ar> Hi, I have the same problem. Corrupted tables: borrowers and deletedborrowers. Update: Koha 22.05.02 over Koha 21.11.09 Ubuntu 20.04 LTS MySQL version 8.0.29 Regards Fernando A. Martinez On 5/7/22 04:35, Dr. Eberhard Pietzsch wrote: > Hello, > > I would like to point out a bug in Koha after the update to 22.05. > > Koha is also included in the package management of Ubuntu 22.04 LTS and can be updated together with Ubuntu. I had skipped the short time preceding Koha update because of errors. However, the current update to 22.05 apparently also contains bugs: > > The structure of the borrowers table seems to have been changed compared to previous versions. Existing user data are not correctly loaded into the new structured table with the update, so that no login, e.g. as superlibrarian, is possible anymore. > > Possibly this phenomenon is caused by the skipped update to the previous version? > > Many greetings > Eberhard Pietzsch > _______________________________________________ > > Koha mailing listhttp://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha From katrin.fischer.83 at web.de Tue Jul 5 22:33:03 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Tue, 5 Jul 2022 12:33:03 +0200 Subject: [Koha] Error in Koha 22.05? In-Reply-To: <48f68a85-5c1f-58a7-f37b-a608135b3c3c@uns.edu.ar> References: <542482724.267230.1657006553609@office.mailbox.org> <48f68a85-5c1f-58a7-f37b-a608135b3c3c@uns.edu.ar> Message-ID: Hi, could you please post more information about the issue? What error message are you seeing? Can you access the tables with SQL? Is this the error maybe: DBI Exception: DBD::mysql::db do failed: Row size too large. Then have a look at: *Bug 28267* - Koha-common package upgrade problem from 20.05.xx to 20.11.04-1 Hope this helps, Katrin On 05.07.22 12:21, Fernando A. Martinez wrote: > Hi, > > I have the same problem. Corrupted tables: borrowers and > deletedborrowers. Update: Koha 22.05.02 over Koha 21.11.09 Ubuntu > 20.04 LTS MySQL version 8.0.29 > > Regards > > Fernando A. Martinez > > On 5/7/22 04:35, Dr. Eberhard Pietzsch wrote: >> Hello, >> >> I would like to point out a bug in Koha after the update to 22.05. >> >> Koha is also included in the package management of Ubuntu 22.04 LTS >> and can be updated together with Ubuntu. I had skipped the short time >> preceding Koha update because of errors. However, the current update >> to 22.05 apparently also contains bugs: >> >> The structure of the borrowers table seems to have been changed >> compared to previous versions. Existing user data are not correctly >> loaded into the new structured table with the update, so that no >> login, e.g. as superlibrarian, is possible anymore. >> >> Possibly this phenomenon is caused by the skipped update to the >> previous version? >> >> Many greetings >> Eberhard Pietzsch >> _______________________________________________ >> >> Koha mailing listhttp://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From fmartinez at uns.edu.ar Tue Jul 5 23:04:46 2022 From: fmartinez at uns.edu.ar (Fernando A. Martinez) Date: Tue, 5 Jul 2022 08:04:46 -0300 Subject: [Koha] Error in Koha 22.05? In-Reply-To: References: <542482724.267230.1657006553609@office.mailbox.org> <48f68a85-5c1f-58a7-f37b-a608135b3c3c@uns.edu.ar> Message-ID: <6ec587b7-2510-31b7-b656-936be4788475@uns.edu.ar> Hi, The update completes without errors (log attached). Then I can't log into the system. (mysqlcheck log attached) Regards Fernando A. Martinez On 5/7/22 07:33, Katrin Fischer wrote: > Hi, > > could you please post more information about the issue? What error > message are you seeing? Can you access the tables with SQL? > > Is this the error maybe: DBI Exception: DBD::mysql::db do failed: Row > size too large. > > Then have a look at: *Bug 28267* > - > Koha-common package upgrade problem from 20.05.xx to 20.11.04-1 > > Hope this helps, > > Katrin > > On 05.07.22 12:21, Fernando A. Martinez wrote: >> Hi, >> >> I have the same problem. Corrupted tables: borrowers and >> deletedborrowers. Update: Koha 22.05.02 over Koha 21.11.09 Ubuntu >> 20.04 LTS MySQL version 8.0.29 >> >> Regards >> >> Fernando A. Martinez >> >> On 5/7/22 04:35, Dr. Eberhard Pietzsch wrote: >>> Hello, >>> >>> I would like to point out a bug in Koha after the update to 22.05. >>> >>> Koha is also included in the package management of Ubuntu 22.04 LTS >>> and can be updated together with Ubuntu. I had skipped the short time >>> preceding Koha update because of errors. However, the current update >>> to 22.05 apparently also contains bugs: >>> >>> The structure of the borrowers table seems to have been changed >>> compared to previous versions. Existing user data are not correctly >>> loaded into the new structured table with the update, so that no >>> login, e.g. as superlibrarian, is possible anymore. >>> >>> Possibly this phenomenon is caused by the skipped update to the >>> previous version? >>> >>> Many greetings >>> Eberhard Pietzsch >>> _______________________________________________ >>> >>> Koha mailing listhttp://koha-community.org >>> Koha at lists.katipo.co.nz >>> Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From fmartinez at uns.edu.ar Tue Jul 5 23:10:07 2022 From: fmartinez at uns.edu.ar (Fernando A. Martinez) Date: Tue, 5 Jul 2022 08:10:07 -0300 Subject: [Koha] Error in Koha 22.05? In-Reply-To: <6ec587b7-2510-31b7-b656-936be4788475@uns.edu.ar> References: <542482724.267230.1657006553609@office.mailbox.org> <48f68a85-5c1f-58a7-f37b-a608135b3c3c@uns.edu.ar> <6ec587b7-2510-31b7-b656-936be4788475@uns.edu.ar> Message-ID: <18f252bc-c6da-cbcd-2a9b-b76601509518@uns.edu.ar> root at dev-bib:~# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required:   libcrypt-openssl-bignum-perl libcrypt-openssl-random-perl libcrypt-openssl-rsa-perl libdata-validate-domain-perl libdata-validate-ip-perl libdbd-sqlite2-perl libmath-base85-perl   libnet-domain-tld-perl libnet-ipv6addr-perl libnetaddr-ip-perl libnetwork-ipv4addr-perl libtext-markdown-perl Use 'apt autoremove' to remove them. The following NEW packages will be installed:   libauth-googleauth-perl libconvert-base32-perl libcrypt-cbc-perl libcrypt-rijndael-perl libdbd-sqlite3-perl libio-socket-ip-perl libmath-random-mt-perl The following packages have been kept back:   libmojolicious-perl The following packages will be upgraded:   koha-common libjson-validator-perl libmojo-jwt-perl libmojolicious-plugin-openapi-perl libtemplate-plugin-gettext-perl 5 upgraded, 7 newly installed, 0 to remove and 1 not upgraded. Need to get 46.1 MB of archives. After this operation, 17.0 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://archive.ubuntu.com/ubuntu focal/universe amd64 libconvert-base32-perl all 0.06-1 [6546 B] Get:2 http://archive.ubuntu.com/ubuntu focal/universe amd64 libmath-random-mt-perl amd64 1.17-1build5 [13.1 kB] Get:3 http://archive.ubuntu.com/ubuntu focal/universe amd64 libcrypt-rijndael-perl amd64 1.14-1build1 [17.3 kB] Get:4 http://archive.ubuntu.com/ubuntu focal/universe amd64 libcrypt-cbc-perl all 2.33-2 [23.5 kB] Get:5 http://archive.ubuntu.com/ubuntu focal/universe amd64 libdbd-sqlite3-perl amd64 1.64-1build1 [154 kB] Get:6 http://debian.koha-community.org/koha 22.05/main amd64 libauth-googleauth-perl all 1.03-1 [13.1 kB] Get:7 http://debian.koha-community.org/koha 22.05/main amd64 libjson-validator-perl all 5.99+really5.08-koha1 [98.2 kB] Get:8 http://debian.koha-community.org/koha 22.05/main amd64 libmojo-jwt-perl all 0.09-1-koha1 [12.1 kB] Get:9 http://debian.koha-community.org/koha 22.05/main amd64 libmojolicious-plugin-openapi-perl all 5.99+really5.05-koha1 [67.4 kB] Get:10 http://debian.koha-community.org/koha 22.05/main amd64 libtemplate-plugin-gettext-perl all 0.6-1~koha2 [22.8 kB] Get:11 http://debian.koha-community.org/koha 22.05/main amd64 koha-common all 22.05.02-1 [45.6 MB] Get:12 http://debian.koha-community.org/koha 22.05/main amd64 libio-socket-ip-perl all 0.41-1 [30.5 kB] Fetched 46.1 MB in 1min 59s (386 kB/s) Preconfiguring packages ... Selecting previously unselected package libconvert-base32-perl. (Reading database ... 92638 files and directories currently installed.) Preparing to unpack .../00-libconvert-base32-perl_0.06-1_all.deb ... Unpacking libconvert-base32-perl (0.06-1) ... Selecting previously unselected package libmath-random-mt-perl. Preparing to unpack .../01-libmath-random-mt-perl_1.17-1build5_amd64.deb ... Unpacking libmath-random-mt-perl (1.17-1build5) ... Selecting previously unselected package libauth-googleauth-perl. Preparing to unpack .../02-libauth-googleauth-perl_1.03-1_all.deb ... Unpacking libauth-googleauth-perl (1.03-1) ... Selecting previously unselected package libcrypt-rijndael-perl. Preparing to unpack .../03-libcrypt-rijndael-perl_1.14-1build1_amd64.deb ... Unpacking libcrypt-rijndael-perl (1.14-1build1) ... Selecting previously unselected package libcrypt-cbc-perl. Preparing to unpack .../04-libcrypt-cbc-perl_2.33-2_all.deb ... Unpacking libcrypt-cbc-perl (2.33-2) ... Selecting previously unselected package libdbd-sqlite3-perl:amd64. Preparing to unpack .../05-libdbd-sqlite3-perl_1.64-1build1_amd64.deb ... Unpacking libdbd-sqlite3-perl:amd64 (1.64-1build1) ... Preparing to unpack .../06-libjson-validator-perl_5.99+really5.08-koha1_all.deb ... Unpacking libjson-validator-perl (5.99+really5.08-koha1) over (5.99+really3.14-koha1) ... Preparing to unpack .../07-libmojo-jwt-perl_0.09-1-koha1_all.deb ... Unpacking libmojo-jwt-perl (0.09-1-koha1) over (0.08-1) ... Preparing to unpack .../08-libmojolicious-plugin-openapi-perl_5.99+really5.05-koha1_all.deb ... Unpacking libmojolicious-plugin-openapi-perl (5.99+really5.05-koha1) over (5.99+really2.16-koha1) ... Preparing to unpack .../09-libtemplate-plugin-gettext-perl_0.6-1~koha2_all.deb ... Unpacking libtemplate-plugin-gettext-perl (0.6-1~koha2) over (0.6-1~koha1) ... Preparing to unpack .../10-koha-common_22.05.02-1_all.deb ... Unpacking koha-common (22.05.02-1) over (21.11.09-3) ... Selecting previously unselected package libio-socket-ip-perl. Preparing to unpack .../11-libio-socket-ip-perl_0.41-1_all.deb ... Unpacking libio-socket-ip-perl (0.41-1) ... Setting up libio-socket-ip-perl (0.41-1) ... Setting up libcrypt-rijndael-perl (1.14-1build1) ... Setting up libjson-validator-perl (5.99+really5.08-koha1) ... Setting up libmath-random-mt-perl (1.17-1build5) ... Setting up libcrypt-cbc-perl (2.33-2) ... Setting up libmojolicious-plugin-openapi-perl (5.99+really5.05-koha1) ... Setting up libdbd-sqlite3-perl:amd64 (1.64-1build1) ... Setting up libtemplate-plugin-gettext-perl (0.6-1~koha2) ... Setting up libmojo-jwt-perl (0.09-1-koha1) ... Setting up libconvert-base32-perl (0.06-1) ... Setting up libauth-googleauth-perl (1.03-1) ... Setting up koha-common (22.05.02-1) ... Installing new version of config file /etc/cron.daily/koha-common ... Installing new version of config file /etc/init.d/koha-common ... Installing new version of config file /etc/koha/SIPconfig.xml ... Installing new version of config file /etc/koha/koha-conf-site.xml.in ... Installing new version of config file /etc/koha/zebradb/marc_defs/marc21/biblios/biblio-zebra-indexdefs.xsl ... Upgrading database schema for dev-bib Upgrade to 21.12.00.000  [07:52:52]: Increase DBRev for 21.12     📜 All that is gold does not glitter,     📜 Not all those who wander are lost;     📜 The old that is strong does not wither,     📜 Deep roots are not reached by the frost. Upgrade to 21.12.00.001  [07:52:52]: Bug 29586 - Add Hold Reminder messaging preference if missing Upgrade to 21.12.00.002  [07:52:53]: Bug 13188 - Allow configuration of required fields when a patron is editing their information via the OPAC     Added new system preference 'PatronSelfModificationMandatoryField' with value '' Upgrade to 21.12.00.003  [07:52:53]: Bug 29457 - Fee Cancellation records the wrong manager_id     WARNING: You may have some incorrect manager_id's recorded against account cancellation lines, please see bugzilla for details.     NOTE: You may already have this bugfix applied at an earlier upgrade. Upgrade to 21.12.00.004  [07:52:53]: Bug 26296 - Replace comma with pipe in OPACSuggestion field preferences Upgrade to 21.12.00.005  [07:52:53]: Bug 29778 - Delete orphan additional contents Upgrade to 21.12.00.006  [07:52:53]: Bug 29557 - Add auto_account_expired to AUTO_RENEWALS notice     Please update your AUTO_RENEWALS notice manually if you have changed or translated it Upgrade to 21.12.00.007  [07:52:53]: Bug 20076 - Add system preference EmailOverduesNoEmail Upgrade to 21.12.00.008  [07:52:53]: Bug 29495 - Drop issue_id constraint from return_claims table Upgrade to 21.12.00.009  [07:52:54]: Bug 29336 - Resize authorised value category fields to 32 chars Upgrade to 21.12.00.010  [07:52:55]: Bug 21729 - Add new column reserves.patron_expiration_date Upgrade to 21.12.00.011  [07:52:55]: Bug 27946 - Add article request fees Upgrade to 21.12.00.012  [07:52:55]: Bug 24220 - Move OpacMoreSearches to additional contents     No OpacMoreSearches preference found. Value was empty or update has already been run. Upgrade to 21.12.00.013  [07:52:56]: Bug 29605 - Resync DB structure for existing installations     Ensure NOT NULL on account_offsets.type     Ensure additional_contents.code is VARCHAR(100)     Ensure additional_contents.lang is VARCHAR(50)     Ensure NOT NULL on search_marc_map.marc_type     Ensure branchtransfers.cancellation_reason enum values are uppercase Upgrade to 21.12.00.014  [07:52:56]: Bug 29596 - Add Yiddish language Upgrade to 21.12.00.015  [07:52:56]: Bug 29943 - Fix typo in NOTIFY_MANAGER notice Upgrade to 21.12.00.016  [07:52:58]: Bug 30060 - Update user_permissions to add primary key and remove null option from code column     Removed any duplicate rows     Added a primary key on user_permissions on borrowernumber, module_bit, code Upgrade to 21.12.00.017  [07:52:58]: Bug 30128 - Change language_subtag_registry.description to varchar(255) Upgrade to 21.12.00.018  [07:52:58]: Bug 19532 - Add Recalls Upgrade to 21.12.00.019  [07:52:58]: Bug 27812 - Remove the ability to transmit a patron's plain text password over email     The notice template ACCTDETAILS no longer has access to the patron's plain text password. Please update the language of your ACCTDETAILS as needed. Upgrade to 21.12.00.020  [07:52:58]: Bug 24221 - Move OpacMySummaryNote to additional contents     No OpacMySummaryNote preference found. Value was empty or update has already been run. Upgrade to 21.12.00.021  [07:52:58]: Bug 30063 - Fix DefaultPatronSearchFields order Upgrade to 21.12.00.022  [07:52:58]: Bug 11083 - Add syspref AuthorityXSLTResultsDisplay Upgrade to 21.12.00.023  [07:52:58]: Bug 20517 - Add SIP2SortBinMapping system preference Upgrade to 21.12.00.024  [07:52:58]: Bug 20398 - Add system preference StaffHighlightedWords Upgrade to 21.12.00.025  [07:52:58]: Bug 29990 - Add new system preference ShowHeadingUse Upgrade to 21.12.00.026  [07:52:58]: Bug 17018 - Split AdvancedSearchTypes for staff and OPAC Upgrade to 21.12.00.027  [07:52:59]: Bug 26346 - Add allow_change_from_staff to virtualshelves table Upgrade to 21.12.00.028  [07:52:59]: Bug 16258 - A preference to enabled/disable edifact Upgrade to 21.12.00.029  [07:52:59]: Bug 30130 - A standard to edi_account Upgrade to 21.12.00.030  [07:52:59]: Bug 30135 - Add EdifactLSQ mapping system preference Upgrade to 21.12.00.031  [07:52:59]: Bug 30481 - DB schema sync for deleteditems Upgrade to 21.12.00.032  [07:52:59]: Bug 30498 - Correct enum search_field.type Upgrade to 21.12.00.033  [07:52:59]: Bug 27783 - Add background_jobs.queue     Added background_jobs.queue Upgrade to 21.12.00.034  [07:52:59]: Bug 30237 - Replace ACCDETAILS notice with WELCOME notice Upgrade to 21.12.00.035  [07:52:59]: Bug 30226 - Add the system preference AllowSetAutomaticRenewal Upgrade to 21.12.00.036  [07:53:00]: Bug 28786 - Add syspref TwoFactorAuthentication, fields secret and auth_method Upgrade to 21.12.00.037  [07:53:00]: Bug 27253 - Fix definition of borrowers.updated_on and deletedborrowers.updated_on     Updated all NULL values of borrowers.updated_on to GREATEST(date_renewed, dateenrolled, lastseen): 0 rows updated     Updated all NULL values of borrowers.updated_on to GREATEST(date_renewed, dateenrolled, lastseen): 0 rows updated     Fixed definition of borrowers.updated_on     Fixed definition of deletedborrowers.updated_on Upgrade to 21.12.00.038  [07:53:00]: Bug 29648 - Move NumSavedReports to table settings and allow tables_settings.default_display_length to be NULL     NumSavedReports value '20' moved to table settings Upgrade to 21.12.00.039  [07:53:00]: Bug 29092 - Add timestamp to account-fines table column settings Upgrade to 21.12.00.040  [07:53:00]: Bug 30565 - Update table stockrotationrotas Upgrade to 21.12.00.041  [07:53:00]: Bug 30449 - Check borrower_attribute_types FK constraint Upgrade to 21.12.00.042  [07:53:00]: Bug 30572 - Adjust search_marc_to_field.sort Upgrade to 21.12.00.043  [07:53:00]: Bug 30108 - Add preference OPACMandatoryHoldDates Upgrade to 21.12.00.044  [07:53:00]: Bug 29894 - Add 2FA (de)enabling notices Upgrade to 21.12.00.045  [07:53:00]: Bug 14242 - Add OPACSuggestionAutoFill system preference Upgrade to 21.12.00.046  [07:53:00]: Bug 22785 - Add chosen column to import_record_matches     chosen column added to import_record_matches Upgrade to 21.12.00.047  [07:53:00]: Bug 28138 - Add system preference RequirePaymentType Upgrade to 21.12.00.048  [07:53:01]: Bug 30291 - Renaming recalls table columns Upgrade to 21.12.00.049  [07:53:01]: Bug 30563 - Add system preference RequireCashRegister Upgrade to 21.12.00.050  [07:53:01]: Bug 29924 - Add password expiration     Added password_expiry_days to categories     Added password_expiration_date field to borrowers     Added password_expiration_date field to borrowers Upgrade to 21.12.00.051  [07:53:01]: Bug 29925 - Add password reset option Upgrade to 21.12.00.052  [07:53:01]: Bug 30290 - Modify AR notices, include TOC line Upgrade to 21.12.00.053  [07:53:01]: Bug 30611 - Add STAFF_PASSWORD_RESET notice Upgrade to 21.12.00.054  [07:53:02]: Bug 23352 - Adding new column 'subscription.ccode' Upgrade to 21.12.00.055  [07:53:02]: Bug 13412 - Add GenerateAuthorityField667 and GenerateAuthorityField670 system preferences Upgrade to 21.12.00.056  [07:53:02]: Bug 30728 - Allow opting out of real-time holds queue updating possible Upgrade to 21.12.00.057  [07:53:02]: Bug 30852 - Add index to article_requests.debit_id Upgrade to 22.05.00.000  [07:53:02]: Koha 22.05.00 release Upgrade to 22.05.00.001  [07:53:02]: Bug 23659 - Add DefaultHoldPickupLocation syspref     Added DefaultHoldPickupLocation syspref Upgrade to 22.05.02.000  [07:53:02]: Koha 22.05.02 release DEV atomic update /usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/bug_30899.pl [07:53:02]: Bug 30899 - Check borrower_attribute_types FK constraint (30449 follow-up) Connection to the memcached servers '__MEMCACHED_SERVERS__' failed. Are the unix socket permissions set properly? Is the host reachable? If you ignore this warning, you will face performance issues Updated the es-ES translations. Enabling plugins on node rabbit at dev-bib: rabbitmq_stomp The following plugins have been configured:   rabbitmq_stomp Applying plugin configuration to rabbit at dev-bib... Plugin configuration unchanged. Failed to enable unit: Unit /run/systemd/generator.late/koha-common.service is transient or generated. Processing triggers for man-db (2.9.1-1) ... Processing triggers for systemd (245.4-4ubuntu3.17) ... ============================================= root at dev-bib:~# mysqlcheck -p koha_test borrowers Enter password: koha_test.borrowers Warning  : InnoDB: The B-tree of index PRIMARY is corrupted. Warning  : InnoDB: Index 'cardnumber' contains 1594 entries, should be 18446744073709551615. Warning  : InnoDB: Index 'userid' contains 1594 entries, should be 18446744073709551615. Warning  : InnoDB: Index 'categorycode' contains 1594 entries, should be 18446744073709551615. Warning  : InnoDB: Index 'branchcode' contains 1594 entries, should be 18446744073709551615. Warning  : InnoDB: Index 'surname_idx' contains 1594 entries, should be 18446744073709551615. Warning  : InnoDB: Index 'firstname_idx' contains 1594 entries, should be 18446744073709551615. Warning  : InnoDB: Index 'othernames_idx' contains 1594 entries, should be 18446744073709551615. Warning  : InnoDB: Index 'sms_provider_id' contains 1594 entries, should be 18446744073709551615. error    : Corrupt root at dev-bib:~# mysqlcheck -p koha_test deletedborrowers Enter password: koha_test.deletedborrowers Warning  : InnoDB: The B-tree of index GEN_CLUST_INDEX is corrupted. Warning  : InnoDB: Index 'borrowernumber' contains 200 entries, should be 18446744073709551615. Warning  : InnoDB: Index 'cardnumber' contains 200 entries, should be 18446744073709551615. Warning  : InnoDB: Index 'sms_provider_id' contains 200 entries, should be 18446744073709551615. error    : Corrupt root at dev-bib:~# Fernando A. Martinez On 5/7/22 08:04, Fernando A. Martinez wrote: > Hi, > > The update completes without errors (log attached). Then I can't log > into the system. (mysqlcheck log attached) Regards > > Fernando A. Martinez > > On 5/7/22 07:33, Katrin Fischer wrote: >> Hi, >> >> could you please post more information about the issue? What error >> message are you seeing? Can you access the tables with SQL? >> >> Is this the error maybe: DBI Exception: DBD::mysql::db do failed: Row >> size too large. >> >> Then have a look at: *Bug 28267* >> - >> Koha-common package upgrade problem from 20.05.xx to 20.11.04-1 >> >> Hope this helps, >> >> Katrin >> >> On 05.07.22 12:21, Fernando A. Martinez wrote: >>> Hi, >>> >>> I have the same problem. Corrupted tables: borrowers and >>> deletedborrowers. Update: Koha 22.05.02 over Koha 21.11.09 Ubuntu >>> 20.04 LTS MySQL version 8.0.29 >>> >>> Regards >>> >>> Fernando A. Martinez >>> >>> On 5/7/22 04:35, Dr. Eberhard Pietzsch wrote: >>>> Hello, >>>> >>>> I would like to point out a bug in Koha after the update to 22.05. >>>> >>>> Koha is also included in the package management of Ubuntu 22.04 LTS >>>> and can be updated together with Ubuntu. I had skipped the short time >>>> preceding Koha update because of errors. However, the current update >>>> to 22.05 apparently also contains bugs: >>>> >>>> The structure of the borrowers table seems to have been changed >>>> compared to previous versions. Existing user data are not correctly >>>> loaded into the new structured table with the update, so that no >>>> login, e.g. as superlibrarian, is possible anymore. >>>> >>>> Possibly this phenomenon is caused by the skipped update to the >>>> previous version? >>>> >>>> Many greetings >>>> Eberhard Pietzsch >>>> _______________________________________________ >>>> >>>> Koha mailing listhttp://koha-community.org >>>> Koha at lists.katipo.co.nz >>>> Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha >>> _______________________________________________ >>> >>> Koha mailing list http://koha-community.org >>> Koha at lists.katipo.co.nz >>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list  http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From eberhard at pietzsch.org Wed Jul 6 00:19:35 2022 From: eberhard at pietzsch.org (Dr. Eberhard Pietzsch) Date: Tue, 5 Jul 2022 14:19:35 +0200 (CEST) Subject: [Koha] Error in Koha 22.05? In-Reply-To: References: <542482724.267230.1657006553609@office.mailbox.org> <48f68a85-5c1f-58a7-f37b-a608135b3c3c@uns.edu.ar> Message-ID: <1344101688.297543.1657023575877@office.mailbox.org> Attached you see an dump of the borrowers table. You can see at the insert statement that the contents are shifted by a few bytes. Some attributes are new compared with earliver versions of Koha. (I have edited the encrypted password) Eberhard > Katrin Fischer hat am 05.07.2022 12:33 CEST geschrieben: > > > Hi, > > could you please post more information about the issue? What error > message are you seeing? Can you access the tables with SQL? > > Is this the error maybe: DBI Exception: DBD::mysql::db do failed: Row > size too large. > > Then have a look at: *Bug 28267* > - > Koha-common package upgrade problem from 20.05.xx to 20.11.04-1 > > Hope this helps, > > Katrin > > On 05.07.22 12:21, Fernando A. Martinez wrote: > > Hi, > > > > I have the same problem. Corrupted tables: borrowers and > > deletedborrowers. Update: Koha 22.05.02 over Koha 21.11.09 Ubuntu > > 20.04 LTS MySQL version 8.0.29 > > > > Regards > > > > Fernando A. Martinez > > > > On 5/7/22 04:35, Dr. Eberhard Pietzsch wrote: > >> Hello, > >> > >> I would like to point out a bug in Koha after the update to 22.05. > >> > >> Koha is also included in the package management of Ubuntu 22.04 LTS > >> and can be updated together with Ubuntu. I had skipped the short time > >> preceding Koha update because of errors. However, the current update > >> to 22.05 apparently also contains bugs: > >> > >> The structure of the borrowers table seems to have been changed > >> compared to previous versions. Existing user data are not correctly > >> loaded into the new structured table with the update, so that no > >> login, e.g. as superlibrarian, is possible anymore. > >> > >> Possibly this phenomenon is caused by the skipped update to the > >> previous version? > >> > >> Many greetings > >> Eberhard Pietzsch > >> _______________________________________________ > >> > >> Koha mailing listhttp://koha-community.org > >> Koha at lists.katipo.co.nz > >> Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From secretary at koha-us.org Wed Jul 6 04:16:23 2022 From: secretary at koha-us.org (Jennifer Marlatt) Date: Tue, 5 Jul 2022 09:16:23 -0700 Subject: [Koha] koha-US Board Meeting reminder: Wednesday, July 6, 2022 Message-ID: The next koha-US Board Meeting is Wednesday, July 6, 2022. When: 8:30a PT / 11:30a ET (time converter ) Where: https://us02web.zoom.us/j/293750042?pwd=SGQzS2pmU3prNFhYRHNaeTFhOHN4QT09 Agenda: https://docs.google.com/document/d/1yxDRnf-JBGe9a6-EbbO4M3Q2zSaHj1OscKxkAl1Yri0/edit?usp=sharing If you have additional topics for the agenda, please send them to secretary at 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 at koha-us.org From c.s.hayward at protonmail.com Wed Jul 6 06:02:30 2022 From: c.s.hayward at protonmail.com (C.S. Hayward) Date: Tue, 05 Jul 2022 18:02:30 +0000 Subject: [Koha] Migrating from one server to another In-Reply-To: <01000181c8b482ca-9bef45b4-aaf6-4953-bc28-60a38a5eae55-000000@email.amazonses.com> References: <7e5265ff-7f93-910a-8774-d2a07e0e5d15@kohasupport.com> <01000181c8b13147-6bd33035-915f-44df-8da3-c7cf945aadc6-000000@email.amazonses.com> <6ddbbc0d-bfa8-3d69-8eb5-1de889d6209a@kohasupport.com> <01000181c8b482ca-9bef45b4-aaf6-4953-bc28-60a38a5eae55-000000@email.amazonses.com> Message-ID: Thank you. I had earlier followed the instructions at http://kohageek.pbworks.com/w/page/60452540/How%20to%20move%20your%20koha%20database%20to%20newly%20installed%20Koha and got an unbranded internal server error at https://library.cjshayward.com and a Koha branded internal server error at https://library-intra.cjshayward.com. Since then (this may have been the equivalent of asking for my tea with cream and lemon) I ran the script you mentioned and https://library.cjshayward.com redirects to https://library.cjshayward.com/cgi-bin/koha/maintenance.pl. A few questions: 1: Have I messed up the system by trying to migrate both ways? 2: Would it likely be less energy to fix the system I have or start over? Would it make sense to do an aptitude purge for koha and then reinstall, or should I be trying a less surgical approach. 3: How can I get useful diagnostics? When I got the earlier 500 error, /var/log/apache2/error.log wasn't getting anything on additional attempted page load. I now have on the system the koha.sql created at http://kohageek.pbworks.com/w/page/60452540/How%20to%20move%20your%20koha%20database%20to%20newly%20installed%20Koha. Thanks, Br. C.S. Hayward, https://c-s-hayward.com ------- Original Message ------- On Monday, July 4th, 2022 at 6:14 AM, Lennon Mazonde wrote: > Forgot to add the link to the GitHub repo, here it is - https://github.com/grandmaestr/koha-scripts. > > Best regards, > > ### Lennon Mazonde > > KohaSupport > > > > > > > > [blob:https://mail.proton.me/e8ef4ba0-e203-49f9-877f-0b7a940b8f83] > > lennon at kohasupport.com > > [blob:https://mail.proton.me/62ee6d68-51dc-4913-952e-6337c32582bb] > > www.kohasupport.com > > [blob:https://mail.proton.me/9edf60da-ed68-47c1-8229-b123f31dd6a0] > > 651 North Broad Street, Middletown, DE 19709, USA > > > > The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. > > On 7/4/22 12:11 PM, Lennon Mazonde wrote: > > > Hi, > > > > > > > > > > I have a repo on GitHub with scripts that might be able to help you. Have a look at the 'koha-migrate' script - I originally wrote it to migrate several Koha MariaDB databases running on a Ubuntu (20.04LTS) server to Amazon Aurora MySQL on AWS but it should work for other use-cases. There are several other scripts there you might find useful as well. As always, test them in a dev environment before running them on your production server :) > > > > > > > > > > If anyone else is interested and would like to contribute to the project, please let me know! > > > > > > > > Best regards, > > > > > > > > > > > > > > Lennon Mazonde > > > > KohaSupport > > > > > > > > > > > > > > > > > > > > lennon at kohasupport.com > > > > www.kohasupport.com > > > > 651 North Broad Street, Middletown, DE 19709, USA > > > > > > > > The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. > > > > > > > > On 7/1/22 5:17 PM, C.S. Hayward wrote: > > > > > > > > (Note: I am not using "migrate" as it is usually used today, meaning switching from ABC software to DEF. I'm referring to relocating an installation's data.) > > > > I would like to migrate my data from one Koha installation on one server to another installation on another server. Both use MariaDB. > > > > Where are instructions suitable to migrating data between two different servers? > > > > > > Thanks, > > Br. C.S. Hayward > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From Heather_Hernandez at nps.gov Wed Jul 6 08:11:06 2022 From: Heather_Hernandez at nps.gov (Hernandez, Heather H) Date: Tue, 5 Jul 2022 20:11:06 +0000 Subject: [Koha] Koha pluging for linking fields and RDA -76X-78X fields In-Reply-To: References: <1315412074.11622.1655212554978.JavaMail.zimbra@ign.gob.ar> <792263670.31439.1655409045724.JavaMail.zimbra@ign.gob.ar> Message-ID: Hello! Apologies for my late reply--we had a family emergency, but all is now well! IMO, the relator codes in $4 are efficient but not as human-friendly as the terms in $e--some libraries use both. (We use only $e terms in new cataloging.) I like the relator terms--Koha displays them well. And Koha links well to whatever number you use in the 001. You're right--we're not using the work-relationship-designators (in RDA Appendix J) because we find the relationships supplied by the indicators in the 78X linking entry fields sufficient--typing in the relationship designators is, well, extra typing. ::grin:: There are relator codes listed on the MARC21 page under "Relators" at MARC Code List for Relators (Network Development and MARC Standards Office, Library of Congress) (loc.gov) (I'm sorry, but I don't know where non-English ones may be.) Since they're MARC21 codes, they're not listed in the RDA Toolkit. And, yes--it can get confusing about what's where! And, Katrin, about Bug 29733, using a linker in Koha similar to the authority linker is an intriguing idea, but it is not what other ILS's and bibliographic utilities do as far as I know (which is limited!)--at the moment, we are able to import our records into Koha from OCLC without change, and the 78X linking works immediately, because Koha linking uses the exact same data in 78X linking entry fields as OCLC. Having to wait, e.g., for a script to one to add something like a $9 field to achieve the linking would not be ideal for us. Also, authority records change constantly--references are added and/or deleted, language and terminology changes, people die and death date is added, etc., etc., etc., so the headings used in the bibliographic records need to change as well, and there are many headings in each bibliographic record, so having Koha create the linkage via a script is worth waiting for the script to run. The linking in 78X linking entry fields must necessarily be thought about by the cataloger(s), and systems with advanced functionality create it automatically (e.g., in OCLC one simply puts the record number into the appropriate MARC field and runs a macro and the rest of the field is populated from the source bib record--I have yet to see if such a macro can work in Koha, but want to!). The relationships have to be thought about by the cataloger, and aren't usually that many, so are easily put in by the cataloger, so at least in my opinion, having Koha create yet another linkage via script is added & not really necessary. But this is only my opinion, based on a very particular workflow--it may serve the vast majority of the Koha community! And a syspref to turn it on or off is always possible. Cheerio! --h2 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ms. Heather Hernandez (she, her, hers) Technical Services Librarian Library catalog: https://keys.bywatersolutions.com/ San Francisco Maritime National Historical Park Research Center 2 Marina Blvd., Bldg. E, 3rd floor, San Francisco, CA 94123-1284 415-561-7032 (office generally Tu-W & F, telecommuting M&Th) heather_hernandez at nps.gov From Heather_Hernandez at nps.gov Wed Jul 6 08:16:08 2022 From: Heather_Hernandez at nps.gov (Hernandez, Heather H) Date: Tue, 5 Jul 2022 20:16:08 +0000 Subject: [Koha] CatalogingSIG July 7 Message-ID: Hi, all! The next Koha-US Cataloging Special Interest Group ("CatSIG") meeting is this Thursday, July 7, 2022, at 8 PT, 9 MT, 10 CT, 11 ET (16:00 UTC) and you don't have to be a member of Koha-US to join us! You don't even need to self-identify as a cataloger! Join us for our usual roundtable of questions, solutions and resource brainstorming, tips, tricks, suggestions, bug & development awareness, and the usual laughter, fun, and fellowship to discuss anything cataloging, authority, or metadata related in Koha. Not sure if it's cataloging related? It probably is! Actual catalogers do attend, as well as the cataloging curious and those who have had cataloging thrust upon them! Information on joining us is on the Koha-US calendar: Events – koha-US Can't make it? No worries--it will be recorded and available on the Koha-US YouTube Channel: https://www.youtube.com/c/kohaUS/playlists (See the Cataloging Special Interest Group's playlist for more cataloging fun!) As ever, feel free to send me any questions or topics for discussion ahead of time! See you there! --h2 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ms. Heather Hernandez (she, her, hers) Technical Services Librarian Library catalog: https://keys.bywatersolutions.com/ San Francisco Maritime National Historical Park Research Center 2 Marina Blvd., Bldg. E, 3rd floor, San Francisco, CA 94123-1284 415-561-7032 (office generally Tu-W & F, telecommuting M&Th) heather_hernandez at nps.gov From lennon at kohasupport.com Thu Jul 7 00:08:35 2022 From: lennon at kohasupport.com (=?UTF-8?Q?Lennon_Mazonde?=) Date: Wed, 6 Jul 2022 12:08:35 +0000 Subject: [Koha] Migrating from one server to another In-Reply-To: References: <7e5265ff-7f93-910a-8774-d2a07e0e5d15@kohasupport.com> <01000181c8b13147-6bd33035-915f-44df-8da3-c7cf945aadc6-000000@email.amazonses.com> <6ddbbc0d-bfa8-3d69-8eb5-1de889d6209a@kohasupport.com> <01000181c8b482ca-9bef45b4-aaf6-4953-bc28-60a38a5eae55-000000@email.amazonses.com> Message-ID: <01000181d3697f07-da9d52dc-9e7d-4c45-b390-784559c5ecaa-000000@email.amazonses.com> Hi,    An internal server error (500) could mean your Koha instance is either not enabled or is not running (run "koha-worker --status") in which case enable it by running "koha-enable instancename" and "koha-worker --start instancename".    NB: I just checked your admin and OPAC domains and it seems like your instance is up and running. You need to complete the web installer setup and you should be good to go.   Best regards,   Lennon lennon at kohasupport.com kohasupport.com   -----Original message----- From: C.S. Hayward Sent: Tuesday, July 5 2022, 8:02 pm To: Lennon Mazonde Cc: koha Subject: Re: [Koha] Migrating from one server to another   Thank you. I had earlier followed the instructions at http://kohageek.pbworks.com/w/page/60452540/How%20to%20move%20your%20koha%20database%20to%20newly%20installed%20Koha and got an unbranded internal server error at https://library.cjshayward.com and a Koha branded internal server error at https://library-intra.cjshayward.com. Since then (this may have been the equivalent of asking for my tea with cream and lemon) I ran the script you mentioned and https://library.cjshayward.com redirects to https://library.cjshayward.com/cgi-bin/koha/maintenance.pl. A few questions: 1: Have I messed up the system by trying to migrate both ways? 2: Would it likely be less energy to fix the system I have or start over? Would it make sense to do an aptitude purge for koha and then reinstall, or should I be trying a less surgical approach. 3: How can I get useful diagnostics? When I got the earlier 500 error, /var/log/apache2/error.log wasn't getting anything on additional attempted page load. I now have on the system the koha.sql created at http://kohageek.pbworks.com/w/page/60452540/How%20to%20move%20your%20koha%20database%20to%20newly%20installed%20Koha. Thanks, Br. C.S. Hayward, https://c-s-hayward.com ------- Original Message ------- On Monday, July 4th, 2022 at 6:14 AM, Lennon Mazonde wrote: > Forgot to add the link to the GitHub repo, here it is - https://github.com/grandmaestr/koha-scripts. > > Best regards, > > ### Lennon Mazonde > > KohaSupport > > > > > > > > [blob:https://mail.proton.me/e8ef4ba0-e203-49f9-877f-0b7a940b8f83] > > lennon at kohasupport.com > > [blob:https://mail.proton.me/62ee6d68-51dc-4913-952e-6337c32582bb] > > www.kohasupport.com > > [blob:https://mail.proton.me/9edf60da-ed68-47c1-8229-b123f31dd6a0] > > 651 North Broad Street, Middletown, DE 19709, USA > > > > The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. > > On 7/4/22 12:11 PM, Lennon Mazonde wrote: > > > Hi, > > > > > > > > > > I have a repo on GitHub with scripts that might be able to help you. Have a look at the 'koha-migrate' script - I originally wrote it to migrate several Koha MariaDB databases running on a Ubuntu (20.04LTS) server to Amazon Aurora MySQL on AWS but it should work for other use-cases. There are several other scripts there you might find useful as well. As always, test them in a dev environment before running them on your production server :) > > > > > > > > > > If anyone else is interested and would like to contribute to the project, please let me know! > > > > > > > > Best regards, > > > > > > > > > > > > > > Lennon Mazonde > > > > KohaSupport > > > > > > > > > > > > > > > > > > > > lennon at kohasupport.com > > > > www.kohasupport.com > > > > 651 North Broad Street, Middletown, DE 19709, USA > > > > > > > > The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. > > > > > > > > On 7/1/22 5:17 PM, C.S. Hayward wrote: > > > > > > > > (Note: I am not using "migrate" as it is usually used today, meaning switching from ABC software to DEF. I'm referring to relocating an installation's data.) > > > > I would like to migrate my data from one Koha installation on one server to another installation on another server. Both use MariaDB. > > > > Where are instructions suitable to migrating data between two different servers? > > > > > > Thanks, > > Br. C.S. Hayward > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From s.graham4 at herts.ac.uk Thu Jul 7 01:42:51 2022 From: s.graham4 at herts.ac.uk (Stephen Graham) Date: Wed, 6 Jul 2022 13:42:51 +0000 Subject: [Koha] Notices and Library Question Message-ID: Hi All - when you set the "Library" for a notice - a circulation notice more specifically, if it matters - is the library referring to the home library of the user or the home library that the item belongs to? Can't seem to work it out from the documentation. Stephen -------------------------------------- Stephen Graham Library Technology Consultant Library and Computing Services University of Hertfordshire Hatfield, Hertfordshire, AL10 9AB Email: s.graham4 at herts.ac.uk Website: herts.ac.uk From Anke.Bruns at gwdg.de Thu Jul 7 03:02:58 2022 From: Anke.Bruns at gwdg.de (Bruns, Anke) Date: Wed, 6 Jul 2022 15:02:58 +0000 Subject: [Koha] Koha 22.05: Where has the columns setting for the patrons list gone? Message-ID: <61ced22e514b4b8a992809c8f65f2db5@gwdg.de> Hi, a minor problem but nonetheless...: In version 20.11 we had the possibility to choose in the staff client which columns from the patron record we wanted to display in the patrons short list. There was a "Columns" button next to the "Export" one. This option seems to have gone with one of the more recent versions (we upgraded directly from 20.11 to 22.05, so no idea when exactly this was the case). Instead there is a "Clear filter" button now. Is there any chance to get the choice of columns option back? E.g. we do not need or want to display the Date of Birth column which isn't populated in our case. Thank you for any advice and best regards, Anke -- Anke Bruns M.A. (LIS) Arbeitsgruppe "Anwendungs- und Informationssysteme" E-Mail: anke.bruns at 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 at 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 --------------------------------------- From c.s.hayward at protonmail.com Thu Jul 7 03:37:05 2022 From: c.s.hayward at protonmail.com (C.S. Hayward) Date: Wed, 06 Jul 2022 15:37:05 +0000 Subject: [Koha] Migrating from one server to another In-Reply-To: <01000181d3697f07-da9d52dc-9e7d-4c45-b390-784559c5ecaa-000000@email.amazonses.com> References: <7e5265ff-7f93-910a-8774-d2a07e0e5d15@kohasupport.com> <01000181c8b13147-6bd33035-915f-44df-8da3-c7cf945aadc6-000000@email.amazonses.com> <6ddbbc0d-bfa8-3d69-8eb5-1de889d6209a@kohasupport.com> <01000181c8b482ca-9bef45b4-aaf6-4953-bc28-60a38a5eae55-000000@email.amazonses.com> <01000181d3697f07-da9d52dc-9e7d-4c45-b390-784559c5ecaa-000000@email.amazonses.com> Message-ID: >From the console: root at library:~# koha-worker --status library * worker running for library (default) [ OK ] root at library:~# koha-enable library Instance library already enabled. root at library:~# koha-worker -start library Error: invalid option switch (-start) root at library:~# koha-worker --start library * Error: worker already running for library (default) [fail] Attempting to access https://library.cjshayward.com still redirects to https://library.cjshayward.com/cgi-bin/koha/maintenance.pl. Advice? Thanks, Br. C.S. Hayward, https://c-s-hayward.com ------- Original Message ------- On Wednesday, July 6th, 2022 at 8:08 AM, Lennon Mazonde lennon at kohasupport.com wrote: > Hi, > > An internal server error (500) could mean your Koha instance is either not enabled or is not running (run "koha-worker --status") in which case enable it by running "koha-enable instancename" and "koha-worker --start instancename". > > NB: I just checked your admin and OPAC domains and it seems like your instance is up and running. You need to complete the web installer setup and you should be good to go. > > Best regards, > > Lennon > > lennon at kohasupport.com > > kohasupport.com > > > -----Original message----- > > From: C.S. Hayward > > Sent: Tuesday, July 5 2022, 8:02 pm > > To: Lennon Mazonde > > Cc: koha > > Subject: Re: [Koha] Migrating from one server to another > > > > Thank you. > > > > I had earlier followed the instructions at http://kohageek.pbworks.com/w/page/60452540/How to move your koha database to newly installed Koha and got an unbranded internal server error at https://library.cjshayward.com and a Koha branded internal server error at https://library-intra.cjshayward.com. > > > > Since then (this may have been the equivalent of asking for my tea with cream and lemon) I ran the script you mentioned and https://library.cjshayward.com redirects to https://library.cjshayward.com/cgi-bin/koha/maintenance.pl. > > > > A few questions: > > > > 1: Have I messed up the system by trying to migrate both ways? > > > > 2: Would it likely be less energy to fix the system I have or start over? Would it make sense to do an aptitude purge for koha and then reinstall, or should I be trying a less surgical approach. > > > > 3: How can I get useful diagnostics? When I got the earlier 500 error, /var/log/apache2/error.log wasn't getting anything on additional attempted page load. > > > > I now have on the system the koha.sql created at http://kohageek.pbworks.com/w/page/60452540/How to move your koha database to newly installed Koha. > > > > Thanks, > > > > Br. C.S. Hayward, https://c-s-hayward.com > > > > ------- Original Message ------- > > On Monday, July 4th, 2022 at 6:14 AM, Lennon Mazonde lennon at kohasupport.com wrote: > > > > > Forgot to add the link to the GitHub repo, here it is - https://github.com/grandmaestr/koha-scripts. > > > > > > Best regards, > > > > > > ### Lennon Mazonde > > > > > > KohaSupport > > > > > > [blob:https://mail.proton.me/e8ef4ba0-e203-49f9-877f-0b7a940b8f83] > > > > > > lennon at kohasupport.com > > > > > > [blob:https://mail.proton.me/62ee6d68-51dc-4913-952e-6337c32582bb] > > > > > > www.kohasupport.com > > > > > > [blob:https://mail.proton.me/9edf60da-ed68-47c1-8229-b123f31dd6a0] > > > > > > 651 North Broad Street, Middletown, DE 19709, USA > > > > > > The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. > > > > > > On 7/4/22 12:11 PM, Lennon Mazonde wrote: > > > > > > > Hi, > > > > > > > > I have a repo on GitHub with scripts that might be able to help you. Have a look at the 'koha-migrate' script - I originally wrote it to migrate several Koha MariaDB databases running on a Ubuntu (20.04LTS) server to Amazon Aurora MySQL on AWS but it should work for other use-cases. There are several other scripts there you might find useful as well. As always, test them in a dev environment before running them on your production server :) > > > > > > > > If anyone else is interested and would like to contribute to the project, please let me know! > > > > > > > > Best regards, > > > > > > > > Lennon Mazonde > > > > > > > > KohaSupport > > > > > > > > lennon at kohasupport.com > > > > > > > > www.kohasupport.com > > > > > > > > 651 North Broad Street, Middletown, DE 19709, USA > > > > > > > > The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. > > > > > > > > On 7/1/22 5:17 PM, C.S. Hayward wrote: > > > > > > > > (Note: I am not using "migrate" as it is usually used today, meaning switching from ABC software to DEF. I'm referring to relocating an installation's data.) > > > > > > > > I would like to migrate my data from one Koha installation on one server to another installation on another server. Both use MariaDB. > > > > > > > > Where are instructions suitable to migrating data between two different servers? > > > > > > > > Thanks, > > > > Br. C.S. Hayward > > > > _______________________________________________ > > > > > > > > Koha mailing list http://koha-community.org > > > > Koha at lists.katipo.co.nz > > > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > > > > _______________________________________________ > > > > > > > > Koha mailing list http://koha-community.org > > > > Koha at lists.katipo.co.nz > > > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From tmcmahon at wlpl.org Thu Jul 7 04:06:33 2022 From: tmcmahon at wlpl.org (Tim McMahon) Date: Wed, 6 Jul 2022 11:06:33 -0500 Subject: [Koha] Migrating from one server to another In-Reply-To: References: <7e5265ff-7f93-910a-8774-d2a07e0e5d15@kohasupport.com> <01000181c8b13147-6bd33035-915f-44df-8da3-c7cf945aadc6-000000@email.amazonses.com> <6ddbbc0d-bfa8-3d69-8eb5-1de889d6209a@kohasupport.com> <01000181c8b482ca-9bef45b4-aaf6-4953-bc28-60a38a5eae55-000000@email.amazonses.com> <01000181d3697f07-da9d52dc-9e7d-4c45-b390-784559c5ecaa-000000@email.amazonses.com> Message-ID: <8cd188a4-f593-98d4-4cc6-104a560007ea@wlpl.org> What happens when you access your staff interface? On 7/6/22 10:37 AM, C.S. Hayward wrote: > From the console: > > root at library:~# koha-worker --status library > * worker running for library (default) [ OK ] > root at library:~# koha-enable library > Instance library already enabled. > root at library:~# koha-worker -start library > Error: invalid option switch (-start) > root at library:~# koha-worker --start library > * Error: worker already running for library (default) [fail] > > Attempting to accesshttps://library.cjshayward.com still redirects tohttps://library.cjshayward.com/cgi-bin/koha/maintenance.pl. > > Advice? > > > Thanks, > > > Br. C.S. Hayward,https://c-s-hayward.com > > > > > ------- Original Message ------- > On Wednesday, July 6th, 2022 at 8:08 AM, Lennon Mazondelennon at kohasupport.com wrote: > > > >> Hi, >> >> An internal server error (500) could mean your Koha instance is either not enabled or is not running (run "koha-worker --status") in which case enable it by running "koha-enable instancename" and "koha-worker --start instancename". >> >> NB: I just checked your admin and OPAC domains and it seems like your instance is up and running. You need to complete the web installer setup and you should be good to go. >> >> Best regards, >> >> Lennon >> >> lennon at kohasupport.com >> >> kohasupport.com >> >>> -----Original message----- >>> From: C.S. Hayward >>> Sent: Tuesday, July 5 2022, 8:02 pm >>> To: Lennon Mazonde >>> Cc: koha >>> Subject: Re: [Koha] Migrating from one server to another >>> >>> Thank you. >>> >>> I had earlier followed the instructions athttp://kohageek.pbworks.com/w/page/60452540/How to move your koha database to newly installed Koha and got an unbranded internal server error athttps://library.cjshayward.com and a Koha branded internal server error athttps://library-intra.cjshayward.com. >>> >>> Since then (this may have been the equivalent of asking for my tea with cream and lemon) I ran the script you mentioned andhttps://library.cjshayward.com redirects tohttps://library.cjshayward.com/cgi-bin/koha/maintenance.pl. >>> >>> A few questions: >>> >>> 1: Have I messed up the system by trying to migrate both ways? >>> >>> 2: Would it likely be less energy to fix the system I have or start over? Would it make sense to do an aptitude purge for koha and then reinstall, or should I be trying a less surgical approach. >>> >>> 3: How can I get useful diagnostics? When I got the earlier 500 error, /var/log/apache2/error.log wasn't getting anything on additional attempted page load. >>> >>> I now have on the system the koha.sql created athttp://kohageek.pbworks.com/w/page/60452540/How to move your koha database to newly installed Koha. >>> >>> Thanks, >>> >>> Br. C.S. Hayward,https://c-s-hayward.com >>> >>> ------- Original Message ------- >>> On Monday, July 4th, 2022 at 6:14 AM, Lennon Mazondelennon at kohasupport.com wrote: >>> >>>> Forgot to add the link to the GitHub repo, here it is -https://github.com/grandmaestr/koha-scripts. >>>> >>>> Best regards, >>>> >>>> ### Lennon Mazonde >>>> >>>> KohaSupport >>>> >>>> [blob:https://mail.proton.me/e8ef4ba0-e203-49f9-877f-0b7a940b8f83] >>>> >>>> lennon at kohasupport.com >>>> >>>> [blob:https://mail.proton.me/62ee6d68-51dc-4913-952e-6337c32582bb] >>>> >>>> www.kohasupport.com >>>> >>>> [blob:https://mail.proton.me/9edf60da-ed68-47c1-8229-b123f31dd6a0] >>>> >>>> 651 North Broad Street, Middletown, DE 19709, USA >>>> >>>> The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. >>>> >>>> On 7/4/22 12:11 PM, Lennon Mazonde wrote: >>>> >>>>> Hi, >>>>> >>>>> I have a repo on GitHub with scripts that might be able to help you. Have a look at the 'koha-migrate' script - I originally wrote it to migrate several Koha MariaDB databases running on a Ubuntu (20.04LTS) server to Amazon Aurora MySQL on AWS but it should work for other use-cases. There are several other scripts there you might find useful as well. As always, test them in a dev environment before running them on your production server :) >>>>> >>>>> If anyone else is interested and would like to contribute to the project, please let me know! >>>>> >>>>> Best regards, >>>>> >>>>> Lennon Mazonde >>>>> >>>>> KohaSupport >>>>> >>>>> lennon at kohasupport.com >>>>> >>>>> www.kohasupport.com >>>>> >>>>> 651 North Broad Street, Middletown, DE 19709, USA >>>>> >>>>> The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. >>>>> >>>>> On 7/1/22 5:17 PM, C.S. Hayward wrote: >>>>> >>>>> (Note: I am not using "migrate" as it is usually used today, meaning switching from ABC software to DEF. I'm referring to relocating an installation's data.) >>>>> >>>>> I would like to migrate my data from one Koha installation on one server to another installation on another server. Both use MariaDB. >>>>> >>>>> Where are instructions suitable to migrating data between two different servers? >>>>> >>>>> Thanks, >>>>> Br. C.S. Hayward >>>>> _______________________________________________ >>>>> >>>>> Koha mailing listhttp://koha-community.org >>>>> Koha at lists.katipo.co.nz >>>>> Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha >>>>> >>>>> _______________________________________________ >>>>> >>>>> Koha mailing listhttp://koha-community.org >>>>> Koha at lists.katipo.co.nz >>>>> Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing listhttp://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha -- *Tim McMahon* West Liberty Public Library From evanstewart406 at gmail.com Thu Jul 7 04:35:40 2022 From: evanstewart406 at gmail.com (Evan Stewart) Date: Wed, 6 Jul 2022 10:35:40 -0600 Subject: [Koha] Error in Koha 22.05? In-Reply-To: <1344101688.297543.1657023575877@office.mailbox.org> References: <542482724.267230.1657006553609@office.mailbox.org> <48f68a85-5c1f-58a7-f37b-a608135b3c3c@uns.edu.ar> <1344101688.297543.1657023575877@office.mailbox.org> Message-ID: Hi Eberhard, I'm interested to see your borrowers table, too. Can you try to resend the dump file (or copy and paste a few rows into the message thread)? The attachment didn't come through. -Evan Stewart On Tue, Jul 5, 2022 at 6:20 AM Dr. Eberhard Pietzsch wrote: > Attached you see an dump of the borrowers table. You can see at the insert > statement that the contents are shifted by a few bytes. Some attributes are > new compared with earliver versions of Koha. > > (I have edited the encrypted password) > > Eberhard > > > Katrin Fischer hat am 05.07.2022 12:33 CEST > geschrieben: > > > > > > Hi, > > > > could you please post more information about the issue? What error > > message are you seeing? Can you access the tables with SQL? > > > > Is this the error maybe: DBI Exception: DBD::mysql::db do failed: Row > > size too large. > > > > Then have a look at: *Bug 28267* > > - > > Koha-common package upgrade problem from 20.05.xx to 20.11.04-1 > > > > Hope this helps, > > > > Katrin > > > > On 05.07.22 12:21, Fernando A. Martinez wrote: > > > Hi, > > > > > > I have the same problem. Corrupted tables: borrowers and > > > deletedborrowers. Update: Koha 22.05.02 over Koha 21.11.09 Ubuntu > > > 20.04 LTS MySQL version 8.0.29 > > > > > > Regards > > > > > > Fernando A. Martinez > > > > > > On 5/7/22 04:35, Dr. Eberhard Pietzsch wrote: > > >> Hello, > > >> > > >> I would like to point out a bug in Koha after the update to 22.05. > > >> > > >> Koha is also included in the package management of Ubuntu 22.04 LTS > > >> and can be updated together with Ubuntu. I had skipped the short time > > >> preceding Koha update because of errors. However, the current update > > >> to 22.05 apparently also contains bugs: > > >> > > >> The structure of the borrowers table seems to have been changed > > >> compared to previous versions. Existing user data are not correctly > > >> loaded into the new structured table with the update, so that no > > >> login, e.g. as superlibrarian, is possible anymore. > > >> > > >> Possibly this phenomenon is caused by the skipped update to the > > >> previous version? > > >> > > >> Many greetings > > >> Eberhard Pietzsch > > >> _______________________________________________ > > >> > > >> Koha mailing listhttp://koha-community.org > > >> Koha at lists.katipo.co.nz > > >> Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha > > > _______________________________________________ > > > > > > Koha mailing list http://koha-community.org > > > Koha at lists.katipo.co.nz > > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From evanstewart406 at gmail.com Thu Jul 7 04:42:38 2022 From: evanstewart406 at gmail.com (Evan Stewart) Date: Wed, 6 Jul 2022 10:42:38 -0600 Subject: [Koha] Patron search not working after upgrade to version 22 Message-ID: Hello, I recently upgraded my Koka 21 to 22. Everything seemed to be working fine until I tried searching for patrons. Using the intranet portal to search for patrons provides zero results. I see my patrons in the borrowers table, but the GUI won't display them. It's like the search function sees no results. I upgraded to version 22.05.02, but the same problem still occurs. I'm using Raspberry Pi OS (Buster). I can add a new patron, but even the new patron does not show in the search results. Is there a way to refresh the indexer that handles patron searching? Any other suggestions? -Evan Stewart Africa's Hope, USA From skaman.tx at gmail.com Thu Jul 7 05:03:53 2022 From: skaman.tx at gmail.com (skaman.tx at gmail.com) Date: Wed, 6 Jul 2022 12:03:53 -0500 Subject: [Koha] Debian koha-common_22.05.02-1_all.deb package dependencies conflict Message-ID: <001801d8915a$5f9b7f60$1ed27e20$@gmail.com> I am running an up-to-date version of Debian Buster. Doing a routine "apt update" today and I encountered the following package upgrade for koha-common (koha-common_22.05.02-1_all.deb) that appears to have surfaced in the past for others. :[user]# apt upgrade -y ... Preconfiguring packages ... /tmp/koha-common.config.kjvlf5: 49: koha-list: not found .. Unpacking libmarc-xml-perl (1.0.5-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-E4Zp2O/1-libmarc-xml-perl_1.0.5-1_all.deb (--unpack): trying to overwrite '/usr/bin/marc2xml', which is also in package libmarc-file-xml-perl 1.0.5-1~koha+1 .... Errors were encountered while processing: /tmp/apt-dpkg-install-sNNjK2/1-libmarc-xml-perl_1.0.5-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) >From past bug reports it appears there is a libmarc-xml-perl package in both the Debian repo and the Koha repo. I tried putting an apt hold on libmarc-xml-perl and then completing the apt upgrade, but this breaks my koha system. So, I'm unable to upgrade koha-common at present. Any suggestions to fix this would be helpful. Scott Leafe Scriptel Ministries From katrin.fischer.83 at web.de Thu Jul 7 05:14:25 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Wed, 6 Jul 2022 19:14:25 +0200 Subject: [Koha] Patron search not working after upgrade to version 22 In-Reply-To: References: Message-ID: Hi Evan, in 22.05 the patron search has been switched to use Koha's REST API. There are also other pages using it. For a test: could you check if you can see your configured libraries in administration? The list is also API driven. The problem is usually related to Koha's dependencies. We have instructions for some older Ubuntu/Debian versions, but I am not sure what would apply to Raspberry Pi. Maybe it's still useful: https://wiki.koha-community.org/wiki/Koha_on_Debian#Support_for_Koha_on_older_versions_of_Debian.2FUbuntu_.28Debian_8.2C_Ubuntu_18.04.2C_Ubuntu_16.04.29 Hope this helps, Katrin On 06.07.22 18:42, Evan Stewart wrote: > Hello, > > I recently upgraded my Koka 21 to 22. Everything seemed to be working fine > until I tried searching for patrons. Using the intranet portal to search > for patrons provides zero results. I see my patrons in the borrowers > table, but the GUI won't display them. It's like the search function sees > no results. > > I upgraded to version 22.05.02, but the same problem still occurs. > > I'm using Raspberry Pi OS (Buster). > > I can add a new patron, but even the new patron does not show in the search > results. > > Is there a way to refresh the indexer that handles patron searching? Any > other suggestions? > > -Evan Stewart > Africa's Hope, USA > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From rainer.stowasser at zamg.ac.at Thu Jul 7 05:17:56 2022 From: rainer.stowasser at zamg.ac.at (Stowasser Rainer) Date: Wed, 6 Jul 2022 17:17:56 +0000 Subject: [Koha] Debian koha-common_22.05.02-1_all.deb package dependencies conflict In-Reply-To: <001801d8915a$5f9b7f60$1ed27e20$@gmail.com> References: <001801d8915a$5f9b7f60$1ed27e20$@gmail.com> Message-ID: <907271B5-453F-4B29-94CE-94D3F7E57F97@zamg.ac.at> Dear Scott I ve think I was one of the first to mention the „problem“ its fixed but Debian has a /var/cache/apt/ lock file just rm it and after that it worked for me Kind regards Hofrat Mag. Rainer Stowasser Head of Library and Archives ZAMG Am 06.07.2022 um 19:03 schrieb skaman.tx at gmail.com: I am running an up-to-date version of Debian Buster. Doing a routine "apt update" today and I encountered the following package upgrade for koha-common (koha-common_22.05.02-1_all.deb) that appears to have surfaced in the past for others. :[user]# apt upgrade -y ... Preconfiguring packages ... /tmp/koha-common.config.kjvlf5: 49: koha-list: not found .. Unpacking libmarc-xml-perl (1.0.5-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-E4Zp2O/1-libmarc-xml-perl_1.0.5-1_all.deb (--unpack): trying to overwrite '/usr/bin/marc2xml', which is also in package libmarc-file-xml-perl 1.0.5-1~koha+1 .... Errors were encountered while processing: /tmp/apt-dpkg-install-sNNjK2/1-libmarc-xml-perl_1.0.5-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) From past bug reports it appears there is a libmarc-xml-perl package in both the Debian repo and the Koha repo. I tried putting an apt hold on libmarc-xml-perl and then completing the apt upgrade, but this breaks my koha system. So, I'm unable to upgrade koha-common at present. Any suggestions to fix this would be helpful. Scott Leafe Scriptel Ministries _______________________________________________ Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha EXTERNAL EMAIL: Do not click any links or open any attachments unless you trust the sender and know the content is safe. From katrin.fischer.83 at web.de Thu Jul 7 05:18:12 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Wed, 6 Jul 2022 19:18:12 +0200 Subject: [Koha] Koha 22.05: Where has the columns setting for the patrons list gone? In-Reply-To: <61ced22e514b4b8a992809c8f65f2db5@gwdg.de> References: <61ced22e514b4b8a992809c8f65f2db5@gwdg.de> Message-ID: Hi Anke, in 22.05 the normal patron search is also used for the circulation patron search. Maybe you meant that list? The settings are in Administration > Table settings > Patrons > memberresultst Hope this helps, Katrin On 06.07.22 17:02, Bruns, Anke wrote: > Hi, > > a minor problem but nonetheless...: In version 20.11 we had the possibility > to choose in the staff client which columns from the patron record we wanted > to display in the patrons short list. There was a "Columns" button next to > the "Export" one. This option seems to have gone with one of the more recent > versions (we upgraded directly from 20.11 to 22.05, so no idea when exactly > this was the case). Instead there is a "Clear filter" button now. > > Is there any chance to get the choice of columns option back? E.g. we do not > need or want to display the Date of Birth column which isn't populated in > our case. > > Thank you for any advice and best regards, > Anke > From tomascohen at gmail.com Thu Jul 7 05:19:14 2022 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Wed, 6 Jul 2022 14:19:14 -0300 Subject: [Koha] Patron search not working after upgrade to version 22 In-Reply-To: References: Message-ID: This is certainly caused by a Koha bug I'm about to submit a patch for [1]. The 22.05 release maintainer is AFK this week so he cannot release a new version yet. Best regards. [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31104 El mié, 6 jul 2022 a las 13:43, Evan Stewart () escribió: > Hello, > > I recently upgraded my Koka 21 to 22. Everything seemed to be working fine > until I tried searching for patrons. Using the intranet portal to search > for patrons provides zero results. I see my patrons in the borrowers > table, but the GUI won't display them. It's like the search function sees > no results. > > I upgraded to version 22.05.02, but the same problem still occurs. > > I'm using Raspberry Pi OS (Buster). > > I can add a new patron, but even the new patron does not show in the search > results. > > Is there a way to refresh the indexer that handles patron searching? Any > other suggestions? > > -Evan Stewart > Africa's Hope, USA > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F From katrin.fischer.83 at web.de Thu Jul 7 05:21:10 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Wed, 6 Jul 2022 19:21:10 +0200 Subject: [Koha] Notices and Library Question In-Reply-To: References: Message-ID: Hi Stephen, the circulation module includes a lot of different notices and I believe the behavior is probably not the same for each of them. For example the *DGST emails use the patron's home library, while a CHECKOUT notice will be sent from the library the staff member performing the checkout is logged in at. Hope this helps, Katrin On 06.07.22 15:42, Stephen Graham wrote: > Hi All - when you set the "Library" for a notice - a circulation notice more specifically, if it matters - is the library referring to the home library of the user or the home library that the item belongs to? Can't seem to work it out from the documentation. > > Stephen > > -------------------------------------- > Stephen Graham > Library Technology Consultant > Library and Computing Services > > University of Hertfordshire > Hatfield, Hertfordshire, AL10 9AB > > Email: s.graham4 at herts.ac.uk > Website: herts.ac.uk > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From skaman.tx at gmail.com Thu Jul 7 05:56:43 2022 From: skaman.tx at gmail.com (skaman.tx at gmail.com) Date: Wed, 6 Jul 2022 12:56:43 -0500 Subject: [Koha] Debian koha-common_22.05.02-1_all.deb package dependencies conflict Message-ID: <003c01d89161$c0efdcf0$42cf96d0$@gmail.com> Thank you, Rainer. Unfortunately, I do not find a lock file there on my instance. Fortunately, we are running our Debian Buster instance as a VM, so reverting to “pre-broken” status is a quick fix for now. So, I just ran “apt upgrade -y” again, and it still gives me the same libmarc-xml-perl package install/overwrite error. Scott From: Stowasser Rainer Sent: Wednesday, July 06, 2022 12:18 PM To: skaman.tx at gmail.com Cc: koha at lists.katipo.co.nz Subject: Re: [Koha] Debian koha-common_22.05.02-1_all.deb package dependencies conflict Dear Scott I ve think I was one of the first to mention the „problem“ its fixed but Debian has a /var/cache/apt/ lock file just rm it and after that it worked for me Kind regards Hofrat Mag. Rainer Stowasser Head of Library and Archives ZAMG Am 06.07.2022 um 19:03 schrieb skaman.tx at gmail.com : I am running an up-to-date version of Debian Buster. Doing a routine "apt update" today and I encountered the following package upgrade for koha-common (koha-common_22.05.02-1_all.deb) that appears to have surfaced in the past for others. :[user]# apt upgrade -y ... Preconfiguring packages ... /tmp/koha-common.config.kjvlf5: 49: koha-list: not found .. Unpacking libmarc-xml-perl (1.0.5-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-E4Zp2O/1-libmarc-xml-perl_1.0.5-1_all.deb (--unpack): trying to overwrite '/usr/bin/marc2xml', which is also in package libmarc-file-xml-perl 1.0.5-1~koha+1 .... Errors were encountered while processing: /tmp/apt-dpkg-install-sNNjK2/1-libmarc-xml-perl_1.0.5-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) >From past bug reports it appears there is a libmarc-xml-perl package in both the Debian repo and the Koha repo. I tried putting an apt hold on libmarc-xml-perl and then completing the apt upgrade, but this breaks my koha system. So, I'm unable to upgrade koha-common at present. Any suggestions to fix this would be helpful. Scott Leafe Scriptel Ministries _______________________________________________ Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha EXTERNAL EMAIL: Do not click any links or open any attachments unless you trust the sender and know the content is safe. From secretary at koha-us.org Thu Jul 7 06:56:44 2022 From: secretary at koha-us.org (Jennifer Marlatt) Date: Wed, 6 Jul 2022 11:56:44 -0700 Subject: [Koha] koha-US Board Meeting Minutes for July 6, 2022 Message-ID: Hello, Here's a link to the minutes from the koha-US board meeting today - https://docs.google.com/document/d/10yUXerjpzrYVKjp-sS79Wwi8HDnve5StU_bsL9pApas/edit?usp=sharing 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, July 13th at 8:30 PT / 9:30 MT / 10:30 CT / 11:30 ET (time converter ). We'll be discussing amendments to the bylaws, the System Administration SIG Chair vacancy, and future conference formats. The agenda is available here - https://docs.google.com/document/d/1AoZyJg6DMGiJys4CcmeL6IzGHSriwtPvRbqxE20nzA4/edit?usp=sharing Join the meeting at https://us02web.zoom.us/j/648572897?pwd=TUpsRE1TYlFPWWxTWFl4TVovSTJ3Zz09 If you have additional topics for the agenda, please send them to secretary at koha-us.org. Jennifer Marlatt koha-US Secretary secretary at koha-us.org From mtj at kohaaloha.com Thu Jul 7 13:51:41 2022 From: mtj at kohaaloha.com (Mason James) Date: Thu, 7 Jul 2022 13:51:41 +1200 Subject: [Koha] Debian koha-common_22.05.02-1_all.deb package dependencies conflict In-Reply-To: <001801d8915a$5f9b7f60$1ed27e20$@gmail.com> References: <001801d8915a$5f9b7f60$1ed27e20$@gmail.com> Message-ID: hi Scott what koha version are you upgrading from? i'm assuming 22.05.00 or 22.05.01? On 7/07/22 5:03 am, skaman.tx at gmail.com wrote: > I am running an up-to-date version of Debian Buster. Doing a routine "apt > update" today and I encountered the following package upgrade for > koha-common (koha-common_22.05.02-1_all.deb) that appears to have surfaced > in the past for others. > > > > > > :[user]# apt upgrade -y > > ... > > Preconfiguring packages ... > > /tmp/koha-common.config.kjvlf5: 49: koha-list: not found > > .. > > Unpacking libmarc-xml-perl (1.0.5-1) ... > > dpkg: error processing archive > /tmp/apt-dpkg-install-E4Zp2O/1-libmarc-xml-perl_1.0.5-1_all.deb (--unpack): > > trying to overwrite '/usr/bin/marc2xml', which is also in package > libmarc-file-xml-perl 1.0.5-1~koha+1 > > .... > > Errors were encountered while processing: > > /tmp/apt-dpkg-install-sNNjK2/1-libmarc-xml-perl_1.0.5-1_all.deb > > E: Sub-process /usr/bin/dpkg returned an error code (1) > > > > > > From past bug reports it appears there is a libmarc-xml-perl package in both > the Debian repo and the Koha repo. > > > > I tried putting an apt hold on libmarc-xml-perl and then completing the apt > upgrade, but this breaks my koha system. So, I'm unable to upgrade > koha-common at present. > > > > Any suggestions to fix this would be helpful. > > > > Scott Leafe > > Scriptel Ministries > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From cmkelleymls at gmail.com Thu Jul 7 13:52:32 2022 From: cmkelleymls at gmail.com (Charles Kelley) Date: Thu, 7 Jul 2022 10:52:32 +0900 Subject: [Koha] Rotating IP Address and Koha Logout In-Reply-To: References: Message-ID: Hello, Alvaro et al! Please pardon the late reply. In our latest exchange, on 6 July 2022 at 09:01 [JST], I received this from Alvaro Cornejo: IP is assigned by the OS system. In your case, AWS. > > I assume you will need to ask AWS to assign/configure you a fixed public IP > address. > Yes, the IT staff eventually figured out what had to be done was to adjust the AWS settings for this particular website. They just wanted confirmation that it wasn't something else going on, probably in Koha, that was causing the premature logouts. The appropriate settings were changed, and the issue vanished. Thanks for the confirmation. There was also this response from Barry Cannon: To temporarily get around this problem you can disable the > SessionRestrictionByIP system preference in Koha. This binds the user's > session ID to their public IP address. If it changes, the session becomes > invalid and Koha will prompt for a new login. > > The changing IP seems to be unrelated to AWS as they appear to be your ISP > addresses. Does the same problem exist outside of your organisation? For > example, at home or on a mobile device. If not then the problem is most > likely related to an outbound proxy at your end - your IT might look into > this. If it still happens elsewhere then perhaps your ISP is doing > something with transparent proxying that they might be able to help you > with. > This is good to know in case the premature logouts resume in the future. It will be something else to look into. But for the time being, the new AWS setting seems to fix the problem. Many thanks! -- よろしくお願いします。 -- Charles. +81-80-4356-2178 [JPN cell] +1-301-741-7122 [US cell] mnogojazyk at aol.com [h] cmkelleymls at gmail.com [p] linkedin.com/in/cmkelleymls Meeting Your Information Needs. Virtually. From skaman.tx at gmail.com Thu Jul 7 14:00:05 2022 From: skaman.tx at gmail.com (Ska Man) Date: Wed, 6 Jul 2022 21:00:05 -0500 Subject: [Koha] Debian koha-common_22.05.02-1_all.deb package dependencies conflict In-Reply-To: References: Message-ID: Mason, we are currently on Koha version 22.05.00. Scott > On Jul 6, 2022, at 8:51 PM, Mason James wrote: > > 22.05.00 From skaman.tx at gmail.com Thu Jul 7 14:01:08 2022 From: skaman.tx at gmail.com (Ska Man) Date: Wed, 6 Jul 2022 21:01:08 -0500 Subject: [Koha] Debian koha-common_22.05.02-1_all.deb package dependencies conflict In-Reply-To: References: Message-ID: <422DAB83-540B-40C6-AB90-D1422CBDC2C5@gmail.com> Mason, we are currently running Koha version 22.05.00. Scott > On Jul 6, 2022, at 8:51 PM, Mason James wrote: > > hi Scott > what koha version are you upgrading from? > > i'm assuming 22.05.00 or 22.05.01? > > >> On 7/07/22 5:03 am, skaman.tx at gmail.com wrote: >> I am running an up-to-date version of Debian Buster. Doing a routine "apt >> update" today and I encountered the following package upgrade for >> koha-common (koha-common_22.05.02-1_all.deb) that appears to have surfaced >> in the past for others. >> >> >> >> :[user]# apt upgrade -y >> >> ... >> >> Preconfiguring packages ... >> >> /tmp/koha-common.config.kjvlf5: 49: koha-list: not found >> >> .. >> >> Unpacking libmarc-xml-perl (1.0.5-1) ... >> >> dpkg: error processing archive >> /tmp/apt-dpkg-install-E4Zp2O/1-libmarc-xml-perl_1.0.5-1_all.deb (--unpack): >> >> trying to overwrite '/usr/bin/marc2xml', which is also in package >> libmarc-file-xml-perl 1.0.5-1~koha+1 >> >> .... >> >> Errors were encountered while processing: >> >> /tmp/apt-dpkg-install-sNNjK2/1-libmarc-xml-perl_1.0.5-1_all.deb >> >> E: Sub-process /usr/bin/dpkg returned an error code (1) >> >> >> >> From past bug reports it appears there is a libmarc-xml-perl package in both >> the Debian repo and the Koha repo. >> >> >> I tried putting an apt hold on libmarc-xml-perl and then completing the apt >> upgrade, but this breaks my koha system. So, I'm unable to upgrade >> koha-common at present. >> >> >> Any suggestions to fix this would be helpful. >> >> >> Scott Leafe >> >> Scriptel Ministries >> >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From mtj at kohaaloha.com Thu Jul 7 14:55:44 2022 From: mtj at kohaaloha.com (Mason James) Date: Thu, 7 Jul 2022 14:55:44 +1200 Subject: [Koha] Debian koha-common_22.05.02-1_all.deb package dependencies conflict In-Reply-To: <422DAB83-540B-40C6-AB90-D1422CBDC2C5@gmail.com> References: <422DAB83-540B-40C6-AB90-D1422CBDC2C5@gmail.com> Message-ID: <444c4f7f-d727-9385-6e9d-91dc43a12d17@kohaaloha.com> aah, ok we recently removed the 'libmarc-file-xml-perl' package, as it became redundant try the following commands...  $ sudo apt remove libmarc-file-xml-perl  $ sudo apt install koha-common On 7/07/22 2:01 pm, Ska Man wrote: > Mason, we are currently running Koha version 22.05.00. > > Scott > >> On Jul 6, 2022, at 8:51 PM, Mason James wrote: >> >> hi Scott >> what koha version are you upgrading from? >> >> i'm assuming 22.05.00 or 22.05.01? >> >> >>> On 7/07/22 5:03 am, skaman.tx at gmail.com wrote: >>> I am running an up-to-date version of Debian Buster. Doing a routine "apt >>> update" today and I encountered the following package upgrade for >>> koha-common (koha-common_22.05.02-1_all.deb) that appears to have surfaced >>> in the past for others. >>> >>> >>> >>> :[user]# apt upgrade -y >>> >>> ... >>> >>> Preconfiguring packages ... >>> >>> /tmp/koha-common.config.kjvlf5: 49: koha-list: not found >>> >>> .. >>> >>> Unpacking libmarc-xml-perl (1.0.5-1) ... >>> >>> dpkg: error processing archive >>> /tmp/apt-dpkg-install-E4Zp2O/1-libmarc-xml-perl_1.0.5-1_all.deb (--unpack): >>> >>> trying to overwrite '/usr/bin/marc2xml', which is also in package >>> libmarc-file-xml-perl 1.0.5-1~koha+1 >>> >>> .... >>> >>> Errors were encountered while processing: >>> >>> /tmp/apt-dpkg-install-sNNjK2/1-libmarc-xml-perl_1.0.5-1_all.deb >>> >>> E: Sub-process /usr/bin/dpkg returned an error code (1) >>> >>> >>> >>> From past bug reports it appears there is a libmarc-xml-perl package in both >>> the Debian repo and the Koha repo. >>> >>> >>> I tried putting an apt hold on libmarc-xml-perl and then completing the apt >>> upgrade, but this breaks my koha system. So, I'm unable to upgrade >>> koha-common at present. >>> >>> >>> Any suggestions to fix this would be helpful. >>> >>> >>> Scott Leafe >>> >>> Scriptel Ministries >>> >>> _______________________________________________ >>> >>> Koha mailing list http://koha-community.org >>> Koha at lists.katipo.co.nz >>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From skaman.tx at gmail.com Thu Jul 7 15:56:11 2022 From: skaman.tx at gmail.com (Ska Man) Date: Wed, 6 Jul 2022 22:56:11 -0500 Subject: [Koha] Debian koha-common_22.05.02-1_all.deb package dependencies conflict In-Reply-To: <444c4f7f-d727-9385-6e9d-91dc43a12d17@kohaaloha.com> References: <444c4f7f-d727-9385-6e9d-91dc43a12d17@kohaaloha.com> Message-ID: Bingo, that worked. Thank you! Scott > On Jul 6, 2022, at 9:55 PM, Mason James wrote: > > aah, ok > we recently removed the 'libmarc-file-xml-perl' package, as it became redundant > > try the following commands... > > $ sudo apt remove libmarc-file-xml-perl > $ sudo apt install koha-common > > >> On 7/07/22 2:01 pm, Ska Man wrote: >> Mason, we are currently running Koha version 22.05.00. >> >> Scott >> >>>> On Jul 6, 2022, at 8:51 PM, Mason James wrote: >>> >>> hi Scott >>> what koha version are you upgrading from? >>> >>> i'm assuming 22.05.00 or 22.05.01? >>> >>> >>>> On 7/07/22 5:03 am, skaman.tx at gmail.com wrote: >>>> I am running an up-to-date version of Debian Buster. Doing a routine "apt >>>> update" today and I encountered the following package upgrade for >>>> koha-common (koha-common_22.05.02-1_all.deb) that appears to have surfaced >>>> in the past for others. >>>> >>>> :[user]# apt upgrade -y >>>> >>>> ... >>>> >>>> Preconfiguring packages ... >>>> >>>> /tmp/koha-common.config.kjvlf5: 49: koha-list: not found >>>> >>>> .. >>>> >>>> Unpacking libmarc-xml-perl (1.0.5-1) ... >>>> >>>> dpkg: error processing archive >>>> /tmp/apt-dpkg-install-E4Zp2O/1-libmarc-xml-perl_1.0.5-1_all.deb (--unpack): >>>> >>>> trying to overwrite '/usr/bin/marc2xml', which is also in package >>>> libmarc-file-xml-perl 1.0.5-1~koha+1 >>>> >>>> .... >>>> >>>> Errors were encountered while processing: >>>> >>>> /tmp/apt-dpkg-install-sNNjK2/1-libmarc-xml-perl_1.0.5-1_all.deb >>>> >>>> E: Sub-process /usr/bin/dpkg returned an error code (1) >>>> >>>> From past bug reports it appears there is a libmarc-xml-perl package in both >>>> the Debian repo and the Koha repo. >>>> >>>> I tried putting an apt hold on libmarc-xml-perl and then completing the apt >>>> upgrade, but this breaks my koha system. So, I'm unable to upgrade >>>> koha-common at present. >>>> >>>> Any suggestions to fix this would be helpful. >>>> >>>> Scott Leafe >>>> >>>> Scriptel Ministries >>>> >>>> _______________________________________________ >>>> >>>> Koha mailing list http://koha-community.org >>>> Koha at lists.katipo.co.nz >>>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From Anke.Bruns at gwdg.de Thu Jul 7 22:52:16 2022 From: Anke.Bruns at gwdg.de (Bruns, Anke) Date: Thu, 7 Jul 2022 10:52:16 +0000 Subject: [Koha] Background jobs in Koha menu "Administration" In-Reply-To: References: Message-ID: <7e1bb0ff574449888fa979a137f43789@gwdg.de> Hi, not sure if this belongs to this thread, but as it concerns /cgi-bin/koha/admin/background_jobs.pl it may fit in. We realized that in 22.05 there is a http 500 error when clicking on "View" in one of the jobs listed on the background jobs overview. This is independent of - the Koha instance (we tried it with two different instances on our server) - whether you navigate to the background jobs overview via menu "Administration > Manage background jobs" or when you just started a batch operation (in our case batch item modification) and from there try to view the job in the list. The corresponding message in the plack-error.log reads: Can't call method "GetPlugins" on an undefined value at /usr/share/koha/lib/Koha/BackgroundJob.pm line 402. And this is line 402 in /usr/share/koha/lib/Koha/BackgroundJob.pm: my @plugins = Koha::Plugins->new()->GetPlugins( { method => 'background_tasks', } ); Should we file a bug for this? Regards, Anke -- Anke Bruns M.A. (LIS) Arbeitsgruppe "Anwendungs- und Informationssysteme" E-Mail: anke.bruns at 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 at 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 --------------------------------------- > -----Ursprüngliche Nachricht----- > Von: Koha Im Auftrag von Michael Kuhn > Gesendet: Mittwoch, 22. Juni 2022 08:53 > An: koha at lists.katipo.co.nz > Betreff: Re: [Koha] Background jobs in Koha menu "Administration" > > Hi Christopher > > Thanks for your meesage. You wrote: > > > With just a cursory look, I would assume something like 1/1 means 1 > > job, 1 completed. Something like 2/1 would mean 2 jobs, 1 completed. > > 0/0, I would assume, means there are no jobs. > > Yes this is also our assumption - but we ask ourselves if there is no > job, why is there a line at all saying there is no job?! The library is > afraid that maybe something went wrong in such a case. > > As said, unfortunately clicking the button "View" does not show more > information like WHAT biblio or item exactly the job is referring to. > > 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 at adminkuhn.ch · W www.adminkuhn.ch > > > > Message: 5 > > Date: Mon, 20 Jun 2022 14:48:02 +0200 > > From: Michael Kuhn > > To: Koha > > Subject: [Koha] Background jobs in Koha menu "Administration" > > Message-ID: > > Content-Type: text/plain; charset=UTF-8; format=flowed > > > > Hi > > > > We saw in Koha 22.05 there is a new Koha menu "Administration > Manage > background jobs". Unfortunately there seems to be no entry in the Koha manual > 22.05 for it, also the context-sensitive help just leads to https://koha- > community.org/manual//21.11/en/html/ (this is in an installation of Koha > 22.05!). > > > > However the shown list has a column "progress" which can say "1/1" or "0/0" > for example. What does ist mean? Library personnel thinks "0/0" > > suggests that something went wrong even if column "Status" says "Finished". > Unfortunately clicking the button "View" does not show more information like > WHAT biblio or item exactly the entry is referring to. > > > > We saw that Bywater Solutions wrote an article about this new menu ( > https://bywatersolutions.com/education/koha-21-11-background-jobs-and-task- > queue-enhancements > > ) but our question is not answered there. Can someone please enlighten us > what "0/0" means? > > > > Best wishes: Michael > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From Anke.Bruns at gwdg.de Thu Jul 7 22:55:58 2022 From: Anke.Bruns at gwdg.de (Bruns, Anke) Date: Thu, 7 Jul 2022 10:55:58 +0000 Subject: [Koha] Background jobs in Koha menu "Administration" In-Reply-To: <7e1bb0ff574449888fa979a137f43789@gwdg.de> References: <7e1bb0ff574449888fa979a137f43789@gwdg.de> Message-ID: ... I forgot to mention that these jobs aren't executed either, but remain in the New status on the overview page. Regards, Anke > -----Ursprüngliche Nachricht----- > Von: Bruns, Anke <> > Gesendet: Donnerstag, 7. Juli 2022 12:52 > An: koha at lists.katipo.co.nz > Betreff: AW: [Koha] Background jobs in Koha menu "Administration" > > Hi, > > not sure if this belongs to this thread, but as it concerns > > /cgi-bin/koha/admin/background_jobs.pl > > it may fit in. > > We realized that in 22.05 there is a http 500 error when clicking on "View" in > one of the jobs listed on the background jobs overview. This is independent of > - the Koha instance (we tried it with two different instances on our server) > - whether you navigate to the background jobs overview via menu > "Administration > Manage background jobs" or when you just started a batch > operation (in our case batch item modification) and from there try to view the > job in the list. > > The corresponding message in the plack-error.log reads: > > Can't call method "GetPlugins" on an undefined value at > /usr/share/koha/lib/Koha/BackgroundJob.pm line 402. > > And this is line 402 in /usr/share/koha/lib/Koha/BackgroundJob.pm: > > my @plugins = Koha::Plugins->new()->GetPlugins( { method => > 'background_tasks', } ); > > Should we file a bug for this? > > Regards, > Anke > > > > -- > Anke Bruns M.A. (LIS) > Arbeitsgruppe "Anwendungs- und Informationssysteme" > E-Mail: anke.bruns at 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 at 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 > --------------------------------------- > > > > > > > -----Ursprüngliche Nachricht----- > > Von: Koha Im Auftrag von Michael Kuhn > > Gesendet: Mittwoch, 22. Juni 2022 08:53 > > An: koha at lists.katipo.co.nz > > Betreff: Re: [Koha] Background jobs in Koha menu "Administration" > > > > Hi Christopher > > > > Thanks for your meesage. You wrote: > > > > > With just a cursory look, I would assume something like 1/1 means 1 > > > job, 1 completed. Something like 2/1 would mean 2 jobs, 1 completed. > > > 0/0, I would assume, means there are no jobs. > > > > Yes this is also our assumption - but we ask ourselves if there is no > > job, why is there a line at all saying there is no job?! The library is > > afraid that maybe something went wrong in such a case. > > > > As said, unfortunately clicking the button "View" does not show more > > information like WHAT biblio or item exactly the job is referring to. > > > > 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 at adminkuhn.ch · W www.adminkuhn.ch > > > > > > > Message: 5 > > > Date: Mon, 20 Jun 2022 14:48:02 +0200 > > > From: Michael Kuhn > > > To: Koha > > > Subject: [Koha] Background jobs in Koha menu "Administration" > > > Message-ID: > > > Content-Type: text/plain; charset=UTF-8; format=flowed > > > > > > Hi > > > > > > We saw in Koha 22.05 there is a new Koha menu "Administration > Manage > > background jobs". Unfortunately there seems to be no entry in the Koha > manual > > 22.05 for it, also the context-sensitive help just leads to https://koha- > > community.org/manual//21.11/en/html/ (this is in an installation of Koha > > 22.05!). > > > > > > However the shown list has a column "progress" which can say "1/1" or > "0/0" > > for example. What does ist mean? Library personnel thinks "0/0" > > > suggests that something went wrong even if column "Status" says > "Finished". > > Unfortunately clicking the button "View" does not show more information like > > WHAT biblio or item exactly the entry is referring to. > > > > > > We saw that Bywater Solutions wrote an article about this new menu ( > > https://bywatersolutions.com/education/koha-21-11-background-jobs-and- > task- > > queue-enhancements > > > ) but our question is not answered there. Can someone please enlighten us > > what "0/0" means? > > > > > > Best wishes: Michael > > > _______________________________________________ > > > > > > Koha mailing list http://koha-community.org > > > Koha at lists.katipo.co.nz > > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From dietrich at teilgedanken.de Thu Jul 7 23:00:09 2022 From: dietrich at teilgedanken.de (Franz Dietrich) Date: Thu, 07 Jul 2022 11:00:09 +0000 Subject: [Koha] Empty PDF file when printing labels Message-ID: <20220707110009.Horde.sV2dWhUq2ub40_Tgs2-8Xsl@nc.teilgedanken.de>   Hey all, I can't figure out the problem on my own right now.   Problem: Label creator ->manage->label batches->select one->export(full or single)->select the options->select PDF A PDF-Editor opens but no pdf is shown. If I download the pdf it says corrupt (the file is 0 Bytes)   I can't find any logs on the server mentioning an issue. The only thing I can find is - which is a 200 Responsecode...:   http://redacted.cloud:80 http://192.168.20.174 - - [07/Jul/2022:07:15:01 +0000] "GET /cgi-bin/koha/labels/http://label-create-pdf.pl?batch_id=2&template_id=25&layout_id=24&start_label=1 HTTP/1.1" 200 308 "http://redacted.cloud/cgi-bin/koha/labels/label-print.pl" "Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0"   what could be next steps to find the issue?       From itmanager at dhi-moskau.org Thu Jul 7 23:43:12 2022 From: itmanager at dhi-moskau.org (DHIM IT) Date: Thu, 7 Jul 2022 11:43:12 +0000 Subject: [Koha] Background jobs in Koha menu "Administration" In-Reply-To: References: <7e1bb0ff574449888fa979a137f43789@gwdg.de> Message-ID: <1EBB08DE-7601-4321-9FDB-654FFE42EAA4@dhi-moskau.org> Hello, I have the same problem. Koha Version: 22.05.02.000 Job ID Status Progress Type Queued Started 3 New 0 / 1 Batch item record deletion 07.07.2022 06:27 Am 07.07.22, 13:56 schrieb "Koha im Auftrag von Bruns, Anke" : ... I forgot to mention that these jobs aren't executed either, but remain in the New status on the overview page. Regards, Anke > -----Ursprüngliche Nachricht----- > Von: Bruns, Anke <> > Gesendet: Donnerstag, 7. Juli 2022 12:52 > An: koha at lists.katipo.co.nz > Betreff: AW: [Koha] Background jobs in Koha menu "Administration" > > Hi, > > not sure if this belongs to this thread, but as it concerns > > /cgi-bin/koha/admin/background_jobs.pl > > it may fit in. > > We realized that in 22.05 there is a http 500 error when clicking on "View" in > one of the jobs listed on the background jobs overview. This is independent of > - the Koha instance (we tried it with two different instances on our server) > - whether you navigate to the background jobs overview via menu > "Administration > Manage background jobs" or when you just started a batch > operation (in our case batch item modification) and from there try to view the > job in the list. > > The corresponding message in the plack-error.log reads: > > Can't call method "GetPlugins" on an undefined value at > /usr/share/koha/lib/Koha/BackgroundJob.pm line 402. > > And this is line 402 in /usr/share/koha/lib/Koha/BackgroundJob.pm: > > my @plugins = Koha::Plugins->new()->GetPlugins( { method => > 'background_tasks', } ); > > Should we file a bug for this? > > Regards, > Anke > > > > -- > Anke Bruns M.A. (LIS) > Arbeitsgruppe "Anwendungs- und Informationssysteme" > E-Mail: anke.bruns at 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 at 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 > --------------------------------------- > > > > > > > -----Ursprüngliche Nachricht----- > > Von: Koha Im Auftrag von Michael Kuhn > > Gesendet: Mittwoch, 22. Juni 2022 08:53 > > An: koha at lists.katipo.co.nz > > Betreff: Re: [Koha] Background jobs in Koha menu "Administration" > > > > Hi Christopher > > > > Thanks for your meesage. You wrote: > > > > > With just a cursory look, I would assume something like 1/1 means 1 > > > job, 1 completed. Something like 2/1 would mean 2 jobs, 1 completed. > > > 0/0, I would assume, means there are no jobs. > > > > Yes this is also our assumption - but we ask ourselves if there is no > > job, why is there a line at all saying there is no job?! The library is > > afraid that maybe something went wrong in such a case. > > > > As said, unfortunately clicking the button "View" does not show more > > information like WHAT biblio or item exactly the job is referring to. > > > > 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 at adminkuhn.ch · W www.adminkuhn.ch > > > > > > > Message: 5 > > > Date: Mon, 20 Jun 2022 14:48:02 +0200 > > > From: Michael Kuhn > > > To: Koha > > > Subject: [Koha] Background jobs in Koha menu "Administration" > > > Message-ID: > > > Content-Type: text/plain; charset=UTF-8; format=flowed > > > > > > Hi > > > > > > We saw in Koha 22.05 there is a new Koha menu "Administration > Manage > > background jobs". Unfortunately there seems to be no entry in the Koha > manual > > 22.05 for it, also the context-sensitive help just leads to https://koha- > > community.org/manual//21.11/en/html/ (this is in an installation of Koha > > 22.05!). > > > > > > However the shown list has a column "progress" which can say "1/1" or > "0/0" > > for example. What does ist mean? Library personnel thinks "0/0" > > > suggests that something went wrong even if column "Status" says > "Finished". > > Unfortunately clicking the button "View" does not show more information like > > WHAT biblio or item exactly the entry is referring to. > > > > > > We saw that Bywater Solutions wrote an article about this new menu ( > > https://bywatersolutions.com/education/koha-21-11-background-jobs-and- > task- > > queue-enhancements > > > ) but our question is not answered there. Can someone please enlighten us > > what "0/0" means? > > > > > > Best wishes: Michael > > > _______________________________________________ > > > > > > Koha mailing list http://koha-community.org > > > Koha at lists.katipo.co.nz > > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha _______________________________________________ Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From jonathan.druart at bugs.koha-community.org Fri Jul 8 01:07:44 2022 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Thu, 7 Jul 2022 15:07:44 +0200 Subject: [Koha] Moving Curbside Pickup plugin to Koha core In-Reply-To: References: Message-ID: The patches are now ready for QA :) Le ven. 29 avr. 2022 à 09:39, Jonathan Druart a écrit : > > Hello, > > I have been sponsored to move the Curbside Pickup plugin to Koha core. > > If you are using this plugin and have enhancement requests or want to highlight some existing bugs, let us know on the bug report. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30650 > > I am aware of the different issues opened on the github repository of the project and will take them into account as much as I can. > > Regards, > Jonathan From s.graham4 at herts.ac.uk Fri Jul 8 02:13:08 2022 From: s.graham4 at herts.ac.uk (Stephen Graham) Date: Thu, 7 Jul 2022 14:13:08 +0000 Subject: [Koha] Notices and Library Question In-Reply-To: References: Message-ID: Thanks Katrin. It’s specifically the overdue notices that I was interested in. I can confirm, after testing, that the library assigned to the notice refers to the home library of the overdue item, not the home library of user who has the item. Stephen From: Koha On Behalf Of Katrin Fischer Sent: 06 July 2022 18:21 To: koha at lists.katipo.co.nz Subject: Re: [Koha] Notices and Library Question Hi Stephen, the circulation module includes a lot of different notices and I believe the behavior is probably not the same for each of them. For example the *DGST emails use the patron's home library, while a CHECKOUT notice will be sent from the library the staff member performing the checkout is logged in at. Hope this helps, Katrin On 06.07.22 15:42, Stephen Graham wrote: > Hi All - when you set the "Library" for a notice - a circulation notice more specifically, if it matters - is the library referring to the home library of the user or the home library that the item belongs to? Can't seem to work it out from the documentation. > > Stephen > > -------------------------------------- > Stephen Graham > Library Technology Consultant > Library and Computing Services > > University of Hertfordshire > Hatfield, Hertfordshire, AL10 9AB > > Email: s.graham4 at herts.ac.uk> > Website: herts.ac.uk > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha _______________________________________________ Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From Anke.Bruns at gwdg.de Fri Jul 8 03:30:45 2022 From: Anke.Bruns at gwdg.de (Bruns, Anke) Date: Thu, 7 Jul 2022 15:30:45 +0000 Subject: [Koha] Koha 22.05: Where has the columns setting for the patrons list gone? In-Reply-To: References: <61ced22e514b4b8a992809c8f65f2db5@gwdg.de> Message-ID: <5f49021f94e94fa18734b06a962ae270@gwdg.de> Hi Katrin, thank you! I meanwhile found out that in some list views in 22.05 the Columns button is present, in others not. I don't know if this was on purpose. The difference between 22.05 and 20.11 I stumbled upon is the following: - Home -> Patrons -> (Search for a list of patrons, or just all patrons) -> in V20.11 just above the table with the patrons list, there is a "Columns" link (it's not actually a "button") permitting to choose which columns of the patron record I want to display. In V22.11 this link is missing. Whereas: - Home -> Tools -> Patron lists -> (Choose one of the patron lists, if existent) -> in the table appearing here, the Columns link is there in 20.11 and in 22.05. Regards, Anke > -----Ursprüngliche Nachricht----- > Von: Koha Im Auftrag von Katrin Fischer > Gesendet: Mittwoch, 6. Juli 2022 19:18 > An: koha at lists.katipo.co.nz > Betreff: Re: [Koha] Koha 22.05: Where has the columns setting for the patrons > list gone? > > Hi Anke, > > in 22.05 the normal patron search is also used for the circulation > patron search. Maybe you meant that list? > > The settings are in Administration > Table settings > Patrons > > memberresultst > > Hope this helps, > > Katrin > > On 06.07.22 17:02, Bruns, Anke wrote: > > Hi, > > > > a minor problem but nonetheless...: In version 20.11 we had the possibility > > to choose in the staff client which columns from the patron record we wanted > > to display in the patrons short list. There was a "Columns" button next to > > the "Export" one. This option seems to have gone with one of the more recent > > versions (we upgraded directly from 20.11 to 22.05, so no idea when exactly > > this was the case). Instead there is a "Clear filter" button now. > > > > Is there any chance to get the choice of columns option back? E.g. we do not > > need or want to display the Date of Birth column which isn't populated in > > our case. > > > > Thank you for any advice and best regards, > > Anke > > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From CBRANNON at cdalibrary.org Fri Jul 8 04:04:45 2022 From: CBRANNON at cdalibrary.org (BRANNON, CHRISTOPHER) Date: Thu, 7 Jul 2022 16:04:45 +0000 Subject: [Koha] The Terrific Every-Other-Thursday Training Video - S2E20 - jQuery: Bootstrap Extras Message-ID: Badges? We don't need no badges. I don't have to show you any stinkin badges! But what I will show you are bootstrap badges and labels. https://youtu.be/GdmlmxkD8qA Christopher Brannon koha-US Vice President From itmanager at dhi-moskau.org Fri Jul 8 07:09:17 2022 From: itmanager at dhi-moskau.org (DHIM IT) Date: Thu, 7 Jul 2022 19:09:17 +0000 Subject: [Koha] Background jobs in Koha menu "Administration" In-Reply-To: References: <7e1bb0ff574449888fa979a137f43789@gwdg.de>, Message-ID: Hello Anke, my solution for the problem is to enable plugins in Koha-conf.xml file: 1 Mit besten Grüßen, Eugen Bastron ________________________________ Von: Koha im Auftrag von Bruns, Anke Gesendet: Thursday, July 7, 2022 1:55:58 PM An: koha at lists.katipo.co.nz Betreff: Re: [Koha] Background jobs in Koha menu "Administration" ... I forgot to mention that these jobs aren't executed either, but remain in the New status on the overview page. Regards, Anke > -----Ursprüngliche Nachricht----- > Von: Bruns, Anke <> > Gesendet: Donnerstag, 7. Juli 2022 12:52 > An: koha at lists.katipo.co.nz > Betreff: AW: [Koha] Background jobs in Koha menu "Administration" > > Hi, > > not sure if this belongs to this thread, but as it concerns > > /cgi-bin/koha/admin/background_jobs.pl > > it may fit in. > > We realized that in 22.05 there is a http 500 error when clicking on "View" in > one of the jobs listed on the background jobs overview. This is independent of > - the Koha instance (we tried it with two different instances on our server) > - whether you navigate to the background jobs overview via menu > "Administration > Manage background jobs" or when you just started a batch > operation (in our case batch item modification) and from there try to view the > job in the list. > > The corresponding message in the plack-error.log reads: > > Can't call method "GetPlugins" on an undefined value at > /usr/share/koha/lib/Koha/BackgroundJob.pm line 402. > > And this is line 402 in /usr/share/koha/lib/Koha/BackgroundJob.pm: > > my @plugins = Koha::Plugins->new()->GetPlugins( { method => > 'background_tasks', } ); > > Should we file a bug for this? > > Regards, > Anke > > > > -- > Anke Bruns M.A. (LIS) > Arbeitsgruppe "Anwendungs- und Informationssysteme" > E-Mail: anke.bruns at 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 at 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 > --------------------------------------- > > > > > > > -----Ursprüngliche Nachricht----- > > Von: Koha Im Auftrag von Michael Kuhn > > Gesendet: Mittwoch, 22. Juni 2022 08:53 > > An: koha at lists.katipo.co.nz > > Betreff: Re: [Koha] Background jobs in Koha menu "Administration" > > > > Hi Christopher > > > > Thanks for your meesage. You wrote: > > > > > With just a cursory look, I would assume something like 1/1 means 1 > > > job, 1 completed. Something like 2/1 would mean 2 jobs, 1 completed. > > > 0/0, I would assume, means there are no jobs. > > > > Yes this is also our assumption - but we ask ourselves if there is no > > job, why is there a line at all saying there is no job?! The library is > > afraid that maybe something went wrong in such a case. > > > > As said, unfortunately clicking the button "View" does not show more > > information like WHAT biblio or item exactly the job is referring to. > > > > 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 at adminkuhn.ch · W www.adminkuhn.ch > > > > > > > Message: 5 > > > Date: Mon, 20 Jun 2022 14:48:02 +0200 > > > From: Michael Kuhn > > > To: Koha > > > Subject: [Koha] Background jobs in Koha menu "Administration" > > > Message-ID: > > > Content-Type: text/plain; charset=UTF-8; format=flowed > > > > > > Hi > > > > > > We saw in Koha 22.05 there is a new Koha menu "Administration > Manage > > background jobs". Unfortunately there seems to be no entry in the Koha > manual > > 22.05 for it, also the context-sensitive help just leads to https://koha- > > community.org/manual//21.11/en/html/ (this is in an installation of Koha > > 22.05!). > > > > > > However the shown list has a column "progress" which can say "1/1" or > "0/0" > > for example. What does ist mean? Library personnel thinks "0/0" > > > suggests that something went wrong even if column "Status" says > "Finished". > > Unfortunately clicking the button "View" does not show more information like > > WHAT biblio or item exactly the entry is referring to. > > > > > > We saw that Bywater Solutions wrote an article about this new menu ( > > https://bywatersolutions.com/education/koha-21-11-background-jobs-and- > task- > > queue-enhancements > > > ) but our question is not answered there. Can someone please enlighten us > > what "0/0" means? > > > > > > Best wishes: Michael > > > _______________________________________________ > > > > > > Koha mailing list http://koha-community.org > > > Koha at lists.katipo.co.nz > > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha _______________________________________________ Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From katrin.fischer.83 at web.de Fri Jul 8 08:29:30 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Thu, 7 Jul 2022 22:29:30 +0200 Subject: [Koha] Empty PDF file when printing labels In-Reply-To: <20220707110009.Horde.sV2dWhUq2ub40_Tgs2-8Xsl@nc.teilgedanken.de> References: <20220707110009.Horde.sV2dWhUq2ub40_Tgs2-8Xsl@nc.teilgedanken.de> Message-ID: Hi Franz, if you open the file in a text editor instead of the PDF viewer, it might contain a readable error message. Hope this helps, Katrin On 07.07.22 13:00, Franz Dietrich wrote: > > Hey all, > I can't figure out the problem on my own right now. > > Problem: > Label creator ->manage->label batches->select one->export(full or single)->select the options->select PDF > A PDF-Editor opens but no pdf is shown. If I download the pdf it says corrupt (the file is 0 Bytes) > > I can't find any logs on the server mentioning an issue. The only thing I can find is - which is a 200 Responsecode...: > > http://redacted.cloud:80 http://192.168.20.174 - - [07/Jul/2022:07:15:01 +0000] "GET /cgi-bin/koha/labels/http://label-create-pdf.pl?batch_id=2&template_id=25&layout_id=24&start_label=1 HTTP/1.1" 200 308 "http://redacted.cloud/cgi-bin/koha/labels/label-print.pl" "Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0" > > what could be next steps to find the issue? > > > > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From cmkelleymls at gmail.com Fri Jul 8 10:38:33 2022 From: cmkelleymls at gmail.com (Charles Kelley) Date: Fri, 8 Jul 2022 07:38:33 +0900 Subject: [Koha] What Happened to Expired News Message-ID: Hello, all! My library is currently upgrading to v. 22.05 from v. 20.05. We can't find the expired news. We keep a lot of our news especially the announcements that are recyclable, e.g., "The catalog is down for maintenance" and "The library will be closed January 1, 2023, for New Year's." All we have to do to recycle is to change the display date range, maybe adjust the text as demonstrated in the holiday sample above, and voila! The edited announcement appears when it's supposed to and vanishes when it's supposed to. Right now, it seems we have to recompose the same announcement time and time again. We have sought a system preference, but alas! If it's there, it doesn't contain the keyword "news" or "announcement" and we cannot find it or guess what it might be called. In v. 22.05, we see a checkbox next to the surviving listings with a count of the entire list; and we see a count of the listings. So does anyone know how to revive an expired news listing? Many thanks for your kind consideration. -- よろしくお願いします。 -- Charles. Until 2022-07-15: Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 +81-80-4356-2178 [JPN cell] From 2022-07-18: Charles Kelley c/o Bob and Ronni DiGioia 147 Mitchel Drive Oakland, MD 21550 USA +1-301-741-7122 [US cell] mnogojazyk at aol.com [h] cmkelleymls at gmail.com [p] linkedin.com/in/cmkelleymls Meeting Your Information Needs. Virtually. From frank at sydt.com.tw Fri Jul 8 14:05:44 2022 From: frank at sydt.com.tw (SYDT - Frank Chou) Date: Fri, 8 Jul 2022 10:05:44 +0800 Subject: [Koha] Please help to set up 21.11 and 22.05 translation function Message-ID: Dear Sir/Madam, We have some people can help to translate during Summer period. We will focus on Chinese-Taiwan and China part, especially Taiwan. But we cannot see these two version in Koha Translation Project. Can someone help put them on? Thanks a lot... Best regards, Frank Chou ---------------------------------------------------------------------------------------------------------- 碩陽數位科技有限公司 Shou Yang Digital Technology Tel: 02-82280288 Fax: 02-82265022 10F. No. 166, Jianyi Rd., Chung Ho Dist., New Taipei City 23511, Taiwan, R.O.C. 23511新北市中和區建一路166號10F http://www.sydt.com.tw From dietrich at teilgedanken.de Fri Jul 8 16:56:52 2022 From: dietrich at teilgedanken.de (Franz Dietrich) Date: Fri, 8 Jul 2022 06:56:52 +0200 Subject: [Koha] Empty PDF file when printing labels In-Reply-To: References: <20220707110009.Horde.sV2dWhUq2ub40_Tgs2-8Xsl@nc.teilgedanken.de> Message-ID: Hi Katrin, Thank you for the hint but if I remember correctly the files really were empty. So no message/content at all. Is there some server side logging that should capture this? If so where do I find this? Thanks again Franz Dietrich Am 07.07.22 um 22:29 schrieb Katrin Fischer: > Hi Franz, > > if you open the file in a text editor instead of the PDF viewer, it > might contain a readable error message. > > Hope this helps, > > Katrin > > On 07.07.22 13:00, Franz Dietrich wrote: >> >> Hey all, >> I can't figure out the problem on my own right now. >> >> Problem: >> Label creator ->manage->label batches->select one->export(full or >> single)->select the options->select PDF >> A PDF-Editor opens but no pdf is shown. If I download the pdf it says >> corrupt (the file is 0 Bytes) >> >> I can't find any logs on the server mentioning an issue. The only >> thing I can find is - which is a 200 Responsecode...: >> >> http://redacted.cloud:80 http://192.168.20.174 - - >> [07/Jul/2022:07:15:01 +0000] "GET >> /cgi-bin/koha/labels/http://label-create-pdf.pl?batch_id=2&template_id=25&layout_id=24&start_label=1 >> HTTP/1.1" 200 308 >> "http://redacted.cloud/cgi-bin/koha/labels/label-print.pl" >> "Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0" >> >> what could be next steps to find the issue? >> >> >> >> >> _______________________________________________ >> >> Koha mailing list  http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list  http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From jonathan.druart at bugs.koha-community.org Fri Jul 8 18:26:28 2022 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Fri, 8 Jul 2022 08:26:28 +0200 Subject: [Koha] What Happened to Expired News In-Reply-To: References: Message-ID: Helle Charles, There is a checkbox "Show expired" on the left, tick it :) Regards, Jonathan Le ven. 8 juil. 2022 à 00:38, Charles Kelley a écrit : > > Hello, all! > > My library is currently upgrading to v. 22.05 from v. 20.05. We can't > find the expired news. > > We keep a lot of our news especially the announcements that are > recyclable, e.g., "The catalog is down for maintenance" and "The library > will be closed January 1, 2023, for New Year's." > > All we have to do to recycle is to change the display date range, maybe > adjust the text as demonstrated in the holiday sample above, and voila! The > edited announcement appears when it's supposed to and vanishes when it's > supposed to. Right now, it seems we have to recompose the same announcement > time and time again. > > We have sought a system preference, but alas! If it's there, it doesn't > contain the keyword "news" or "announcement" and we cannot find it or guess > what it might be called. In v. 22.05, we see a checkbox next to the > surviving listings with a count of the entire list; and we see a count of > the listings. > > So does anyone know how to revive an expired news listing? > > Many thanks for your kind consideration. > > -- > よろしくお願いします。 > > -- Charles. > > Until 2022-07-15: > Charles Kelley, MLS > PSC 704 Box 1029 > APO AP 96338 > +81-80-4356-2178 [JPN cell] > > From 2022-07-18: > Charles Kelley > c/o Bob and Ronni DiGioia > 147 Mitchel Drive > Oakland, MD 21550 USA > +1-301-741-7122 [US cell] > > mnogojazyk at aol.com [h] > cmkelleymls at gmail.com [p] > > linkedin.com/in/cmkelleymls > Meeting Your Information Needs. Virtually. > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From tomascohen at gmail.com Fri Jul 8 23:14:50 2022 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Fri, 8 Jul 2022 08:14:50 -0300 Subject: [Koha] Background jobs in Koha menu "Administration" In-Reply-To: References: <7e1bb0ff574449888fa979a137f43789@gwdg.de> Message-ID: I'm filling a report on bugzilla to provide a proper fix. Thanks El jue, 7 jul 2022 16:09, DHIM IT escribió: > Hello Anke, > > my solution for the problem is to enable plugins in Koha-conf.xml file: > > > 1 > > > > Mit besten Grüßen, > Eugen Bastron > ________________________________ > Von: Koha im Auftrag von Bruns, Anke < > Anke.Bruns at gwdg.de> > Gesendet: Thursday, July 7, 2022 1:55:58 PM > An: koha at lists.katipo.co.nz > Betreff: Re: [Koha] Background jobs in Koha menu "Administration" > > ... I forgot to mention that these jobs aren't executed either, but remain > in the New status on the overview page. > > Regards, > Anke > > > -----Ursprüngliche Nachricht----- > > Von: Bruns, Anke <> > > Gesendet: Donnerstag, 7. Juli 2022 12:52 > > An: koha at lists.katipo.co.nz > > Betreff: AW: [Koha] Background jobs in Koha menu "Administration" > > > > Hi, > > > > not sure if this belongs to this thread, but as it concerns > > > > /cgi-bin/koha/admin/background_jobs.pl > > > > it may fit in. > > > > We realized that in 22.05 there is a http 500 error when clicking on > "View" in > > one of the jobs listed on the background jobs overview. This is > independent of > > - the Koha instance (we tried it with two different instances on our > server) > > - whether you navigate to the background jobs overview via menu > > "Administration > Manage background jobs" or when you just started a > batch > > operation (in our case batch item modification) and from there try to > view the > > job in the list. > > > > The corresponding message in the plack-error.log reads: > > > > Can't call method "GetPlugins" on an undefined value at > > /usr/share/koha/lib/Koha/BackgroundJob.pm line 402. > > > > And this is line 402 in /usr/share/koha/lib/Koha/BackgroundJob.pm: > > > > my @plugins = Koha::Plugins->new()->GetPlugins( { method => > > 'background_tasks', } ); > > > > Should we file a bug for this? > > > > Regards, > > Anke > > > > > > > > -- > > Anke Bruns M.A. (LIS) > > Arbeitsgruppe "Anwendungs- und Informationssysteme" > > E-Mail: anke.bruns at 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 at 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 > > --------------------------------------- > > > > > > > > > > > > > -----Ursprüngliche Nachricht----- > > > Von: Koha Im Auftrag von Michael > Kuhn > > > Gesendet: Mittwoch, 22. Juni 2022 08:53 > > > An: koha at lists.katipo.co.nz > > > Betreff: Re: [Koha] Background jobs in Koha menu "Administration" > > > > > > Hi Christopher > > > > > > Thanks for your meesage. You wrote: > > > > > > > With just a cursory look, I would assume something like 1/1 means 1 > > > > job, 1 completed. Something like 2/1 would mean 2 jobs, 1 > completed. > > > > 0/0, I would assume, means there are no jobs. > > > > > > Yes this is also our assumption - but we ask ourselves if there is no > > > job, why is there a line at all saying there is no job?! The library is > > > afraid that maybe something went wrong in such a case. > > > > > > As said, unfortunately clicking the button "View" does not show more > > > information like WHAT biblio or item exactly the job is referring to. > > > > > > 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 at adminkuhn.ch · W www.adminkuhn.ch< > http://www.adminkuhn.ch> > > > > > > > > > > Message: 5 > > > > Date: Mon, 20 Jun 2022 14:48:02 +0200 > > > > From: Michael Kuhn > > > > To: Koha > > > > Subject: [Koha] Background jobs in Koha menu "Administration" > > > > Message-ID: > > > > Content-Type: text/plain; charset=UTF-8; format=flowed > > > > > > > > Hi > > > > > > > > We saw in Koha 22.05 there is a new Koha menu "Administration > > Manage > > > background jobs". Unfortunately there seems to be no entry in the Koha > > manual > > > 22.05 for it, also the context-sensitive help just leads to > https://koha- > > > community.org/manual//21.11/en/html/ (this is in an installation of > Koha > > > 22.05!). > > > > > > > > However the shown list has a column "progress" which can say "1/1" or > > "0/0" > > > for example. What does ist mean? Library personnel thinks "0/0" > > > > suggests that something went wrong even if column "Status" says > > "Finished". > > > Unfortunately clicking the button "View" does not show more > information like > > > WHAT biblio or item exactly the entry is referring to. > > > > > > > > We saw that Bywater Solutions wrote an article about this new menu ( > > > https://bywatersolutions.com/education/koha-21-11-background-jobs-and- > > task- > > > queue-enhancements > > > > ) but our question is not answered there. Can someone please > enlighten us > > > what "0/0" means? > > > > > > > > Best wishes: Michael > > > > _______________________________________________ > > > > > > > > Koha mailing list http://koha-community.org > > > > Koha at lists.katipo.co.nz > > > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > > > > > _______________________________________________ > > > > > > Koha mailing list http://koha-community.org > > > Koha at lists.katipo.co.nz > > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From tomascohen at gmail.com Fri Jul 8 23:19:20 2022 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Fri, 8 Jul 2022 08:19:20 -0300 Subject: [Koha] Background jobs in Koha menu "Administration" In-Reply-To: References: Message-ID: It is / There was an initial issue with indexing in Elasticsearch, that generated the 0/0. That's fixed already. El mar, 21 jun 2022 14:04, BRANNON, CHRISTOPHER escribió: > Michael, > With just a cursory look, I would assume something like 1/1 means > 1 job, 1 completed. Something like 2/1 would mean 2 jobs, 1 completed. > 0/0, I would assume, means there are no jobs. > ___________________________ > Christopher Brannon > IT Coordinator > > 702 E Front Ave > Coeur d'Alene, ID 83814 > (208)769-2315 Ext. 456 > cbrannon at cdalibrary.org > www.cdalibrary.org > Keep tabs on us at: > > Message: 5 > Date: Mon, 20 Jun 2022 14:48:02 +0200 > From: Michael Kuhn > To: Koha > Subject: [Koha] Background jobs in Koha menu "Administration" > Message-ID: > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi > > We saw in Koha 22.05 there is a new Koha menu "Administration > Manage > background jobs". Unfortunately there seems to be no entry in the Koha > manual 22.05 for it, also the context-sensitive help just leads to > https://koha-community.org/manual//21.11/en/html/ (this is in an > installation of Koha 22.05!). > > However the shown list has a column "progress" which can say "1/1" or > "0/0" for example. What does ist mean? Library personnel thinks "0/0" > suggests that something went wrong even if column "Status" says > "Finished". Unfortunately clicking the button "View" does not show more > information like WHAT biblio or item exactly the entry is referring to. > > We saw that Bywater Solutions wrote an article about this new menu ( > https://bywatersolutions.com/education/koha-21-11-background-jobs-and-task-queue-enhancements > ) but our question is not answered there. Can someone please enlighten us > what "0/0" means? > > Best wishes: Michael > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From knoakes at egrps.org Sat Jul 9 03:15:51 2022 From: knoakes at egrps.org (Kyle Noakes) Date: Fri, 8 Jul 2022 11:15:51 -0400 Subject: [Koha] Patron search not working after upgrade to version 22 In-Reply-To: References: Message-ID: I am having the same problem as Evan on Debian 10 (Buster) after the upgrade to 22.05.00 that has continued to 22.05.02. I did attempt to add Tomas's patch to my pagination file manually, but it did not work, although admittedly I have rarely needed to hand add any patch so I could have done something wrong. I was also unable to find any errors in the logs that mention long search strings before I tried the pagination fix anyway. I am unable to search for any patron string, not just long ones. I can't even click on a letter in the alphabet to search and receive any results. I did enable the API in administration. I can also see my branches in libraries. Thank you, Kyle Noakes Manager of Information Systems East Grand Rapids Public Schools 616-974-0157 On Wed, Jul 6, 2022 at 1:20 PM Tomas Cohen Arazi wrote: > This is certainly caused by a Koha bug I'm about to submit a patch for [1]. > The 22.05 release maintainer is AFK this week so he cannot release a new > version yet. > > Best regards. > > [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31104 > > El mié, 6 jul 2022 a las 13:43, Evan Stewart () > escribió: > > > Hello, > > > > I recently upgraded my Koka 21 to 22. Everything seemed to be working > fine > > until I tried searching for patrons. Using the intranet portal to search > > for patrons provides zero results. I see my patrons in the borrowers > > table, but the GUI won't display them. It's like the search function > sees > > no results. > > > > I upgraded to version 22.05.02, but the same problem still occurs. > > > > I'm using Raspberry Pi OS (Buster). > > > > I can add a new patron, but even the new patron does not show in the > search > > results. > > > > Is there a way to refresh the indexer that handles patron searching? Any > > other suggestions? > > > > -Evan Stewart > > Africa's Hope, USA > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > -- > Tomás Cohen Arazi > Theke Solutions (http://theke.io) > ✆ +54 9351 3513384 > GPG: B2F3C15F > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From vbovictor at gmail.com Sat Jul 9 04:36:34 2022 From: vbovictor at gmail.com (Victor Barroso Oliveira) Date: Fri, 8 Jul 2022 13:36:34 -0300 Subject: [Koha] How can I keep only one cover image in OPAC? Message-ID: Hello, How can I keep only one cover image in OPAC? I enabled the options OPACAmazonCoverImages and OPACLocalCoverImages From oleonard at myacpl.org Sat Jul 9 05:46:04 2022 From: oleonard at myacpl.org (Owen Leonard) Date: Fri, 8 Jul 2022 13:46:04 -0400 Subject: [Koha] How can I keep only one cover image in OPAC? In-Reply-To: References: Message-ID: > How can I keep only one cover image in OPAC? If you are using OPACAmazonCoverImages you're not keeping anything, you're loading the image directly from Amazon (if they have one with a matching ISBN). OPACLocalCoverImages allows you to manually upload a cover image for a record, so you have complete control over whether something has a local cover image. -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org From vbovictor at gmail.com Sat Jul 9 06:18:24 2022 From: vbovictor at gmail.com (Victor Barroso Oliveira) Date: Fri, 8 Jul 2022 15:18:24 -0300 Subject: [Koha] How can I keep only one cover image in OPAC? In-Reply-To: References: Message-ID: The question is when he retrieves an incorrect Amazon book cover. For this case, I choose to store the cover locally, but the opac displays both images (Amazon and local). In this case how could I remove only the cover presentation from Amazon. Em sex., 8 de jul. de 2022 às 14:46, Owen Leonard escreveu: > > How can I keep only one cover image in OPAC? > > If you are using OPACAmazonCoverImages you're not keeping anything, > you're loading the image directly from Amazon (if they have one with a > matching ISBN). > > OPACLocalCoverImages allows you to manually upload a cover image for a > record, so you have complete control over whether something has a > local cover image. > > -- Owen > > -- > Web Developer > Athens County Public Libraries > (740) 737-6006 > https://www.myacpl.org > From katrin.fischer.83 at web.de Sat Jul 9 06:36:50 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Fri, 8 Jul 2022 20:36:50 +0200 Subject: [Koha] Patron search not working after upgrade to version 22 In-Reply-To: References: Message-ID: Hi Kyle, the API settings in administration are not related to Koha's internal use of the API, so if you are not using the API exeternally, you can turn these off again. Did you test if the list of libraries is visible for you in administration? If the list doesn't show, your problem is probably not the bug Tomas mentioned. What does your /etc/apt/sources.list.d/koha.list entry look like? Hope this helps, Katrin On 08.07.22 17:15, Kyle Noakes wrote: > I am having the same problem as Evan on Debian 10 (Buster) after the > upgrade to 22.05.00 that has continued to 22.05.02. I did attempt to add > Tomas's patch to my pagination file manually, but it did not work, > although admittedly I have rarely needed to hand add any patch so I could > have done something wrong. I was also unable to find any errors in the logs > that mention long search strings before I tried the pagination fix anyway. > I am unable to search for any patron string, not just long ones. I can't > even click on a letter in the alphabet to search and receive any results. > > I did enable the API in administration. I can also see my branches in > libraries. > > Thank you, > > Kyle Noakes > Manager of Information Systems > East Grand Rapids Public Schools > 616-974-0157 > > > On Wed, Jul 6, 2022 at 1:20 PM Tomas Cohen Arazi > wrote: > >> This is certainly caused by a Koha bug I'm about to submit a patch for [1]. >> The 22.05 release maintainer is AFK this week so he cannot release a new >> version yet. >> >> Best regards. >> >> [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31104 >> >> El mié, 6 jul 2022 a las 13:43, Evan Stewart () >> escribió: >> >>> Hello, >>> >>> I recently upgraded my Koka 21 to 22. Everything seemed to be working >> fine >>> until I tried searching for patrons. Using the intranet portal to search >>> for patrons provides zero results. I see my patrons in the borrowers >>> table, but the GUI won't display them. It's like the search function >> sees >>> no results. >>> >>> I upgraded to version 22.05.02, but the same problem still occurs. >>> >>> I'm using Raspberry Pi OS (Buster). >>> >>> I can add a new patron, but even the new patron does not show in the >> search >>> results. >>> >>> Is there a way to refresh the indexer that handles patron searching? Any >>> other suggestions? >>> >>> -Evan Stewart >>> Africa's Hope, USA >>> _______________________________________________ >>> >>> Koha mailing list http://koha-community.org >>> Koha at lists.katipo.co.nz >>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >>> >> >> -- >> Tomás Cohen Arazi >> Theke Solutions (http://theke.io) >> ✆ +54 9351 3513384 >> GPG: B2F3C15F >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From egpetridis at gmail.com Sat Jul 9 07:46:40 2022 From: egpetridis at gmail.com (Manos PETRIDIS) Date: Fri, 8 Jul 2022 22:46:40 +0300 Subject: [Koha] Empty PDF file when printing labels In-Reply-To: References: <20220707110009.Horde.sV2dWhUq2ub40_Tgs2-8Xsl@nc.teilgedanken.de> Message-ID: Might bug 28806 be related? https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28806 Στις Παρ 8 Ιουλ 2022 στις 7:58 πμ ο χρήστης Franz Dietrich < dietrich at teilgedanken.de> έγραψε: > Hi Katrin, > > Thank you for the hint but if I remember correctly the files really were > empty. So no message/content at all. > Is there some server side logging that should capture this? If so where > do I find this? > > Thanks again > Franz Dietrich > > Am 07.07.22 um 22:29 schrieb Katrin Fischer: > > Hi Franz, > > > > if you open the file in a text editor instead of the PDF viewer, it > > might contain a readable error message. > > > > Hope this helps, > > > > Katrin > > > > On 07.07.22 13:00, Franz Dietrich wrote: > >> > >> Hey all, > >> I can't figure out the problem on my own right now. > >> > >> Problem: > >> Label creator ->manage->label batches->select one->export(full or > >> single)->select the options->select PDF > >> A PDF-Editor opens but no pdf is shown. If I download the pdf it says > >> corrupt (the file is 0 Bytes) > >> > >> I can't find any logs on the server mentioning an issue. The only > >> thing I can find is - which is a 200 Responsecode...: > >> > >> http://redacted.cloud:80 http://192.168.20.174 - - > >> [07/Jul/2022:07:15:01 +0000] "GET > >> /cgi-bin/koha/labels/ > http://label-create-pdf.pl?batch_id=2&template_id=25&layout_id=24&start_label=1 > >> HTTP/1.1" 200 308 > >> "http://redacted.cloud/cgi-bin/koha/labels/label-print.pl" > >> "Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0" > >> > >> what could be next steps to find the issue? > >> > >> > >> > >> > >> _______________________________________________ > >> > >> Koha mailing list http://koha-community.org > >> Koha at lists.katipo.co.nz > >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From ephetteplace at cca.edu Sat Jul 9 08:00:43 2022 From: ephetteplace at cca.edu (Eric Phetteplace) Date: Fri, 8 Jul 2022 13:00:43 -0700 Subject: [Koha] How can I keep only one cover image in OPAC? In-Reply-To: References: Message-ID: We've done this with jQuery in OpacUserJS. Whenever we have a local cover image, we prefer it. I don't understand the use case for displaying multiple cover images (they should be identical or one is wrong, no?). I'm away from my laptop but can share our script later, though I'm sure the new image display for opac-details breaks it. Best, Eric Phetteplace Systems Librarian California College of the Arts On Fri, Jul 8, 2022, 11:19 Victor Barroso Oliveira wrote: > The question is when he retrieves an incorrect Amazon book cover. > For this case, I choose to store the cover locally, but the opac displays > both images (Amazon and local). > In this case how could I remove only the cover presentation from Amazon. > > Em sex., 8 de jul. de 2022 às 14:46, Owen Leonard > escreveu: > > > > How can I keep only one cover image in OPAC? > > > > If you are using OPACAmazonCoverImages you're not keeping anything, > > you're loading the image directly from Amazon (if they have one with a > > matching ISBN). > > > > OPACLocalCoverImages allows you to manually upload a cover image for a > > record, so you have complete control over whether something has a > > local cover image. > > > > -- Owen > > > > -- > > Web Developer > > Athens County Public Libraries > > (740) 737-6006 > > https://www.myacpl.org > > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From dietrich at teilgedanken.de Sat Jul 9 17:26:01 2022 From: dietrich at teilgedanken.de (Franz Dietrich) Date: Sat, 9 Jul 2022 07:26:01 +0200 Subject: [Koha] Empty PDF file when printing labels In-Reply-To: References: <20220707110009.Horde.sV2dWhUq2ub40_Tgs2-8Xsl@nc.teilgedanken.de> Message-ID: <34521ee4-85a6-94d5-91c6-a18d00a8f548@teilgedanken.de> That is most likely the one... I was checking individual books to check it works at all but probably all of them had an encoding issue... Would there be an error somewhere if it was an encoding issue? I could try to fix it even though I do not know any perl. And thanks for the hint I did not find that bug yet! Franz Dietrich Am 08.07.22 um 21:46 schrieb Manos PETRIDIS: > Might bug 28806 be related? > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28806 > > > > Στις Παρ 8 Ιουλ 2022 στις 7:58 πμ ο χρήστης Franz Dietrich > > έγραψε: > > Hi Katrin, > > Thank you for the hint but if I remember correctly the files really > were > empty. So no message/content at all. > Is there some server side logging that should capture this? If so where > do I find this? > > Thanks again > Franz Dietrich > > Am 07.07.22 um 22:29 schrieb Katrin Fischer: > > Hi Franz, > > > > if you open the file in a text editor instead of the PDF viewer, it > > might contain a readable error message. > > > > Hope this helps, > > > > Katrin > > > > On 07.07.22 13:00, Franz Dietrich wrote: > >> > >> Hey all, > >> I can't figure out the problem on my own right now. > >> > >> Problem: > >> Label creator ->manage->label batches->select one->export(full or > >> single)->select the options->select PDF > >> A PDF-Editor opens but no pdf is shown. If I download the pdf it > says > >> corrupt (the file is 0 Bytes) > >> > >> I can't find any logs on the server mentioning an issue. The only > >> thing I can find is - which is a 200 Responsecode...: > >> > >> http://redacted.cloud:80 > http://192.168.20.174 - - > >> [07/Jul/2022:07:15:01 +0000] "GET > >> > /cgi-bin/koha/labels/http://label-create-pdf.pl?batch_id=2&template_id=25&layout_id=24&start_label=1 > > > >> HTTP/1.1" 200 308 > >> "http://redacted.cloud/cgi-bin/koha/labels/label-print.pl > " > >> "Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 > Firefox/102.0" > >> > >> what could be next steps to find the issue? > >> > >> > >> > >> > >> _______________________________________________ > >> > >> Koha mailing list http://koha-community.org > > >> Koha at lists.katipo.co.nz > >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > From egpetridis at gmail.com Sat Jul 9 18:58:55 2022 From: egpetridis at gmail.com (Manos PETRIDIS) Date: Sat, 9 Jul 2022 09:58:55 +0300 Subject: [Koha] Empty PDF file when printing labels In-Reply-To: <34521ee4-85a6-94d5-91c6-a18d00a8f548@teilgedanken.de> References: <20220707110009.Horde.sV2dWhUq2ub40_Tgs2-8Xsl@nc.teilgedanken.de> <34521ee4-85a6-94d5-91c6-a18d00a8f548@teilgedanken.de> Message-ID: You’re welcome, funny thing is quick (spine/ridge) labels print fine for those same items. Apparently there are different approaches between the two print procedures. MP Στις Σάβ 9 Ιουλ 2022 στις 8:26 πμ ο χρήστης Franz Dietrich < dietrich at teilgedanken.de> έγραψε: > That is most likely the one... I was checking individual books to check > it works at all but probably all of them had an encoding issue... > > Would there be an error somewhere if it was an encoding issue? I could > try to fix it even though I do not know any perl. > > And thanks for the hint I did not find that bug yet! > > Franz Dietrich > > Am 08.07.22 um 21:46 schrieb Manos PETRIDIS: > > Might bug 28806 be related? > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28806 > > > > > > > > Στις Παρ 8 Ιουλ 2022 στις 7:58 πμ ο χρήστης Franz Dietrich > > > έγραψε: > > > > Hi Katrin, > > > > Thank you for the hint but if I remember correctly the files really > > were > > empty. So no message/content at all. > > Is there some server side logging that should capture this? If so > where > > do I find this? > > > > Thanks again > > Franz Dietrich > > > > Am 07.07.22 um 22:29 schrieb Katrin Fischer: > > > Hi Franz, > > > > > > if you open the file in a text editor instead of the PDF viewer, > it > > > might contain a readable error message. > > > > > > Hope this helps, > > > > > > Katrin > > > > > > On 07.07.22 13:00, Franz Dietrich wrote: > > >> > > >> Hey all, > > >> I can't figure out the problem on my own right now. > > >> > > >> Problem: > > >> Label creator ->manage->label batches->select one->export(full or > > >> single)->select the options->select PDF > > >> A PDF-Editor opens but no pdf is shown. If I download the pdf it > > says > > >> corrupt (the file is 0 Bytes) > > >> > > >> I can't find any logs on the server mentioning an issue. The only > > >> thing I can find is - which is a 200 Responsecode...: > > >> > > >> http://redacted.cloud:80 > > http://192.168.20.174 - - > > >> [07/Jul/2022:07:15:01 +0000] "GET > > >> > > /cgi-bin/koha/labels/ > http://label-create-pdf.pl?batch_id=2&template_id=25&layout_id=24&start_label=1 > > < > http://label-create-pdf.pl?batch_id=2&template_id=25&layout_id=24&start_label=1 > > > > > > >> HTTP/1.1" 200 308 > > >> "http://redacted.cloud/cgi-bin/koha/labels/label-print.pl > > " > > >> "Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 > > Firefox/102.0" > > >> > > >> what could be next steps to find the issue? > > >> > > >> > > >> > > >> > > >> _______________________________________________ > > >> > > >> Koha mailing list http://koha-community.org > > > > >> Koha at lists.katipo.co.nz > > >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > _______________________________________________ > > > > > > Koha mailing list http://koha-community.org > > > > > Koha at lists.katipo.co.nz > > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > > _______________________________________________ > > > > Koha mailing list http://koha-community.org < > http://koha-community.org> > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > From ephetteplace at cca.edu Sun Jul 10 14:34:58 2022 From: ephetteplace at cca.edu (Eric Phetteplace) Date: Sat, 9 Jul 2022 19:34:58 -0700 Subject: [Koha] How can I keep only one cover image in OPAC? In-Reply-To: References: Message-ID: OK this is how we handle cover images on the search results and opac details pages: https://github.com/cca/koha_snippets/blob/main/catalog-js/double-cover-img.js let selector = $('.coverimages').length ? '.coverimages' : '#bookcover' if ($(selector).length && !!MutationObserver) { let observer = new MutationObserver((mutations) => { for (let mutation of mutations) { let covers = $(mutation.target).closest(selector) if (covers.find('[id*="-thumbnail"] img').length === 2) { covers.find('[id^="coce-thumbnail"]').remove() } } }) Array.from(document.querySelectorAll(selector)).forEach((el) => { observer.observe(el, { subtree: true, childList: true }) }) } It's more complicated than you'd expect because cover images from COCE are loaded asynchronously and, as far as I know, Koha doesn't give you any event hooks to know when they've loaded. So I set up a mutation observer to watch the cover image elements for both pages and remove the COCE one if there are two. I haven't tested if this works if you're using Amazon and local cover images but I assume, if it does not, it is a small adjustment. Best, ERIC PHETTEPLACE Systems Librarian, Libraries (he/him) ephetteplace at cca.edu | o 510.594.3660 (cca) 5212 Broadway | Oakland, CA | 94618 CCA is situated on the traditional unceded lands of the Ohlone peoples. Black-owned bookstores in Oakland: Ashay by the Bay , Marcus Books :(){ :|: & };: On Fri, Jul 8, 2022 at 1:00 PM Eric Phetteplace wrote: > We've done this with jQuery in OpacUserJS. Whenever we have a local cover > image, we prefer it. I don't understand the use case for displaying > multiple cover images (they should be identical or one is wrong, no?). I'm > away from my laptop but can share our script later, though I'm sure the new > image display for opac-details breaks it. > > Best, > Eric Phetteplace > Systems Librarian > California College of the Arts > > On Fri, Jul 8, 2022, 11:19 Victor Barroso Oliveira > wrote: > >> The question is when he retrieves an incorrect Amazon book cover. >> For this case, I choose to store the cover locally, but the opac displays >> both images (Amazon and local). >> In this case how could I remove only the cover presentation from Amazon. >> >> Em sex., 8 de jul. de 2022 às 14:46, Owen Leonard >> escreveu: >> >> > > How can I keep only one cover image in OPAC? >> > >> > If you are using OPACAmazonCoverImages you're not keeping anything, >> > you're loading the image directly from Amazon (if they have one with a >> > matching ISBN). >> > >> > OPACLocalCoverImages allows you to manually upload a cover image for a >> > record, so you have complete control over whether something has a >> > local cover image. >> > >> > -- Owen >> > >> > -- >> > Web Developer >> > Athens County Public Libraries >> > (740) 737-6006 >> > https://www.myacpl.org >> > >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> > From cmkelleymls at gmail.com Mon Jul 11 11:26:25 2022 From: cmkelleymls at gmail.com (Charles Kelley) Date: Mon, 11 Jul 2022 08:26:25 +0900 Subject: [Koha] What Happened to Expired News In-Reply-To: References: Message-ID: Hello, all! In our latest exchange, on 9 July 2022 at 09:01 [JST], I received this from Jonathan Druart : There is a checkbox "Show expired" on the left, tick it :) > A few others wrote with similar coaching. I must be obtuse. I expected the expired checkbox to be with the list of news items. Oh, well, thanks for the help. I found it. -- よろしくお願いします。 -- Charles. +81-80-4356-2178 [JPN cell] +1-301-741-7122 [US cell] mnogojazyk at aol.com [h] cmkelleymls at gmail.com [p] linkedin.com/in/cmkelleymls Meeting Your Information Needs. Virtually. From keith at thesorbos.com Mon Jul 11 14:42:51 2022 From: keith at thesorbos.com (Keith Sorbo) Date: Sun, 10 Jul 2022 21:42:51 -0500 Subject: [Koha] Site user lacks priviledges for koha-dump Message-ID: I am attempting to move my library instance to a new server using the koha-dump command When I run the command, I get Error: 'Access denied; you need (at least one of) the PROCESS privilege(s) for this operation' when trying to dump tablespaces How can I correct this? Keith From evanstewart406 at gmail.com Mon Jul 11 15:48:46 2022 From: evanstewart406 at gmail.com (Evan Stewart) Date: Sun, 10 Jul 2022 21:48:46 -0600 Subject: [Koha] Patron search not working after upgrade to version 22 In-Reply-To: References: Message-ID: Hi, I found the solution on Raspberry Pi OS (based on Debian 10). I noticed that after running apt upgrade two packages were held back: - libmojolicious-perl - libmojolicious-plugin-openapi-perl I didn't notice them before and probably wouldn't have noticed them had I not learned about the REST API and then read a little about it in the Koha documentation (thanks Katrin!). Once I saw the REST API references the OpenAPI format I figured these packages were the culprit. Also, I confirmed in my About Koha settings page that the Open API module was flagged as "not installed" after I upgraded to Koha 22. The solution for me was to install the two packages with apt. Not sure why they were held back using "apt upgrade", but running "sudo apt install libmojolicious-plugin-openapi-perl" called in all other dependent packages; including the upgrade for libmojolicious-perl and nine other new packages. I rebooted my Raspberry Pi, logged into Koha and all is good. The Open API module is listed as "Installed" in the About Koha settings page and the patron search and library listing is working. Kyle, hopefully this helps your machine. -Evan Stewart On Fri, Jul 8, 2022 at 12:37 PM Katrin Fischer wrote: > Hi Kyle, > > the API settings in administration are not related to Koha's internal > use of the API, so if you are not using the API exeternally, you can > turn these off again. > > Did you test if the list of libraries is visible for you in > administration? If the list doesn't show, your problem is probably not > the bug Tomas mentioned. > > What does your /etc/apt/sources.list.d/koha.list entry look like? > > Hope this helps, > > Katrin > > > On 08.07.22 17:15, Kyle Noakes wrote: > > I am having the same problem as Evan on Debian 10 (Buster) after the > > upgrade to 22.05.00 that has continued to 22.05.02. I did attempt to add > > Tomas's patch to my pagination file manually, but it did not work, > > although admittedly I have rarely needed to hand add any patch so I could > > have done something wrong. I was also unable to find any errors in the > logs > > that mention long search strings before I tried the pagination fix > anyway. > > I am unable to search for any patron string, not just long ones. I can't > > even click on a letter in the alphabet to search and receive any results. > > > > I did enable the API in administration. I can also see my branches in > > libraries. > > > > Thank you, > > > > Kyle Noakes > > Manager of Information Systems > > East Grand Rapids Public Schools > > 616-974-0157 > > > > > > On Wed, Jul 6, 2022 at 1:20 PM Tomas Cohen Arazi > > wrote: > > > >> This is certainly caused by a Koha bug I'm about to submit a patch for > [1]. > >> The 22.05 release maintainer is AFK this week so he cannot release a new > >> version yet. > >> > >> Best regards. > >> > >> [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31104 > >> > >> El mié, 6 jul 2022 a las 13:43, Evan Stewart ( >) > >> escribió: > >> > >>> Hello, > >>> > >>> I recently upgraded my Koka 21 to 22. Everything seemed to be working > >> fine > >>> until I tried searching for patrons. Using the intranet portal to > search > >>> for patrons provides zero results. I see my patrons in the borrowers > >>> table, but the GUI won't display them. It's like the search function > >> sees > >>> no results. > >>> > >>> I upgraded to version 22.05.02, but the same problem still occurs. > >>> > >>> I'm using Raspberry Pi OS (Buster). > >>> > >>> I can add a new patron, but even the new patron does not show in the > >> search > >>> results. > >>> > >>> Is there a way to refresh the indexer that handles patron searching? > Any > >>> other suggestions? > >>> > >>> -Evan Stewart > >>> Africa's Hope, USA > >>> _______________________________________________ > >>> > >>> Koha mailing list http://koha-community.org > >>> Koha at lists.katipo.co.nz > >>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > >>> > >> > >> -- > >> Tomás Cohen Arazi > >> Theke Solutions (http://theke.io) > >> ✆ +54 9351 3513384 > >> GPG: B2F3C15F > >> _______________________________________________ > >> > >> Koha mailing list http://koha-community.org > >> Koha at lists.katipo.co.nz > >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > >> > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From evanstewart406 at gmail.com Mon Jul 11 16:28:16 2022 From: evanstewart406 at gmail.com (Evan Stewart) Date: Sun, 10 Jul 2022 22:28:16 -0600 Subject: [Koha] Site user lacks priviledges for koha-dump In-Reply-To: References: Message-ID: Hi Keith, Try using "sudo" with the command and include the instance name of the library (For example, my library instance is named "catalog"). Sudo gives your account the extra admin privileges it needs to run the command. Anytime I run this command I type it as: sudo koha-dump catalog When prompted, I enter my Linux user account password because it has sudo privileges. If you don't know your library instance name, then run the command: sudo koha-list Your instance name (or instances if multiple are installed) will be listed. -Evan Stewart Africa's Hope, USA On Sun, Jul 10, 2022 at 8:43 PM Keith Sorbo wrote: > I am attempting to move my library instance to a new server using the > koha-dump command > > When I run the command, I get > > Error: 'Access denied; you need (at least one of) the PROCESS privilege(s) > for this operation' when trying to dump tablespaces > > How can I correct this? > > Keith > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From evanstewart406 at gmail.com Mon Jul 11 16:31:36 2022 From: evanstewart406 at gmail.com (Evan Stewart) Date: Sun, 10 Jul 2022 22:31:36 -0600 Subject: [Koha] Site user lacks priviledges for koha-dump In-Reply-To: References: Message-ID: Hi Keith, Sorry if my answer is too basic. You might have already tried these steps. Just starting with the extra basics to double check the easy items. My old helpdesk days are showing through. : ) -Evan On Sun, Jul 10, 2022 at 10:28 PM Evan Stewart wrote: > Hi Keith, > > Try using "sudo" with the command and include the instance name of the > library (For example, my library instance is named "catalog"). Sudo gives > your account the extra admin privileges it needs to run the command. > > Anytime I run this command I type it as: > > sudo koha-dump catalog > > When prompted, I enter my Linux user account password because it has sudo > privileges. > > If you don't know your library instance name, then run the command: > > sudo koha-list > > Your instance name (or instances if multiple are installed) will be listed. > > -Evan Stewart > Africa's Hope, USA > > On Sun, Jul 10, 2022 at 8:43 PM Keith Sorbo wrote: > >> I am attempting to move my library instance to a new server using the >> koha-dump command >> >> When I run the command, I get >> >> Error: 'Access denied; you need (at least one of) the PROCESS privilege(s) >> for this operation' when trying to dump tablespaces >> >> How can I correct this? >> >> Keith >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> > From mik at adminkuhn.ch Mon Jul 11 23:41:03 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Mon, 11 Jul 2022 13:41:03 +0200 Subject: [Koha] Failing authentication via CAS after update to Koha 21.11.09 Message-ID: <30f17401-5dc6-b07c-8db9-383c6d8b3376@adminkuhn.ch> Hi We are using Debian GNU/Linux 10 with Koha 21.11.09 (after an update from Debian 9 and Koha 19.05.02). Since the update the CAS authentication via Koha OPAC is no more working. The content of system preferences "OPACBaseURL", "casAuthentication", "casLogout" and "casServerUrl" has not changed; the new preference "casServerVersion" ist correctly set to "CAS 2 or earlier". It is possible to successfully log into the CAS server but when trying to access the Koha OPAC via CAS ("Log in using a CAS account") the response is always "Sorry, the CAS login failed." and the user is not logged into his Koha account. The logs don't show no error. I was checking all changes made in bugs 21973 22585 23771 20854 and 28417 but to no avail. Does anyone have an idea how to debug 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 at adminkuhn.ch · W www.adminkuhn.ch From keith at thesorbos.com Tue Jul 12 02:47:57 2022 From: keith at thesorbos.com (Keith Sorbo) Date: Mon, 11 Jul 2022 09:47:57 -0500 Subject: [Koha] Site user lacks priviledges for koha-dump In-Reply-To: References: Message-ID: Thanks, Evan, I am already running as root. I looked at the script and it pulls the mysql username and password from the library koha-config.xml. I am rather surprised that during installation, the koha system did not give sufficient grants to this user. Keith On Sun, Jul 10, 2022 at 11:28 PM Evan Stewart wrote: > Hi Keith, > > Try using "sudo" with the command and include the instance name of the > library (For example, my library instance is named "catalog"). Sudo gives > your account the extra admin privileges it needs to run the command. > > Anytime I run this command I type it as: > > sudo koha-dump catalog > > When prompted, I enter my Linux user account password because it has sudo > privileges. > > If you don't know your library instance name, then run the command: > > sudo koha-list > > Your instance name (or instances if multiple are installed) will be listed. > > -Evan Stewart > Africa's Hope, USA > > On Sun, Jul 10, 2022 at 8:43 PM Keith Sorbo wrote: > >> I am attempting to move my library instance to a new server using the >> koha-dump command >> >> When I run the command, I get >> >> Error: 'Access denied; you need (at least one of) the PROCESS privilege(s) >> for this operation' when trying to dump tablespaces >> >> How can I correct this? >> >> Keith >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> > From CBRANNON at cdalibrary.org Tue Jul 12 05:06:49 2022 From: CBRANNON at cdalibrary.org (BRANNON, CHRISTOPHER) Date: Mon, 11 Jul 2022 17:06:49 +0000 Subject: [Koha] What Happened to Expired News Message-ID: I must be obtuse as well. I would have expected the same thing. I understand why it is over there, but it blends in a bit with everything else. It seems like if it is an active filter, it should read "Hide expired contents" and be checked by default. ___________________________ Christopher Brannon IT Coordinator 702 E Front Ave Coeur d'Alene, ID 83814 (208)769-2315 Ext. 456 cbrannon at cdalibrary.org www.cdalibrary.org Keep tabs on us at:    >> I must be obtuse. I expected the expired checkbox to be with the list of news items. Oh, well, thanks for the help. I found it. From evanstewart406 at gmail.com Tue Jul 12 06:27:33 2022 From: evanstewart406 at gmail.com (Evan Stewart) Date: Mon, 11 Jul 2022 12:27:33 -0600 Subject: [Koha] Site user lacks priviledges for koha-dump In-Reply-To: References: Message-ID: Hi Keith, Thanks for the confirmation. I'm surprised too that the Koha install didn't get the higher privileges for the DB tables. That's why I thought it might be a Linux root issue because my Koha install gave privileges to root for all MariaDB tables. Were you able to solve the problem by granting more privileges to the mysql user? -Evan On Mon, Jul 11, 2022 at 8:48 AM Keith Sorbo wrote: > Thanks, Evan, > > I am already running as root. > > I looked at the script and it pulls the mysql username and password from > the library koha-config.xml. > > I am rather surprised that during installation, the koha system did not > give sufficient grants to this user. > > Keith > > On Sun, Jul 10, 2022 at 11:28 PM Evan Stewart > wrote: > >> Hi Keith, >> >> Try using "sudo" with the command and include the instance name of the >> library (For example, my library instance is named "catalog"). Sudo gives >> your account the extra admin privileges it needs to run the command. >> >> Anytime I run this command I type it as: >> >> sudo koha-dump catalog >> >> When prompted, I enter my Linux user account password because it has sudo >> privileges. >> >> If you don't know your library instance name, then run the command: >> >> sudo koha-list >> >> Your instance name (or instances if multiple are installed) will be >> listed. >> >> -Evan Stewart >> Africa's Hope, USA >> >> On Sun, Jul 10, 2022 at 8:43 PM Keith Sorbo wrote: >> >>> I am attempting to move my library instance to a new server using the >>> koha-dump command >>> >>> When I run the command, I get >>> >>> Error: 'Access denied; you need (at least one of) the PROCESS >>> privilege(s) >>> for this operation' when trying to dump tablespaces >>> >>> How can I correct this? >>> >>> Keith >>> _______________________________________________ >>> >>> Koha mailing list http://koha-community.org >>> Koha at lists.katipo.co.nz >>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >>> >> From evanstewart406 at gmail.com Tue Jul 12 07:04:57 2022 From: evanstewart406 at gmail.com (Evan Stewart) Date: Mon, 11 Jul 2022 13:04:57 -0600 Subject: [Koha] Patron search not working after upgrade to version 22 In-Reply-To: References: Message-ID: Correction to my apt install command in the previous reply. To fix, I upgraded "libmojolicious-perl" and " libmojolicious-plugin-openapi-perl" upgraded with it. I ran: sudo apt install libmojolicious-perl -Evan On Sun, Jul 10, 2022 at 9:48 PM Evan Stewart wrote: > Hi, > > I found the solution on Raspberry Pi OS (based on Debian 10). I noticed > that after running apt upgrade two packages were held back: > > - libmojolicious-perl > - libmojolicious-plugin-openapi-perl > > I didn't notice them before and probably wouldn't have noticed them had I > not learned about the REST API and then read a little about it in the Koha > documentation (thanks Katrin!). Once I saw the REST API references the > OpenAPI format I figured these packages were the culprit. Also, I > confirmed in my About Koha settings page that the Open API module was > flagged as "not installed" after I upgraded to Koha 22. > > The solution for me was to install the two packages with apt. Not sure > why they were held back using "apt upgrade", but running "sudo apt install > libmojolicious-plugin-openapi-perl" called in all other dependent packages; > including the upgrade for libmojolicious-perl and nine other new packages. > > I rebooted my Raspberry Pi, logged into Koha and all is good. The Open > API module is listed as "Installed" in the About Koha settings page and the > patron search and library listing is working. > > Kyle, hopefully this helps your machine. > > -Evan Stewart > > > > On Fri, Jul 8, 2022 at 12:37 PM Katrin Fischer > wrote: > >> Hi Kyle, >> >> the API settings in administration are not related to Koha's internal >> use of the API, so if you are not using the API exeternally, you can >> turn these off again. >> >> Did you test if the list of libraries is visible for you in >> administration? If the list doesn't show, your problem is probably not >> the bug Tomas mentioned. >> >> What does your /etc/apt/sources.list.d/koha.list entry look like? >> >> Hope this helps, >> >> Katrin >> >> >> On 08.07.22 17:15, Kyle Noakes wrote: >> > I am having the same problem as Evan on Debian 10 (Buster) after the >> > upgrade to 22.05.00 that has continued to 22.05.02. I did attempt to add >> > Tomas's patch to my pagination file manually, but it did not work, >> > although admittedly I have rarely needed to hand add any patch so I >> could >> > have done something wrong. I was also unable to find any errors in the >> logs >> > that mention long search strings before I tried the pagination fix >> anyway. >> > I am unable to search for any patron string, not just long ones. I can't >> > even click on a letter in the alphabet to search and receive any >> results. >> > >> > I did enable the API in administration. I can also see my branches in >> > libraries. >> > >> > Thank you, >> > >> > Kyle Noakes >> > Manager of Information Systems >> > East Grand Rapids Public Schools >> > 616-974-0157 >> > >> > >> > On Wed, Jul 6, 2022 at 1:20 PM Tomas Cohen Arazi >> > wrote: >> > >> >> This is certainly caused by a Koha bug I'm about to submit a patch for >> [1]. >> >> The 22.05 release maintainer is AFK this week so he cannot release a >> new >> >> version yet. >> >> >> >> Best regards. >> >> >> >> [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31104 >> >> >> >> El mié, 6 jul 2022 a las 13:43, Evan Stewart (< >> evanstewart406 at gmail.com>) >> >> escribió: >> >> >> >>> Hello, >> >>> >> >>> I recently upgraded my Koka 21 to 22. Everything seemed to be working >> >> fine >> >>> until I tried searching for patrons. Using the intranet portal to >> search >> >>> for patrons provides zero results. I see my patrons in the borrowers >> >>> table, but the GUI won't display them. It's like the search function >> >> sees >> >>> no results. >> >>> >> >>> I upgraded to version 22.05.02, but the same problem still occurs. >> >>> >> >>> I'm using Raspberry Pi OS (Buster). >> >>> >> >>> I can add a new patron, but even the new patron does not show in the >> >> search >> >>> results. >> >>> >> >>> Is there a way to refresh the indexer that handles patron searching? >> Any >> >>> other suggestions? >> >>> >> >>> -Evan Stewart >> >>> Africa's Hope, USA >> >>> _______________________________________________ >> >>> >> >>> Koha mailing list http://koha-community.org >> >>> Koha at lists.katipo.co.nz >> >>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> >>> >> >> >> >> -- >> >> Tomás Cohen Arazi >> >> Theke Solutions (http://theke.io) >> >> ✆ +54 9351 3513384 >> >> GPG: B2F3C15F >> >> _______________________________________________ >> >> >> >> Koha mailing list http://koha-community.org >> >> Koha at lists.katipo.co.nz >> >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> >> >> > _______________________________________________ >> > >> > Koha mailing list http://koha-community.org >> > Koha at lists.katipo.co.nz >> > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> > From tomascohen at gmail.com Tue Jul 12 07:15:26 2022 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Mon, 11 Jul 2022 16:15:26 -0300 Subject: [Koha] Patron search not working after upgrade to version 22 In-Reply-To: References: Message-ID: New package version requires new library versions. You should use 'dist-upgrade' when jumping between mayor versions of Koha so new dependencies are pulled. When you upgrade between minor versions, this shouldn't be needed, but it has happened recently that fixing bugs sometimes requires upgrading libraries as well. Keep it in mind I'm glad you sorted it out El lun, 11 jul 2022 a las 16:06, Evan Stewart () escribió: > Correction to my apt install command in the previous reply. > > To fix, I upgraded "libmojolicious-perl" and " > libmojolicious-plugin-openapi-perl" upgraded with it. > > I ran: sudo apt install libmojolicious-perl > > -Evan > > On Sun, Jul 10, 2022 at 9:48 PM Evan Stewart > wrote: > > > Hi, > > > > I found the solution on Raspberry Pi OS (based on Debian 10). I noticed > > that after running apt upgrade two packages were held back: > > > > - libmojolicious-perl > > - libmojolicious-plugin-openapi-perl > > > > I didn't notice them before and probably wouldn't have noticed them had I > > not learned about the REST API and then read a little about it in the > Koha > > documentation (thanks Katrin!). Once I saw the REST API references the > > OpenAPI format I figured these packages were the culprit. Also, I > > confirmed in my About Koha settings page that the Open API module was > > flagged as "not installed" after I upgraded to Koha 22. > > > > The solution for me was to install the two packages with apt. Not sure > > why they were held back using "apt upgrade", but running "sudo apt > install > > libmojolicious-plugin-openapi-perl" called in all other dependent > packages; > > including the upgrade for libmojolicious-perl and nine other new > packages. > > > > I rebooted my Raspberry Pi, logged into Koha and all is good. The Open > > API module is listed as "Installed" in the About Koha settings page and > the > > patron search and library listing is working. > > > > Kyle, hopefully this helps your machine. > > > > -Evan Stewart > > > > > > > > On Fri, Jul 8, 2022 at 12:37 PM Katrin Fischer > > > wrote: > > > >> Hi Kyle, > >> > >> the API settings in administration are not related to Koha's internal > >> use of the API, so if you are not using the API exeternally, you can > >> turn these off again. > >> > >> Did you test if the list of libraries is visible for you in > >> administration? If the list doesn't show, your problem is probably not > >> the bug Tomas mentioned. > >> > >> What does your /etc/apt/sources.list.d/koha.list entry look like? > >> > >> Hope this helps, > >> > >> Katrin > >> > >> > >> On 08.07.22 17:15, Kyle Noakes wrote: > >> > I am having the same problem as Evan on Debian 10 (Buster) after the > >> > upgrade to 22.05.00 that has continued to 22.05.02. I did attempt to > add > >> > Tomas's patch to my pagination file manually, but it did not work, > >> > although admittedly I have rarely needed to hand add any patch so I > >> could > >> > have done something wrong. I was also unable to find any errors in the > >> logs > >> > that mention long search strings before I tried the pagination fix > >> anyway. > >> > I am unable to search for any patron string, not just long ones. I > can't > >> > even click on a letter in the alphabet to search and receive any > >> results. > >> > > >> > I did enable the API in administration. I can also see my branches in > >> > libraries. > >> > > >> > Thank you, > >> > > >> > Kyle Noakes > >> > Manager of Information Systems > >> > East Grand Rapids Public Schools > >> > 616-974-0157 > >> > > >> > > >> > On Wed, Jul 6, 2022 at 1:20 PM Tomas Cohen Arazi < > tomascohen at gmail.com> > >> > wrote: > >> > > >> >> This is certainly caused by a Koha bug I'm about to submit a patch > for > >> [1]. > >> >> The 22.05 release maintainer is AFK this week so he cannot release a > >> new > >> >> version yet. > >> >> > >> >> Best regards. > >> >> > >> >> [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31104 > >> >> > >> >> El mié, 6 jul 2022 a las 13:43, Evan Stewart (< > >> evanstewart406 at gmail.com>) > >> >> escribió: > >> >> > >> >>> Hello, > >> >>> > >> >>> I recently upgraded my Koka 21 to 22. Everything seemed to be > working > >> >> fine > >> >>> until I tried searching for patrons. Using the intranet portal to > >> search > >> >>> for patrons provides zero results. I see my patrons in the > borrowers > >> >>> table, but the GUI won't display them. It's like the search > function > >> >> sees > >> >>> no results. > >> >>> > >> >>> I upgraded to version 22.05.02, but the same problem still occurs. > >> >>> > >> >>> I'm using Raspberry Pi OS (Buster). > >> >>> > >> >>> I can add a new patron, but even the new patron does not show in the > >> >> search > >> >>> results. > >> >>> > >> >>> Is there a way to refresh the indexer that handles patron searching? > >> Any > >> >>> other suggestions? > >> >>> > >> >>> -Evan Stewart > >> >>> Africa's Hope, USA > >> >>> _______________________________________________ > >> >>> > >> >>> Koha mailing list http://koha-community.org > >> >>> Koha at lists.katipo.co.nz > >> >>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > >> >>> > >> >> > >> >> -- > >> >> Tomás Cohen Arazi > >> >> Theke Solutions (http://theke.io) > >> >> ✆ +54 9351 3513384 > >> >> GPG: B2F3C15F > >> >> _______________________________________________ > >> >> > >> >> Koha mailing list http://koha-community.org > >> >> Koha at lists.katipo.co.nz > >> >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > >> >> > >> > _______________________________________________ > >> > > >> > Koha mailing list http://koha-community.org > >> > Koha at lists.katipo.co.nz > >> > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > >> _______________________________________________ > >> > >> Koha mailing list http://koha-community.org > >> Koha at lists.katipo.co.nz > >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > >> > > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F From keith at thesorbos.com Tue Jul 12 07:34:38 2022 From: keith at thesorbos.com (Keith Sorbo) Date: Mon, 11 Jul 2022 14:34:38 -0500 Subject: [Koha] Site user lacks priviledges for koha-dump In-Reply-To: References: Message-ID: I haven't yet figured out what privileges are needed. On Mon, Jul 11, 2022 at 1:27 PM Evan Stewart wrote: > Hi Keith, > > Thanks for the confirmation. I'm surprised too that the Koha install > didn't get the higher privileges for the DB tables. That's why I thought > it might be a Linux root issue because my Koha install gave privileges to > root for all MariaDB tables. > > Were you able to solve the problem by granting more privileges to the > mysql user? > > -Evan > > On Mon, Jul 11, 2022 at 8:48 AM Keith Sorbo wrote: > >> Thanks, Evan, >> >> I am already running as root. >> >> I looked at the script and it pulls the mysql username and password from >> the library koha-config.xml. >> >> I am rather surprised that during installation, the koha system did not >> give sufficient grants to this user. >> >> Keith >> >> On Sun, Jul 10, 2022 at 11:28 PM Evan Stewart >> wrote: >> >>> Hi Keith, >>> >>> Try using "sudo" with the command and include the instance name of the >>> library (For example, my library instance is named "catalog"). Sudo gives >>> your account the extra admin privileges it needs to run the command. >>> >>> Anytime I run this command I type it as: >>> >>> sudo koha-dump catalog >>> >>> When prompted, I enter my Linux user account password because it has >>> sudo privileges. >>> >>> If you don't know your library instance name, then run the command: >>> >>> sudo koha-list >>> >>> Your instance name (or instances if multiple are installed) will be >>> listed. >>> >>> -Evan Stewart >>> Africa's Hope, USA >>> >>> On Sun, Jul 10, 2022 at 8:43 PM Keith Sorbo wrote: >>> >>>> I am attempting to move my library instance to a new server using the >>>> koha-dump command >>>> >>>> When I run the command, I get >>>> >>>> Error: 'Access denied; you need (at least one of) the PROCESS >>>> privilege(s) >>>> for this operation' when trying to dump tablespaces >>>> >>>> How can I correct this? >>>> >>>> Keith >>>> _______________________________________________ >>>> >>>> Koha mailing list http://koha-community.org >>>> Koha at lists.katipo.co.nz >>>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >>>> >>> From evanstewart406 at gmail.com Tue Jul 12 07:53:40 2022 From: evanstewart406 at gmail.com (Evan Stewart) Date: Mon, 11 Jul 2022 13:53:40 -0600 Subject: [Koha] Patron search not working after upgrade to version 22 In-Reply-To: References: Message-ID: Hi Tomas, Thank you for the tip. I'll keep the dist-upgrade in mind. -Evan On Mon, Jul 11, 2022 at 1:15 PM Tomas Cohen Arazi wrote: > New package version requires new library versions. You should use > 'dist-upgrade' when jumping between mayor versions of Koha so new > dependencies are pulled. > When you upgrade between minor versions, this shouldn't be needed, but it > has happened recently that fixing bugs sometimes requires upgrading > libraries as well. > > Keep it in mind > > I'm glad you sorted it out > > El lun, 11 jul 2022 a las 16:06, Evan Stewart () > escribió: > >> Correction to my apt install command in the previous reply. >> >> To fix, I upgraded "libmojolicious-perl" and " >> libmojolicious-plugin-openapi-perl" upgraded with it. >> >> I ran: sudo apt install libmojolicious-perl >> >> -Evan >> >> On Sun, Jul 10, 2022 at 9:48 PM Evan Stewart >> wrote: >> >> > Hi, >> > >> > I found the solution on Raspberry Pi OS (based on Debian 10). I noticed >> > that after running apt upgrade two packages were held back: >> > >> > - libmojolicious-perl >> > - libmojolicious-plugin-openapi-perl >> > >> > I didn't notice them before and probably wouldn't have noticed them had >> I >> > not learned about the REST API and then read a little about it in the >> Koha >> > documentation (thanks Katrin!). Once I saw the REST API references the >> > OpenAPI format I figured these packages were the culprit. Also, I >> > confirmed in my About Koha settings page that the Open API module was >> > flagged as "not installed" after I upgraded to Koha 22. >> > >> > The solution for me was to install the two packages with apt. Not sure >> > why they were held back using "apt upgrade", but running "sudo apt >> install >> > libmojolicious-plugin-openapi-perl" called in all other dependent >> packages; >> > including the upgrade for libmojolicious-perl and nine other new >> packages. >> > >> > I rebooted my Raspberry Pi, logged into Koha and all is good. The Open >> > API module is listed as "Installed" in the About Koha settings page and >> the >> > patron search and library listing is working. >> > >> > Kyle, hopefully this helps your machine. >> > >> > -Evan Stewart >> > >> > >> > >> > On Fri, Jul 8, 2022 at 12:37 PM Katrin Fischer < >> katrin.fischer.83 at web.de> >> > wrote: >> > >> >> Hi Kyle, >> >> >> >> the API settings in administration are not related to Koha's internal >> >> use of the API, so if you are not using the API exeternally, you can >> >> turn these off again. >> >> >> >> Did you test if the list of libraries is visible for you in >> >> administration? If the list doesn't show, your problem is probably not >> >> the bug Tomas mentioned. >> >> >> >> What does your /etc/apt/sources.list.d/koha.list entry look like? >> >> >> >> Hope this helps, >> >> >> >> Katrin >> >> >> >> >> >> On 08.07.22 17:15, Kyle Noakes wrote: >> >> > I am having the same problem as Evan on Debian 10 (Buster) after the >> >> > upgrade to 22.05.00 that has continued to 22.05.02. I did attempt to >> add >> >> > Tomas's patch to my pagination file manually, but it did not work, >> >> > although admittedly I have rarely needed to hand add any patch so I >> >> could >> >> > have done something wrong. I was also unable to find any errors in >> the >> >> logs >> >> > that mention long search strings before I tried the pagination fix >> >> anyway. >> >> > I am unable to search for any patron string, not just long ones. I >> can't >> >> > even click on a letter in the alphabet to search and receive any >> >> results. >> >> > >> >> > I did enable the API in administration. I can also see my branches in >> >> > libraries. >> >> > >> >> > Thank you, >> >> > >> >> > Kyle Noakes >> >> > Manager of Information Systems >> >> > East Grand Rapids Public Schools >> >> > 616-974-0157 >> >> > >> >> > >> >> > On Wed, Jul 6, 2022 at 1:20 PM Tomas Cohen Arazi < >> tomascohen at gmail.com> >> >> > wrote: >> >> > >> >> >> This is certainly caused by a Koha bug I'm about to submit a patch >> for >> >> [1]. >> >> >> The 22.05 release maintainer is AFK this week so he cannot release a >> >> new >> >> >> version yet. >> >> >> >> >> >> Best regards. >> >> >> >> >> >> [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31104 >> >> >> >> >> >> El mié, 6 jul 2022 a las 13:43, Evan Stewart (< >> >> evanstewart406 at gmail.com>) >> >> >> escribió: >> >> >> >> >> >>> Hello, >> >> >>> >> >> >>> I recently upgraded my Koka 21 to 22. Everything seemed to be >> working >> >> >> fine >> >> >>> until I tried searching for patrons. Using the intranet portal to >> >> search >> >> >>> for patrons provides zero results. I see my patrons in the >> borrowers >> >> >>> table, but the GUI won't display them. It's like the search >> function >> >> >> sees >> >> >>> no results. >> >> >>> >> >> >>> I upgraded to version 22.05.02, but the same problem still occurs. >> >> >>> >> >> >>> I'm using Raspberry Pi OS (Buster). >> >> >>> >> >> >>> I can add a new patron, but even the new patron does not show in >> the >> >> >> search >> >> >>> results. >> >> >>> >> >> >>> Is there a way to refresh the indexer that handles patron >> searching? >> >> Any >> >> >>> other suggestions? >> >> >>> >> >> >>> -Evan Stewart >> >> >>> Africa's Hope, USA >> >> >>> _______________________________________________ >> >> >>> >> >> >>> Koha mailing list http://koha-community.org >> >> >>> Koha at lists.katipo.co.nz >> >> >>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> >> >>> >> >> >> >> >> >> -- >> >> >> Tomás Cohen Arazi >> >> >> Theke Solutions (http://theke.io) >> >> >> ✆ +54 9351 3513384 >> >> >> GPG: B2F3C15F >> >> >> _______________________________________________ >> >> >> >> >> >> Koha mailing list http://koha-community.org >> >> >> Koha at lists.katipo.co.nz >> >> >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> >> >> >> >> > _______________________________________________ >> >> > >> >> > Koha mailing list http://koha-community.org >> >> > Koha at lists.katipo.co.nz >> >> > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> >> _______________________________________________ >> >> >> >> Koha mailing list http://koha-community.org >> >> Koha at lists.katipo.co.nz >> >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> >> >> > >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> > > > -- > Tomás Cohen Arazi > Theke Solutions (http://theke.io) > ✆ +54 9351 3513384 > GPG: B2F3C15F > From Barbara.Johnson at bedfordtx.gov Tue Jul 12 08:22:35 2022 From: Barbara.Johnson at bedfordtx.gov (Barbara Johnson) Date: Mon, 11 Jul 2022 20:22:35 +0000 Subject: [Koha] Benefits of attending KohaCon22 in person Message-ID: Benefits of attending KohaCon22 in person Networking - build strong relationships with your peers through face-to-face interactions which can result in long-lasting, supportive professional connections New perspectives - getting out of the office, changing your environment, and going on a mission to seek support and education will help you come back to the workplace rejuvenated Brainstorming - in person events inspire people to think creatively, share ideas, engage in problem solving, and push their own boundaries Risk taking - invest in yourself, step outside your comfort zone, challenge yourself in a new environment, put yourself out there and get noticed, meet new people who can open doors to success Engagement - attending a conference in person increases engagement and participation by encouraging you to be fully present. In person attendees benefit from eye-to-eye contact, non-verbal cues and body language that leads to a more fluid and dynamic exchange of ideas and collaboration. Fun - incredible eateries, history-making breweries, and a vibrant arts and culture scene are just a few of the reasons to visit Lawrence, Kansas in person. Register for the conference here - https://koha-us.org/events/conferences/kohacon22/#tab1 Barbara Johnson koha-US President, 2022 KohaCon22 Conference Chair CONFIDENTIALITY NOTICE: This City of Bedford (CoB) email transmission is intended only for the use of the individual to whom it is addressed and may contain information that is confidential, privileged, and exempt from disclosure. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you have received this email in error, please notify the sender immediately by return email and destroy all electronic and paper copies of the original message and any attachments immediately. From mtj at kohaaloha.com Tue Jul 12 15:16:02 2022 From: mtj at kohaaloha.com (Mason James) Date: Tue, 12 Jul 2022 15:16:02 +1200 Subject: [Koha] Site user lacks priviledges for koha-dump In-Reply-To: References: Message-ID: <9396a7bb-4385-7098-6cec-309ba2f8f62a@kohaaloha.com> hi Keith the following command shows the user's privs, for an instance called 'dev1'...  mysql> SHOW GRANTS FOR 'koha_dev1'@'localhost'\G the following command grants the required privs...  mysql> GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, REFERENCES, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, EVENT, TRIGGER ON `koha_dev1`.* TO `koha_dev1`@`localhost`; you'll need to replace 'dev1' with your instance's name On 12/07/22 7:34 am, Keith Sorbo wrote: > I haven't yet figured out what privileges are needed. > > On Mon, Jul 11, 2022 at 1:27 PM Evan Stewart > wrote: > >> Hi Keith, >> >> Thanks for the confirmation. I'm surprised too that the Koha install >> didn't get the higher privileges for the DB tables. That's why I thought >> it might be a Linux root issue because my Koha install gave privileges to >> root for all MariaDB tables. >> >> Were you able to solve the problem by granting more privileges to the >> mysql user? >> >> -Evan >> >> On Mon, Jul 11, 2022 at 8:48 AM Keith Sorbo wrote: >> >>> Thanks, Evan, >>> >>> I am already running as root. >>> >>> I looked at the script and it pulls the mysql username and password from >>> the library koha-config.xml. >>> >>> I am rather surprised that during installation, the koha system did not >>> give sufficient grants to this user. >>> >>> Keith >>> >>> On Sun, Jul 10, 2022 at 11:28 PM Evan Stewart >>> wrote: >>> >>>> Hi Keith, >>>> >>>> Try using "sudo" with the command and include the instance name of the >>>> library (For example, my library instance is named "catalog"). Sudo gives >>>> your account the extra admin privileges it needs to run the command. >>>> >>>> Anytime I run this command I type it as: >>>> >>>> sudo koha-dump catalog >>>> >>>> When prompted, I enter my Linux user account password because it has >>>> sudo privileges. >>>> >>>> If you don't know your library instance name, then run the command: >>>> >>>> sudo koha-list >>>> >>>> Your instance name (or instances if multiple are installed) will be >>>> listed. >>>> >>>> -Evan Stewart >>>> Africa's Hope, USA >>>> >>>> On Sun, Jul 10, 2022 at 8:43 PM Keith Sorbo wrote: >>>> >>>>> I am attempting to move my library instance to a new server using the >>>>> koha-dump command >>>>> >>>>> When I run the command, I get >>>>> >>>>> Error: 'Access denied; you need (at least one of) the PROCESS >>>>> privilege(s) >>>>> for this operation' when trying to dump tablespaces >>>>> >>>>> How can I correct this? >>>>> >>>>> Keith >>>>> _______________________________________________ >>>>> >>>>> Koha mailing list http://koha-community.org >>>>> Koha at lists.katipo.co.nz >>>>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >>>>> > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From mtj at kohaaloha.com Tue Jul 12 15:22:26 2022 From: mtj at kohaaloha.com (Mason James) Date: Tue, 12 Jul 2022 15:22:26 +1200 Subject: [Koha] Site user lacks priviledges for koha-dump In-Reply-To: <9396a7bb-4385-7098-6cec-309ba2f8f62a@kohaaloha.com> References: <9396a7bb-4385-7098-6cec-309ba2f8f62a@kohaaloha.com> Message-ID: aah... if you look at koha-create, it simply assigns ALL privs so that's the easier fix :) mysql> GRANT ALL PRIVILEGES ON `koha_dev1`.* TO `koha_dev1`@`localhost`; mysql> FLUSH PRIVILEGES; On 12/07/22 3:16 pm, Mason James wrote: > hi Keith > > the following command shows the user's privs, for an instance called 'dev1'... >  mysql> SHOW GRANTS FOR 'koha_dev1'@'localhost'\G > > > the following command grants the required privs... >  mysql> GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, REFERENCES, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, EVENT, TRIGGER ON `koha_dev1`.* TO `koha_dev1`@`localhost`; > > > you'll need to replace 'dev1' with your instance's name > > > > On 12/07/22 7:34 am, Keith Sorbo wrote: >> I haven't yet figured out what privileges are needed. >> >> On Mon, Jul 11, 2022 at 1:27 PM Evan Stewart >> wrote: >> >>> Hi Keith, >>> >>> Thanks for the confirmation.  I'm surprised too that the Koha install >>> didn't get the higher privileges for the DB tables.  That's why I thought >>> it might be a Linux root issue because my Koha install gave privileges to >>> root for all MariaDB tables. >>> >>> Were you able to solve the problem by granting more privileges to the >>> mysql user? >>> >>> -Evan >>> >>> On Mon, Jul 11, 2022 at 8:48 AM Keith Sorbo wrote: >>> >>>> Thanks, Evan, >>>> >>>> I am already running as root. >>>> >>>> I looked at the script and it pulls the mysql username and password from >>>> the library koha-config.xml. >>>> >>>> I am rather surprised that during installation, the koha system did not >>>> give sufficient grants to this user. >>>> >>>> Keith >>>> >>>> On Sun, Jul 10, 2022 at 11:28 PM Evan Stewart >>>> wrote: >>>> >>>>> Hi Keith, >>>>> >>>>> Try using "sudo" with the command and include the instance name of the >>>>> library (For example, my library instance is named "catalog"). Sudo gives >>>>> your account the extra admin privileges it needs to run the command. >>>>> >>>>> Anytime I run this command I type it as: >>>>> >>>>> sudo koha-dump catalog >>>>> >>>>> When prompted, I enter my Linux user account password because it has >>>>> sudo privileges. >>>>> >>>>> If you don't know your library instance name, then run the command: >>>>> >>>>> sudo koha-list >>>>> >>>>> Your instance name (or instances if multiple are installed) will be >>>>> listed. >>>>> >>>>> -Evan Stewart >>>>> Africa's Hope, USA >>>>> >>>>> On Sun, Jul 10, 2022 at 8:43 PM Keith Sorbo wrote: >>>>> >>>>>> I am attempting to move my library instance to a new server using the >>>>>> koha-dump command >>>>>> >>>>>> When I run the command, I get >>>>>> >>>>>> Error: 'Access denied; you need (at least one of) the PROCESS >>>>>> privilege(s) >>>>>> for this operation' when trying to dump tablespaces >>>>>> >>>>>> How can I correct this? >>>>>> >>>>>> Keith >>>>>> _______________________________________________ >>>>>> >>>>>> Koha mailing list  http://koha-community.org >>>>>> Koha at lists.katipo.co.nz >>>>>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >>>>>> >> _______________________________________________ >> >> Koha mailing list  http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From toni.afandi at gmail.com Tue Jul 12 15:41:59 2022 From: toni.afandi at gmail.com (Toni Afandi) Date: Tue, 12 Jul 2022 10:41:59 +0700 Subject: [Koha] Searching in Koha Message-ID: Hello everyone, This is a long annoying thing I found in Koha. Everytime we click a subject that contains a subfield, we get no results. Say we have a subject that contains a subfield like this : Religions -- Relations (‡aReligions‡xRelations). When I click on that subject, Koha says : "No results found!" searching box become : (su,complete-subfield:{Religions}) AND (su,complete-subfield:{Relations.}) Any thoughts? We use Koha 20.11.18.000 with Zebra. Regards. *Toni Afandi* *Librarian* *STT SAAT* From katrin.fischer.83 at web.de Tue Jul 12 22:22:01 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Tue, 12 Jul 2022 12:22:01 +0200 Subject: [Koha] Searching in Koha In-Reply-To: References: Message-ID: <7f812a9d-941b-96a6-08d6-96f3d13115f1@web.de> Hi Toni, have a look at the TraceSubjectSubdivisions and TraceCompleteSubfields system preference. Maybe playing with the different settings will give you better results. Hope this helps Katrin || On 12.07.22 05:41, Toni Afandi wrote: > Hello everyone, > > This is a long annoying thing I found in Koha. Everytime we click a > subject that contains a subfield, we get no results. > Say we have a subject that contains a subfield like this : Religions -- > Relations (‡aReligions‡xRelations). > > When I click on that subject, Koha says : "No results found!" > searching box become : (su,complete-subfield:{Religions}) AND > (su,complete-subfield:{Relations.}) > > Any thoughts? > > We use Koha 20.11.18.000 with Zebra. > > Regards. > > > *Toni Afandi* > *Librarian* > *STT SAAT* > _______________________________________________ > > Koha mailing listhttp://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha From aedwarddurai at gmail.com Tue Jul 12 23:27:22 2022 From: aedwarddurai at gmail.com (edward durai) Date: Tue, 12 Jul 2022 16:57:22 +0530 Subject: [Koha] to import bulk book details - please advise Message-ID: Hi Koha Team, We Organization has 5000 books. I just wanted to import duplicate entry for 5000 books using import excel. is it possible? so that we can edit and update whenever we have time. is there any other possibility to enter 5000 books quickly? thanks, edward From toni.afandi at gmail.com Wed Jul 13 01:01:48 2022 From: toni.afandi at gmail.com (Toni Afandi) Date: Tue, 12 Jul 2022 20:01:48 +0700 Subject: [Koha] Searching in Koha In-Reply-To: <7f812a9d-941b-96a6-08d6-96f3d13115f1@web.de> References: <7f812a9d-941b-96a6-08d6-96f3d13115f1@web.de> Message-ID: Dear Katrin, Thank you for your suggestion. It works now. I set TraceSubjectSubdivisions to Include and TraceCompleteSubfields to Don't force. You're the best! *Toni Afandi* *Librarian* *STT SAAT* On Tue, Jul 12, 2022 at 5:22 PM Katrin Fischer wrote: > Hi Toni, > > have a look at the TraceSubjectSubdivisions and TraceCompleteSubfields > system preference. Maybe playing with the different settings will give > you better results. > > Hope this helps > > Katrin > || > > On 12.07.22 05:41, Toni Afandi wrote: > > Hello everyone, > > > > This is a long annoying thing I found in Koha. Everytime we click a > > subject that contains a subfield, we get no results. > > Say we have a subject that contains a subfield like this : Religions -- > > Relations (‡aReligions‡xRelations). > > < > http://opac.seabs.ac.id/cgi-bin/koha/opac-authoritiesdetail.pl?authid=62971 > > > > When I click on that subject, Koha says : "No results found!" > > searching box become : (su,complete-subfield:{Religions}) AND > > (su,complete-subfield:{Relations.}) > > > > Any thoughts? > > > > We use Koha 20.11.18.000 with Zebra. > > > > Regards. > > > > > > *Toni Afandi* > > *Librarian* > > *STT SAAT* > > _______________________________________________ > > > > Koha mailing listhttp://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From Anke.Bruns at gwdg.de Wed Jul 13 01:42:51 2022 From: Anke.Bruns at gwdg.de (Bruns, Anke) Date: Tue, 12 Jul 2022 13:42:51 +0000 Subject: [Koha] to import bulk book details - please advise In-Reply-To: References: Message-ID: <595597ad84614215bbaa3bcf7c1279ac@gwdg.de> Hi Edward, could you please explain your request a bit more? Do you explicitly want to import 5000 title records as duplicates of 5000 existing records, so as a result there are 10000 records? Or did you mean import the same data with deduplication in the process, so that the 5000 existing records are overwritten? What exactly would you like to know about Excel import? Best regards, Anke > -----Ursprüngliche Nachricht----- > Von: Koha Im Auftrag von edward durai > Gesendet: Dienstag, 12. Juli 2022 13:27 > An: koha at lists.katipo.co.nz > Betreff: [Koha] to import bulk book details - please advise > > Hi Koha Team, > We Organization has 5000 books. I just wanted to import duplicate entry for > 5000 books using import excel. > > is it possible? so that we can edit and update whenever we have time. > > is there any other possibility to enter 5000 books quickly? > > thanks, > edward > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From isabel.pineda at ds.edu.sv Wed Jul 13 03:05:47 2022 From: isabel.pineda at ds.edu.sv (Isabel Pineda) Date: Tue, 12 Jul 2022 15:05:47 +0000 Subject: [Koha] Empty PDF file when printing labels In-Reply-To: <20220707110009.Horde.sV2dWhUq2ub40_Tgs2-8Xsl@nc.teilgedanken.de> References: <20220707110009.Horde.sV2dWhUq2ub40_Tgs2-8Xsl@nc.teilgedanken.de> Message-ID: Hi. I am experiencing this problem when I try to print a single label and I reported a bug: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29994 When I add another label and export the label batch, everything works. Maybe this is the case with you too? Best regards Isabel -----Mensaje original----- De: Koha En nombre de Franz Dietrich Enviado el: jueves, 7 de julio de 2022 05:00 Para: Comunidad Koha (koha at lists.katipo.co.nz) Asunto: [Koha] Empty PDF file when printing labels   Hey all, I can't figure out the problem on my own right now.   Problem: Label creator ->manage->label batches->select one->export(full or single)->select the options->select PDF A PDF-Editor opens but no pdf is shown. If I download the pdf it says corrupt (the file is 0 Bytes)   I can't find any logs on the server mentioning an issue. The only thing I can find is - which is a 200 Responsecode...:   http://redacted.cloud:80 http://192.168.20.174 - - [07/Jul/2022:07:15:01 +0000] "GET /cgi-bin/koha/labels/http://label-create-pdf.pl?batch_id=2&template_id=25&layout_id=24&start_label=1 HTTP/1.1" 200 308 "http://redacted.cloud/cgi-bin/koha/labels/label-print.pl" "Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0"   what could be next steps to find the issue?       _______________________________________________ Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From caroline.cyr-la-rose at inlibro.com Wed Jul 13 04:27:29 2022 From: caroline.cyr-la-rose at inlibro.com (Caroline Cyr La Rose) Date: Tue, 12 Jul 2022 12:27:29 -0400 Subject: [Koha] Empty PDF file when printing labels In-Reply-To: References: <20220707110009.Horde.sV2dWhUq2ub40_Tgs2-8Xsl@nc.teilgedanken.de> Message-ID: <6a0f81ab-074f-4c44-c785-0585d6c7ac51@inlibro.com> Hello all, I just tried this in 22.05 and master and I was able to reproduce the problem. For me, it seems to only occur if you click on the 'Export' button in the table. The two other buttons ('Export full batch' and 'Export selected items') worked well for me even if there was only one label in the batch. I added the test plan in Isabel's bug report. I wasn't able to reproduce Franz's problem, however, which seems to be happening with all buttons. Caroline On 2022-07-12 11:05, Isabel Pineda wrote: > Hi. > I am experiencing this problem when I try to print a single label and I reported a bug:https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29994 > When I add another label and export the label batch, everything works. Maybe this is the case with you too? > > Best regards > Isabel > > > > -----Mensaje original----- > De: Koha En nombre de Franz Dietrich > Enviado el: jueves, 7 de julio de 2022 05:00 > Para: Comunidad Koha (koha at lists.katipo.co.nz) > Asunto: [Koha] Empty PDF file when printing labels > > > Hey all, > I can't figure out the problem on my own right now. > > Problem: > Label creator ->manage->label batches->select one->export(full or single)->select the options->select PDF A PDF-Editor opens but no pdf is shown. If I download the pdf it says corrupt (the file is 0 Bytes) > > I can't find any logs on the server mentioning an issue. The only thing I can find is - which is a 200 Responsecode...: > > http://redacted.cloud:80 http://192.168.20.174 - - [07/Jul/2022:07:15:01 +0000] "GET /cgi-bin/koha/labels/http://label-create-pdf.pl?batch_id=2&template_id=25&layout_id=24&start_label=1 HTTP/1.1" 200 308"http://redacted.cloud/cgi-bin/koha/labels/label-print.pl" "Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0" > > what could be next steps to find the issue? > > > > > _______________________________________________ > > Koha mailing listhttp://koha-community.org Koha at lists.katipo.co.nz > Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing listhttp://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha Caroline Cyr La Rose, M.L.I.S. Librarian | Product Manager Phone: 1-833-465-4276, ext. 221 Caroline.Cyr-La-Rose at inLibro.com INLiBRO | Document Technologies Specialists | www.inLibro.com From schulera at caryinstitute.org Wed Jul 13 05:04:28 2022 From: schulera at caryinstitute.org (Amy Schuler) Date: Tue, 12 Jul 2022 13:04:28 -0400 Subject: [Koha] KOHA and linked data? Message-ID: Hi all, forgive the question if this has been discussed to death already, and I missed it. What is the latest development(s) on linked data in KOHA? I see on the wiki here https://wiki.koha-community.org/wiki/Linked_Data_RFC and here https://wiki.koha-community.org/wiki/A_First_Step_Towards_RDF_in_Koha_RFC that some planning has taken place. I'm interested in whether anything in that 'work that needs to be done" has occurred. Doesn't look like those pages have been updated since 2017. Thanks! -- Amy C. Schuler (she/her) Director, Information Services & Library Cary Institute of Ecosystem Studies | 2801 Sharon Turnpike | Millbrook, NY www.caryinstitute.org From Heather_Hernandez at nps.gov Wed Jul 13 05:36:52 2022 From: Heather_Hernandez at nps.gov (Hernandez, Heather H) Date: Tue, 12 Jul 2022 17:36:52 +0000 Subject: [Koha] KOHA and linked data? In-Reply-To: References: Message-ID: Hi, Amy! Can​ one discuss linked data to death?!? I think not! (Says the cataloger!:) ) It comes up a lot at our Koha-US Cataloging Special Interest Group meetings, and we're always happy about to chat about it and Koha there--please feel free to join us (info at the Koha-US calendar site, Calendar – koha-US , and you don't have to be a member to join in, or even in the U.S.!) There are bugs in Bugzilla related to BIBFRAME: Bug List (koha-community.org) And it's being developed and used, e.g., at our last SIG (recordings of them are on the Koha-US YouTube channel!), this article came up from April 2022--not Koha, but EBSCO & Novelist activities: EBSCO and Novelist use BIBFRAME to facilitate discoverability -- Breeding, Marshall [Library Technology Guides] (And since a lot of Koha users are also EBSCO users, might be of interest?) And this is a good update on the Library of Congress' use of BIBFRAME: https://youtu.be/pjr056DMpZc From what I've seen, BIBFRAME is super-neato-cool! And MARC21-BIBFRAME conversion is around and happening. But, IMO, the sheer volume of data in MARC21 is going to make it viable for a looooooooooooong time. (And, just FYI, "Koha" is a Maori word, according to The Koha Logo : Origins and Explanation - Koha Wiki (koha-community.org) it means, "The word Koha is a maori word meaning gift or donation - or perhaps more "giving your specialty to the collective event". Possibly even a sense of quid pro quo. In traditional maori society (and still) you would bring a koha (Contribution) to an event like a funeral or wedding or big meeting, often food or the specialty of your region. When it's your turn to hold an event all your guests will bring a Koha, to ease the burden of catering for a lot of people.") Cheerio! --h2 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ms. Heather Hernandez (she, her, hers) Technical Services Librarian Library catalog: https://keys.bywatersolutions.com/ San Francisco Maritime National Historical Park Research Center 2 Marina Blvd., Bldg. E, 3rd floor, San Francisco, CA 94123-1284 415-561-7032 (office generally Tu-W & F, telecommuting M&Th) heather_hernandez at nps.gov From secretary at koha-us.org Wed Jul 13 06:21:14 2022 From: secretary at koha-us.org (Jennifer Marlatt) Date: Tue, 12 Jul 2022 11:21:14 -0700 Subject: [Koha] koha-US General Meeting reminder: Wednesday, July 13, 2022 Message-ID: The next koha-US general meeting is *tomorrow, *Wednesday, July 13, 2022. When: 8:30a PT / 11:30a ET / 16:30 UTC (time converter ) Where: https://us02web.zoom.us/j/648572897?pwd=TUpsRE1TYlFPWWxTWFl4TVovSTJ3Zz09 Agenda: https://docs.google.com/document/d/1AoZyJg6DMGiJys4CcmeL6IzGHSriwtPvRbqxE20nzA4/edit?usp=sharing If you have additional topics for the agenda, please send them to secretary at 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 at koha-us.org From mamcet.library10 at gmail.com Wed Jul 13 15:51:37 2022 From: mamcet.library10 at gmail.com (MASTeR Library) Date: Wed, 13 Jul 2022 09:21:37 +0530 Subject: [Koha] to import bulk book details - please advise In-Reply-To: <595597ad84614215bbaa3bcf7c1279ac@gwdg.de> References: <595597ad84614215bbaa3bcf7c1279ac@gwdg.de> Message-ID: How to Book Bibliography Data Convert Excel to MARC format https://www.youtube.com/watch?v=92bdWN054R0 On Tue, Jul 12, 2022 at 7:13 PM Bruns, Anke wrote: > Hi Edward, > > could you please explain your request a bit more? > > Do you explicitly want to import 5000 title records as duplicates of 5000 > existing records, so as a result there are 10000 records? Or did you mean > import the same data with deduplication in the process, so that the 5000 > existing records are overwritten? > > What exactly would you like to know about Excel import? > > Best regards, > Anke > > > > -----Ursprüngliche Nachricht----- > > Von: Koha Im Auftrag von edward durai > > Gesendet: Dienstag, 12. Juli 2022 13:27 > > An: koha at lists.katipo.co.nz > > Betreff: [Koha] to import bulk book details - please advise > > > > Hi Koha Team, > > We Organization has 5000 books. I just wanted to import duplicate entry > for > > 5000 books using import excel. > > > > is it possible? so that we can edit and update whenever we have time. > > > > is there any other possibility to enter 5000 books quickly? > > > > thanks, > > edward > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > -- Thanking you.. Librarian, MAMCET Trichy-Chennai Trunk Road, Siruganur, Tiruchirappalli-621 105. From grishavkumar at gmail.com Wed Jul 13 16:56:19 2022 From: grishavkumar at gmail.com (Rishav Kumar Gond) Date: Wed, 13 Jul 2022 10:26:19 +0530 Subject: [Koha] Availability of open source sms driver. Message-ID: Hi all, Is there any open source sms driver available to integrate with Koha so that we can send sms to our patrons. Location is India. Thanks and regards Rishav From mik at adminkuhn.ch Wed Jul 13 19:07:03 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Wed, 13 Jul 2022 09:07:03 +0200 Subject: [Koha] Call for news - Newsletter July 2022 Message-ID: Hi I'm collecting news for the July 2022 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 -- 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 at adminkuhn.ch · W www.adminkuhn.ch From Anke.Bruns at gwdg.de Thu Jul 14 01:07:57 2022 From: Anke.Bruns at gwdg.de (Bruns, Anke) Date: Wed, 13 Jul 2022 13:07:57 +0000 Subject: [Koha] Background jobs in Koha menu "Administration" In-Reply-To: References: <7e1bb0ff574449888fa979a137f43789@gwdg.de>, Message-ID: Hi Eugen, thanks a lot, this solved the problem for us, too. Best regards, Anke > -----Ursprüngliche Nachricht----- > Von: DHIM IT > Gesendet: Donnerstag, 7. Juli 2022 21:09 > An: Bruns, Anke ; koha at lists.katipo.co.nz > Betreff: Re: [Koha] Background jobs in Koha menu "Administration" > > Hello Anke, > > my solution for the problem is to enable plugins in Koha-conf.xml file: > > > 1 > > > > > Mit besten Grüßen, > Eugen Bastron > ________________________________ > > Von: Koha im Auftrag von Bruns, Anke > > Gesendet: Thursday, July 7, 2022 1:55:58 PM > An: koha at lists.katipo.co.nz > Betreff: Re: [Koha] Background jobs in Koha menu "Administration" > > ... I forgot to mention that these jobs aren't executed either, but remain in > the New status on the overview page. > > Regards, > Anke > > > -----Ursprüngliche Nachricht----- > > Von: Bruns, Anke <> > > Gesendet: Donnerstag, 7. Juli 2022 12:52 > > An: koha at lists.katipo.co.nz > > Betreff: AW: [Koha] Background jobs in Koha menu "Administration" > > > > Hi, > > > > not sure if this belongs to this thread, but as it concerns > > > > /cgi-bin/koha/admin/background_jobs.pl > > > > it may fit in. > > > > We realized that in 22.05 there is a http 500 error when clicking on "View" > in > > one of the jobs listed on the background jobs overview. This is > independent of > > - the Koha instance (we tried it with two different instances on our server) > > - whether you navigate to the background jobs overview via menu > > "Administration > Manage background jobs" or when you just started a > batch > > operation (in our case batch item modification) and from there try to view > the > > job in the list. > > > > The corresponding message in the plack-error.log reads: > > > > Can't call method "GetPlugins" on an undefined value at > > /usr/share/koha/lib/Koha/BackgroundJob.pm line 402. > > > > And this is line 402 in /usr/share/koha/lib/Koha/BackgroundJob.pm: > > > > my @plugins = Koha::Plugins->new()->GetPlugins( { method => > > 'background_tasks', } ); > > > > Should we file a bug for this? > > > > Regards, > > Anke > > > > > > > > -- > > Anke Bruns M.A. (LIS) > > Arbeitsgruppe "Anwendungs- und Informationssysteme" > > E-Mail: anke.bruns at 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 at 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 > > --------------------------------------- > > > > > > > > > > > > > -----Ursprüngliche Nachricht----- > > > Von: Koha Im Auftrag von Michael > Kuhn > > > Gesendet: Mittwoch, 22. Juni 2022 08:53 > > > An: koha at lists.katipo.co.nz > > > Betreff: Re: [Koha] Background jobs in Koha menu "Administration" > > > > > > Hi Christopher > > > > > > Thanks for your meesage. You wrote: > > > > > > > With just a cursory look, I would assume something like 1/1 means 1 > > > > job, 1 completed. Something like 2/1 would mean 2 jobs, 1 completed. > > > > 0/0, I would assume, means there are no jobs. > > > > > > Yes this is also our assumption - but we ask ourselves if there is no > > > job, why is there a line at all saying there is no job?! The library is > > > afraid that maybe something went wrong in such a case. > > > > > > As said, unfortunately clicking the button "View" does not show more > > > information like WHAT biblio or item exactly the job is referring to. > > > > > > 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 at adminkuhn.ch · W www.adminkuhn.ch > > > > > > > > > > > Message: 5 > > > > Date: Mon, 20 Jun 2022 14:48:02 +0200 > > > > From: Michael Kuhn > > > > To: Koha > > > > Subject: [Koha] Background jobs in Koha menu "Administration" > > > > Message-ID: > > > > Content-Type: text/plain; charset=UTF-8; format=flowed > > > > > > > > Hi > > > > > > > > We saw in Koha 22.05 there is a new Koha menu "Administration > > Manage > > > background jobs". Unfortunately there seems to be no entry in the Koha > > manual > > > 22.05 for it, also the context-sensitive help just leads to https://koha- > > > > community.org/manual//21.11/en/html/ (this is in an installation of > Koha > > > 22.05!). > > > > > > > > However the shown list has a column "progress" which can say "1/1" or > > "0/0" > > > for example. What does ist mean? Library personnel thinks "0/0" > > > > suggests that something went wrong even if column "Status" says > > "Finished". > > > Unfortunately clicking the button "View" does not show more > information like > > > WHAT biblio or item exactly the entry is referring to. > > > > > > > > We saw that Bywater Solutions wrote an article about this new menu ( > > > https://bywatersolutions.com/education/koha-21-11-background-jobs- > and- jobs-and-> > > task- > > > queue-enhancements > > > > ) but our question is not answered there. Can someone please > enlighten us > > > what "0/0" means? > > > > > > > > Best wishes: Michael > > > > _______________________________________________ > > > > > > > > Koha mailing list http://koha-community.org > > > > Koha at lists.katipo.co.nz > > > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > > > > > _______________________________________________ > > > > > > Koha mailing list http://koha-community.org > > > Koha at lists.katipo.co.nz > > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From viliam.polonec at snk.sk Thu Jul 14 01:52:46 2022 From: viliam.polonec at snk.sk (Viliam Polonec) Date: Wed, 13 Jul 2022 15:52:46 +0200 Subject: [Koha] KOHA repeatable item subfield Message-ID: <50f3b1d2-24c0-8d9f-8630-b6a4d8fd9bcd@snk.sk> Hi Is it possible to have in KOHA repeatable subfields in items, for example 952$z public note. I know that it's possible to add checkbox in bibliographic framework but I don't know if koha is suitable with that thank you regards Viliam From aedwarddurai at gmail.com Thu Jul 14 01:54:57 2022 From: aedwarddurai at gmail.com (edward durai) Date: Wed, 13 Jul 2022 19:24:57 +0530 Subject: [Koha] to import bulk book details - please advise In-Reply-To: <595597ad84614215bbaa3bcf7c1279ac@gwdg.de> References: <595597ad84614215bbaa3bcf7c1279ac@gwdg.de> Message-ID: its fresh entry. please share if you have excel template to import On Tue, Jul 12, 2022 at 7:12 PM Bruns, Anke wrote: > Hi Edward, > > could you please explain your request a bit more? > > Do you explicitly want to import 5000 title records as duplicates of 5000 > existing records, so as a result there are 10000 records? Or did you mean > import the same data with deduplication in the process, so that the 5000 > existing records are overwritten? > > What exactly would you like to know about Excel import? > > Best regards, > Anke > > > > -----Ursprüngliche Nachricht----- > > Von: Koha Im Auftrag von edward durai > > Gesendet: Dienstag, 12. Juli 2022 13:27 > > An: koha at lists.katipo.co.nz > > Betreff: [Koha] to import bulk book details - please advise > > > > Hi Koha Team, > > We Organization has 5000 books. I just wanted to import duplicate entry > for > > 5000 books using import excel. > > > > is it possible? so that we can edit and update whenever we have time. > > > > is there any other possibility to enter 5000 books quickly? > > > > thanks, > > edward > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From Anke.Bruns at gwdg.de Thu Jul 14 02:00:15 2022 From: Anke.Bruns at gwdg.de (Bruns, Anke) Date: Wed, 13 Jul 2022 14:00:15 +0000 Subject: [Koha] Batch item modification, problem with location Message-ID: <0120a12270c0466f853d5c241f142359@gwdg.de> Hi, when I try to modify a batch of items to assign a location (authorized value LOC, would be 952$c) to them, there are in the dropdown list of possible locations only those belonging to a different branch from the branch my items belong to (as both their home and holding branch). Thus, I cannot assign my desired location via batch item modification. I stumbled upon this in 20.11 and 22.05. I would expect to see either all locations from the LOC authorized value in the dropdown list (requiring some mindfulness when batch assigning them to items), or those belonging to the items' respective home and/or holding branch. Is this a bug? I checked Bugzilla, but wasn't sure if any of the bugs there fit. Thanks and regards, Anke -- Anke Bruns M.A. (LIS) Arbeitsgruppe "Anwendungs- und Informationssysteme" E-Mail: anke.bruns at 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 at 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 --------------------------------------- From Anke.Bruns at gwdg.de Thu Jul 14 02:10:51 2022 From: Anke.Bruns at gwdg.de (Bruns, Anke) Date: Wed, 13 Jul 2022 14:10:51 +0000 Subject: [Koha] to import bulk book details - please advise In-Reply-To: References: <595597ad84614215bbaa3bcf7c1279ac@gwdg.de> Message-ID: <74d24ab99b5b4e2185d97bd1c0e9c80b@gwdg.de> I use MarcEdit’s Delimited Text Translator to create MARC records from a .csv file exported from Excel. The template depends on what data is in which column of the table, so it has to be created by yourself according to your data. The template can be saved for future uses. https://marcedit.reeset.net/. Anke Von: edward durai Gesendet: Mittwoch, 13. Juli 2022 15:55 An: Bruns, Anke Cc: koha at lists.katipo.co.nz Betreff: Re: [Koha] to import bulk book details - please advise its fresh entry. please share if you have excel template to import On Tue, Jul 12, 2022 at 7:12 PM Bruns, Anke > wrote: Hi Edward, could you please explain your request a bit more? Do you explicitly want to import 5000 title records as duplicates of 5000 existing records, so as a result there are 10000 records? Or did you mean import the same data with deduplication in the process, so that the 5000 existing records are overwritten? What exactly would you like to know about Excel import? Best regards, Anke > -----Ursprüngliche Nachricht----- > Von: Koha > Im Auftrag von edward durai > Gesendet: Dienstag, 12. Juli 2022 13:27 > An: koha at lists.katipo.co.nz > Betreff: [Koha] to import bulk book details - please advise > > Hi Koha Team, > We Organization has 5000 books. I just wanted to import duplicate entry for > 5000 books using import excel. > > is it possible? so that we can edit and update whenever we have time. > > is there any other possibility to enter 5000 books quickly? > > thanks, > edward > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From Fred.King at Medstar.net Thu Jul 14 02:37:43 2022 From: Fred.King at Medstar.net (King, Fred) Date: Wed, 13 Jul 2022 14:37:43 +0000 Subject: [Koha] [EXTERNAL] KOHA repeatable item subfield In-Reply-To: <50f3b1d2-24c0-8d9f-8630-b6a4d8fd9bcd@snk.sk> References: <50f3b1d2-24c0-8d9f-8630-b6a4d8fd9bcd@snk.sk> Message-ID: Yes. To take 95$z as an example, Make the field repeatable If you're using the Koha cataloging function, add the $z fields one by one. If you're using MarcEdit, the $z fields have to be on the same 952 line. In the OPAC, the fields will be shown with a | separating them. For example, see http://cheerfulvalleypl.online/cgi-bin/koha/opac-detail.pl?biblionumber=8685 Fred King, MSLS, AHIP Medical Librarian, MedStar Washington Hospital Center fred.king at medstar.net 202-877-6670 ORCID 0000-0001-5266-0279 MedStar Authors Catalog: http://medstarauthors.org By replacing your morning coffee with green tea you can lose up to 87% of what little joy you still have left in your life. --Trad -----Original Message----- From: Koha On Behalf Of Viliam Polonec Sent: Wednesday, July 13, 2022 9:53 AM To: koha at lists.katipo.co.nz Subject: [EXTERNAL] [Koha] KOHA repeatable item subfield **ATTENTION: This email originated from outside the MedStar Health network. ** DO NOT CLICK links or attachments unless you recognize the sender and know the content is safe. Hi Is it possible to have in KOHA repeatable subfields in items, for example 952$z public note. I know that it's possible to add checkbox in bibliographic framework but I don't know if koha is suitable with that thank you regards Viliam _______________________________________________ Koha mailing list https://urldefense.com/v3/__http://koha-community.org__;!!D7IIWT94AA!-r3Q9D099lT_omx2cOs1ER0H-s_5sdqP-i2DEGQHn0GwszPcPnYPL7UvZvYBfotuuDu8g7CvrckIH_5I0hUPR5fRN3k$ Koha at lists.katipo.co.nz Unsubscribe: https://urldefense.com/v3/__https://lists.katipo.co.nz/mailman/listinfo/koha__;!!D7IIWT94AA!-r3Q9D099lT_omx2cOs1ER0H-s_5sdqP-i2DEGQHn0GwszPcPnYPL7UvZvYBfotuuDu8g7CvrckIH_5I0hUPjF_Juls$ ---------------------------------------------------------------------- MedStar Health is a not-for-profit, integrated healthcare delivery system, the largest in Maryland and the Washington, D.C., region. Nationally recognized for clinical quality in heart, orthopedics, cancer and GI. IMPORTANT: This e-mail (including any attachments) may contain information that is private, confidential, or protected by attorney-client or other privilege. If you received this e-mail in error, please delete it from your system without copying it and notify sender by reply e-mail, so that our records can be corrected... Thank you. Help conserve valuable resources - only print this email if necessary. From c.s.hayward at protonmail.com Thu Jul 14 03:15:17 2022 From: c.s.hayward at protonmail.com (C.S. Hayward) Date: Wed, 13 Jul 2022 15:15:17 +0000 Subject: [Koha] Migrating from one server to another In-Reply-To: <8cd188a4-f593-98d4-4cc6-104a560007ea@wlpl.org> References: <7e5265ff-7f93-910a-8774-d2a07e0e5d15@kohasupport.com> <01000181c8b13147-6bd33035-915f-44df-8da3-c7cf945aadc6-000000@email.amazonses.com> <6ddbbc0d-bfa8-3d69-8eb5-1de889d6209a@kohasupport.com> <01000181c8b482ca-9bef45b4-aaf6-4953-bc28-60a38a5eae55-000000@email.amazonses.com> <01000181d3697f07-da9d52dc-9e7d-4c45-b390-784559c5ecaa-000000@email.amazonses.com> <8cd188a4-f593-98d4-4cc6-104a560007ea@wlpl.org> Message-ID: It gives the staff admin interface. I have an immediate difficulty moving ahead. It is requesting a username and password. There is one username and password pair in koha-conf.xml; it's not accepted. I also tried usernames I had from the old website and they are likewise not accepted. How can I dig up or reset the setup administrative username and password, given that the library name is simply 'library'? Thanks, Br. C.S. Hayward, https://c-s-hayward.com ------- Original Message ------- On Wednesday, July 6th, 2022 at 12:06 PM, Tim McMahon wrote: > What happens when you access your staff interface? > > On 7/6/22 10:37 AM, C.S. Hayward wrote: > > > From the console: > > > > root at library:~# koha-worker --status library > > * worker running for library (default) [ OK ] > > root at library:~# koha-enable library > > Instance library already enabled. > > root at library:~# koha-worker -start library > > Error: invalid option switch (-start) > > root at library:~# koha-worker --start library > > * Error: worker already running for library (default) [fail] > > > > Attempting to accesshttps://library.cjshayward.com still redirects tohttps://library.cjshayward.com/cgi-bin/koha/maintenance.pl. > > > > Advice? > > > > Thanks, > > > > Br. C.S. Hayward,https://c-s-hayward.com > > > > ------- Original Message ------- > > On Wednesday, July 6th, 2022 at 8:08 AM, Lennon Mazondelennon at kohasupport.com wrote: > > > > > Hi, > > > > > > An internal server error (500) could mean your Koha instance is either not enabled or is not running (run "koha-worker --status") in which case enable it by running "koha-enable instancename" and "koha-worker --start instancename". > > > > > > NB: I just checked your admin and OPAC domains and it seems like your instance is up and running. You need to complete the web installer setup and you should be good to go. > > > > > > Best regards, > > > > > > Lennon > > > > > > lennon at kohasupport.com > > > > > > kohasupport.com > > > > > > > -----Original message----- > > > > From: C.S. Hayward > > > > Sent: Tuesday, July 5 2022, 8:02 pm > > > > To: Lennon Mazonde > > > > Cc: koha > > > > Subject: Re: [Koha] Migrating from one server to another > > > > > > > > Thank you. > > > > > > > > I had earlier followed the instructions athttp://kohageek.pbworks.com/w/page/60452540/How to move your koha database to newly installed Koha and got an unbranded internal server error athttps://library.cjshayward.com and a Koha branded internal server error athttps://library-intra.cjshayward.com. > > > > > > > > Since then (this may have been the equivalent of asking for my tea with cream and lemon) I ran the script you mentioned andhttps://library.cjshayward.com redirects tohttps://library.cjshayward.com/cgi-bin/koha/maintenance.pl. > > > > > > > > A few questions: > > > > > > > > 1: Have I messed up the system by trying to migrate both ways? > > > > > > > > 2: Would it likely be less energy to fix the system I have or start over? Would it make sense to do an aptitude purge for koha and then reinstall, or should I be trying a less surgical approach. > > > > > > > > 3: How can I get useful diagnostics? When I got the earlier 500 error, /var/log/apache2/error.log wasn't getting anything on additional attempted page load. > > > > > > > > I now have on the system the koha.sql created athttp://kohageek.pbworks.com/w/page/60452540/How to move your koha database to newly installed Koha. > > > > > > > > Thanks, > > > > > > > > Br. C.S. Hayward,https://c-s-hayward.com > > > > > > > > ------- Original Message ------- > > > > On Monday, July 4th, 2022 at 6:14 AM, Lennon Mazondelennon at kohasupport.com wrote: > > > > > > > > > Forgot to add the link to the GitHub repo, here it is -https://github.com/grandmaestr/koha-scripts. > > > > > > > > > > Best regards, > > > > > > > > > > ### Lennon Mazonde > > > > > > > > > > KohaSupport > > > > > > > > > > [blob:https://mail.proton.me/e8ef4ba0-e203-49f9-877f-0b7a940b8f83] > > > > > > > > > > lennon at kohasupport.com > > > > > > > > > > [blob:https://mail.proton.me/62ee6d68-51dc-4913-952e-6337c32582bb] > > > > > > > > > > www.kohasupport.com > > > > > > > > > > [blob:https://mail.proton.me/9edf60da-ed68-47c1-8229-b123f31dd6a0] > > > > > > > > > > 651 North Broad Street, Middletown, DE 19709, USA > > > > > > > > > > The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. > > > > > > > > > > On 7/4/22 12:11 PM, Lennon Mazonde wrote: > > > > > > > > > > > Hi, > > > > > > > > > > > > I have a repo on GitHub with scripts that might be able to help you. Have a look at the 'koha-migrate' script - I originally wrote it to migrate several Koha MariaDB databases running on a Ubuntu (20.04LTS) server to Amazon Aurora MySQL on AWS but it should work for other use-cases. There are several other scripts there you might find useful as well. As always, test them in a dev environment before running them on your production server :) > > > > > > > > > > > > If anyone else is interested and would like to contribute to the project, please let me know! > > > > > > > > > > > > Best regards, > > > > > > > > > > > > Lennon Mazonde > > > > > > > > > > > > KohaSupport > > > > > > > > > > > > lennon at kohasupport.com > > > > > > > > > > > > www.kohasupport.com > > > > > > > > > > > > 651 North Broad Street, Middletown, DE 19709, USA > > > > > > > > > > > > The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. > > > > > > > > > > > > On 7/1/22 5:17 PM, C.S. Hayward wrote: > > > > > > > > > > > > (Note: I am not using "migrate" as it is usually used today, meaning switching from ABC software to DEF. I'm referring to relocating an installation's data.) > > > > > > > > > > > > I would like to migrate my data from one Koha installation on one server to another installation on another server. Both use MariaDB. > > > > > > > > > > > > Where are instructions suitable to migrating data between two different servers? > > > > > > > > > > > > Thanks, > > > > > > Br. C.S. Hayward > > > > > > _______________________________________________ > > > > > > > > > > > > Koha mailing listhttp://koha-community.org > > > > > > Koha at lists.katipo.co.nz > > > > > > Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > > > Koha mailing listhttp://koha-community.org > > > > > > Koha at lists.katipo.co.nz > > > > > > Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > > _______________________________________________ > > > > Koha mailing listhttp://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha > > -- > Tim McMahon > West Liberty Public Library > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From Fred.King at Medstar.net Thu Jul 14 03:18:28 2022 From: Fred.King at Medstar.net (King, Fred) Date: Wed, 13 Jul 2022 15:18:28 +0000 Subject: [Koha] to import bulk book details - please advise In-Reply-To: <74d24ab99b5b4e2185d97bd1c0e9c80b@gwdg.de> References: <595597ad84614215bbaa3bcf7c1279ac@gwdg.de> <74d24ab99b5b4e2185d97bd1c0e9c80b@gwdg.de> Message-ID: My colleague Lauren Denny and I are doing a presentation on this very thing at KohaCon in September. For more information, see https://koha-us.org/events/conferences/kohacon22/ (We're presenting on Thursday, 22 September, but you need to come for the other presentations, too!) Fred King, MSLS, AHIP Medical Librarian, MedStar Washington Hospital Center fred.king at medstar.net 202-877-6670 ORCID 0000-0001-5266-0279 MedStar Authors Catalog: http://medstarauthors.org By replacing your morning coffee with green tea you can lose up to 87% of what little joy you still have left in your life. --Trad -----Original Message----- From: Koha On Behalf Of Bruns, Anke Sent: Wednesday, July 13, 2022 10:11 AM To: edward durai Cc: koha at lists.katipo.co.nz Subject: [EXTERNAL] Re: [Koha] to import bulk book details - please advise **ATTENTION: This email originated from outside the MedStar Health network. ** DO NOT CLICK links or attachments unless you recognize the sender and know the content is safe. I use MarcEdit’s Delimited Text Translator to create MARC records from a .csv file exported from Excel. The template depends on what data is in which column of the table, so it has to be created by yourself according to your data. The template can be saved for future uses. https://urldefense.com/v3/__https://marcedit.reeset.net/__;!!D7IIWT94AA!9-PUuvl3WiZKNaEhdCJZliOZ2ZhxxxOci4h9Xx9Ww9CpaFNiNL52QA8sqIyh5nQ2sMQJkeQx7wys9B7pPTE1G0Y$ . Anke Von: edward durai Gesendet: Mittwoch, 13. Juli 2022 15:55 An: Bruns, Anke Cc: koha at lists.katipo.co.nz Betreff: Re: [Koha] to import bulk book details - please advise its fresh entry. please share if you have excel template to import On Tue, Jul 12, 2022 at 7:12 PM Bruns, Anke > wrote: Hi Edward, could you please explain your request a bit more? Do you explicitly want to import 5000 title records as duplicates of 5000 existing records, so as a result there are 10000 records? Or did you mean import the same data with deduplication in the process, so that the 5000 existing records are overwritten? What exactly would you like to know about Excel import? Best regards, Anke > -----Ursprüngliche Nachricht----- > Von: Koha > Im Auftrag von edward durai > Gesendet: Dienstag, 12. Juli 2022 13:27 > An: koha at lists.katipo.co.nz > Betreff: [Koha] to import bulk book details - please advise > > Hi Koha Team, > We Organization has 5000 books. I just wanted to import duplicate > entry for > 5000 books using import excel. > > is it possible? so that we can edit and update whenever we have time. > > is there any other possibility to enter 5000 books quickly? > > thanks, > edward > _______________________________________________ > > Koha mailing list > https://urldefense.com/v3/__http://koha-community.org__;!!D7IIWT94AA!9 > -PUuvl3WiZKNaEhdCJZliOZ2ZhxxxOci4h9Xx9Ww9CpaFNiNL52QA8sqIyh5nQ2sMQJkeQ > x7wys9B7p8oBFU2o$ Koha at lists.katipo.co.nz > > Unsubscribe: > https://urldefense.com/v3/__https://lists.katipo.co.nz/mailman/listinf > o/koha__;!!D7IIWT94AA!9-PUuvl3WiZKNaEhdCJZliOZ2ZhxxxOci4h9Xx9Ww9CpaFNi > NL52QA8sqIyh5nQ2sMQJkeQx7wys9B7pGS_qN3Q$ _______________________________________________ Koha mailing list https://urldefense.com/v3/__http://koha-community.org__;!!D7IIWT94AA!9-PUuvl3WiZKNaEhdCJZliOZ2ZhxxxOci4h9Xx9Ww9CpaFNiNL52QA8sqIyh5nQ2sMQJkeQx7wys9B7p8oBFU2o$ Koha at lists.katipo.co.nz Unsubscribe: https://urldefense.com/v3/__https://lists.katipo.co.nz/mailman/listinfo/koha__;!!D7IIWT94AA!9-PUuvl3WiZKNaEhdCJZliOZ2ZhxxxOci4h9Xx9Ww9CpaFNiNL52QA8sqIyh5nQ2sMQJkeQx7wys9B7pGS_qN3Q$ ---------------------------------------------------------------------- MedStar Health is a not-for-profit, integrated healthcare delivery system, the largest in Maryland and the Washington, D.C., region. Nationally recognized for clinical quality in heart, orthopedics, cancer and GI. IMPORTANT: This e-mail (including any attachments) may contain information that is private, confidential, or protected by attorney-client or other privilege. If you received this e-mail in error, please delete it from your system without copying it and notify sender by reply e-mail, so that our records can be corrected... Thank you. Help conserve valuable resources - only print this email if necessary. From c.s.hayward at protonmail.com Thu Jul 14 07:25:02 2022 From: c.s.hayward at protonmail.com (C.S. Hayward) Date: Wed, 13 Jul 2022 19:25:02 +0000 Subject: [Koha] Migrating from one server to another In-Reply-To: References: <6ddbbc0d-bfa8-3d69-8eb5-1de889d6209a@kohasupport.com> <01000181c8b482ca-9bef45b4-aaf6-4953-bc28-60a38a5eae55-000000@email.amazonses.com> <01000181d3697f07-da9d52dc-9e7d-4c45-b390-784559c5ecaa-000000@email.amazonses.com> <8cd188a4-f593-98d4-4cc6-104a560007ea@wlpl.org> Message-ID: <6I3TZ2zNTQ2SGV6Tw9VpwWlMGGaSwV4mCHoVJfioEf6CEZz9NAwbgfMVe-vW2NM8TwjJ8C3oOpyj3HURL2JuRTJMh3wylBTCJwUt3iuvxWQ=@protonmail.com> Breadcrumb/defect remark for future people looking at this: The username was "koha_[instance name]"; in my case, it was "koha_library". The password was given by running "koha_passwd [instance name]" at the command line. Somewhere along the way I was told that the information I wanted was a username/password pair in the koha-conf.xml. That is erroneous, and it is a defect that the user is directed there instead of specifying a username of "koha_[instance name]" and a password obtainable by running "koha_passwd [instance name]". Br. C.S. Hayward, https://c-s-hayward.com. ------- Original Message ------- On Wednesday, July 13th, 2022 at 11:15 AM, C.S. Hayward wrote: > It gives the staff admin interface. > > I have an immediate difficulty moving ahead. It is requesting a username and password. There is one username and password pair in koha-conf.xml; it's not accepted. I also tried usernames I had from the old website and they are likewise not accepted. > > How can I dig up or reset the setup administrative username and password, given that the library name is simply 'library'? > > > Thanks, > > Br. C.S. Hayward, https://c-s-hayward.com > > ------- Original Message ------- > On Wednesday, July 6th, 2022 at 12:06 PM, Tim McMahon tmcmahon at wlpl.org wrote: > > > > > What happens when you access your staff interface? > > > > On 7/6/22 10:37 AM, C.S. Hayward wrote: > > > > > From the console: > > > > > > root at library:~# koha-worker --status library > > > * worker running for library (default) [ OK ] > > > root at library:~# koha-enable library > > > Instance library already enabled. > > > root at library:~# koha-worker -start library > > > Error: invalid option switch (-start) > > > root at library:~# koha-worker --start library > > > * Error: worker already running for library (default) [fail] > > > > > > Attempting to accesshttps://library.cjshayward.com still redirects tohttps://library.cjshayward.com/cgi-bin/koha/maintenance.pl. > > > > > > Advice? > > > > > > Thanks, > > > > > > Br. C.S. Hayward,https://c-s-hayward.com > > > > > > ------- Original Message ------- > > > On Wednesday, July 6th, 2022 at 8:08 AM, Lennon Mazondelennon at kohasupport.com wrote: > > > > > > > Hi, > > > > > > > > An internal server error (500) could mean your Koha instance is either not enabled or is not running (run "koha-worker --status") in which case enable it by running "koha-enable instancename" and "koha-worker --start instancename". > > > > > > > > NB: I just checked your admin and OPAC domains and it seems like your instance is up and running. You need to complete the web installer setup and you should be good to go. > > > > > > > > Best regards, > > > > > > > > Lennon > > > > > > > > lennon at kohasupport.com > > > > > > > > kohasupport.com > > > > > > > > > -----Original message----- > > > > > From: C.S. Hayward > > > > > Sent: Tuesday, July 5 2022, 8:02 pm > > > > > To: Lennon Mazonde > > > > > Cc: koha > > > > > Subject: Re: [Koha] Migrating from one server to another > > > > > > > > > > Thank you. > > > > > > > > > > I had earlier followed the instructions athttp://kohageek.pbworks.com/w/page/60452540/How to move your koha database to newly installed Koha and got an unbranded internal server error athttps://library.cjshayward.com and a Koha branded internal server error athttps://library-intra.cjshayward.com. > > > > > > > > > > Since then (this may have been the equivalent of asking for my tea with cream and lemon) I ran the script you mentioned andhttps://library.cjshayward.com redirects tohttps://library.cjshayward.com/cgi-bin/koha/maintenance.pl. > > > > > > > > > > A few questions: > > > > > > > > > > 1: Have I messed up the system by trying to migrate both ways? > > > > > > > > > > 2: Would it likely be less energy to fix the system I have or start over? Would it make sense to do an aptitude purge for koha and then reinstall, or should I be trying a less surgical approach. > > > > > > > > > > 3: How can I get useful diagnostics? When I got the earlier 500 error, /var/log/apache2/error.log wasn't getting anything on additional attempted page load. > > > > > > > > > > I now have on the system the koha.sql created athttp://kohageek.pbworks.com/w/page/60452540/How to move your koha database to newly installed Koha. > > > > > > > > > > Thanks, > > > > > > > > > > Br. C.S. Hayward,https://c-s-hayward.com > > > > > > > > > > ------- Original Message ------- > > > > > On Monday, July 4th, 2022 at 6:14 AM, Lennon Mazondelennon at kohasupport.com wrote: > > > > > > > > > > > Forgot to add the link to the GitHub repo, here it is -https://github.com/grandmaestr/koha-scripts. > > > > > > > > > > > > Best regards, > > > > > > > > > > > > ### Lennon Mazonde > > > > > > > > > > > > KohaSupport > > > > > > > > > > > > [blob:https://mail.proton.me/e8ef4ba0-e203-49f9-877f-0b7a940b8f83] > > > > > > > > > > > > lennon at kohasupport.com > > > > > > > > > > > > [blob:https://mail.proton.me/62ee6d68-51dc-4913-952e-6337c32582bb] > > > > > > > > > > > > www.kohasupport.com > > > > > > > > > > > > [blob:https://mail.proton.me/9edf60da-ed68-47c1-8229-b123f31dd6a0] > > > > > > > > > > > > 651 North Broad Street, Middletown, DE 19709, USA > > > > > > > > > > > > The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. > > > > > > > > > > > > On 7/4/22 12:11 PM, Lennon Mazonde wrote: > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > I have a repo on GitHub with scripts that might be able to help you. Have a look at the 'koha-migrate' script - I originally wrote it to migrate several Koha MariaDB databases running on a Ubuntu (20.04LTS) server to Amazon Aurora MySQL on AWS but it should work for other use-cases. There are several other scripts there you might find useful as well. As always, test them in a dev environment before running them on your production server :) > > > > > > > > > > > > > > If anyone else is interested and would like to contribute to the project, please let me know! > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > Lennon Mazonde > > > > > > > > > > > > > > KohaSupport > > > > > > > > > > > > > > lennon at kohasupport.com > > > > > > > > > > > > > > www.kohasupport.com > > > > > > > > > > > > > > 651 North Broad Street, Middletown, DE 19709, USA > > > > > > > > > > > > > > The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. > > > > > > > > > > > > > > On 7/1/22 5:17 PM, C.S. Hayward wrote: > > > > > > > > > > > > > > (Note: I am not using "migrate" as it is usually used today, meaning switching from ABC software to DEF. I'm referring to relocating an installation's data.) > > > > > > > > > > > > > > I would like to migrate my data from one Koha installation on one server to another installation on another server. Both use MariaDB. > > > > > > > > > > > > > > Where are instructions suitable to migrating data between two different servers? > > > > > > > > > > > > > > Thanks, > > > > > > > Br. C.S. Hayward > > > > > > > _______________________________________________ > > > > > > > > > > > > > > Koha mailing listhttp://koha-community.org > > > > > > > Koha at lists.katipo.co.nz > > > > > > > Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > > > > > Koha mailing listhttp://koha-community.org > > > > > > > Koha at lists.katipo.co.nz > > > > > > > Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > > > _______________________________________________ > > > > > > Koha mailing listhttp://koha-community.org > > > Koha at lists.katipo.co.nz > > > Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha > > > > -- > > Tim McMahon > > West Liberty Public Library > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From c.s.hayward at protonmail.com Thu Jul 14 07:39:28 2022 From: c.s.hayward at protonmail.com (C.S. Hayward) Date: Wed, 13 Jul 2022 19:39:28 +0000 Subject: [Koha] One somewhat discussion-y question Message-ID: Using HTTPS for routine web activity is no longer the future of the web; it is the present of the web. Firefox displays intimidating warnings, comparable to an invalid certificate warnings, before letting you access an HTTP connection that cannot be upgraded to HTTPS. It's not clear to me whether there are any particularly good ways to get a certificate for a server on the LAN. I can see some duct-tape-y switching DNS entries so that you get a Let's Encrypt certificate which is served up for a library.[your domain here] server, but I can't think of any good way to use it. This would seem to mean that the practice of running a server, available on the LAN as 192.168.x.x or 10.x.x.x, is a casualty of the web being upgraded to HTTPS for normal use. I can see obvious ways of restricting use to a LAN (by limiting connections to a single IP or IP range for a NATted LAN), but just putting something on a LAN at a 192.168.x.x or 10.x.x.x address looks to me like a casualty of change. For what it's worth... Br. C.S. Hayward, https://cjshayward.com From secretary at koha-us.org Thu Jul 14 08:00:48 2022 From: secretary at koha-us.org (Jennifer Marlatt) Date: Wed, 13 Jul 2022 13:00:48 -0700 Subject: [Koha] koha-US General Meeting Minutes - July 13, 2022 Message-ID: Hello, Here's a link to the minutes from the koha-US general meeting today - https://docs.google.com/document/d/1dwEhXB8-IAcztDyKxrN6CqenZI4kVJ9qFoFj2IIjef8/edit?usp=sharing koha-US meetings are open to all! General meetings are held on the second Wednesday of each month at 8:30 PT / 9:30 MT / 10:30 CT / 11:30 ET. Jennifer Marlatt koha-US Secretary secretary at koha-us.org From jcoehoorn at york.edu Thu Jul 14 08:29:15 2022 From: jcoehoorn at york.edu (Coehoorn, Joel) Date: Wed, 13 Jul 2022 15:29:15 -0500 Subject: [Koha] One somewhat discussion-y question In-Reply-To: References: Message-ID: I definitely agree it makes little sense anymore to deploy an HTTP only option, and my own apache config for koha has the HTTP ports set to redirect to HTTPS. If this really is a LAN-only installation, with no public access, then you are also likely to have control over the machines accessing the service and can force them to trust a self-signed certificate from the koha server, at least as far as the circulation/staff workstations and any library-provided public access catalog stations are concerned. If this also includes the OPAC catalog for guests, if it really is internal-LAN-only then a number of public wifi solutions will allow you to include a captive portal that can check certificate availability before granting internet access, and deploy the needed certificate as part of onboarding. I am sympathetic, though, to the argument that the same libraries lacking IT capabilities for a public catalog also likely lack capabilities to implement quality wifi onboarding. The LetsEncrypt certificates are free, it's not hard or expensive to buy a domain and get help once to set things up to forward a port from the public internet connection to an internal server so LetsEncrypt can do domain validation. But it's another thing entirely to be sure your server is hardened and sufficiently monitored/maintained in a way you can be comfortable exposing it to the public internet, and not every library can do that. Sometimes there are other reasons to keep a catalog private for local patrons only, too. I feel like the major web browsers are right to implement warnings about HTTP traffic, but too aggressive about including those warnings for traffic to non-routable IPs... but it's not something we have the power to change, so those smaller libraries will have to find a way to live within the new world. *Joel Coehoorn* York University* | *Director of Information Technology Office: 402-363-5603 | @YUITDept *The mission of York University is to transform lives through Christ-centered education and to equip students for lifelong service to God, family and society*. On Wed, Jul 13, 2022 at 2:39 PM C.S. Hayward wrote: > Using HTTPS for routine web activity is no longer the future of the web; > it is the present of the web. Firefox displays intimidating warnings, > comparable to an invalid certificate warnings, before letting you access an > HTTP connection that cannot be upgraded to HTTPS. > > It's not clear to me whether there are any particularly good ways to get a > certificate for a server on the LAN. I can see some duct-tape-y switching > DNS entries so that you get a Let's Encrypt certificate which is served up > for a library.[your domain here] server, but I can't think of any good way > to use it. > > This would seem to mean that the practice of running a server, available > on the LAN as 192.168.x.x or 10.x.x.x, is a casualty of the web being > upgraded to HTTPS for normal use. I can see obvious ways of restricting use > to a LAN (by limiting connections to a single IP or IP range for a NATted > LAN), but just putting something on a LAN at a 192.168.x.x or 10.x.x.x > address looks to me like a casualty of change. > > > For what it's worth... > > > Br. C.S. Hayward, https://cjshayward.com > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From rtr.himanshu at gmail.com Thu Jul 14 23:19:30 2022 From: rtr.himanshu at gmail.com (Himanshu Aggarwal) Date: Thu, 14 Jul 2022 16:49:30 +0530 Subject: [Koha] Lock a Certain field Message-ID: Is there a way to restrict editing of Date by catalogers -- Assistant Librarian, Confucius Institute Scholar 13-14, R.D. National College, Bandra (W.) From mik at adminkuhn.ch Thu Jul 14 23:30:43 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Thu, 14 Jul 2022 13:30:43 +0200 Subject: [Koha] Failing authentication via CAS after update to Koha 21.11.09 In-Reply-To: <30f17401-5dc6-b07c-8db9-383c6d8b3376@adminkuhn.ch> References: <30f17401-5dc6-b07c-8db9-383c6d8b3376@adminkuhn.ch> Message-ID: Hi We're quite desperate since using CAS all our users can no more log into their Koha accounts. Is there really no way how to debug problems with the authentication via CAS? We would be very happy if there is a way how to find out what Perl scripts "opac-user.pl" or "Auth_with_cas.pm" are really doing. Unfortunately they are not verbose at all and don't write anything into the log files. Is it possible to force these scripts to output what they are actually doing? For example I tried the following in "Auth_with_cas.pm", but file "/tmp/perloutput.txt" stayed empty. open STDERR, ">", "/tmp/perloutput.txt" or die "$0: dup: $!"; print STDERR "defaultcasserver: $defaultcasserver\n"; print STDERR "casservers: $casservers\n"; close (STDERR); 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 at adminkuhn.ch · W www.adminkuhn.ch -------- Weitergeleitete Nachricht -------- Betreff: [Koha] Failing authentication via CAS after update to Koha 21.11.09 Datum: Mon, 11 Jul 2022 13:41:03 +0200 Von: Michael Kuhn Antwort an: Michael Kuhn Organisation: Admin Kuhn GmbH An: Koha Hi We are using Debian GNU/Linux 10 with Koha 21.11.09 (after an update from Debian 9 and Koha 19.05.02). Since the update the CAS authentication via Koha OPAC is no more working. The content of system preferences "OPACBaseURL", "casAuthentication", "casLogout" and "casServerUrl" has not changed; the new preference "casServerVersion" ist correctly set to "CAS 2 or earlier". It is possible to successfully log into the CAS server but when trying to access the Koha OPAC via CAS ("Log in using a CAS account") the response is always "Sorry, the CAS login failed." and the user is not logged into his Koha account. The logs don't show no error. I was checking all changes made in bugs 21973 22585 23771 20854 and 28417 but to no avail. Does anyone have an idea how to debug this problem? Best wishes: Michael From mik at adminkuhn.ch Thu Jul 14 23:33:51 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Thu, 14 Jul 2022 13:33:51 +0200 Subject: [Koha] Lock a Certain field In-Reply-To: References: Message-ID: Hi Himanshu > Is there a way to restrict editing of Date by catalogers The following article by Kelly McElligott (Bywater Solutions) may answer your question: * https://bywatersolutions.com/education/monday-minutes-protecting-marc-fields Hope this helps. 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 at adminkuhn.ch · W www.adminkuhn.ch From grishavkumar at gmail.com Thu Jul 14 23:36:53 2022 From: grishavkumar at gmail.com (Rishav Kumar Gond) Date: Thu, 14 Jul 2022 17:06:53 +0530 Subject: [Koha] Adding https into koha opac site. Message-ID: Hi all, Is there a way to get https to my koha opac with let's encrypt. Regards Rishav From c.s.hayward at protonmail.com Fri Jul 15 01:03:51 2022 From: c.s.hayward at protonmail.com (C.S. Hayward) Date: Thu, 14 Jul 2022 13:03:51 +0000 Subject: [Koha] Adding https into koha opac site. In-Reply-To: References: Message-ID: <4ETebpK8mV3y3ngvptg4jahhDWrgMlW7xzEqGdfCDqEijza85VFHrt3a-7pFeVz8nCT8wJcc5Uiqej6iGwH-VXTTTQpff-4r4k3GkAIgHrc=@protonmail.com> Let's Encrypt has a homepage at https://letsencrypt.org, and a "Getting Started" documentation page at https://letsencrypt.org/getting-started/. I'd encourage you to peruse the latter. Br. C.S. Hayward, https://cjshayward.com. ------- Original Message ------- On Thursday, July 14th, 2022 at 7:36 AM, Rishav Kumar Gond wrote: > Hi all, > Is there a way to get https to my koha opac with let's encrypt. > > Regards > Rishav > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From cornejo.alvaro at gmail.com Fri Jul 15 02:36:56 2022 From: cornejo.alvaro at gmail.com (Alvaro Cornejo) Date: Thu, 14 Jul 2022 09:36:56 -0500 Subject: [Koha] Adding https into koha opac site. In-Reply-To: References: Message-ID: HI, Yes, it does work pretty straight forward. Just follow let's encrypt tutorials in order to generate & install your certificates. Regards Alvaro |----------------------------------------------------------------------------------------| Stay safe / Cuídate/ Reste sécurisé *7* Switch off as you go / Apaga lo que no usas / Débranchez au fur et à mesure. *q *Recycle always / Recicla siempre / Recyclez toujours P Print only if absolutely necessary / Imprime solo si es necesario / Imprimez seulement si nécessaire Le jeu. 14 juil. 2022 à 06:37, Rishav Kumar Gond a écrit : > Hi all, > Is there a way to get https to my koha opac with let's encrypt. > > Regards > Rishav > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From Heather_Hernandez at nps.gov Fri Jul 15 02:46:39 2022 From: Heather_Hernandez at nps.gov (Hernandez, Heather H) Date: Thu, 14 Jul 2022 14:46:39 +0000 Subject: [Koha] koha-US General Meeting Minutes - July 13, 2022 In-Reply-To: References: Message-ID: Hi! Thank you so much for taking and distributing the minutes--I wasn't able to attend the meeting and read them avidly, and found the section about in-person vs. virtual conferencing particularly interesting, and thought I might just chime in a little about this. I would love to attend an in-person Koha conference and although my employer is willing, my employer just can't cover all the costs. I have been told, often, by colleagues in the library world who have the means to personally pay costs, that paying the rest of the costs personally is considered a worthwhile career investment. Sure. But one has to be affluent enough to actually have the extra money to cover these costs. Also, one has to be physically and mentally healthy enough to do the travel, and one's household has to be economically, physically, and mentally healthy enough to support a member leaving and traveling. Traveling to in person conferences is mostly the realm of the affluent and able. So I would very much urge the continued support of virtual conference attendance and participation. I have been fortunate to attend some in person conferences in the past, and, yes, they were all everyone says they are--so much more than virtual attendance. But I can't travel to an in person conference, and no many people that can't and that don't feel comfortable discussing why​ they can't attend--they are not comfortable outing themselves and exposing themselves to potential poverty-shaming, and/or disability (physical and/or mental) discrimination. So, please, conference planners--please continue virtual conferences of some sort. It's very important for the inclusivity of all. And, yes, encourage in person attendance, but please realize that any free, virtual attendance makes participation more possible for those without the economic, physical, and/or mental means to attend in person. And thank you all for the inclusive and supportive community that makes me comfortable saying all this! Cheerio!! --h2 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ms. Heather Hernandez (she, her, hers) Technical Services Librarian Library catalog: https://keys.bywatersolutions.com/ San Francisco Maritime National Historical Park Research Center 2 Marina Blvd., Bldg. E, 3rd floor, San Francisco, CA 94123-1284 415-561-7032 (office generally Tu-W & F, telecommuting M&Th) heather_hernandez at nps.gov From c.s.hayward at protonmail.com Fri Jul 15 03:48:54 2022 From: c.s.hayward at protonmail.com (C.S. Hayward) Date: Thu, 14 Jul 2022 15:48:54 +0000 Subject: [Koha] Making field optional Message-ID: I am interested in making MARC field tag 040 subfield c optional. Two basic questions: 1: Is this something that would make you wince? 2: How can I go about doing that? Thanks, Br. C.S. Hayward, https://cjshayward.com, https://c-s-hayward.com From rtr.himanshu at gmail.com Fri Jul 15 04:58:32 2022 From: rtr.himanshu at gmail.com (Himanshu Aggarwal) Date: Thu, 14 Jul 2022 22:28:32 +0530 Subject: [Koha] Making field optional In-Reply-To: References: Message-ID: You can change from Mandatory to Important wherein even if one does not choose it the record can still be saved. On Thu, Jul 14, 2022 at 9:19 PM C.S. Hayward wrote: > I am interested in making MARC field tag 040 subfield c optional. > > Two basic questions: > > 1: Is this something that would make you wince? > > 2: How can I go about doing that? > > > Thanks, > Br. C.S. Hayward, https://cjshayward.com, https://c-s-hayward.com > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > -- Assistant Librarian, Confucius Institute Scholar 13-14, R.D. National College, Bandra (W.) From c.s.hayward at protonmail.com Fri Jul 15 05:19:14 2022 From: c.s.hayward at protonmail.com (C.S. Hayward) Date: Thu, 14 Jul 2022 17:19:14 +0000 Subject: [Koha] Making field optional In-Reply-To: References: Message-ID: Thank you. How can I navigate to the screen where I can change this, or what is the relative URL? Thanks, Br. C.S. Hayward. ------- Original Message ------- On Thursday, July 14th, 2022 at 12:58 PM, Himanshu Aggarwal wrote: > You can change from Mandatory to Important wherein even if one does not choose it the record can still be saved. > > On Thu, Jul 14, 2022 at 9:19 PM C.S. Hayward wrote: > > > I am interested in making MARC field tag 040 subfield c optional. > > > > Two basic questions: > > > > 1: Is this something that would make you wince? > > > > 2: How can I go about doing that? > > > > > > Thanks, > > Br. C.S. Hayward, https://cjshayward.com, https://c-s-hayward.com > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > > -- > Assistant Librarian, > Confucius Institute Scholar 13-14, > R.D. National College, > Bandra (W.) From katrin.fischer.83 at web.de Fri Jul 15 05:30:08 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Thu, 14 Jul 2022 19:30:08 +0200 Subject: [Koha] Making field optional In-Reply-To: References: Message-ID: <67eb93bc-f129-91e4-cc51-cf258c8a96e4@web.de> Hi, I am not a cataloger, so I am not going to judge :) * Go to Administration > Bibliographic MARC frameworks * Choose MARC structure for the framework you want to update * Search for the field and 'Edit subfields' * Remove the mandatory flag from the subfield Hope this helps, Katrin On 14.07.22 17:48, C.S. Hayward wrote: > I am interested in making MARC field tag 040 subfield c optional. > > Two basic questions: > > 1: Is this something that would make you wince? > > 2: How can I go about doing that? > > > Thanks, > Br. C.S. Hayward, https://cjshayward.com, https://c-s-hayward.com > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From c.s.hayward at protonmail.com Fri Jul 15 05:38:41 2022 From: c.s.hayward at protonmail.com (C.S. Hayward) Date: Thu, 14 Jul 2022 17:38:41 +0000 Subject: [Koha] Making field optional In-Reply-To: <67eb93bc-f129-91e4-cc51-cf258c8a96e4@web.de> References: <67eb93bc-f129-91e4-cc51-cf258c8a96e4@web.de> Message-ID: Just what the doctor ordered! Thanks, as usual, Br. C.S. Hayward ------- Original Message ------- On Thursday, July 14th, 2022 at 1:30 PM, Katrin Fischer wrote: > Hi, > > I am not a cataloger, so I am not going to judge :) > > * Go to Administration > Bibliographic MARC frameworks > > > * Choose MARC structure for the framework you want to update > > * Search for the field and 'Edit subfields' > > * Remove the mandatory flag from the subfield > > Hope this helps, > > Katrin > > On 14.07.22 17:48, C.S. Hayward wrote: > > > I am interested in making MARC field tag 040 subfield c optional. > > > > Two basic questions: > > > > 1: Is this something that would make you wince? > > > > 2: How can I go about doing that? > > > > Thanks, > > Br. C.S. Hayward, https://cjshayward.com, https://c-s-hayward.com > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From katrin.fischer.83 at web.de Fri Jul 15 05:48:58 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Thu, 14 Jul 2022 19:48:58 +0200 Subject: [Koha] Error in Koha 22.05? In-Reply-To: <1344101688.297543.1657023575877@office.mailbox.org> References: <542482724.267230.1657006553609@office.mailbox.org> <48f68a85-5c1f-58a7-f37b-a608135b3c3c@uns.edu.ar> <1344101688.297543.1657023575877@office.mailbox.org> Message-ID: <7b4f7013-1c9a-53f1-0356-73ff361aad6f@web.de> Hi Eberhard, I am not sure if the problem would be visible in the data. Maybe some ideas what to try instead: * Can you reset the password of your user? This would require the password recovery feature to be enabled. * Can you log in with a new superlibrarian account created from command line? (http://kohageek.blogspot.com/2018/07/create-super-librarian-by-command-line.html) * What is the message shown when you try to log in? Is there anything visible in the logs when the login fails? Hope this helps, Katrin On 05.07.22 14:19, Dr. Eberhard Pietzsch wrote: > Attached you see an dump of the borrowers table. You can see at the insert statement that the contents are shifted by a few bytes. Some attributes are new compared with earliver versions of Koha. > > (I have edited the encrypted password) > > Eberhard > >> Katrin Fischer hat am 05.07.2022 12:33 CEST geschrieben: >> >> >> Hi, >> >> could you please post more information about the issue? What error >> message are you seeing? Can you access the tables with SQL? >> >> Is this the error maybe: DBI Exception: DBD::mysql::db do failed: Row >> size too large. >> >> Then have a look at: *Bug 28267* >> - >> Koha-common package upgrade problem from 20.05.xx to 20.11.04-1 >> >> Hope this helps, >> >> Katrin >> >> On 05.07.22 12:21, Fernando A. Martinez wrote: >>> Hi, >>> >>> I have the same problem. Corrupted tables: borrowers and >>> deletedborrowers. Update: Koha 22.05.02 over Koha 21.11.09 Ubuntu >>> 20.04 LTS MySQL version 8.0.29 >>> >>> Regards >>> >>> Fernando A. Martinez >>> >>> On 5/7/22 04:35, Dr. Eberhard Pietzsch wrote: >>>> Hello, >>>> >>>> I would like to point out a bug in Koha after the update to 22.05. >>>> >>>> Koha is also included in the package management of Ubuntu 22.04 LTS >>>> and can be updated together with Ubuntu. I had skipped the short time >>>> preceding Koha update because of errors. However, the current update >>>> to 22.05 apparently also contains bugs: >>>> >>>> The structure of the borrowers table seems to have been changed >>>> compared to previous versions. Existing user data are not correctly >>>> loaded into the new structured table with the update, so that no >>>> login, e.g. as superlibrarian, is possible anymore. >>>> >>>> Possibly this phenomenon is caused by the skipped update to the >>>> previous version? >>>> >>>> Many greetings >>>> Eberhard Pietzsch >>>> _______________________________________________ >>>> >>>> Koha mailing listhttp://koha-community.org >>>> Koha at lists.katipo.co.nz >>>> Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha >>> _______________________________________________ >>> >>> Koha mailing list http://koha-community.org >>> Koha at lists.katipo.co.nz >>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From c.s.hayward at protonmail.com Fri Jul 15 05:53:41 2022 From: c.s.hayward at protonmail.com (C.S. Hayward) Date: Thu, 14 Jul 2022 17:53:41 +0000 Subject: [Koha] Making field optional In-Reply-To: References: <67eb93bc-f129-91e4-cc51-cf258c8a96e4@web.de> Message-ID: Followup question: I have made 040 c an optional field. However, 040 is still a required field in that one of its subfields is required to be filled. How can I change things so that 040 itself is not required? Thanks, Br. C.S. Hayward. ------- Original Message ------- On Thursday, July 14th, 2022 at 1:38 PM, C.S. Hayward wrote: > Just what the doctor ordered! > > > Thanks, as usual, > Br. C.S. Hayward > > > ------- Original Message ------- > On Thursday, July 14th, 2022 at 1:30 PM, Katrin Fischer katrin.fischer.83 at web.de wrote: > > > > > Hi, > > > > I am not a cataloger, so I am not going to judge :) > > > > * Go to Administration > Bibliographic MARC frameworks > > > > * Choose MARC structure for the framework you want to update > > > > * Search for the field and 'Edit subfields' > > > > * Remove the mandatory flag from the subfield > > > > Hope this helps, > > > > Katrin > > > > On 14.07.22 17:48, C.S. Hayward wrote: > > > > > I am interested in making MARC field tag 040 subfield c optional. > > > > > > Two basic questions: > > > > > > 1: Is this something that would make you wince? > > > > > > 2: How can I go about doing that? > > > > > > Thanks, > > > Br. C.S. Hayward, https://cjshayward.com, https://c-s-hayward.com > > > _______________________________________________ > > > > > > Koha mailing list http://koha-community.org > > > Koha at lists.katipo.co.nz > > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From katrin.fischer.83 at web.de Fri Jul 15 06:10:17 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Thu, 14 Jul 2022 20:10:17 +0200 Subject: [Koha] Batch item modification, problem with location In-Reply-To: <0120a12270c0466f853d5c241f142359@gwdg.de> References: <0120a12270c0466f853d5c241f142359@gwdg.de> Message-ID: Hi Anke, I think maybe you only see the locations available to the library you are logged in as. Could this be the case? I am not sure if it was intended to limit the batch item edit form like this, but it's always worth filing a bug if something doesn't work as expected. I am not sure what the general expectation here is, but I like your suggestion that it should depend on the items selected somehow. Hope this helps, Katrin On 13.07.22 16:00, Bruns, Anke wrote: > Hi, > > when I try to modify a batch of items to assign a location (authorized value > LOC, would be 952$c) to them, there are in the dropdown list of possible > locations only those belonging to a different branch from the branch my > items belong to (as both their home and holding branch). > > Thus, I cannot assign my desired location via batch item modification. I > stumbled upon this in 20.11 and 22.05. > > I would expect to see either all locations from the LOC authorized value in > the dropdown list (requiring some mindfulness when batch assigning them to > items), or those belonging to the items' respective home and/or holding > branch. > > Is this a bug? I checked Bugzilla, but wasn't sure if any of the bugs there > fit. > > Thanks and regards, > Anke > From ephetteplace at cca.edu Fri Jul 15 06:11:22 2022 From: ephetteplace at cca.edu (Eric Phetteplace) Date: Thu, 14 Jul 2022 11:11:22 -0700 Subject: [Koha] Making field optional In-Reply-To: References: <67eb93bc-f129-91e4-cc51-cf258c8a96e4@web.de> Message-ID: I assume you remove the "mandatory" flag for *all* subfields and then the field itself is not mandatory. Best, ERIC PHETTEPLACE Systems Librarian, Libraries (he/him) ephetteplace at cca.edu | o 510.594.3660 (cca) 5212 Broadway | Oakland, CA | 94618 CCA is situated on the traditional unceded lands of the Ohlone peoples. Black-owned bookstores in Oakland: Ashay by the Bay , Marcus Books :(){ :|: & };: On Thu, Jul 14, 2022 at 10:54 AM C.S. Hayward wrote: > Followup question: I have made 040 c an optional field. However, 040 is > still a required field in that one of its subfields is required to be > filled. How can I change things so that 040 itself is not required? > > > Thanks, > Br. C.S. Hayward. > > > ------- Original Message ------- > On Thursday, July 14th, 2022 at 1:38 PM, C.S. Hayward < > c.s.hayward at protonmail.com> wrote: > > > > Just what the doctor ordered! > > > > > > Thanks, as usual, > > Br. C.S. Hayward > > > > > > ------- Original Message ------- > > On Thursday, July 14th, 2022 at 1:30 PM, Katrin Fischer > katrin.fischer.83 at web.de wrote: > > > > > > > > > Hi, > > > > > > I am not a cataloger, so I am not going to judge :) > > > > > > * Go to Administration > Bibliographic MARC frameworks > > > > > > * Choose MARC structure for the framework you want to update > > > > > > * Search for the field and 'Edit subfields' > > > > > > * Remove the mandatory flag from the subfield > > > > > > Hope this helps, > > > > > > Katrin > > > > > > On 14.07.22 17:48, C.S. Hayward wrote: > > > > > > > I am interested in making MARC field tag 040 subfield c optional. > > > > > > > > Two basic questions: > > > > > > > > 1: Is this something that would make you wince? > > > > > > > > 2: How can I go about doing that? > > > > > > > > Thanks, > > > > Br. C.S. Hayward, https://cjshayward.com, https://c-s-hayward.com > > > > _______________________________________________ > > > > > > > > Koha mailing list http://koha-community.org > > > > Koha at lists.katipo.co.nz > > > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > > _______________________________________________ > > > > > > Koha mailing list http://koha-community.org > > > Koha at lists.katipo.co.nz > > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From katrin.fischer.83 at web.de Fri Jul 15 06:17:12 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Thu, 14 Jul 2022 20:17:12 +0200 Subject: [Koha] Making field optional In-Reply-To: References: <67eb93bc-f129-91e4-cc51-cf258c8a96e4@web.de> Message-ID: Hi Eric, you are right - I did not read correctoy. Update to the previous instructions: Instead of 'Edit subfields' look at 'Edit tag' - the field itself can also be set to mandatory. Katrin On 14.07.22 20:11, Eric Phetteplace wrote: > I assume you remove the "mandatory" flag for *all* subfields and then the > field itself is not mandatory. > > Best, > > ERIC PHETTEPLACE Systems Librarian, Libraries (he/him) > > ephetteplace at cca.edu | o 510.594.3660 (cca) > > 5212 Broadway | Oakland, CA | 94618 > > CCA is situated on the traditional unceded lands of the Ohlone peoples. > > Black-owned bookstores in Oakland: Ashay by the Bay > , Marcus Books > > > :(){ :|: & };: > > > On Thu, Jul 14, 2022 at 10:54 AM C.S. Hayward > wrote: > >> Followup question: I have made 040 c an optional field. However, 040 is >> still a required field in that one of its subfields is required to be >> filled. How can I change things so that 040 itself is not required? >> >> >> Thanks, >> Br. C.S. Hayward. >> >> >> ------- Original Message ------- >> On Thursday, July 14th, 2022 at 1:38 PM, C.S. Hayward < >> c.s.hayward at protonmail.com> wrote: >> >> >>> Just what the doctor ordered! >>> >>> >>> Thanks, as usual, >>> Br. C.S. Hayward >>> >>> >>> ------- Original Message ------- >>> On Thursday, July 14th, 2022 at 1:30 PM, Katrin Fischer >> katrin.fischer.83 at web.de wrote: >>> >>> >>>> Hi, >>>> >>>> I am not a cataloger, so I am not going to judge :) >>>> >>>> * Go to Administration > Bibliographic MARC frameworks >>>> >>>> * Choose MARC structure for the framework you want to update >>>> >>>> * Search for the field and 'Edit subfields' >>>> >>>> * Remove the mandatory flag from the subfield >>>> >>>> Hope this helps, >>>> >>>> Katrin >>>> >>>> On 14.07.22 17:48, C.S. Hayward wrote: >>>> >>>>> I am interested in making MARC field tag 040 subfield c optional. >>>>> >>>>> Two basic questions: >>>>> >>>>> 1: Is this something that would make you wince? >>>>> >>>>> 2: How can I go about doing that? >>>>> >>>>> Thanks, >>>>> Br. C.S. Hayward, https://cjshayward.com, https://c-s-hayward.com >>>>> _______________________________________________ >>>>> >>>>> Koha mailing list http://koha-community.org >>>>> Koha at lists.katipo.co.nz >>>>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >>>> _______________________________________________ >>>> >>>> Koha mailing list http://koha-community.org >>>> Koha at lists.katipo.co.nz >>>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From katrin.fischer.83 at web.de Fri Jul 15 06:29:22 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Thu, 14 Jul 2022 20:29:22 +0200 Subject: [Koha] Translation mistakes ru-RU In-Reply-To: <09B05801-6305-4A17-A362-77ED055440B8@dhi-moskau.org> References: <09B05801-6305-4A17-A362-77ED055440B8@dhi-moskau.org> Message-ID: <0823880d-46d1-1a7e-95a3-06a7d4981cec@web.de> Hi Eugen, translations are maintained using Pootle on https://translate.koha-community.org. Translations can be suggested or submitted directly, depending on permissions. Permissions for editing a language can be requested on the koha-translate mailing list. Please make sure you include the language and your Pootle username in the email. Hope this helps, Katrin On 04.07.22 15:05, DHIM IT wrote: > Dear Colleagues, > > I found some mistakes in the translation ru-RU. > > How can I provide to all KOHA users right translation? > > Mit besten Grüßen, > > Eugen Bastron > IT-Manager > > Deutsches Historisches Institut Moskau > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From katrin.fischer.83 at web.de Fri Jul 15 06:35:06 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Thu, 14 Jul 2022 20:35:06 +0200 Subject: [Koha] Please help to set up 21.11 and 22.05 translation function In-Reply-To: References: Message-ID: <71bf10c8-103c-e170-97cd-2ed03a459a0d@web.de> Hi Frank, I can see the 21.11 and 22.05 projects for Chinese (China) and Chinese (Taiwan) on translate.koha-community.org. Do you still have problems or has this been resolved? Katrin On 08.07.22 04:05, SYDT - Frank Chou wrote: > Dear Sir/Madam, > > We have some people can help to translate during Summer period. > We will focus on Chinese-Taiwan and China part, especially Taiwan. > But we cannot see these two version in Koha Translation Project. > Can someone help put them on? > Thanks a lot... > > Best regards, > > Frank Chou > ---------------------------------------------------------------------------------------------------------- > 碩陽數位科技有限公司 > Shou Yang Digital Technology > Tel: 02-82280288 > Fax: 02-82265022 > 10F. No. 166, Jianyi Rd., Chung Ho Dist., New Taipei City 23511, Taiwan, > R.O.C. > 23511新北市中和區建一路166號10F > http://www.sydt.com.tw > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From tobrienu at gmail.com Sat Jul 16 10:56:59 2022 From: tobrienu at gmail.com (Tom Obrien) Date: Sat, 16 Jul 2022 01:56:59 +0300 Subject: [Koha] Postfix setup on ubuntu 20 Message-ID: Dear all, I am trying to configure postfix in ubuntu 20 but I get error: cat /etc/ssl/certs/thawte_premium_server_ca.pem | sudo tee -a /etc/postfix/cacert.pem cat: /etc/ssl/certs/thawte_premium_server_ca.pem: no such file or directory when I run: cat /etc/ssl/certs/Thawte_Premium_Server_CA.pem | sudo tee -a /etc/postfix/cacert.pem Can somebody advise me how I can go about this?. Will be grateful. Tom From cornejo.alvaro at gmail.com Sun Jul 17 01:53:18 2022 From: cornejo.alvaro at gmail.com (Alvaro Cornejo) Date: Sat, 16 Jul 2022 08:53:18 -0500 Subject: [Koha] Postfix setup on ubuntu 20 In-Reply-To: References: Message-ID: Hi Check the path to your certificates /etc/ssl/certs/Thawte_Premium_Server_CA.pem and/or that the certificate you want to use is really " Thawte_Premium_Server_CA.pem" What the command is trying to do is copying the content of your Thawte certificate to postfix accepted certificate list Regards, Alvaro |----------------------------------------------------------------------------------------| Stay safe / Cuídate/ Reste sécurisé *7* Switch off as you go / Apaga lo que no usas / Débranchez au fur et à mesure. *q *Recycle always / Recicla siempre / Recyclez toujours P Print only if absolutely necessary / Imprime solo si es necesario / Imprimez seulement si nécessaire Le ven. 15 juil. 2022 à 17:57, Tom Obrien a écrit : > Dear all, > I am trying to configure postfix in ubuntu 20 but I get error: > cat /etc/ssl/certs/thawte_premium_server_ca.pem | sudo tee -a > /etc/postfix/cacert.pem cat: /etc/ssl/certs/thawte_premium_server_ca.pem: > no such file or directory > when I run: > > cat /etc/ssl/certs/Thawte_Premium_Server_CA.pem | sudo tee -a > /etc/postfix/cacert.pem > > Can somebody advise me how I can go about this?. > > Will be grateful. > > Tom > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From jitendranamdev124 at gmail.com Sun Jul 17 15:48:02 2022 From: jitendranamdev124 at gmail.com (jitendra namdev) Date: Sun, 17 Jul 2022 09:18:02 +0530 Subject: [Koha] Koha Digest, Vol 201, Issue 17 In-Reply-To: References: Message-ID: Dear, First make the directory for the same mkdir /etc/postfix/cacert.pem cat: /etc/ssl/certs/thawte_premium_server_ca.pem Then do the same step. On Sun, 17 Jul 2022, 5:30 am , wrote: > Send Koha mailing list submissions to > koha at lists.katipo.co.nz > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.katipo.co.nz/mailman/listinfo/koha > or, via email, send a message with subject or body 'help' to > koha-request at lists.katipo.co.nz > > You can reach the person managing the list at > koha-owner at lists.katipo.co.nz > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Koha digest..." > > > Today's Topics: > > 1. Re: Postfix setup on ubuntu 20 (Alvaro Cornejo) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 16 Jul 2022 08:53:18 -0500 > From: Alvaro Cornejo > To: Tom Obrien > Cc: koha > Subject: Re: [Koha] Postfix setup on ubuntu 20 > Message-ID: > < > CAO55aG_XwuTSGUrd8CdwuTCmV+_3_RuLwJO1S2Pf+cWG7H6ZUA at mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hi > > Check the path to your certificates > /etc/ssl/certs/Thawte_Premium_Server_CA.pem and/or that the certificate you > want to use is really " Thawte_Premium_Server_CA.pem" > > What the command is trying to do is copying the content of your Thawte > certificate to postfix accepted certificate list > > Regards, > > Alvaro > > |----------------------------------------------------------------------------------------| > Stay safe / Cuídate/ Reste sécurisé > *7* Switch off as you go / Apaga lo que no usas / Débranchez au fur et à > mesure. > *q *Recycle always / Recicla siempre / Recyclez toujours > P Print only if absolutely necessary / Imprime solo si es necesario / > Imprimez seulement si nécessaire > > > Le ven. 15 juil. 2022 à 17:57, Tom Obrien a écrit : > > > Dear all, > > I am trying to configure postfix in ubuntu 20 but I get error: > > cat /etc/ssl/certs/thawte_premium_server_ca.pem | sudo tee -a > > /etc/postfix/cacert.pem cat: /etc/ssl/certs/thawte_premium_server_ca.pem: > > no such file or directory > > when I run: > > > > cat /etc/ssl/certs/Thawte_Premium_Server_CA.pem | sudo tee -a > > /etc/postfix/cacert.pem > > > > Can somebody advise me how I can go about this?. > > > > Will be grateful. > > > > Tom > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Koha mailing list > Koha at lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha > > > ------------------------------ > > End of Koha Digest, Vol 201, Issue 17 > ************************************* > From lianda at akademia.ac.za Mon Jul 18 01:50:31 2022 From: lianda at akademia.ac.za (Lianda Coetzer) Date: Sun, 17 Jul 2022 13:50:31 +0000 Subject: [Koha] Koha: Overdue Notices Message-ID: Good day I am the Librarian at Akademia, a private higher education institution in South Africa. I have 28 years of experience as a librarian and we have been using Koha for the past two years. I have a question regarding setting up the overdue notices. I have installed the plugin: patron emailer - but my messages keep on pending. Could anybody advise on what I am doing wrong? I have created a CSV list from notices and slips and also tried the list created from the circulation module - overdues - but still no success. Any assistance will be highly appreciated. Kind regards Lianda Vriendelike groete / Kind regards [Logo] Lianda Coetzer Bibliotekaris Librarian Akademia, Gerhardstraat 117, Centurion // 0861 222 888 lianda at akademia.ac.za www.akademia.ac.za [Logo] [Logo] Akademia MSW (Maatskappyregistrasienommer: 2005/024616/08) is by die Departement van Ho?r Onderwys en Opleiding as privaat ho?ronderwysinstelling geregistreer ingevolge die Wet op Ho?r Onderwys, 1997 Registrasienommer: 2011/HE08/005 | Akademia NPO (Company Registration Number: 2005/024616/08) is registered with the Department of Higher Education and Training as a higher education institution in terms of the Higher Education Act, 1997 * Registration number: 2011 / HE08 / 005 Die volle inhoud van hierdie e-pos en enige aanhangsels wat met die amptelike sake van Akademia verband hou, is die privaat eiendom van Akademia. Dit is vertroulik, wetlik geprivilegeer en regtens beskerm. Akademia besit en onderskryf nie enige ander inhoud nie. Die menings en opinies is di? van die afsender, tensy daar duidelik gemeld word dat dit di? van Akademia is. Die persoon aan wie die e-pos gerig is, is die enigste gemagtigde ontvanger daarvan. Stel die afsender asseblief dadelik in kennis indien die e-pos u onopsetlik bereik het en moet nie die inhoud lees, openbaar maak of op enige wyse gebruik nie, maar skrap dit permanent van u stelsel. Akademia kan nie verseker dat die integriteit van hierdie kommunikasie intak is of dat dit vry van foute, virusse, onderskeppings of steurings is nie. From tomascohen at gmail.com Mon Jul 18 02:37:26 2022 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Sun, 17 Jul 2022 11:37:26 -0300 Subject: [Koha] Koha: Overdue Notices In-Reply-To: References: Message-ID: It sounds like you don't have the 'process_message_queue.pl' cronjob set to run on the server. Best regards El dom, 17 jul 2022 10:51, Lianda Coetzer escribió: > Good day > > I am the Librarian at Akademia, a private higher education institution in > South Africa. I have 28 years of experience as a librarian and we have been > using Koha for the past two years. > > I have a question regarding setting up the overdue notices. I have > installed the plugin: patron emailer - but my messages keep on pending. > Could anybody advise on what I am doing wrong? I have created a CSV list > from notices and slips and also tried the list created from the circulation > module - overdues - but still no success. > > Any assistance will be highly appreciated. > > Kind regards > Lianda > > Vriendelike groete / Kind regards > > [Logo] > > Lianda Coetzer > > Bibliotekaris > Librarian > > Akademia, Gerhardstraat 117, Centurion // 0861 222 888 > > lianda at akademia.ac.za > www.akademia.ac.za > > [Logo] > > [Logo] > > Akademia MSW (Maatskappyregistrasienommer: 2005/024616/08) is by die > Departement van Ho?r Onderwys en Opleiding as privaat > ho?ronderwysinstelling geregistreer ingevolge die Wet op Ho?r Onderwys, > 1997 Registrasienommer: 2011/HE08/005 | Akademia NPO (Company Registration > Number: 2005/024616/08) is registered with the Department of Higher > Education and Training as a higher education institution in terms of the > Higher Education Act, 1997 * Registration number: 2011 / HE08 / 005 > > Die volle inhoud van hierdie e-pos en enige aanhangsels wat met die > amptelike sake van Akademia verband hou, is die privaat eiendom van > Akademia. Dit is vertroulik, wetlik geprivilegeer en regtens beskerm. > Akademia besit en onderskryf nie enige ander inhoud nie. Die menings en > opinies is di? van die afsender, tensy daar duidelik gemeld word dat dit > di? van Akademia is. Die persoon aan wie die e-pos gerig is, is die enigste > gemagtigde ontvanger daarvan. Stel die afsender asseblief dadelik in kennis > indien die e-pos u onopsetlik bereik het en moet nie die inhoud lees, > openbaar maak of op enige wyse gebruik nie, maar skrap dit permanent van u > stelsel. Akademia kan nie verseker dat die integriteit van hierdie > kommunikasie intak is of dat dit vry van foute, virusse, onderskeppings of > steurings is nie. > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From tomascohen at gmail.com Mon Jul 18 02:42:33 2022 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Sun, 17 Jul 2022 11:42:33 -0300 Subject: [Koha] Failing authentication via CAS after update to Koha 21.11.09 In-Reply-To: <30f17401-5dc6-b07c-8db9-383c6d8b3376@adminkuhn.ch> References: <30f17401-5dc6-b07c-8db9-383c6d8b3376@adminkuhn.ch> Message-ID: Are you sure the CAS server is functional? Can you try pointing your Koha or a replica to the Apereo XAS demo sites? For debugging, you should use warn "$variable"; And look for those warns in the usual logs. Remember to restart plack everytime you change the code. Hope it helps! El lun, 11 jul 2022 8:41, Michael Kuhn escribió: > Hi > > We are using Debian GNU/Linux 10 with Koha 21.11.09 (after an update > from Debian 9 and Koha 19.05.02). > > Since the update the CAS authentication via Koha OPAC is no more > working. The content of system preferences "OPACBaseURL", > "casAuthentication", "casLogout" and "casServerUrl" has not changed; the > new preference "casServerVersion" ist correctly set to "CAS 2 or earlier". > > It is possible to successfully log into the CAS server but when trying > to access the Koha OPAC via CAS ("Log in using a CAS account") the > response is always "Sorry, the CAS login failed." and the user is not > logged into his Koha account. The logs don't show no error. > > I was checking all changes made in bugs 21973 22585 23771 20854 and > 28417 but to no avail. > > Does anyone have an idea how to debug 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 at adminkuhn.ch · W www.adminkuhn.ch > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From victor at tuxayo.net Mon Jul 18 12:07:03 2022 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Mon, 18 Jul 2022 02:07:03 +0200 Subject: [Koha] Time to translate: string freeze to prepare Koha 21.05.17 has begun Message-ID: <324f70b3-7636-b465-ca44-1995e0d2e7f2@tuxayo.net> Hi, String freeze is into effect as of now for the 21.05.x maintenance branch. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 21.05, then you must also copy it to 21.11 and 22.05. Otherwise your work will be lost for future versions. Happy translating :) -- Victor Grousset/tuxayo From plzulu34 at gmail.com Mon Jul 18 18:11:08 2022 From: plzulu34 at gmail.com (Paul Zulu) Date: Mon, 18 Jul 2022 08:11:08 +0200 Subject: [Koha] NUMBER OF KOHA RECORDS Message-ID: Dear Koha Community Can anyone assist me by giving the maximum number of records Koha can accommodate? Thank you. -- Paul Zulu Sub-Librarian II Mulungushi University Library P.O Box 80415 KABWE, ZAMBIA Cell: 0977875006 E-mail: plzulu34 at gmail.com From mik at adminkuhn.ch Mon Jul 18 21:22:04 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Mon, 18 Jul 2022 11:22:04 +0200 Subject: [Koha] Failing authentication via CAS after update to Koha 21.11.09 In-Reply-To: References: <30f17401-5dc6-b07c-8db9-383c6d8b3376@adminkuhn.ch> Message-ID: Hi Tomas You wrote: > Are you sure the CAS server is functional? Yes, when clicking "Log in using a CAS account" the login dialogue of the CAS server appears, after logging in it can be proven that the login there was successful. But the Koha OPAC seems to think the login failed and it says "Sorry, the CAS login failed." This seems to happen because Koha script "Auth.pm" returns 1 for "invalidCasLogin" but I can't find out why. > Can you try pointing your Koha or a replica to the Apereo XAS demo > sites? I found https://apereo.github.io/cas/index.html and I changed "casServerUrl" to "https://apereo.github.io/cas/" but when I click "Log in using a CAS account" there is a message "404 File not found" instead of showing me a the CAS server dialogue. > For debugging, you should use > > warn "$variable"; > > And look for those warns in the usual logs. Remember to restart plack > everytime you change the code. This worked but due to my limited knowledge of Perl and the Koha authentication process via CAS it didn't help me further... Can maybe someone confirm that the CAS server login actually works with Koha 21.11.09? As said we didn't change the CAS configuration since Koha 19.05.02. 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 at adminkuhn.ch · W www.adminkuhn.ch > El lun, 11 jul 2022 8:41, Michael Kuhn > escribió: > > Hi > > We are using Debian GNU/Linux 10 with Koha 21.11.09 (after an update > from Debian 9 and Koha 19.05.02). > > Since the update the CAS authentication via Koha OPAC is no more > working. The content of system preferences "OPACBaseURL", > "casAuthentication", "casLogout" and "casServerUrl" has not changed; > the > new preference "casServerVersion" ist correctly set to "CAS 2 or > earlier". > > It is possible to successfully log into the CAS server but when trying > to access the Koha OPAC via CAS ("Log in using a CAS account") the > response is always "Sorry, the CAS login failed." and the user is not > logged into his Koha account. The logs don't show no error. > > I was checking all changes made in bugs 21973 22585 23771 20854 and > 28417 but to no avail. > > Does anyone have an idea how to debug 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 at adminkuhn.ch > · W www.adminkuhn.ch > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > From mik at adminkuhn.ch Mon Jul 18 22:03:54 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Mon, 18 Jul 2022 12:03:54 +0200 Subject: [Koha] Failing authentication via CAS after update to Koha 21.11.09 In-Reply-To: References: <30f17401-5dc6-b07c-8db9-383c6d8b3376@adminkuhn.ch> Message-ID: <22fc47b2-3c5d-fb15-5423-8b7f66fe4318@adminkuhn.ch> Hi Tomas I saw I was using the wrong URL to the Apereo XAS demo site - instead of "https://apereo.github.io/cas/" it is actually "https://casserver.herokuapp.com/cas". So I tried anew using this URL but still the CAS login into Koha fails ("Sorry, the CAS login failed."). I also tried this URL on my Koha demo site using 22.05.00 but the login doesn't work either. 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 at adminkuhn.ch · W www.adminkuhn.ch Am 18.07.22 um 11:22 schrieb Michael Kuhn: > Hi Tomas > > You wrote: > > > Are you sure the CAS server is functional? > > Yes, when clicking "Log in using a CAS account" the login dialogue of > the CAS server appears, after logging in it can be proven that the login > there was successful. > > But the Koha OPAC seems to think the login failed and it says "Sorry, > the CAS login failed." This seems to happen because Koha script > "Auth.pm" returns 1 for "invalidCasLogin" but I can't find out why. > > > Can you try pointing your Koha or a replica to the Apereo XAS demo > > sites? > > I found https://apereo.github.io/cas/index.html and I changed > "casServerUrl" to "https://apereo.github.io/cas/" but when I click "Log > in using a CAS account" there is a message "404 File not found" instead > of showing me a the CAS server dialogue. > > > For debugging, you should use > > > > warn "$variable"; > > > > And look for those warns in the usual logs. Remember to restart plack > > everytime you change the code. > > This worked but due to my limited knowledge of Perl and the Koha > authentication process via CAS it didn't help me further... > > Can maybe someone confirm that the CAS server login actually works with > Koha 21.11.09? As said we didn't change the CAS configuration since Koha > 19.05.02. > > Best wishes: Michael From katrin.fischer.83 at web.de Mon Jul 18 22:14:35 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Mon, 18 Jul 2022 12:14:35 +0200 Subject: [Koha] Failing authentication via CAS after update to Koha 21.11.09 In-Reply-To: <22fc47b2-3c5d-fb15-5423-8b7f66fe4318@adminkuhn.ch> References: <30f17401-5dc6-b07c-8db9-383c6d8b3376@adminkuhn.ch> <22fc47b2-3c5d-fb15-5423-8b7f66fe4318@adminkuhn.ch> Message-ID: <252bcac9-e735-b2b7-4064-2f8483faefdf@web.de> Hi Michael, do you have user information for this CAS server? I didn't find any sample login yet. Can you log in using the URL directly in the browser? Best wishes, Katrin On 18.07.22 12:03, Michael Kuhn wrote: > Hi Tomas > > I saw I was using the wrong URL to the Apereo XAS demo site - instead > of "https://apereo.github.io/cas/" it is actually > "https://casserver.herokuapp.com/cas". So I tried anew using this URL > but still the CAS login into Koha fails ("Sorry, the CAS login failed."). > > I also tried this URL on my Koha demo site using 22.05.00 but the > login doesn't work either. > > Best wishes: Michael From mik at adminkuhn.ch Mon Jul 18 22:25:57 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Mon, 18 Jul 2022 12:25:57 +0200 Subject: [Koha] Failing authentication via CAS after update to Koha 21.11.09 In-Reply-To: <252bcac9-e735-b2b7-4064-2f8483faefdf@web.de> References: <30f17401-5dc6-b07c-8db9-383c6d8b3376@adminkuhn.ch> <22fc47b2-3c5d-fb15-5423-8b7f66fe4318@adminkuhn.ch> <252bcac9-e735-b2b7-4064-2f8483faefdf@web.de> Message-ID: Hi Katrin You wrote: > do you have user information for this CAS server? I didn't find any > sample login yet. Can you log in using the URL directly in the > browser? Yes, the URL and the login (casuser / Mellon) for the demo sites can be found at https://apereo.github.io/cas/Demos.html Logging in at https://casserver.herokuapp.com/cas using these credentials is successful. It's just Koha that won't accept it. 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 at adminkuhn.ch · W www.adminkuhn.ch > On 18.07.22 12:03, Michael Kuhn wrote: >> Hi Tomas >> >> I saw I was using the wrong URL to the Apereo XAS demo site - instead >> of "https://apereo.github.io/cas/" it is actually >> "https://casserver.herokuapp.com/cas". So I tried anew using this URL >> but still the CAS login into Koha fails ("Sorry, the CAS login failed."). >> >> I also tried this URL on my Koha demo site using 22.05.00 but the >> login doesn't work either. >> >> Best wishes: Michael > _______________________________________________ > > Koha mailing list  http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From katrin.fischer.83 at web.de Mon Jul 18 22:34:41 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Mon, 18 Jul 2022 12:34:41 +0200 Subject: [Koha] Failing authentication via CAS after update to Koha 21.11.09 In-Reply-To: References: <30f17401-5dc6-b07c-8db9-383c6d8b3376@adminkuhn.ch> <22fc47b2-3c5d-fb15-5423-8b7f66fe4318@adminkuhn.ch> <252bcac9-e735-b2b7-4064-2f8483faefdf@web.de> Message-ID: <434b49c4-e26c-ff43-4a11-a67f926c6b43@web.de> Hi Michael, I have tried to set it up in your demo, hope you don't mind! You also need a user with username casuser, but the problem I am seeing is that the login link doesn't show in the OPAC in the first place. Only the heading. So there is some problem there for sure. But: If I log in on the website and then refresh the login page in Koha, I am logged in successfully. Hope this helps, Katrin On 18.07.22 12:25, Michael Kuhn wrote: > Hi Katrin > > You wrote: > > > do you have user information for this CAS server? I didn't find any > > sample login yet. Can you log in using the URL directly in the > > browser? > > Yes, the URL and the login (casuser / Mellon) for the demo sites can > be found at https://apereo.github.io/cas/Demos.html > > Logging in at https://casserver.herokuapp.com/cas using these > credentials is successful. It's just Koha that won't accept it. > > Best wishes: Michael From katrin.fischer.83 at web.de Mon Jul 18 22:48:18 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Mon, 18 Jul 2022 12:48:18 +0200 Subject: [Koha] Failing authentication via CAS after update to Koha 21.11.09 In-Reply-To: <434b49c4-e26c-ff43-4a11-a67f926c6b43@web.de> References: <30f17401-5dc6-b07c-8db9-383c6d8b3376@adminkuhn.ch> <22fc47b2-3c5d-fb15-5423-8b7f66fe4318@adminkuhn.ch> <252bcac9-e735-b2b7-4064-2f8483faefdf@web.de> <434b49c4-e26c-ff43-4a11-a67f926c6b43@web.de> Message-ID: <27566e60-683b-9f50-82a1-25afa8d1f8e8@web.de> Hi Michael, sorry, it was probably a glitch with the local login, I now also see the "Sorry, the CAS login failed." message and the login doesn't work :( But the login link now appeared. Katrin On 18.07.22 12:34, Katrin Fischer wrote: > Hi Michael, > > I have tried to set it up in your demo, hope you don't mind! > > You also need a user with username casuser, but the problem I am seeing > is that the login link doesn't show in the OPAC in the first place. Only > the heading. So there is some problem there for sure. > > But: If I log in on the website and then refresh the login page in Koha, > I am logged in successfully. > > Hope this helps, > > Katrin > > > On 18.07.22 12:25, Michael Kuhn wrote: >> Hi Katrin >> >> You wrote: >> >> > do you have user information for this CAS server? I didn't find any >> > sample login yet. Can you log in using the URL directly in the >> > browser? >> >> Yes, the URL and the login (casuser / Mellon) for the demo sites can >> be found at https://apereo.github.io/cas/Demos.html >> >> Logging in at https://casserver.herokuapp.com/cas using these >> credentials is successful. It's just Koha that won't accept it. >> >> Best wishes: Michael > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From mik at adminkuhn.ch Mon Jul 18 23:31:26 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Mon, 18 Jul 2022 13:31:26 +0200 Subject: [Koha] Failing authentication via CAS after update to Koha 21.11.09 In-Reply-To: <27566e60-683b-9f50-82a1-25afa8d1f8e8@web.de> References: <30f17401-5dc6-b07c-8db9-383c6d8b3376@adminkuhn.ch> <22fc47b2-3c5d-fb15-5423-8b7f66fe4318@adminkuhn.ch> <252bcac9-e735-b2b7-4064-2f8483faefdf@web.de> <434b49c4-e26c-ff43-4a11-a67f926c6b43@web.de> <27566e60-683b-9f50-82a1-25afa8d1f8e8@web.de> Message-ID: Hi Katrin Meanwhile I was able to login into Koha using casServerUrl https://casserver.herokuapp.com/cas and CAS/Koha-User "casuser" (which I first had to create) on my Koha 22.05.00 demo site as well as on the productive Koha 21.11.09 installation. But the login using the original casServerUrl still doesn't work. So for the moment I think there is a problem with the original CAS-Server. Best wishes and thanks for your support! 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 at adminkuhn.ch · W www.adminkuhn.ch Am 18.07.22 um 12:48 schrieb Katrin Fischer: > Hi Michael, > > sorry, it was probably a glitch with the local login, I now also see the > "Sorry, the CAS login failed." message and the login doesn't work :( > > But the login link now appeared. > > Katrin > > > On 18.07.22 12:34, Katrin Fischer wrote: >> Hi Michael, >> >> I have tried to set it up in your demo, hope you don't mind! >> >> You also need a user with username casuser, but the problem I am seeing >> is that the login link doesn't show in the OPAC in the first place. Only >> the heading. So there is some problem there for sure. >> >> But: If I log in on the website and then refresh the login page in Koha, >> I am logged in successfully. >> >> Hope this helps, >> >> Katrin >> >> >> On 18.07.22 12:25, Michael Kuhn wrote: >>> Hi Katrin >>> >>> You wrote: >>> >>> > do you have user information for this CAS server? I didn't find any >>> > sample login yet. Can you log in using the URL directly in the >>> > browser? >>> >>> Yes, the URL and the login (casuser / Mellon) for the demo sites can >>> be found at https://apereo.github.io/cas/Demos.html >>> >>> Logging in at https://casserver.herokuapp.com/cas using these >>> credentials is successful. It's just Koha that won't accept it. >>> >>> Best wishes: Michael >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list  http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From cornejo.alvaro at gmail.com Tue Jul 19 03:58:18 2022 From: cornejo.alvaro at gmail.com (Alvaro Cornejo) Date: Mon, 18 Jul 2022 10:58:18 -0500 Subject: [Koha] NUMBER OF KOHA RECORDS In-Reply-To: References: Message-ID: Hi Paul Koha does not have a record limit. Limit is determined by your drive space and memory size. Of course, the bigger the DB and the bigger the patrons, the more powerful the hardware required. Regards, Alvaro |----------------------------------------------------------------------------------------| Stay safe / Cuídate/ Reste sécurisé *7* Switch off as you go / Apaga lo que no usas / Débranchez au fur et à mesure. *q *Recycle always / Recicla siempre / Recyclez toujours P Print only if absolutely necessary / Imprime solo si es necesario / Imprimez seulement si nécessaire Le lun. 18 juil. 2022 à 01:11, Paul Zulu a écrit : > Dear Koha Community > > Can anyone assist me by giving the maximum number of records Koha can > accommodate? Thank you. > > -- > Paul Zulu > Sub-Librarian II > Mulungushi University Library > P.O Box 80415 > KABWE, ZAMBIA > Cell: 0977875006 > E-mail: plzulu34 at gmail.com > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From Barbara.Johnson at bedfordtx.gov Tue Jul 19 04:58:23 2022 From: Barbara.Johnson at bedfordtx.gov (Barbara Johnson) Date: Mon, 18 Jul 2022 16:58:23 +0000 Subject: [Koha] =?windows-1252?q?KohaCon22_=96_Registration_closes_August_?= =?windows-1252?q?31=2C_2022?= Message-ID: KohaCon22 will be held from (Tuesday-Friday) 20-23 September 2022 in Lawrence, Kansas, USA. This will be a hybrid conference with both in-person and online attendance and participation options. Join us in Lawrence where you can 'Level Up' with Koha through face-to-face networking, brainstorming, problem solving and sharing ideas. * KohaCon22 is free to attend. Register here – https://forms.gle/KBRTYZYGBx35iMMf7 * View the conference schedule here – https://koha-us.org/events/conferences/kohacon22/#tab3 * Hotel, air and ground transportation information – https://koha-us.org/events/conferences/kohacon22/#tab5 For more details and the most up-to-date information on the conference, please keep an eye on the conference page at http://koha-us.org/events/conferences/kohacon22/ If you have questions please direct them to the koha-US conference committee at conferences at koha-us.org. ----- Barbara Glassford Johnson koha-US President, 2022 CONFIDENTIALITY NOTICE: This City of Bedford (CoB) email transmission is intended only for the use of the individual to whom it is addressed and may contain information that is confidential, privileged, and exempt from disclosure. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you have received this email in error, please notify the sender immediately by return email and destroy all electronic and paper copies of the original message and any attachments immediately. From katrin.fischer.83 at web.de Tue Jul 19 05:14:58 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Mon, 18 Jul 2022 19:14:58 +0200 Subject: [Koha] Failing authentication via CAS after update to Koha 21.11.09 In-Reply-To: References: <30f17401-5dc6-b07c-8db9-383c6d8b3376@adminkuhn.ch> <22fc47b2-3c5d-fb15-5423-8b7f66fe4318@adminkuhn.ch> <252bcac9-e735-b2b7-4064-2f8483faefdf@web.de> <434b49c4-e26c-ff43-4a11-a67f926c6b43@web.de> <27566e60-683b-9f50-82a1-25afa8d1f8e8@web.de> Message-ID: Hi Michael, hope you can figure out the issue soon. Could something have changed with the usernames/logins? Best wishes, Katrin On 18.07.22 13:31, Michael Kuhn wrote: > Hi Katrin > > Meanwhile I was able to login into Koha using casServerUrl > https://casserver.herokuapp.com/cas and CAS/Koha-User "casuser" (which > I first had to create) on my Koha 22.05.00 demo site as well as on the > productive Koha 21.11.09 installation. > > But the login using the original casServerUrl still doesn't work. So > for the moment I think there is a problem with the original CAS-Server. > > Best wishes and thanks for your support! > > Michael From plzulu34 at gmail.com Tue Jul 19 18:25:57 2022 From: plzulu34 at gmail.com (Paul Zulu) Date: Tue, 19 Jul 2022 08:25:57 +0200 Subject: [Koha] NUMBER OF KOHA RECORDS In-Reply-To: References: Message-ID: Thank you for the information. On Mon, Jul 18, 2022 at 5:58 PM Alvaro Cornejo wrote: > Hi Paul > > Koha does not have a record limit. Limit is determined by your drive space > and memory size. > > Of course, the bigger the DB and the bigger the patrons, the more powerful > the hardware required. > > Regards, > > Alvaro > > |----------------------------------------------------------------------------------------| > Stay safe / Cuídate/ Reste sécurisé > *7* Switch off as you go / Apaga lo que no usas / Débranchez au fur et à > mesure. > *q *Recycle always / Recicla siempre / Recyclez toujours > P Print only if absolutely necessary / Imprime solo si es necesario / > Imprimez seulement si nécessaire > > > Le lun. 18 juil. 2022 à 01:11, Paul Zulu a écrit : > >> Dear Koha Community >> >> Can anyone assist me by giving the maximum number of records Koha can >> accommodate? Thank you. >> >> -- >> Paul Zulu >> Sub-Librarian II >> Mulungushi University Library >> P.O Box 80415 >> KABWE, ZAMBIA >> Cell: 0977875006 >> E-mail: plzulu34 at gmail.com >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> > -- Paul Zulu Sub-Librarian II Mulungushi University Library P.O Box 80415 KABWE, ZAMBIA Cell: 0977875006 E-mail: plzulu34 at gmail.com From sami_rasheed at yahoo.com Tue Jul 19 20:56:55 2022 From: sami_rasheed at yahoo.com (Sami M. Rasheed) Date: Tue, 19 Jul 2022 08:56:55 +0000 (UTC) Subject: [Koha] Koha upgrade schema issue References: <2062025918.2366128.1658221015968.ref@mail.yahoo.com> Message-ID: <2062025918.2366128.1658221015968@mail.yahoo.com> Kindly, Koha Group Please let me know how to correct the Koha upgrade schema issue. The system displays the following error while I'm using the (koha-upgrade-schema library) to upgrade the Koha system: DEV atomic update /usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/bug_30899.pl  [11:37:44]: Bug 30899 - Check borrower_attribute_types FK constraint (30449 follow-up) I'm using: Koha version: 21.11 OS version: Ubuntu 20.04.4 LTS MySQL version: mysql Ver 8.0.29 -0ubuntu0.20.04.3 for Linux on x86_64 ((Ubuntu)) Thanks Sami Abu Darbeya From amutsikiwa at gmail.com Tue Jul 19 22:30:20 2022 From: amutsikiwa at gmail.com (Admire Mutsikiwa) Date: Tue, 19 Jul 2022 11:30:20 +0100 Subject: [Koha] Warm standby backup server for Koha Message-ID: Good day. Above matter refers. I would like to have a deployment architecture where I have two Koha servers running the same version of Koha and periodically, the warm backup server's MySQL server is synchronised with the primary server. I would appreciate how such a setup could be implemented. Kind regards, Admire Mutsikiwa +447361470772 linkedin.com/in/admire-mutsikiwa-9b187937 From katrin.fischer.83 at web.de Tue Jul 19 22:42:21 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Tue, 19 Jul 2022 12:42:21 +0200 Subject: [Koha] Koha upgrade schema issue In-Reply-To: <2062025918.2366128.1658221015968@mail.yahoo.com> References: <2062025918.2366128.1658221015968.ref@mail.yahoo.com> <2062025918.2366128.1658221015968@mail.yahoo.com> Message-ID: <645f924a-1b89-d3db-041b-36022294468b@web.de> Hi, what error did you get? Katrin On 19.07.22 10:56, Sami M. Rasheed wrote: > > > Kindly, Koha Group > Please let me know how to correct the Koha upgrade schema issue. > The system displays the following error while I'm using the (koha-upgrade-schema library) to upgrade the Koha system: > > > > DEV atomic update /usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/bug_30899.pl  [11:37:44]: Bug 30899 - Check borrower_attribute_types FK constraint (30449 follow-up) > > I'm using: > > Koha version: 21.11 > > OS version: Ubuntu 20.04.4 LTS > > MySQL version: mysql Ver 8.0.29 -0ubuntu0.20.04.3 for Linux on x86_64 ((Ubuntu)) > > Thanks > Sami Abu Darbeya > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From lennon at kohasupport.com Tue Jul 19 22:43:47 2022 From: lennon at kohasupport.com (=?UTF-8?Q?Lennon_Mazonde?=) Date: Tue, 19 Jul 2022 10:43:47 +0000 Subject: [Koha] Warm standby backup server for Koha In-Reply-To: References: Message-ID: <01000182160e8934-172b2221-a8e9-4bca-b259-d142a81cf5e8-000000@email.amazonses.com> Hi Admire, I think one way to do it would be schedule a cron job that dumps and exports your database from server A to B. I wrote a bash script to migrate databases between MySQL/MariaDB servers that might help - it's available on GitHub at https://github.com/grandmaestr/koha-scripts. You'll need to modify it a bit to suit your use case but feel free to clone the repo.  Best regards, Lennon Mazonde KohaSupport lennon at kohasupport.com www.kohasupport.com 651 North Broad Street, Middletown, DE 19709, USA The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. On 7/19/22 12:30 PM, Admire Mutsikiwa wrote: Good day. Above matter refers. I would like to have a deployment architecture where I have two Koha servers running the same version of Koha and periodically, the warm backup server's MySQL server is synchronised with the primary server. I would appreciate how such a setup could be implemented. Kind regards, Admire Mutsikiwa +447361470772 linkedin.com/in/admire-mutsikiwa-9b187937 _______________________________________________ Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From naveen at neduet.edu.pk Tue Jul 19 23:07:52 2022 From: naveen at neduet.edu.pk (Ms. Naveen Ali) Date: Tue, 19 Jul 2022 16:07:52 +0500 (PKT) Subject: [Koha] Customizing Bibliographic Frameworks Message-ID: <1274210658.485450.1658228872958.JavaMail.zimbra@neduet.edu.pk> Dear All, I am customizing a bibliographic framework for our library. I have changed the 'Text for Librarian' and 'Text for OPAC' fields for some 952 sub fields such as $t, $f, $i etc. The changes are visible in the Edit Items Form. However when using Item Search or viewing on OPAC the customized labels are not shown. Rather the default labels are shown. How do I resolve this. With thanks and best regards, Naveen Ali ITM-JE (EAKL) Inst Representative for HEC Digital Library Resources. NEDUET, Karachi. From mik at adminkuhn.ch Wed Jul 20 01:13:13 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Tue, 19 Jul 2022 15:13:13 +0200 Subject: [Koha] Adding items to a list not possible in Koha 21.11.09 Message-ID: Hi Recently we updated to Koha 21.11.09. Now in the staff client when selecting one or more items in a result list and trying to add it to a list by clicking "Add to list", then selecting the respective list, Koha says "No item was selected". Which is of course not true. However it is not possible to add any items from a result list to "Your lists" or "Public lists". Is this a bug or does anyone know the reason for this behaviour? Maybe there is some connection to bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24522 (Nothing happens when trying to add nothing to a list in staff) 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 at adminkuhn.ch · W www.adminkuhn.ch From M.de.Rooy at rijksmuseum.nl Wed Jul 20 01:25:25 2022 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Tue, 19 Jul 2022 13:25:25 +0000 Subject: [Koha] Adding items to a list not possible in Koha 21.11.09 In-Reply-To: References: Message-ID: Sounds like a bug I recently resolved. Check Bugzilla. ________________________________ Van: Koha namens Michael Kuhn Verzonden: dinsdag 19 juli 2022 15:13 Aan: Koha Onderwerp: [Koha] Adding items to a list not possible in Koha 21.11.09 Hi Recently we updated to Koha 21.11.09. Now in the staff client when selecting one or more items in a result list and trying to add it to a list by clicking "Add to list", then selecting the respective list, Koha says "No item was selected". Which is of course not true. However it is not possible to add any items from a result list to "Your lists" or "Public lists". Is this a bug or does anyone know the reason for this behaviour? Maybe there is some connection to bug https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.koha-community.org%2Fbugzilla3%2Fshow_bug.cgi%3Fid%3D24522&data=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C1587a8b0b5ec40cfcf5c08da69889204%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938332548379463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5xd%2BUXz6rMh3jqpRH28UoSOt5NyiL7w5bz9Sgugf0ws%3D&reserved=0 (Nothing happens when trying to add nothing to a list in staff) 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 at adminkuhn.ch · W https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.adminkuhn.ch%2F&data=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C1587a8b0b5ec40cfcf5c08da69889204%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938332548379463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=j%2FZYs4eilzQZXFp%2Fe6fmzouPLBvS9kdw7qOx71hmH2k%3D&reserved=0 _______________________________________________ Koha mailing list https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkoha-community.org%2F&data=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C1587a8b0b5ec40cfcf5c08da69889204%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938332548379463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=t4YI4miSfzY0f6im89q6g3GB6Zv1jcGtsgS8GEBYylc%3D&reserved=0 Koha at lists.katipo.co.nz Unsubscribe: https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.katipo.co.nz%2Fmailman%2Flistinfo%2Fkoha&data=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C1587a8b0b5ec40cfcf5c08da69889204%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938332548379463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=eaV4pr%2BN0y1RAuwrWH%2FYiV9tA7qKGv7TqxOtbmlv7Xw%3D&reserved=0 From cornejo.alvaro at gmail.com Wed Jul 20 01:40:37 2022 From: cornejo.alvaro at gmail.com (Alvaro Cornejo) Date: Tue, 19 Jul 2022 08:40:37 -0500 Subject: [Koha] Warm standby backup server for Koha In-Reply-To: References: Message-ID: Hi You can do this with mysql independently from koha. Mysql has the possibility to automatically synchronize db between two, or more, mysql instances. Just be sure to have both servers with the same MySql, OS and koha versions to avoid issues. Regards, Alvaro |----------------------------------------------------------------------------------------| Stay safe / Cuídate/ Reste sécurisé *7* Switch off as you go / Apaga lo que no usas / Débranchez au fur et à mesure. *q *Recycle always / Recicla siempre / Recyclez toujours P Print only if absolutely necessary / Imprime solo si es necesario / Imprimez seulement si nécessaire Le mar. 19 juil. 2022 à 05:31, Admire Mutsikiwa a écrit : > Good day. Above matter refers. I would like to have a deployment > architecture where I have two Koha servers running the same version of Koha > and periodically, the warm backup server's MySQL server is synchronised > with the primary server. I would appreciate how such a setup could be > implemented. > > > Kind regards, > > Admire Mutsikiwa > +447361470772 > linkedin.com/in/admire-mutsikiwa-9b187937 > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From cornejo.alvaro at gmail.com Wed Jul 20 01:44:21 2022 From: cornejo.alvaro at gmail.com (Alvaro Cornejo) Date: Tue, 19 Jul 2022 08:44:21 -0500 Subject: [Koha] Customizing Bibliographic Frameworks In-Reply-To: <1274210658.485450.1658228872958.JavaMail.zimbra@neduet.edu.pk> References: <1274210658.485450.1658228872958.JavaMail.zimbra@neduet.edu.pk> Message-ID: Hi Have you restarted plack and/or your browser? Regards |----------------------------------------------------------------------------------------| Stay safe / Cuídate/ Reste sécurisé *7* Switch off as you go / Apaga lo que no usas / Débranchez au fur et à mesure. *q *Recycle always / Recicla siempre / Recyclez toujours P Print only if absolutely necessary / Imprime solo si es necesario / Imprimez seulement si nécessaire Le mar. 19 juil. 2022 à 06:10, Ms. Naveen Ali a écrit : > Dear All, > > I am customizing a bibliographic framework for our library. > I have changed the 'Text for Librarian' and 'Text for OPAC' fields for > some 952 sub fields such as $t, $f, $i etc. > The changes are visible in the Edit Items Form. > However when using Item Search or viewing on OPAC the customized labels > are not shown. Rather the default labels are shown. > How do I resolve this. > > With thanks and best regards, > > Naveen Ali > > ITM-JE (EAKL) > Inst Representative for > HEC Digital Library Resources. > NEDUET, Karachi. > > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From mik at adminkuhn.ch Wed Jul 20 02:15:00 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Tue, 19 Jul 2022 16:15:00 +0200 Subject: [Koha] Adding items to a list not possible in Koha 21.11.09 In-Reply-To: References: Message-ID: <9eba8200-2e72-6300-0aed-452736c703de@adminkuhn.ch> Hi Marcel Are you maybe talking about Bug 30925 (Creating public list by adding items to new list creates a private list)? System preference "OpacAllowPublicListCreation" was already set to "Allow". I changed files "addbybiblionumber.tt" and "opac-addbybiblionumber.tt" according to https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=136373&action=diff - I even restarted the full host. It didn't change the behaviour in Koha 21.11.09. This it is not possible anymore to add items to lists. 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 at adminkuhn.ch · W www.adminkuhn.ch Am 19.07.22 um 15:25 schrieb Marcel de Rooy: > Sounds like a bug I recently resolved. Check Bugzilla. > ------------------------------------------------------------------------ > *Van:* Koha namens Michael Kuhn > > *Verzonden:* dinsdag 19 juli 2022 15:13 > *Aan:* Koha > *Onderwerp:* [Koha] Adding items to a list not possible in Koha 21.11.09 > Hi > > Recently we updated to Koha 21.11.09. > > Now in the staff client when selecting one or more items in a result > list and trying to add it to a list by clicking "Add to list", then > selecting the respective list, Koha says "No item was selected". Which > is of course not true. However it is not possible to add any items from > a result list to "Your lists" or "Public lists". > > Is this a bug or does anyone know the reason for this behaviour? > > Maybe there is some connection to bug > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.koha-community.org%2Fbugzilla3%2Fshow_bug.cgi%3Fid%3D24522&data=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C1587a8b0b5ec40cfcf5c08da69889204%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938332548379463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5xd%2BUXz6rMh3jqpRH28UoSOt5NyiL7w5bz9Sgugf0ws%3D&reserved=0 > > (Nothing > happens when trying to add nothing to a list in staff) > > 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 at adminkuhn.ch · W > https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.adminkuhn.ch%2F&data=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C1587a8b0b5ec40cfcf5c08da69889204%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938332548379463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=j%2FZYs4eilzQZXFp%2Fe6fmzouPLBvS9kdw7qOx71hmH2k%3D&reserved=0 > > _______________________________________________ > > Koha mailing list > https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkoha-community.org%2F&data=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C1587a8b0b5ec40cfcf5c08da69889204%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938332548379463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=t4YI4miSfzY0f6im89q6g3GB6Zv1jcGtsgS8GEBYylc%3D&reserved=0 > > Koha at lists.katipo.co.nz > Unsubscribe: > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.katipo.co.nz%2Fmailman%2Flistinfo%2Fkoha&data=05%7C01%7Cm.de.rooy%40rijksmuseum.nl%7C1587a8b0b5ec40cfcf5c08da69889204%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938332548379463%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=eaV4pr%2BN0y1RAuwrWH%2FYiV9tA7qKGv7TqxOtbmlv7Xw%3D&reserved=0 > From M.de.Rooy at rijksmuseum.nl Wed Jul 20 02:31:03 2022 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Tue, 19 Jul 2022 14:31:03 +0000 Subject: [Koha] Adding items to a list not possible in Koha 21.11.09 In-Reply-To: <9eba8200-2e72-6300-0aed-452736c703de@adminkuhn.ch> References: <9eba8200-2e72-6300-0aed-452736c703de@adminkuhn.ch> Message-ID: Okay, your problem is not the same 🙂 But I tried to reproduce with 20.11 and master. (Not having 21.11 at hand.) And I could add items to a list in staff as well as OPAC. So not sure whats going on. Anyone else trying in 21.11 ? ________________________________ Van: Michael Kuhn Verzonden: dinsdag 19 juli 2022 16:15 Aan: Marcel de Rooy ; Koha Onderwerp: Re: [Koha] Adding items to a list not possible in Koha 21.11.09 Hi Marcel Are you maybe talking about Bug 30925 (Creating public list by adding items to new list creates a private list)? System preference "OpacAllowPublicListCreation" was already set to "Allow". I changed files "addbybiblionumber.tt" and "opac-addbybiblionumber.tt" according to https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.koha-community.org%2Fbugzilla3%2Fattachment.cgi%3Fid%3D136373%26action%3Ddiff&data=05%7C01%7CM.de.Rooy%40rijksmuseum.nl%7C6ef2b4593b644b33b04508da699111b7%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938369032944389%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Yg%2B7VtMNIl6nJI4nASHEx7siwEwKJC48kXa9x3btdeg%3D&reserved=0 - I even restarted the full host. It didn't change the behaviour in Koha 21.11.09. This it is not possible anymore to add items to lists. 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 at adminkuhn.ch · W https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.adminkuhn.ch%2F&data=05%7C01%7CM.de.Rooy%40rijksmuseum.nl%7C6ef2b4593b644b33b04508da699111b7%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938369032944389%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=O299%2FC8CmpvOmVf8fBFTBacvgqmA%2BV2tfsaRQbnWPq0%3D&reserved=0 Am 19.07.22 um 15:25 schrieb Marcel de Rooy: > Sounds like a bug I recently resolved. Check Bugzilla. > ------------------------------------------------------------------------ > *Van:* Koha namens Michael Kuhn > > *Verzonden:* dinsdag 19 juli 2022 15:13 > *Aan:* Koha > *Onderwerp:* [Koha] Adding items to a list not possible in Koha 21.11.09 > Hi > > Recently we updated to Koha 21.11.09. > > Now in the staff client when selecting one or more items in a result > list and trying to add it to a list by clicking "Add to list", then > selecting the respective list, Koha says "No item was selected". Which > is of course not true. However it is not possible to add any items from > a result list to "Your lists" or "Public lists". > > Is this a bug or does anyone know the reason for this behaviour? > > Maybe there is some connection to bug > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.koha-community.org%2Fbugzilla3%2Fshow_bug.cgi%3Fid%3D24522&data=05%7C01%7CM.de.Rooy%40rijksmuseum.nl%7C6ef2b4593b644b33b04508da699111b7%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938369032944389%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pVOW%2FmilyKYYgKW0OKd5BW0RaRuQ3CtQ2IjKEY6%2FLwk%3D&reserved=0 > > (Nothing > happens when trying to add nothing to a list in staff) > > 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 at adminkuhn.ch · W > https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.adminkuhn.ch%2F&data=05%7C01%7CM.de.Rooy%40rijksmuseum.nl%7C6ef2b4593b644b33b04508da699111b7%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938369032944389%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=O299%2FC8CmpvOmVf8fBFTBacvgqmA%2BV2tfsaRQbnWPq0%3D&reserved=0 > > _______________________________________________ > > Koha mailing list > https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkoha-community.org%2F&data=05%7C01%7CM.de.Rooy%40rijksmuseum.nl%7C6ef2b4593b644b33b04508da699111b7%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938369032944389%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0OObTrgVWWeM3PAyFfCGF16mXvOHlmoa5s79L11L6Xw%3D&reserved=0 > > Koha at lists.katipo.co.nz > Unsubscribe: > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.katipo.co.nz%2Fmailman%2Flistinfo%2Fkoha&data=05%7C01%7CM.de.Rooy%40rijksmuseum.nl%7C6ef2b4593b644b33b04508da699111b7%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637938369032944389%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BLt6Ljz8bb%2F8K5S9DJ7B7wcG7gcxq3Crt%2FDURixQqhY%3D&reserved=0 > From c.s.hayward at protonmail.com Wed Jul 20 03:49:42 2022 From: c.s.hayward at protonmail.com (C.S. Hayward) Date: Tue, 19 Jul 2022 15:49:42 +0000 Subject: [Koha] Success so far Message-ID: I’ve emailed the list about various difficulties, and gotten to a point where the Koha server has been running smoothly, and I am able to enjoy Koha and use it as desired. Thank you for all your help! Sent from Proton Mail for iOS From ephetteplace at cca.edu Wed Jul 20 04:02:20 2022 From: ephetteplace at cca.edu (Eric Phetteplace) Date: Tue, 19 Jul 2022 09:02:20 -0700 Subject: [Koha] Customizing Bibliographic Frameworks In-Reply-To: References: <1274210658.485450.1658228872958.JavaMail.zimbra@neduet.edu.pk> Message-ID: I think the text on the OPAC does not change, you'd need to edit the XSLT templates. The "Text for OPAC" will show up under the MARC view tab, but not the "Normal view". See here in the Koha Manual https://koha-community.org/manual/21.05/en/html/administration.html#edit-a-marc-field-tag > The ‘Label for lib’ is what will show in the staff interface if you have advancedMARCeditor set to display labels > The ‘Label for OPAC’ is what will show on the MARC view in the OPAC Editing the XSLT is a bit more involved but you could do it if you're locally hosted. Best, ERIC PHETTEPLACE Systems Librarian, Libraries (he/him) ephetteplace at cca.edu | o 510.594.3660 (cca) 5212 Broadway | Oakland, CA | 94618 CCA is situated on the traditional unceded lands of the Ohlone peoples. Black-owned bookstores in Oakland: Ashay by the Bay , Marcus Books :(){ :|: & };: On Tue, Jul 19, 2022 at 6:45 AM Alvaro Cornejo wrote: > Hi > > Have you restarted plack and/or your browser? > > Regards > > |----------------------------------------------------------------------------------------| > Stay safe / Cuídate/ Reste sécurisé > *7* Switch off as you go / Apaga lo que no usas / Débranchez au fur et à > mesure. > *q *Recycle always / Recicla siempre / Recyclez toujours > P Print only if absolutely necessary / Imprime solo si es necesario / > Imprimez seulement si nécessaire > > > Le mar. 19 juil. 2022 à 06:10, Ms. Naveen Ali a > écrit : > > > Dear All, > > > > I am customizing a bibliographic framework for our library. > > I have changed the 'Text for Librarian' and 'Text for OPAC' fields for > > some 952 sub fields such as $t, $f, $i etc. > > The changes are visible in the Edit Items Form. > > However when using Item Search or viewing on OPAC the customized labels > > are not shown. Rather the default labels are shown. > > How do I resolve this. > > > > With thanks and best regards, > > > > Naveen Ali > > > > ITM-JE (EAKL) > > Inst Representative for > > HEC Digital Library Resources. > > NEDUET, Karachi. > > > > > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From eb at efdss.org Wed Jul 20 05:49:23 2022 From: eb at efdss.org (Elaine Bradtke) Date: Tue, 19 Jul 2022 10:49:23 -0700 Subject: [Koha] Error message on upgrade Message-ID: We're not sure what this means, and or what we need to do to correct it, if anything. Upgrade to 22.05.02.000 [18:18:02]: Koha 22.05.02 release DEV atomic update /usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/ bug_30899.pl [18:18:02]: Bug 30899 - Check borrower_attribute_types FK constraint (30449 follow-up) NO PLURAL FORM HEADER FOUND - DEFAULTING TO 2 Elaine Bradtke VWML English Folk Dance and Song Society Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY Tel +44 (0) 20 7485 2206 (This number is for the English Folk Dance and Song Society in London, England. If you wish to phone me personally, send an e-mail first. I work off site) -------------------------------------------------------------------------- Registered Company No. 297142 Charity Registered in England and Wales No. 305999 From david at davidnind.com Wed Jul 20 09:21:03 2022 From: david at davidnind.com (David Nind) Date: Wed, 20 Jul 2022 09:21:03 +1200 Subject: [Koha] Proposals now open for hosting KohaCon23 Message-ID: Summary ------------ The request for proposals to host KohaCon 2023 is now open! If you or your organization would like to *organize KohaCon23*, please enter all the required information on the KohaCon 2023 proposals wiki page:[1] https://wiki.koha-community.org/wiki/KohaCon23_Proposals The closing date for bids is *6 September 2022 23:59 UTC*. Proposals received will be discussed at the *7 September 2022 General IRC Meeting* ( https://wiki.koha-community.org/wiki/General_IRC_meeting_7_September_2022). 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 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 *6 September 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. Reply to this email 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. David Nind | david at davidnind.com From sami_rasheed at yahoo.com Wed Jul 20 16:55:16 2022 From: sami_rasheed at yahoo.com (Sami M. Rasheed) Date: Wed, 20 Jul 2022 04:55:16 +0000 (UTC) Subject: [Koha] Koha upgrade schema issue In-Reply-To: References: Message-ID: <2037564597.41125.1658292916923@mail.yahoo.com> Dear Kartin, I have this error: DEV atomic update /usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/bug_30899.pl  [11:37:44]: Bug 30899 - Check borrower_attribute_types FK constraint (30449 follow-up) I'm using: Koha version: 21.11 OS version: Ubuntu 20.04.4 LTS MySQL version: mysql Ver 8.0.29 -0ubuntu0.20.04.3 for Linux on x86_64 ((Ubuntu)) Thanks From katrin.fischer.83 at web.de Wed Jul 20 23:01:48 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Wed, 20 Jul 2022 13:01:48 +0200 Subject: [Koha] Koha upgrade schema issue In-Reply-To: <2037564597.41125.1658292916923@mail.yahoo.com> References: <2037564597.41125.1658292916923@mail.yahoo.com> Message-ID: Hi Sami, this is just feedback about a database update that has been run, not an error. The only thing strange about it is that it's a DEV update and not a regular one. Which exact version did you update to? (21.11.?) Hope this helps, Katrin On 20.07.22 06:55, Sami M. Rasheed wrote: > Dear Kartin, > I have this error: > DEV atomic update /usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/bug_30899.pl  [11:37:44]: Bug 30899 - Check borrower_attribute_types FK constraint (30449 follow-up) > > I'm using: > > Koha version: 21.11 > > OS version: Ubuntu 20.04.4 LTS > > MySQL version: mysql Ver 8.0.29 -0ubuntu0.20.04.3 for Linux on x86_64 ((Ubuntu)) > Thanks > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From tobrienu at gmail.com Thu Jul 21 05:13:05 2022 From: tobrienu at gmail.com (Tom Obrien) Date: Wed, 20 Jul 2022 20:13:05 +0300 Subject: [Koha] Postfix setup on ubuntu 20 In-Reply-To: References: Message-ID: Hi all, I am still getting challenges in setting postfix to work. Is there an alternative that is easier to set as mail server that I can use for koha to send emails. I have installed koha 21 on Ubuntu 20 LTS. Regards Tom On Sat, Jul 16, 2022 at 4:54 PM Alvaro Cornejo wrote: > Hi > > Check the path to your certificates > /etc/ssl/certs/Thawte_Premium_Server_CA.pem and/or that the certificate you > want to use is really " Thawte_Premium_Server_CA.pem" > > What the command is trying to do is copying the content of your Thawte > certificate to postfix accepted certificate list > > Regards, > > Alvaro > > |----------------------------------------------------------------------------------------| > Stay safe / Cuídate/ Reste sécurisé > *7* Switch off as you go / Apaga lo que no usas / Débranchez au fur et à > mesure. > *q *Recycle always / Recicla siempre / Recyclez toujours > P Print only if absolutely necessary / Imprime solo si es necesario / > Imprimez seulement si nécessaire > > > Le ven. 15 juil. 2022 à 17:57, Tom Obrien a écrit : > >> Dear all, >> I am trying to configure postfix in ubuntu 20 but I get error: >> cat /etc/ssl/certs/thawte_premium_server_ca.pem | sudo tee -a >> /etc/postfix/cacert.pem cat: /etc/ssl/certs/thawte_premium_server_ca.pem: >> no such file or directory >> when I run: >> >> cat /etc/ssl/certs/Thawte_Premium_Server_CA.pem | sudo tee -a >> /etc/postfix/cacert.pem >> >> Can somebody advise me how I can go about this?. >> >> Will be grateful. >> >> Tom >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> > From tobrienu at gmail.com Thu Jul 21 13:58:43 2022 From: tobrienu at gmail.com (Tom Obrien) Date: Thu, 21 Jul 2022 04:58:43 +0300 Subject: [Koha] Postfix setup on ubuntu 20 In-Reply-To: References: Message-ID: Hi all, I am still getting challenges in setting postfix to work. Is there an alternative that is easier to set as mail server that I can use for koha to send emails. I have installed koha 21 on Ubuntu 20 LTS. Regards Tom On Sat, Jul 16, 2022 at 4:54 PM Alvaro Cornejo wrote: > Hi > > Check the path to your certificates > /etc/ssl/certs/Thawte_Premium_Server_CA.pem and/or that the certificate you > want to use is really " Thawte_Premium_Server_CA.pem" > > What the command is trying to do is copying the content of your Thawte > certificate to postfix accepted certificate list > > Regards, > > Alvaro > > |----------------------------------------------------------------------------------------| > Stay safe / Cuídate/ Reste sécurisé > *7* Switch off as you go / Apaga lo que no usas / Débranchez au fur et à > mesure. > *q *Recycle always / Recicla siempre / Recyclez toujours > P Print only if absolutely necessary / Imprime solo si es necesario / > Imprimez seulement si nécessaire > > > Le ven. 15 juil. 2022 à 17:57, Tom Obrien a écrit : > >> Dear all, >> I am trying to configure postfix in ubuntu 20 but I get error: >> cat /etc/ssl/certs/thawte_premium_server_ca.pem | sudo tee -a >> /etc/postfix/cacert.pem cat: /etc/ssl/certs/thawte_premium_server_ca.pem: >> no such file or directory >> when I run: >> >> cat /etc/ssl/certs/Thawte_Premium_Server_CA.pem | sudo tee -a >> /etc/postfix/cacert.pem >> >> Can somebody advise me how I can go about this?. >> >> Will be grateful. >> >> Tom >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> > From russellgeeps at gmail.com Thu Jul 21 18:57:48 2022 From: russellgeeps at gmail.com (Russel G. P. Shihepo) Date: Thu, 21 Jul 2022 07:57:48 +0100 Subject: [Koha] Postfix setup on ubuntu 20 In-Reply-To: References: Message-ID: Hi Tom You can try to explore these methods below, they all worked 100% for me *Method 1:* *Configure Email in Koha using In-built SMTP Module* *instructions at:* http://libtechnophile.blogspot.com/2022/02/configure-email-in-koha-using-in-built.html *Method 2: * *Install Exim mail server as the MTA/SMTP for Koha to send emails* *Instructions: * https://ubuntu.com/server/docs/mail-exim4 *other instructions on exim if the above don't work: * http://kohageek.blogspot.com/2017/05/configure-exim-with-gmail-to-send-notices.html Best of luck! Best regards, Russel Shihepo On Thu, Jul 21, 2022 at 2:59 AM Tom Obrien wrote: > Hi all, > I am still getting challenges in setting postfix to work. Is there an > alternative that is easier to set as mail server that I can use for koha > to send emails. I have installed koha 21 on Ubuntu 20 LTS. > > Regards > Tom > > On Sat, Jul 16, 2022 at 4:54 PM Alvaro Cornejo > wrote: > > > Hi > > > > Check the path to your certificates > > /etc/ssl/certs/Thawte_Premium_Server_CA.pem and/or that the certificate > you > > want to use is really " Thawte_Premium_Server_CA.pem" > > > > What the command is trying to do is copying the content of your Thawte > > certificate to postfix accepted certificate list > > > > Regards, > > > > Alvaro > > > > > |----------------------------------------------------------------------------------------| > > Stay safe / Cuídate/ Reste sécurisé > > *7* Switch off as you go / Apaga lo que no usas / Débranchez au fur et à > > mesure. > > *q *Recycle always / Recicla siempre / Recyclez toujours > > P Print only if absolutely necessary / Imprime solo si es necesario / > > Imprimez seulement si nécessaire > > > > > > Le ven. 15 juil. 2022 à 17:57, Tom Obrien a écrit : > > > >> Dear all, > >> I am trying to configure postfix in ubuntu 20 but I get error: > >> cat /etc/ssl/certs/thawte_premium_server_ca.pem | sudo tee -a > >> /etc/postfix/cacert.pem cat: > /etc/ssl/certs/thawte_premium_server_ca.pem: > >> no such file or directory > >> when I run: > >> > >> cat /etc/ssl/certs/Thawte_Premium_Server_CA.pem | sudo tee -a > >> /etc/postfix/cacert.pem > >> > >> Can somebody advise me how I can go about this?. > >> > >> Will be grateful. > >> > >> Tom > >> _______________________________________________ > >> > >> Koha mailing list http://koha-community.org > >> Koha at lists.katipo.co.nz > >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > >> > > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From egpetridis at gmail.com Fri Jul 22 05:36:13 2022 From: egpetridis at gmail.com (Manos PETRIDIS) Date: Thu, 21 Jul 2022 20:36:13 +0300 Subject: [Koha] Question on search.pl sort options Message-ID: Hello all, I remember that one of the sort options in /cgi-bin/koha/catalogue/search.pl was sorting by call number. Examples may still be found at http://lib.zilcc.ru/cgi-bin/koha/opac-search.pl and http://lib-2dim-kalam.thess.sch.gr/cgi-bin/koha/opac-search.pl but also at https://koha-community.org/manual/18.11/en/html/searching.html I know that the examples above are OPAC searches but I remember distinctly that the sort by callnumber was an option in intranet search as well. Now, in the current koha version the sort by callnumber option has been changed to sort by Class number. I've searched bugzilla and found no mention of such a need, to change sort options that is. Is the change documented somewhere? kind regards, Manos Petridis From loveandmarigold at gmail.com Fri Jul 22 05:41:31 2022 From: loveandmarigold at gmail.com (Sanjay Uchcharia) Date: Thu, 21 Jul 2022 23:11:31 +0530 Subject: [Koha] =?utf-8?q?=28no_subject=29?= Message-ID: What is Shelving Control Number and how to apply & how to use it. From gwilliams at nekls.org Fri Jul 22 08:27:57 2022 From: gwilliams at nekls.org (George) Date: Thu, 21 Jul 2022 15:27:57 -0500 Subject: [Koha] The Terrific Every-Other-Thursday Training Video - Season 2 / Episode 21 - Debugging jQuery and CSS Message-ID: <726322fb-2587-9091-feec-a4e2c1fab38c@nekls.org> Learn about a couple of tools to help you compare and contrast Koha with and without your CSS/jQuery changes. -- George Williams Pronouns: he/him Next Search Catalog Coordinator Send NEXT support e-mails to nexthelp at nekls.org NEKLS Office: 785-838-4090 Toll Free: 888-296-6963 Fax: 785-838-3989 Next After-Hours: 785-813-1356 For specific support issues, please use: Next Catalog Support: nexthelp at nekls.org Courier Support: chandwork at nekls.org Technology Support: tech at nekls.org 4317 W 6th St, Lawrence, KS, 66049 From grishavkumar at gmail.com Fri Jul 22 17:13:05 2022 From: grishavkumar at gmail.com (Rishav Kumar Gond) Date: Fri, 22 Jul 2022 10:43:05 +0530 Subject: [Koha] Koha as CMS in 21.11 version Message-ID: Hi all, I am facing difficulty in implementing Koha as CMS because of some changes in opac-main.tt due to version upgrade in 21.11, kindly help if possible. Regards, Rishav From cjf at wmu.se Fri Jul 22 20:50:55 2022 From: cjf at wmu.se (Fairlamb, Christina) Date: Fri, 22 Jul 2022 10:50:55 +0200 Subject: [Koha] 22.05 - Search Patrons Page Empty Message-ID: Hello, Since upgrading to 22.05 when using the search patron feature. on the actual search patron page, the table shows up blank, with no patrons matching the search term. Without pressing enter in the search bar it does generate matching patrons whilst typing and they can be selected and used as usual, it's just the table on the search patron page that shows nothing. -- Christina From christos.hayward at gmail.com Sun Jul 24 01:01:39 2022 From: christos.hayward at gmail.com (Christos Hayward) Date: Sat, 23 Jul 2022 09:01:39 -0400 Subject: [Koha] One thing I realized Message-ID: I earlier write that I saw only duct tape-ish ways of getting HTTPS over a LAN. At least one implementation was mentioned, a self-signed certificate that all computers on the LAN would be made to accept. I saw another, arguably cleaner way to get HTTPS over a LAN. Make a website, perhaps a bare stub to minimize surface areas to vulnerabilities, publicly, at https://library.xyz.com. Then cron a copying of the certificates from the public site to a server on the LAN. Then set a local DNS (or, worse, hosts files) to assign library.xyz.com the local network IP of the net. This would seem to sidestep at least some of the security implications for having a library server on the public network. -- Unworthy Br. *Christos Hayward*, author and apologist, and more importantly novice at *St. Demetrios Orthodox Monastery * (monastery webshop ). I invite you to visit my *author site* (author bio , bookshelf ). One title is Happiness in an Age of Crisis: Ancient Wisdom from the Eastern Orthodox Church . My most recent posting is a purchasable "How do I love thee?" shirt . From tomascohen at gmail.com Sun Jul 24 07:25:44 2022 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Sat, 23 Jul 2022 16:25:44 -0300 Subject: [Koha] One thing I realized In-Reply-To: References: Message-ID: You can have the server on a DMZ and access it through a reverse proxy that does SSL. El sáb, 23 jul 2022 10:02, Christos Hayward escribió: > I earlier write that I saw only duct tape-ish ways of getting HTTPS over a > LAN. At least one implementation was mentioned, a self-signed certificate > that all computers on the LAN would be made to accept. > > I saw another, arguably cleaner way to get HTTPS over a LAN. Make a > website, perhaps a bare stub to minimize surface areas to vulnerabilities, > publicly, at https://library.xyz.com. Then cron a copying of the > certificates from the public site to a server on the LAN. Then set a local > DNS (or, worse, hosts files) to assign library.xyz.com the local network > IP > of the net. > > This would seem to sidestep at least some of the security implications for > having a library server on the public network. > > -- > > Unworthy Br. *Christos Hayward*, author and apologist, and more importantly > novice at *St. Demetrios Orthodox Monastery > * (monastery > webshop ). > > I invite you to visit my *author site* (author > bio > , bookshelf >). > One title is Happiness in an Age of Crisis: Ancient Wisdom from the Eastern > Orthodox Church . > > My most recent posting is a purchasable "How do I love thee?" shirt > . > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From katrin.fischer.83 at web.de Sun Jul 24 23:03:27 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sun, 24 Jul 2022 13:03:27 +0200 Subject: [Koha] Error message on upgrade In-Reply-To: References: Message-ID: Hi Elaine, the first part is the message that a database update has been run. In 22.05.02 one update was not moved to the db_revs, but this is not a problem, as it has still been run and there was no error. The second part looks like it might be a warning about a language/translation installed, but should possibly also not cause you an issue. Hope this helps, Katrin On 19.07.22 19:49, Elaine Bradtke wrote: > We're not sure what this means, and or what we need to do to correct it, if > anything. > > Upgrade to 22.05.02.000 [18:18:02]: Koha 22.05.02 release > DEV atomic update > /usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/ > bug_30899.pl [18:18:02]: Bug 30899 - Check borrower_attribute_types FK > constraint (30449 follow-up) > NO PLURAL FORM HEADER FOUND - DEFAULTING TO 2 > > Elaine Bradtke > VWML > English Folk Dance and Song Society > Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY > Tel +44 (0) 20 7485 2206 (This number is for the English Folk Dance and > Song Society in London, England. If you wish to phone me personally, send > an e-mail first. I work off site) > -------------------------------------------------------------------------- > Registered Company No. 297142 > Charity Registered in England and Wales No. 305999 > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From katrin.fischer.83 at web.de Sun Jul 24 23:12:26 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sun, 24 Jul 2022 13:12:26 +0200 Subject: [Koha] Question on search.pl sort options In-Reply-To: References: Message-ID: <6b15096f-8d46-7214-4cc0-b9be4838bfeb@web.de> Hi Manos, I checked the current development branch and I see a callnumber sort option in OPAC and staff interface. Which version are you looking at? Are you using Zebra or Elasticsearch? Could it be a local customization? Hope this helps, Katrin On 21.07.22 19:36, Manos PETRIDIS wrote: > Hello all, > > I remember that one of the sort options in /cgi-bin/koha/catalogue/search.pl > was sorting by call number. > Examples may still be found at > http://lib.zilcc.ru/cgi-bin/koha/opac-search.pl and > http://lib-2dim-kalam.thess.sch.gr/cgi-bin/koha/opac-search.pl but also at > https://koha-community.org/manual/18.11/en/html/searching.html > I know that the examples above are OPAC searches but I remember distinctly > that the sort by callnumber was an option in intranet search as well. > > Now, in the current koha version the sort by callnumber option has been > changed to sort by Class number. > I've searched bugzilla and found no mention of such a need, to change sort > options that is. > > Is the change documented somewhere? > > kind regards, > Manos Petridis > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From egpetridis at gmail.com Sun Jul 24 23:37:04 2022 From: egpetridis at gmail.com (Manos PETRIDIS) Date: Sun, 24 Jul 2022 14:37:04 +0300 Subject: [Koha] Question on search.pl sort options In-Reply-To: <6b15096f-8d46-7214-4cc0-b9be4838bfeb@web.de> References: <6b15096f-8d46-7214-4cc0-b9be4838bfeb@web.de> Message-ID: I’m using the latest stock version, installed via packages. 22.05.02.000 to be exact. Your comment though made me think laterally and found out that it is a difference between en and en-GB English interfaces. Many thanks for your time and effort! Στις Κυρ 24 Ιουλ 2022 στις 2:13 μμ ο χρήστης Katrin Fischer < katrin.fischer.83 at web.de> έγραψε: > Hi Manos, > > I checked the current development branch and I see a callnumber sort > option in OPAC and staff interface. > > Which version are you looking at? Are you using Zebra or Elasticsearch? > > Could it be a local customization? > > Hope this helps, > > Katrin > > On 21.07.22 19:36, Manos PETRIDIS wrote: > > Hello all, > > > > I remember that one of the sort options in /cgi-bin/koha/catalogue/ > search.pl > > was sorting by call number. > > Examples may still be found at > > http://lib.zilcc.ru/cgi-bin/koha/opac-search.pl and > > http://lib-2dim-kalam.thess.sch.gr/cgi-bin/koha/opac-search.pl but also > at > > https://koha-community.org/manual/18.11/en/html/searching.html > > I know that the examples above are OPAC searches but I remember > distinctly > > that the sort by callnumber was an option in intranet search as well. > > > > Now, in the current koha version the sort by callnumber option has been > > changed to sort by Class number. > > I've searched bugzilla and found no mention of such a need, to change > sort > > options that is. > > > > Is the change documented somewhere? > > > > kind regards, > > Manos Petridis > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From katrin.fischer.83 at web.de Sun Jul 24 23:41:13 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sun, 24 Jul 2022 13:41:13 +0200 Subject: [Koha] Question on search.pl sort options In-Reply-To: References: <6b15096f-8d46-7214-4cc0-b9be4838bfeb@web.de> Message-ID: <7a860eb0-f9ad-583f-dfb9-1d196348f2fd@web.de> Thx for sharing the explanation :) On 24.07.22 13:37, Manos PETRIDIS wrote: > I’m using the latest stock version, installed via packages. > 22.05.02.000 to be exact. > > Your comment though made me think laterally and found out that it is a > difference between en and en-GB English interfaces. > > Many thanks for your time and effort! > > Στις Κυρ 24 Ιουλ 2022 στις 2:13 μμ ο χρήστης Katrin Fischer > έγραψε: > > Hi Manos, > > I checked the current development branch and I see a callnumber sort > option in OPAC and staff interface. > > Which version are you looking at? Are you using Zebra or > Elasticsearch? > > Could it be a local customization? > > Hope this helps, > > Katrin > > On 21.07.22 19:36, Manos PETRIDIS wrote: > > Hello all, > > > > I remember that one of the sort options in > /cgi-bin/koha/catalogue/search.pl > > was sorting by call number. > > Examples may still be found at > > http://lib.zilcc.ru/cgi-bin/koha/opac-search.pl and > > http://lib-2dim-kalam.thess.sch.gr/cgi-bin/koha/opac-search.pl > but also at > > https://koha-community.org/manual/18.11/en/html/searching.html > > I know that the examples above are OPAC searches but I remember > distinctly > > that the sort by callnumber was an option in intranet search as > well. > > > > Now, in the current koha version the sort by callnumber option > has been > > changed to sort by Class number. > > I've searched bugzilla and found no mention of such a need, to > change sort > > options that is. > > > > Is the change documented somewhere? > > > > kind regards, > > Manos Petridis > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From arouss1980 at gmail.com Sun Jul 24 23:53:15 2022 From: arouss1980 at gmail.com (Andreas Roussos) Date: Sun, 24 Jul 2022 14:53:15 +0300 Subject: [Koha] Adding items to a list not possible in Koha 21.11.09 In-Reply-To: References: Message-ID: <9cb9c517-3194-908e-d181-5d6c244e6c72@gmail.com> Hi Michael, I've tried to reproduce the issue you describe on a development 21.11.09 instance that I set up, but was not successful. So, I have a few questions for you to help me diagnose this ;-) Assuming a package installation, have you restarted the koha-common service following the upgrade? Have you performed a hard refresh of your web browser's cache? (hit CTRL-F5) Finally, which version of Koha did you upgrade from? Kind regards, Andreas From katrin.fischer.83 at web.de Mon Jul 25 00:26:18 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sun, 24 Jul 2022 14:26:18 +0200 Subject: [Koha] Koha 22.05: Where has the columns setting for the patrons list gone? In-Reply-To: <5f49021f94e94fa18734b06a962ae270@gwdg.de> References: <61ced22e514b4b8a992809c8f65f2db5@gwdg.de> <5f49021f94e94fa18734b06a962ae270@gwdg.de> Message-ID: Hi Anke, sorry for the late reply. I see the same on current master: the patron search table doesn't have a 'Columns' link. I don't know if this was intentional with moving the search to the API or if it was an oversight. Katrin On 07.07.22 17:30, Bruns, Anke wrote: > Hi Katrin, > > thank you! I meanwhile found out that in some list views in 22.05 the Columns button is present, in others not. I don't know if this was on purpose. > > The difference between 22.05 and 20.11 I stumbled upon is the following: > > - Home -> Patrons -> (Search for a list of patrons, or just all patrons) -> in V20.11 just above the table with the patrons list, there is a "Columns" link (it's not actually a "button") permitting to choose which columns of the patron record I want to display. In V22.11 this link is missing. > > Whereas: > > - Home -> Tools -> Patron lists -> (Choose one of the patron lists, if existent) -> in the table appearing here, the Columns link is there in 20.11 and in 22.05. > > Regards, > Anke > >> -----Ursprüngliche Nachricht----- >> Von: Koha Im Auftrag von Katrin Fischer >> Gesendet: Mittwoch, 6. Juli 2022 19:18 >> An: koha at lists.katipo.co.nz >> Betreff: Re: [Koha] Koha 22.05: Where has the columns setting for the patrons >> list gone? >> >> Hi Anke, >> >> in 22.05 the normal patron search is also used for the circulation >> patron search. Maybe you meant that list? >> >> The settings are in Administration > Table settings > Patrons > >> memberresultst >> >> Hope this helps, >> >> Katrin >> >> On 06.07.22 17:02, Bruns, Anke wrote: >>> Hi, >>> >>> a minor problem but nonetheless...: In version 20.11 we had the possibility >>> to choose in the staff client which columns from the patron record we wanted >>> to display in the patrons short list. There was a "Columns" button next to >>> the "Export" one. This option seems to have gone with one of the more recent >>> versions (we upgraded directly from 20.11 to 22.05, so no idea when exactly >>> this was the case). Instead there is a "Clear filter" button now. >>> >>> Is there any chance to get the choice of columns option back? E.g. we do not >>> need or want to display the Date of Birth column which isn't populated in >>> our case. >>> >>> Thank you for any advice and best regards, >>> Anke >>> >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From katrin.fischer.83 at web.de Mon Jul 25 00:30:18 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sun, 24 Jul 2022 14:30:18 +0200 Subject: [Koha] 22.05 - Search Patrons Page Empty In-Reply-To: References: Message-ID: <9cbd4c59-2127-eafe-0d61-7a6627816cde@web.de> Hi Christina, this sounds like a problem with the API. To verify if that is the cause of your problem: If you go to Administration > Libraries, does the table with the libraries show? If it doesn't: * How did you install Koha? * Which OS and which version of it are you using? * And if you can: what does your /etc/apt/sources.list.d/koha.list look like? Hope this helps, Katrin On 22.07.22 10:50, Fairlamb, Christina wrote: > Hello, > > Since upgrading to 22.05 when using the search patron feature. on the > actual search patron page, the table shows up blank, with no patrons > matching the search term. Without pressing enter in the search bar it does > generate matching patrons whilst typing and they can be selected and used > as usual, it's just the table on the search patron page that shows nothing. > From evanstewart406 at gmail.com Mon Jul 25 09:43:19 2022 From: evanstewart406 at gmail.com (Evan Stewart) Date: Sun, 24 Jul 2022 16:43:19 -0500 Subject: [Koha] 22.05 - Search Patrons Page Empty In-Reply-To: <9cbd4c59-2127-eafe-0d61-7a6627816cde@web.de> References: <9cbd4c59-2127-eafe-0d61-7a6627816cde@web.de> Message-ID: Hi Christina, I had the same problem on my recent update to Koha 22. I am running Raspberry Pi OS (based on Debian 10). I solved the problem by installing a missing software package that was skipped when I ran the upgrade to Koha 22. Can you go to the Koha information page: *More* > *About Koha* and click the *Perl Modules* tab. Check the status of this module: "Mojolicious::Plugin::OpenAPI" Does it show as installed or not installed? -Evan Stewart On Sun, Jul 24, 2022 at 7:30 AM Katrin Fischer wrote: > Hi Christina, > > this sounds like a problem with the API. > > To verify if that is the cause of your problem: If you go to > Administration > Libraries, does the table with the libraries show? If > it doesn't: > > * How did you install Koha? > * Which OS and which version of it are you using? > * And if you can: what does your /etc/apt/sources.list.d/koha.list > look like? > > Hope this helps, > > Katrin > > > On 22.07.22 10:50, Fairlamb, Christina wrote: > > Hello, > > > > Since upgrading to 22.05 when using the search patron feature. on the > > actual search patron page, the table shows up blank, with no patrons > > matching the search term. Without pressing enter in the search bar it > does > > generate matching patrons whilst typing and they can be selected and used > > as usual, it's just the table on the search patron page that shows > nothing. > > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From dcook at prosentient.com.au Mon Jul 25 12:39:36 2022 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Mon, 25 Jul 2022 10:39:36 +1000 Subject: [Koha] One thing I realized (HTTPS over a LAN) In-Reply-To: References: Message-ID: <055b01d89fbf$09043430$1b0c9c90$@prosentient.com.au> Is the goal to have a Koha library system that is not available on the Internet but does have HTTPS over the local network? While I haven't personalized used it, you could look at the DNS-01 challenge with Let's Encrypt: https://letsencrypt.org/docs/challenge-types/. That would give a lot of options. If you didn't want to have any public sites, you could use a third-party hosted DNS provider with an API. You can point public DNS at internal IP addresses. AWS does this all the time for servers. You could look at this for a more specific example: https://blog.heckel.io/2018/08/05/issuing-lets-encrypt-certificates-for-65000-internal-servers/ This would be an even cleaner solution. And if you didn't want that IP address public for whatever reason, you could probably do a split DNS so that only local servers see the IP address, but that's going a bit more above and beyond. Ways and ways... 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 -----Original Message----- Message: 1 Date: Sat, 23 Jul 2022 09:01:39 -0400 From: Christos Hayward To: koha Subject: [Koha] One thing I realized Message-ID: Content-Type: text/plain; charset="UTF-8" I earlier write that I saw only duct tape-ish ways of getting HTTPS over a LAN. At least one implementation was mentioned, a self-signed certificate that all computers on the LAN would be made to accept. I saw another, arguably cleaner way to get HTTPS over a LAN. Make a website, perhaps a bare stub to minimize surface areas to vulnerabilities, publicly, at https://library.xyz.com. Then cron a copying of the certificates from the public site to a server on the LAN. Then set a local DNS (or, worse, hosts files) to assign library.xyz.com the local network IP of the net. This would seem to sidestep at least some of the security implications for having a library server on the public network. -- Unworthy Br. *Christos Hayward*, author and apologist, and more importantly novice at *St. Demetrios Orthodox Monastery * (monastery webshop ). I invite you to visit my *author site* (author bio , bookshelf ). One title is Happiness in an Age of Crisis: Ancient Wisdom from the Eastern Orthodox Church . My most recent posting is a purchasable "How do I love thee?" shirt . ------------------------------ Message: 2 Date: Sat, 23 Jul 2022 16:25:44 -0300 From: Tomas Cohen Arazi To: Christos Hayward Cc: koha Subject: Re: [Koha] One thing I realized Message-ID: Content-Type: text/plain; charset="UTF-8" You can have the server on a DMZ and access it through a reverse proxy that does SSL. El sáb, 23 jul 2022 10:02, Christos Hayward escribió: > I earlier write that I saw only duct tape-ish ways of getting HTTPS > over a LAN. At least one implementation was mentioned, a self-signed > certificate that all computers on the LAN would be made to accept. > > I saw another, arguably cleaner way to get HTTPS over a LAN. Make a > website, perhaps a bare stub to minimize surface areas to > vulnerabilities, publicly, at https://library.xyz.com. Then cron a > copying of the certificates from the public site to a server on the > LAN. Then set a local DNS (or, worse, hosts files) to assign > library.xyz.com the local network IP of the net. > > This would seem to sidestep at least some of the security implications > for having a library server on the public network. > > -- > > Unworthy Br. *Christos Hayward*, author and apologist, and more > importantly novice at *St. Demetrios Orthodox Monastery > * (monastery webshop > ). > > I invite you to visit my *author site* > (author bio , bookshelf > >). > One title is Happiness in an Age of Crisis: Ancient Wisdom from the > Eastern Orthodox Church . > > My most recent posting is a purchasable "How do I love thee?" shirt > . > _______________________________________________ > > Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From jonathan.druart at bugs.koha-community.org Mon Jul 25 18:54:43 2022 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Mon, 25 Jul 2022 08:54:43 +0200 Subject: [Koha] Koha 22.05: Where has the columns setting for the patrons list gone? In-Reply-To: References: <61ced22e514b4b8a992809c8f65f2db5@gwdg.de> <5f49021f94e94fa18734b06a962ae270@gwdg.de> Message-ID: I've opened bug 31229 - column visibility broken on patron search view https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31229 I am about to submit a patch Le dim. 24 juil. 2022 à 14:26, Katrin Fischer a écrit : > > Hi Anke, > > sorry for the late reply. I see the same on current master: the patron > search table doesn't have a 'Columns' link. I don't know if this was > intentional with moving the search to the API or if it was an oversight. > > Katrin > > On 07.07.22 17:30, Bruns, Anke wrote: > > Hi Katrin, > > > > thank you! I meanwhile found out that in some list views in 22.05 the Columns button is present, in others not. I don't know if this was on purpose. > > > > The difference between 22.05 and 20.11 I stumbled upon is the following: > > > > - Home -> Patrons -> (Search for a list of patrons, or just all patrons) -> in V20.11 just above the table with the patrons list, there is a "Columns" link (it's not actually a "button") permitting to choose which columns of the patron record I want to display. In V22.11 this link is missing. > > > > Whereas: > > > > - Home -> Tools -> Patron lists -> (Choose one of the patron lists, if existent) -> in the table appearing here, the Columns link is there in 20.11 and in 22.05. > > > > Regards, > > Anke > > > >> -----Ursprüngliche Nachricht----- > >> Von: Koha Im Auftrag von Katrin Fischer > >> Gesendet: Mittwoch, 6. Juli 2022 19:18 > >> An: koha at lists.katipo.co.nz > >> Betreff: Re: [Koha] Koha 22.05: Where has the columns setting for the patrons > >> list gone? > >> > >> Hi Anke, > >> > >> in 22.05 the normal patron search is also used for the circulation > >> patron search. Maybe you meant that list? > >> > >> The settings are in Administration > Table settings > Patrons > > >> memberresultst > >> > >> Hope this helps, > >> > >> Katrin > >> > >> On 06.07.22 17:02, Bruns, Anke wrote: > >>> Hi, > >>> > >>> a minor problem but nonetheless...: In version 20.11 we had the possibility > >>> to choose in the staff client which columns from the patron record we wanted > >>> to display in the patrons short list. There was a "Columns" button next to > >>> the "Export" one. This option seems to have gone with one of the more recent > >>> versions (we upgraded directly from 20.11 to 22.05, so no idea when exactly > >>> this was the case). Instead there is a "Clear filter" button now. > >>> > >>> Is there any chance to get the choice of columns option back? E.g. we do not > >>> need or want to display the Date of Birth column which isn't populated in > >>> our case. > >>> > >>> Thank you for any advice and best regards, > >>> Anke > >>> > >> _______________________________________________ > >> > >> Koha mailing list http://koha-community.org > >> Koha at lists.katipo.co.nz > >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From mik at adminkuhn.ch Mon Jul 25 19:40:52 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Mon, 25 Jul 2022 09:40:52 +0200 Subject: [Koha] Adding items to a list not possible in Koha 21.11.09 In-Reply-To: <9cb9c517-3194-908e-d181-5d6c244e6c72@gmail.com> References: <9cb9c517-3194-908e-d181-5d6c244e6c72@gmail.com> Message-ID: Hi Andreas You wrote: > I've tried to reproduce the issue you describe on a development > 21.11.09 instance that I set up, but was not successful. > > So, I have a few questions for you to help me diagnose this ;-) > > Assuming a package installation, have you restarted the koha-common > service following the upgrade? Yes, we have. We have also restarted the complete host. > Have you performed a hard refresh of your web browser's cache? (hit > CTRL-F5) Yes, we did. > Finally, which version of Koha did you upgrade from? We have updated from Debian 9 to 10, then from Koha 19.05.02 to 21.11.09. 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 at adminkuhn.ch · W www.adminkuhn.ch From jonathan.druart at bugs.koha-community.org Mon Jul 25 20:21:27 2022 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Mon, 25 Jul 2022 10:21:27 +0200 Subject: [Koha] Electronic resource management module (ERM) in Koha - quick update Message-ID: Hi, I have been working during the last months on implementing a first version of what could be an ERM module in Koha. To help getting feedback from end-users we have created a sandbox that has the latest version of the code: https://staff-erm.sandboxes.biblibre.eu/cgi-bin/koha/erm/erm.pl For developers who would like to read the code and help get them onboard, an entry point page has been written with some details about the implementation: https://tree.taiga.io/project/joubu-koha-erm/wiki/home The code is available at https://gitlab.com/joubu/Koha/-/commits/erm An overview of the current state of the development can be found on this kanban board: https://tree.taiga.io/project/joubu-koha-erm/kanban Any feedback, ideas, contributions are greatly welcomed! Regards, Jonathan From loveandmarigold at gmail.com Mon Jul 25 21:25:50 2022 From: loveandmarigold at gmail.com (Sanjay Uchcharia) Date: Mon, 25 Jul 2022 14:55:50 +0530 Subject: [Koha] What is Shelving Control Number and how to apply & how to use it. Message-ID: What is Shelving Control Number and how to apply & how to use it. From arthur.suzuki at biblibre.com Mon Jul 25 23:05:04 2022 From: arthur.suzuki at biblibre.com (Arthur) Date: Mon, 25 Jul 2022 13:05:04 +0200 Subject: [Koha] Koha 21.11.10 released Message-ID: <5fbb7ff7-8ea5-b4f0-5203-9cc4083e7b67@biblibre.com> Hello, I'm very proud to announce the release of Koha 21.11.10. This release contains several bugfixes, 2 enhancements and a security fix. More information can be found here : https://koha-community.org/koha-21-11-10-release/ Enjoy! 🌅🚀 Arthur Suzuki, Developper @BibLibre ---------------------- Releases notes for Koha 21.11.10 25 Jul 2022 Koha is the first free and open source software library automation package (ILS). Development is sponsored by libraries of varying types and sizes, volunteers, and support companies from around the world. The website for the Koha project is: * Koha Community Koha 21.11.10 can be downloaded from: * Download Installation instructions can be found at: * Koha Wiki * OR in the INSTALL files that come in the tarball Koha 21.11.10 is a bugfix/maintenance release with security fixes. It includes 1 security fixes, 2 enhancements, 13 bugfixes. System requirements You can learn about the system components (like OS and database) needed for running Koha here: https://wiki.koha-community.org/wiki/System_requirements_and_recommendations Security bugs Koha * [30969] Cross site scripting (XSS) attack in OPAC authority search ( opac-authorities-home.pl ) Enhancements Cataloging * [30997] "CGI::param called in list context" warning in detail.pl flooding error log This fixes the cause of "CGI::param called in list context from" warning messages that appear in the log files when viewing record detail pages in the staff interface. Templates * [30786] Capitalization in (Opac)AdvancedSearchTypes This fixes the descriptions for the AdvancedSearchTypes and OpacAdvancedSearchTypes system preferences - sentence case is now used for "..Shelving location..". Critical bugs fixed Cataloging * [30234] Serial local covers don't appear in the staff interface for other libraries with SeparateHoldings This fixes the display of item-specific local cover images in the staff interface. Before this, item images were not shown for holdings on the record's details view page. Circulation * [29504] Confirm item parts requires force_checkout permission (checkouts tab) Lists * [30925] Creating public list by adding items to new list creates a private list Patrons * [31005] Cannot edit patrons in other categories if an extended attribute is mandatory and limited to a category This fixes an error when a mandatory patron attribute limited to a specific patron category was causing a '500 error' when editing a patron not in that category. REST API * [30677] Unknown column 'biblioitem.title' in 'where clause' 500 error in API /api/v1/acquisitions/orders Searching - Elasticsearch * [30883] Authorities merge is limited to 100 biblio with Elasticsearch This fixes the hard-coded limit of 100 when merging authorities (when Elasticsearch is the search engine). When merging authorities where the term is used over 100 times, only the first 100 authorities would be merged and the old term deleted, irrespective of the value set in the AuthorityMergeLimit system preference. Other bugs fixed Hold requests * [12630] Prioritizing "Hold starts on date" -holds causes all other holds to be prioritized as well! * [28529] Item type-constrained biblio-level holds should honour max_holds as item-level do * [30207] Librarians with only "place_holds" permission can no longer update hold pickup locations I18N/L10N * [30958] OPAC Overdrive search result page broken for translations *Sponsored by* /Melbourne Athenaeum Library, Australia/ Notices * [28355] Add warning note about Email SMS driver option for SMSSendDriver This updates the text for the SMSSendDriver system preference. The Email SMS driver option is no longer recommended unless you use a dedicated SMS to Email gateway. Many mobile providers offer inconsistent support for the email to SMS gateway (sometimes it works, and sometimes it doesn't), which can cause frustration for patrons. OPAC * [30989] Tags with some special characters are not encoded right This fixes tags with special characters (such as +) so that the searching returns results when the tag is selected (from the record detail view in the OPAC and staff interface, and from the search results, tag cloud, and list pages in the OPAC). Staff Client * [30970] holdst columns don't match actual columns in 'Holds waiting' Documentation The Koha manual is maintained in Sphinx. The home page for Koha documentation is * Koha Documentation The Git repository for the Koha manual can be found at * Koha Git Repository Translations Complete or near-complete translations of the OPAC and staff interface are available in this release for the following languages: * Arabic (87.4%) * Armenian (100%) * Armenian (Classical) (89%) * Bulgarian (92.3%) * Chinese (Taiwan) (79.5%) * Czech (76.4%) * English (New Zealand) (59.1%) * English (USA) * Finnish (92.3%) * French (95.1%) * French (Canada) (92.9%) * German (100%) * German (Switzerland) (58.8%) * Greek (60.3%) * Hindi (99.9%) * Italian (100%) * Nederlands-Nederland (Dutch-The Netherlands) (86.9%) * Norwegian Bokmål (63.3%) * Polish (99.2%) * Portuguese (91.1%) * Portuguese (Brazil) (83.8%) * Russian (84.9%) * Slovak (73.2%) * Spanish (100%) * Swedish (82.3%) * Telugu (95.3%) * Turkish (99.6%) * Ukrainian (75.9%) Partial translations are available for various other languages. The Koha team welcomes additional translations; please see * Koha Translation Info For information about translating Koha, and join the koha-translate list to volunteer: * Koha Translate List The most up-to-date translations can be found at: * Koha Translation Release Team The release team for Koha 21.11.10 is * Release Manager: Jonathan Druart * Release Manager assistants: o Martin Renvoize o Tomás Cohen Arazi * QA Manager: Katrin Fischer * QA Team: o Agustín Moyano o Andrew Nugged o David Cook o Joonas Kylmälä o Julian Maurice o Kyle M Hall o Marcel de Rooy o Martin Renvoize o Nick Clemens o Petro Vashchuk o Tomás Cohen Arazi o Victor Grousset * Topic Experts: o UI Design -- Owen Leonard o REST API -- Tomás Cohen Arazi o Elasticsearch -- Fridolin Somers o Zebra -- Fridolin Somers o Accounts -- Martin Renvoize * Bug Wranglers: o Sally Healey * Packaging Manager: * Documentation Manager: David Nind * Documentation Team: o David Nind o Lucy Vaux-Harvey * Translation Managers: o Bernardo González Kriegel * Wiki curators: o Thomas Dukleth * Release Maintainers: o 21.05 -- Kyle M Hall o 20.11 -- Fridolin Somers o 20.05 -- Victor Grousset o 19.11 -- Wainui Witika-Park * Release Maintainer assistants: o 21.05 -- Nick Clemens * Release Maintainer mentors: o 19.11 -- Aleisha Amohia Credits We thank the following libraries, companies, and other institutions who are known to have sponsored new features in Koha 21.11.10 * Melbourne Athenaeum Library, Australia We thank the following individuals who contributed patches to Koha 21.11.10 * Tomás Cohen Arazi (2) * Alex Buckley (1) * Nick Clemens (4) * Jonathan Druart (3) * Katrin Fischer (3) * Lucas Gass (1) * Kyle M Hall (4) * Olli-Antti Kivilahti (1) * David Nind (1) * Martin Renvoize (5) * Marcel de Rooy (1) * Fridolin Somers (1) * Arthur Suzuki (5) * Koha translators (1) * Petro Vashchuk (1) We thank the following libraries, companies, and other institutions who contributed patches to Koha 21.11.10 * BibLibre (7) * Bibliotheksservice-Zentrum Baden-Württemberg (BSZ) (3) * ByWater-Solutions (9) * Catalyst (1) * David Nind (1) * Independant Individuals (1) * Koha Community Developers (3) * PTFS-Europe (5) * Rijksmuseum (1) * Theke Solutions (2) We also especially thank the following individuals who tested patches for Koha * Tomás Cohen Arazi (22) * Christopher Brannon (1) * Chris Cormack (1) * Jonathan Druart (3) * Katrin Fischer (8) * Lucas Gass (21) * Victor Grousset (2) * Kyle M Hall (1) * Lucy Harrison (1) * Sally Healey (1) * Owen Leonard (1) * David Nind (12) * Martin Renvoize (7) * Marcel de Rooy (3) * Fridolin Somers (2) * Arthur Suzuki (26) We regret any omissions. If a contributor has been inadvertently missed, please send a patch against these release notes to koha-devel at lists.koha-community.org. Revision control notes The Koha project uses Git for version control. The current development version of Koha can be retrieved by checking out the master branch of: * Koha Git Repository The branch for this version of Koha and future bugfixes in this release line is 21.11.x. Bugs and feature requests Bug reports and feature requests can be filed at the Koha bug tracker at: * Koha Bugzilla He rau ringa e oti ai. (Many hands finish the work) Autogenerated release notes updated last on 25 Jul 2022 08:55:11. From knoakes at egrps.org Tue Jul 26 04:03:57 2022 From: knoakes at egrps.org (Kyle Noakes) Date: Mon, 25 Jul 2022 12:03:57 -0400 Subject: [Koha] Patron search not working after upgrade to version 22 In-Reply-To: References: Message-ID: Thanks for those ideas Evan. I did already find those not up to date before posting, yet still deal with the problem. I did find that we are able to search for patrons using the card number instead of the last name. I thought I was going to be fine just rolling back to my old server version and database since I am at a school during the summer, but then noticed in the logs that my staff have been checking things out using ID so I am unable to just go back to that old version as easily as I thought. Maybe someone will have an idea of why I can search by card number, but not last name. Thank you, Kyle Noakes Manager of Information Systems East Grand Rapids Public Schools 616-974-0157 On Mon, Jul 11, 2022 at 3:05 PM Evan Stewart wrote: > Correction to my apt install command in the previous reply. > > To fix, I upgraded "libmojolicious-perl" and " > libmojolicious-plugin-openapi-perl" upgraded with it. > > I ran: sudo apt install libmojolicious-perl > > -Evan > > On Sun, Jul 10, 2022 at 9:48 PM Evan Stewart > wrote: > > > Hi, > > > > I found the solution on Raspberry Pi OS (based on Debian 10). I noticed > > that after running apt upgrade two packages were held back: > > > > - libmojolicious-perl > > - libmojolicious-plugin-openapi-perl > > > > I didn't notice them before and probably wouldn't have noticed them had I > > not learned about the REST API and then read a little about it in the > Koha > > documentation (thanks Katrin!). Once I saw the REST API references the > > OpenAPI format I figured these packages were the culprit. Also, I > > confirmed in my About Koha settings page that the Open API module was > > flagged as "not installed" after I upgraded to Koha 22. > > > > The solution for me was to install the two packages with apt. Not sure > > why they were held back using "apt upgrade", but running "sudo apt > install > > libmojolicious-plugin-openapi-perl" called in all other dependent > packages; > > including the upgrade for libmojolicious-perl and nine other new > packages. > > > > I rebooted my Raspberry Pi, logged into Koha and all is good. The Open > > API module is listed as "Installed" in the About Koha settings page and > the > > patron search and library listing is working. > > > > Kyle, hopefully this helps your machine. > > > > -Evan Stewart > > > > > > > > On Fri, Jul 8, 2022 at 12:37 PM Katrin Fischer > > > wrote: > > > >> Hi Kyle, > >> > >> the API settings in administration are not related to Koha's internal > >> use of the API, so if you are not using the API exeternally, you can > >> turn these off again. > >> > >> Did you test if the list of libraries is visible for you in > >> administration? If the list doesn't show, your problem is probably not > >> the bug Tomas mentioned. > >> > >> What does your /etc/apt/sources.list.d/koha.list entry look like? > >> > >> Hope this helps, > >> > >> Katrin > >> > >> > >> On 08.07.22 17:15, Kyle Noakes wrote: > >> > I am having the same problem as Evan on Debian 10 (Buster) after the > >> > upgrade to 22.05.00 that has continued to 22.05.02. I did attempt to > add > >> > Tomas's patch to my pagination file manually, but it did not work, > >> > although admittedly I have rarely needed to hand add any patch so I > >> could > >> > have done something wrong. I was also unable to find any errors in the > >> logs > >> > that mention long search strings before I tried the pagination fix > >> anyway. > >> > I am unable to search for any patron string, not just long ones. I > can't > >> > even click on a letter in the alphabet to search and receive any > >> results. > >> > > >> > I did enable the API in administration. I can also see my branches in > >> > libraries. > >> > > >> > Thank you, > >> > > >> > Kyle Noakes > >> > Manager of Information Systems > >> > East Grand Rapids Public Schools > >> > 616-974-0157 > >> > > >> > > >> > On Wed, Jul 6, 2022 at 1:20 PM Tomas Cohen Arazi < > tomascohen at gmail.com> > >> > wrote: > >> > > >> >> This is certainly caused by a Koha bug I'm about to submit a patch > for > >> [1]. > >> >> The 22.05 release maintainer is AFK this week so he cannot release a > >> new > >> >> version yet. > >> >> > >> >> Best regards. > >> >> > >> >> [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31104 > >> >> > >> >> El mié, 6 jul 2022 a las 13:43, Evan Stewart (< > >> evanstewart406 at gmail.com>) > >> >> escribió: > >> >> > >> >>> Hello, > >> >>> > >> >>> I recently upgraded my Koka 21 to 22. Everything seemed to be > working > >> >> fine > >> >>> until I tried searching for patrons. Using the intranet portal to > >> search > >> >>> for patrons provides zero results. I see my patrons in the > borrowers > >> >>> table, but the GUI won't display them. It's like the search > function > >> >> sees > >> >>> no results. > >> >>> > >> >>> I upgraded to version 22.05.02, but the same problem still occurs. > >> >>> > >> >>> I'm using Raspberry Pi OS (Buster). > >> >>> > >> >>> I can add a new patron, but even the new patron does not show in the > >> >> search > >> >>> results. > >> >>> > >> >>> Is there a way to refresh the indexer that handles patron searching? > >> Any > >> >>> other suggestions? > >> >>> > >> >>> -Evan Stewart > >> >>> Africa's Hope, USA > >> >>> _______________________________________________ > >> >>> > >> >>> Koha mailing list http://koha-community.org > >> >>> Koha at lists.katipo.co.nz > >> >>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > >> >>> > >> >> > >> >> -- > >> >> Tomás Cohen Arazi > >> >> Theke Solutions (http://theke.io) > >> >> ✆ +54 9351 3513384 > >> >> GPG: B2F3C15F > >> >> _______________________________________________ > >> >> > >> >> Koha mailing list http://koha-community.org > >> >> Koha at lists.katipo.co.nz > >> >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > >> >> > >> > _______________________________________________ > >> > > >> > Koha mailing list http://koha-community.org > >> > Koha at lists.katipo.co.nz > >> > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > >> _______________________________________________ > >> > >> Koha mailing list http://koha-community.org > >> Koha at lists.katipo.co.nz > >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > >> > > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From Fred.King at Medstar.net Tue Jul 26 04:05:56 2022 From: Fred.King at Medstar.net (King, Fred) Date: Mon, 25 Jul 2022 16:05:56 +0000 Subject: [Koha] [EXTERNAL] What is Shelving Control Number and how to apply & how to use it. In-Reply-To: References: Message-ID: The Shelving Control Number is defined the Library of Congress MARC 21 Format for Holdings Data for field 852 (https://www.loc.gov/marc/holdings/hd852.html): > 4 - Shelving control number > Item is shelved by a shelving control number, which is contained in subfield $j (Shelving control > number). My interpretation of this statement is that the Shelving Control Number can be whatever you would like it to be. If you want "Display Department" to indicate the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying "Beware of the Leopard," then that's what it is. Fred King, MSLS, AHIP Medical Librarian, MedStar Washington Hospital Center fred.king at medstar.net 202-877-6670 ORCID 0000-0001-5266-0279 MedStar Authors Catalog: http://medstarauthors.org By replacing your morning coffee with green tea you can lose up to 87% of what little joy you still have left in your life. --Trad -----Original Message----- From: Koha On Behalf Of Sanjay Uchcharia Sent: Monday, July 25, 2022 5:26 AM To: koha at lists.katipo.co.nz Subject: [EXTERNAL] [Koha] What is Shelving Control Number and how to apply & how to use it. **ATTENTION: This email originated from outside the MedStar Health network. ** DO NOT CLICK links or attachments unless you recognize the sender and know the content is safe. What is Shelving Control Number and how to apply & how to use it. _______________________________________________ Koha mailing list https://urldefense.com/v3/__http://koha-community.org__;!!D7IIWT94AA!9BDQ4GCHC98bR_6fsqcA65DouE9YdffhKJM0C04GDSeTcCltnSqQ7nOfDHeJBI36jEEYj_ppmze7VErTqwcNV1mAAAo$ Koha at lists.katipo.co.nz Unsubscribe: https://urldefense.com/v3/__https://lists.katipo.co.nz/mailman/listinfo/koha__;!!D7IIWT94AA!9BDQ4GCHC98bR_6fsqcA65DouE9YdffhKJM0C04GDSeTcCltnSqQ7nOfDHeJBI36jEEYj_ppmze7VErTqwcN2AL-A3I$ ---------------------------------------------------------------------- MedStar Health is a not-for-profit, integrated healthcare delivery system, the largest in Maryland and the Washington, D.C., region. Nationally recognized for clinical quality in heart, orthopedics, cancer and GI. IMPORTANT: This e-mail (including any attachments) may contain information that is private, confidential, or protected by attorney-client or other privilege. If you received this e-mail in error, please delete it from your system without copying it and notify sender by reply e-mail, so that our records can be corrected... Thank you. Help conserve valuable resources - only print this email if necessary. From lucas at bywatersolutions.com Tue Jul 26 04:39:55 2022 From: lucas at bywatersolutions.com (Lucas Gass) Date: Mon, 25 Jul 2022 10:39:55 -0600 Subject: [Koha] Koha 22.05.03 is here! Message-ID: Hello, Hola, Bonjour, Guten tag, and Olá! The Koha community is proud to announce the release of Koha 22.05.03! Koha 22.05.02 includes 1 security fix, 8 enhancements, and 32 bugfixes. The full release notes can be found here: https://koha-community.org/koha-22-05-03-released/ Debian packages should be available shortly! -- Lucas Gass Web Developer From katrin.fischer.83 at web.de Tue Jul 26 08:29:14 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Mon, 25 Jul 2022 22:29:14 +0200 Subject: [Koha] Patron search not working after upgrade to version 22 In-Reply-To: References: Message-ID: <72c4b0e3-29af-f2a6-6191-85108d126eb8@web.de> Hi Kyle, did you do the check with the Administration > Libraries table I suggested? If the table doesn't show your configured libraries, it's pointing to the API not working correctly. I can imagine because cardnumber gives only one result, this bypasses the API and goes to the account directly. Hope this helps, Katrin On 25.07.22 18:03, Kyle Noakes wrote: > Thanks for those ideas Evan. I did already find those not up to date > before posting, yet still deal with the problem. > > I did find that we are able to search for patrons using the card > number instead of the last name. I thought I was going to be fine just > rolling back to my old server version and database since I am at a > school during the summer, but then noticed in the logs that my staff > have been checking things out using ID so I am unable to just go back > to that old version as easily as I thought. > > Maybe someone will have an idea of why I can search by card number, > but not last name. > > Thank you, > > Kyle Noakes > Manager of Information Systems > East Grand Rapids Public Schools > 616-974-0157 > > > On Mon, Jul 11, 2022 at 3:05 PM Evan Stewart > wrote: > > Correction to my apt install command in the previous reply. > > To fix, I upgraded "libmojolicious-perl" and " > libmojolicious-plugin-openapi-perl" upgraded with it. > > I ran:  sudo apt install libmojolicious-perl > > -Evan > > On Sun, Jul 10, 2022 at 9:48 PM Evan Stewart > > wrote: > > > Hi, > > > > I found the solution on Raspberry Pi OS (based on Debian 10). I > noticed > > that after running apt upgrade two packages were held back: > > > >    - libmojolicious-perl > >    - libmojolicious-plugin-openapi-perl > > > > I didn't notice them before and probably wouldn't have noticed > them had I > > not learned about the REST API and then read a little about it > in the Koha > > documentation (thanks Katrin!). Once I saw the REST API > references the > > OpenAPI format I figured these packages were the culprit.  Also, I > > confirmed in my About Koha settings page that the Open API > module was > > flagged as "not installed" after I upgraded to Koha 22. > > > > The solution for me was to install the two packages with apt.  > Not sure > > why they were held back using "apt upgrade", but running "sudo > apt install > > libmojolicious-plugin-openapi-perl" called in all other > dependent packages; > > including the upgrade for libmojolicious-perl and nine other new > packages. > > > > I rebooted my Raspberry Pi, logged into Koha and all is good.  > The Open > > API module is listed as "Installed" in the About Koha settings > page and the > > patron search and library listing is working. > > > > Kyle, hopefully this helps your machine. > > > > -Evan Stewart > > > > > > > > On Fri, Jul 8, 2022 at 12:37 PM Katrin Fischer > > > wrote: > > > >> Hi Kyle, > >> > >> the API settings in administration are not related to Koha's > internal > >> use of the API, so if you are not using the API exeternally, > you can > >> turn these off again. > >> > >> Did you test if the list of libraries is visible for you in > >> administration? If the list doesn't show, your problem is > probably not > >> the bug Tomas mentioned. > >> > >> What does your /etc/apt/sources.list.d/koha.list entry look like? > >> > >> Hope this helps, > >> > >> Katrin > >> > >> > >> On 08.07.22 17:15, Kyle Noakes wrote: > >> > I am having the same problem as Evan on Debian 10 (Buster) > after the > >> > upgrade to 22.05.00 that has continued to 22.05.02. I did > attempt to add > >> > Tomas's patch to my pagination file manually, but it did not > work, > >> > although admittedly I have rarely needed to hand add any > patch so I > >> could > >> > have done something wrong. I was also unable to find any > errors in the > >> logs > >> > that mention long search strings before I tried the > pagination fix > >> anyway. > >> > I am unable to search for any patron string, not just long > ones. I can't > >> > even click on a letter in the alphabet to search and receive any > >> results. > >> > > >> > I did enable the API in administration. I can also see my > branches in > >> > libraries. > >> > > >> > Thank you, > >> > > >> > Kyle Noakes > >> > Manager of Information Systems > >> > East Grand Rapids Public Schools > >> > 616-974-0157 > >> > > >> > > >> > On Wed, Jul 6, 2022 at 1:20 PM Tomas Cohen Arazi > > >> > wrote: > >> > > >> >> This is certainly caused by a Koha bug I'm about to submit a > patch for > >> [1]. > >> >> The 22.05 release maintainer is AFK this week so he cannot > release a > >> new > >> >> version yet. > >> >> > >> >> Best regards. > >> >> > >> >> [1] > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31104 > >> >> > >> >> El mié, 6 jul 2022 a las 13:43, Evan Stewart (< > >> evanstewart406 at gmail.com>) > >> >> escribió: > >> >> > >> >>> Hello, > >> >>> > >> >>> I recently upgraded my Koka 21 to 22. Everything seemed to > be working > >> >> fine > >> >>> until I tried searching for patrons. Using the intranet > portal to > >> search > >> >>> for patrons provides zero results.  I see my patrons in the > borrowers > >> >>> table, but the GUI won't display them. It's like the search > function > >> >> sees > >> >>> no results. > >> >>> > >> >>> I upgraded to version 22.05.02, but the same problem still > occurs. > >> >>> > >> >>> I'm using Raspberry Pi OS (Buster). > >> >>> > >> >>> I can add a new patron, but even the new patron does not > show in the > >> >> search > >> >>> results. > >> >>> > >> >>> Is there a way to refresh the indexer that handles patron > searching? > >> Any > >> >>> other suggestions? > >> >>> > >> >>> -Evan Stewart > >> >>> Africa's Hope, USA > >> >>> _______________________________________________ > >> >>> > >> >>> Koha mailing list http://koha-community.org > >> >>> Koha at lists.katipo.co.nz > >> >>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > >> >>> > >> >> > >> >> -- > >> >> Tomás Cohen Arazi > >> >> Theke Solutions (http://theke.io) > >> >> ✆ +54 9351 3513384 > >> >> GPG: B2F3C15F > >> >> _______________________________________________ > >> >> > >> >> Koha mailing list http://koha-community.org > >> >> Koha at lists.katipo.co.nz > >> >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > >> >> > >> > _______________________________________________ > >> > > >> > Koha mailing list http://koha-community.org > >> > Koha at lists.katipo.co.nz > >> > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > >> _______________________________________________ > >> > >> Koha mailing list http://koha-community.org > >> Koha at lists.katipo.co.nz > >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > >> > > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From keith at thesorbos.com Tue Jul 26 09:01:57 2022 From: keith at thesorbos.com (Keith Sorbo) Date: Mon, 25 Jul 2022 16:01:57 -0500 Subject: [Koha] 500 Errors on search after update Message-ID: After upgrading to the latest (22.05.02.000), I am getting 500 errors when a search should return a biblio entry. This happens on the OPAC and when I do a search under the cataloging section in the staff site. I am able to search for patrons with no apparent problem.(I did have quite a bit of trouble updating my database) I ran rebuild zebra and it made no difference. How do I detect what is causing this problem? From knoakes at egrps.org Tue Jul 26 11:55:32 2022 From: knoakes at egrps.org (Kyle Noakes) Date: Mon, 25 Jul 2022 19:55:32 -0400 Subject: [Koha] Patron search not working after upgrade to version 22 In-Reply-To: <72c4b0e3-29af-f2a6-6191-85108d126eb8@web.de> References: <72c4b0e3-29af-f2a6-6191-85108d126eb8@web.de> Message-ID: Hi Katrin, I am able to see all libraries under administration. I did put that in my original email, but I was not clear in my wording. On Mon, Jul 25, 2022, 4:29 PM Katrin Fischer wrote: > Hi Kyle, > > did you do the check with the Administration > Libraries table I > suggested? If the table doesn't show your configured libraries, it's > pointing to the API not working correctly. > > I can imagine because cardnumber gives only one result, this bypasses the > API and goes to the account directly. > > Hope this helps, > > Katrin > On 25.07.22 18:03, Kyle Noakes wrote: > > Thanks for those ideas Evan. I did already find those not up to date > before posting, yet still deal with the problem. > > I did find that we are able to search for patrons using the card number > instead of the last name. I thought I was going to be fine just rolling > back to my old server version and database since I am at a school during > the summer, but then noticed in the logs that my staff have been checking > things out using ID so I am unable to just go back to that old version as > easily as I thought. > > Maybe someone will have an idea of why I can search by card number, but > not last name. > > Thank you, > > Kyle Noakes > Manager of Information Systems > East Grand Rapids Public Schools > 616-974-0157 > > > On Mon, Jul 11, 2022 at 3:05 PM Evan Stewart > wrote: > >> Correction to my apt install command in the previous reply. >> >> To fix, I upgraded "libmojolicious-perl" and " >> libmojolicious-plugin-openapi-perl" upgraded with it. >> >> I ran: sudo apt install libmojolicious-perl >> >> -Evan >> >> On Sun, Jul 10, 2022 at 9:48 PM Evan Stewart >> wrote: >> >> > Hi, >> > >> > I found the solution on Raspberry Pi OS (based on Debian 10). I noticed >> > that after running apt upgrade two packages were held back: >> > >> > - libmojolicious-perl >> > - libmojolicious-plugin-openapi-perl >> > >> > I didn't notice them before and probably wouldn't have noticed them had >> I >> > not learned about the REST API and then read a little about it in the >> Koha >> > documentation (thanks Katrin!). Once I saw the REST API references the >> > OpenAPI format I figured these packages were the culprit. Also, I >> > confirmed in my About Koha settings page that the Open API module was >> > flagged as "not installed" after I upgraded to Koha 22. >> > >> > The solution for me was to install the two packages with apt. Not sure >> > why they were held back using "apt upgrade", but running "sudo apt >> install >> > libmojolicious-plugin-openapi-perl" called in all other dependent >> packages; >> > including the upgrade for libmojolicious-perl and nine other new >> packages. >> > >> > I rebooted my Raspberry Pi, logged into Koha and all is good. The Open >> > API module is listed as "Installed" in the About Koha settings page and >> the >> > patron search and library listing is working. >> > >> > Kyle, hopefully this helps your machine. >> > >> > -Evan Stewart >> > >> > >> > >> > On Fri, Jul 8, 2022 at 12:37 PM Katrin Fischer < >> katrin.fischer.83 at web.de> >> > wrote: >> > >> >> Hi Kyle, >> >> >> >> the API settings in administration are not related to Koha's internal >> >> use of the API, so if you are not using the API exeternally, you can >> >> turn these off again. >> >> >> >> Did you test if the list of libraries is visible for you in >> >> administration? If the list doesn't show, your problem is probably not >> >> the bug Tomas mentioned. >> >> >> >> What does your /etc/apt/sources.list.d/koha.list entry look like? >> >> >> >> Hope this helps, >> >> >> >> Katrin >> >> >> >> >> >> On 08.07.22 17:15, Kyle Noakes wrote: >> >> > I am having the same problem as Evan on Debian 10 (Buster) after the >> >> > upgrade to 22.05.00 that has continued to 22.05.02. I did attempt to >> add >> >> > Tomas's patch to my pagination file manually, but it did not work, >> >> > although admittedly I have rarely needed to hand add any patch so I >> >> could >> >> > have done something wrong. I was also unable to find any errors in >> the >> >> logs >> >> > that mention long search strings before I tried the pagination fix >> >> anyway. >> >> > I am unable to search for any patron string, not just long ones. I >> can't >> >> > even click on a letter in the alphabet to search and receive any >> >> results. >> >> > >> >> > I did enable the API in administration. I can also see my branches in >> >> > libraries. >> >> > >> >> > Thank you, >> >> > >> >> > Kyle Noakes >> >> > Manager of Information Systems >> >> > East Grand Rapids Public Schools >> >> > 616-974-0157 >> >> > >> >> > >> >> > On Wed, Jul 6, 2022 at 1:20 PM Tomas Cohen Arazi < >> tomascohen at gmail.com> >> >> > wrote: >> >> > >> >> >> This is certainly caused by a Koha bug I'm about to submit a patch >> for >> >> [1]. >> >> >> The 22.05 release maintainer is AFK this week so he cannot release a >> >> new >> >> >> version yet. >> >> >> >> >> >> Best regards. >> >> >> >> >> >> [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31104 >> >> >> >> >> >> El mié, 6 jul 2022 a las 13:43, Evan Stewart (< >> >> evanstewart406 at gmail.com>) >> >> >> escribió: >> >> >> >> >> >>> Hello, >> >> >>> >> >> >>> I recently upgraded my Koka 21 to 22. Everything seemed to be >> working >> >> >> fine >> >> >>> until I tried searching for patrons. Using the intranet portal to >> >> search >> >> >>> for patrons provides zero results. I see my patrons in the >> borrowers >> >> >>> table, but the GUI won't display them. It's like the search >> function >> >> >> sees >> >> >>> no results. >> >> >>> >> >> >>> I upgraded to version 22.05.02, but the same problem still occurs. >> >> >>> >> >> >>> I'm using Raspberry Pi OS (Buster). >> >> >>> >> >> >>> I can add a new patron, but even the new patron does not show in >> the >> >> >> search >> >> >>> results. >> >> >>> >> >> >>> Is there a way to refresh the indexer that handles patron >> searching? >> >> Any >> >> >>> other suggestions? >> >> >>> >> >> >>> -Evan Stewart >> >> >>> Africa's Hope, USA >> >> >>> _______________________________________________ >> >> >>> >> >> >>> Koha mailing list http://koha-community.org >> >> >>> Koha at lists.katipo.co.nz >> >> >>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> >> >>> >> >> >> >> >> >> -- >> >> >> Tomás Cohen Arazi >> >> >> Theke Solutions (http://theke.io) >> >> >> ✆ +54 9351 3513384 >> >> >> GPG: B2F3C15F >> >> >> _______________________________________________ >> >> >> >> >> >> Koha mailing list http://koha-community.org >> >> >> Koha at lists.katipo.co.nz >> >> >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> >> >> >> >> > _______________________________________________ >> >> > >> >> > Koha mailing list http://koha-community.org >> >> > Koha at lists.katipo.co.nz >> >> > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> >> _______________________________________________ >> >> >> >> Koha mailing list http://koha-community.org >> >> Koha at lists.katipo.co.nz >> >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> >> >> > >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> > From victor at tuxayo.net Tue Jul 26 15:15:04 2022 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Tue, 26 Jul 2022 05:15:04 +0200 Subject: [Koha] =?utf-8?q?Koha_21=2E05=2E17_released=2C_=E2=9A=A0_security?= =?utf-8?q?_release?= Message-ID: <6967a4e6-be0d-27d1-9dbe-905267015ac0@tuxayo.net> Hello! :) The Koha Community is happy to announce the release of Koha 21.05.17 The full release notes can be found at: https://koha-community.org/koha-21-05-17-released/ Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo From mik at adminkuhn.ch Tue Jul 26 20:25:05 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Tue, 26 Jul 2022 10:25:05 +0200 Subject: [Koha] Accessing DNB databases via SRU and HTTPS Message-ID: Hi We had a working Koha configuration to access the database of the German national library (Deutsche Nationalbibliothek / DNB) via SRU and HTTP. But since 19 July requests using the HTTP-protocol will be redirected to the HTTPS-protocol by "HTTP-Statuscode 301 Moved Permanently" (see https://lists.dnb.de/pipermail/ons-sru-ru/2022-July/000015.html). The search via HTTPS is working via yaz-client: # yaz-client https://services.dnb.de/sru/dnb Z> sru GET 1.1 Z> find "Marx" Z> s 1 So in our Koha configuration we changed port 80 to port 443 - but when searching anything Koha immediately (apparently without really searching) returns "Nothing found". It's is the same with both databases "sru/dnb" (bibliographic data) and "sru/authorities" (authorities). Has anyone been successful recently when trying to access the DNB databases via SRU and HTTPS? 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 at adminkuhn.ch · W www.adminkuhn.ch From mik at adminkuhn.ch Tue Jul 26 22:31:48 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Tue, 26 Jul 2022 12:31:48 +0200 Subject: [Koha] Accessing DNB databases via SRU and HTTPS In-Reply-To: <1fd079d4943c47e3a695c6cbc70e191e@gwdg.de> References: <1fd079d4943c47e3a695c6cbc70e191e@gwdg.de> Message-ID: <78e699c3-37e4-ac7f-07e1-a49fe36014a1@adminkuhn.ch> Hi Anke Thank you very much! You wrote: > our config still works well - see screenshot. We have exactly the same configuration - but when trying to access we are getting the following error message: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request Reason: Error reading from remote server I tested the same configuration on my demo installation https://koha.adminkuhn.ch - there it works well. The demo installation is directly in the internet with no (outgoing) firewalls involved. > Changing 80 to 443 doesn't help - the SRU search doesn't work anymore > with that setting. Changing 80 to 443 didn't help either on my demo installation. Thus I think this is a problem of the local firewall of our library that doesn't like the redirect from port 80 to 443. It will have to be solved locally. 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 at adminkuhn.ch · W www.adminkuhn.ch From domm at plix.at Wed Jul 27 01:46:24 2022 From: domm at plix.at (domm at plix.at) Date: Tue, 26 Jul 2022 15:46:24 +0200 Subject: [Koha] Accessing DNB databases via SRU and HTTPS In-Reply-To: References: Message-ID: On 2022-07-26 10:25, Michael Kuhn wrote: > We had a working Koha configuration to access the database of the > German national library (Deutsche Nationalbibliothek / DNB) via SRU > and HTTP. But since 19 July requests using the HTTP-protocol will be > redirected to the HTTPS-protocol by "HTTP-Statuscode 301 Moved We had a similar problem, see https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30332 I first fiddled with some proxys, but in the end updating libyaz5 fixed the issue. (which remindes me that I need to report that in the ticket and close the bug...) Greetings, domm From arouss1980 at gmail.com Wed Jul 27 03:43:51 2022 From: arouss1980 at gmail.com (Andreas Roussos) Date: Tue, 26 Jul 2022 18:43:51 +0300 Subject: [Koha] Adding items to a list not possible in Koha 21.11.09 In-Reply-To: References: <9cb9c517-3194-908e-d181-5d6c244e6c72@gmail.com> Message-ID: <0c83a286-8b7a-35cb-7c0f-4b5d3170117a@gmail.com> Hello again Michael, Thank you very much for taking the time to provide these details! I'm interested in finding what's causing this misbehaviour, so please bear with me as I bombard you with more questions! ;-) Have you made any staff interface customisations with JavaScript or jQuery? Is there anything in your instance's IntranetUserJS system preference that refers to the .addtolist or .selection CSS classes? Do you have any active browser plugins that could interfere with your browser's JavaScript and/or LocalStorage capabilities? Have you tried adding a record to a list using a different browser? Does anything helpful get printed in your browser's console? (starting from the point in time where you perform the catalog search, and ending when you click on "Add to list -> List name") Have you had any Koha plugins installed or enabled recently? Thanks! Kind regards, Andreas On 2022-07-25 10:40, Michael Kuhn wrote: > Hi Andreas > > You wrote: > > > I've tried to reproduce the issue you describe on a development > > 21.11.09 instance that I set up, but was not successful. > > > > So, I have a few questions for you to help me diagnose this ;-) > > > > Assuming a package installation, have you restarted the koha-common > > service following the upgrade? > > Yes, we have. We have also restarted the complete host. > > > Have you performed a hard refresh of your web browser's cache? (hit > > CTRL-F5) > > Yes, we did. > > > Finally, which version of Koha did you upgrade from? > > We have updated from Debian 9 to 10, then from Koha 19.05.02 to 21.11.09. > > Best wishes: Michael From mik at adminkuhn.ch Wed Jul 27 04:31:33 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Tue, 26 Jul 2022 18:31:33 +0200 Subject: [Koha] Adding items to a list not possible in Koha 21.11.09 In-Reply-To: <0c83a286-8b7a-35cb-7c0f-4b5d3170117a@gmail.com> References: <9cb9c517-3194-908e-d181-5d6c244e6c72@gmail.com> <0c83a286-8b7a-35cb-7c0f-4b5d3170117a@gmail.com> Message-ID: <4f429f3b-90de-da1a-d6bd-ba4c8e23b0a5@adminkuhn.ch> Hello Andreas > Thank you very much for taking the time to provide these details! > > I'm interested in finding what's causing this misbehaviour, so > please bear with me as I bombard you with more questions! ;-) > > Have you made any staff interface customisations with JavaScript > or jQuery? Is there anything in your instance's IntranetUserJS > system preference that refers to the .addtolist or .selection > CSS classes? No customisations. > Do you have any active browser plugins that could interfere with > your browser's JavaScript and/or LocalStorage capabilities? Personally, I'm using the webbrowser officially supported by Koha, Mozilla Firefox 91.10.0esr and I'm not aware of any plugin that would interfere or had ever interfered anywhere. > Have you tried adding a record to a list using a different browser? I just tried it with Google Chrome 103.0.5060.53 but it is the same - a small popup appears, saying "No item was selected". > Does anything helpful get printed in your browser's console? > (starting from the point in time where you perform the catalog > search, and ending when you click on "Add to list -> List name") Just after the search the following is written into the browser console: sendRemoveListener on closed conduit textern at jlebon.com.3985729651140 ConduitsChild.jsm:108 _send resource://gre/modules/ConduitsChild.jsm:108 _send self-hosted:1282 removeListener resource://gre/modules/ExtensionChild.jsm:663 removeListener resource://gre/modules/ExtensionChild.jsm:886 onChanged chrome://extensions/content/child/ext-storage.js:332 removeListener resource://gre/modules/ExtensionCommon.jsm:2534 revoke resource://gre/modules/ExtensionCommon.jsm:2556 close resource://gre/modules/ExtensionCommon.jsm:2561 unload resource://gre/modules/ExtensionCommon.jsm:922 close resource://gre/modules/ExtensionContent.jsm:934 destroyed resource://gre/modules/ExtensionContent.jsm:1012 observe resource://gre/modules/ExtensionContent.jsm:1030 But there is no further message when actually trying to add the checked record to the list. > Have you had any Koha plugins installed or enabled recently? No, there are no Koha plugins installed on this host. As the librarian has meanwhile told me it is possible to add records from the second page of a result list, but NOT from the first page of a result list - I can confirm that. It is also possible to add records from the single hit (detail view). Thus the librarian is now searching the wanted records from the first page one by one to add them to the list... 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 at adminkuhn.ch · W www.adminkuhn.ch > On 2022-07-25 10:40, Michael Kuhn wrote: >> Hi Andreas >> >> You wrote: >> >>  > I've tried to reproduce the issue you describe on a development >>  > 21.11.09 instance that I set up, but was not successful. >>  > >>  > So, I have a few questions for you to help me diagnose this ;-) >>  > >>  > Assuming a package installation, have you restarted the koha-common >>  > service following the upgrade? >> >> Yes, we have. We have also restarted the complete host. >> >>  > Have you performed a hard refresh of your web browser's cache? (hit >>  > CTRL-F5) >> >> Yes, we did. >> >>  > Finally, which version of Koha did you upgrade from? >> >> We have updated from Debian 9 to 10, then from Koha 19.05.02 to 21.11.09. >> >> Best wishes: Michael From secretary at koha-us.org Wed Jul 27 11:19:41 2022 From: secretary at koha-us.org (Jennifer Marlatt) Date: Tue, 26 Jul 2022 16:19:41 -0700 Subject: [Koha] koha-US August 2022 Events & Meetings Message-ID: koha-US online meetings and events are free and open to all. See our calendar for a full list: http://koha-us.org/calendar/. For Google Calendar users, add our events calendar to your list for easy access to meeting times and links: https://calendar.google.com/calendar/u/1?cid=a29oYS11cy5vcmdfZG1xb2pkczE5ZnU4bDhiZDZyb2dlajluNDhAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ *Meetings* Board Meeting - Wednesday, August 3 @ 8:30a PT / 11:30a ET / 15:30 UTC General Meeting - Wednesday, August 10 @ 8:30a PT / 11:30a ET / 15:30 UTC *Special Interest Groups* Circulation - Tuesday, August 2 @ 10:00a PT / 1:00p ET / 17:00 UTC Cataloging - Thursday, August 4 @ 8:00a PT / 11:00a ET / 15:00 UTC System Administration - Tuesday, August 9 @ 8:00a PT / 11:00p ET / 15:00 UTC Acquisitions - Tuesday, August 16 @ 9:00a PT / 12:00p ET / 16:00 UTC Web Development - Thursday, August 18 @ 10:00a PT / 1:00p ET / 17:00 UTC Demonstration Instance - Tuesday, August 23 @ 8:00a PT / 11:00a ET / 15:00 UTC Visit http://koha-us.org/special-interest-groups/ to learn more and sign up for topic-specific mailing lists. Most meetings and events are recorded and made available at https://www.youtube.com/kohaus Jennifer Marlatt koha-US Secretary secretary at koha-us.org From gveranis at dataly.gr Wed Jul 27 18:50:24 2022 From: gveranis at dataly.gr (gveranis at dataly.gr) Date: Wed, 27 Jul 2022 09:50:24 +0300 Subject: [Koha] Adding items to a list not possible in Koha 21.11.09 In-Reply-To: <4f429f3b-90de-da1a-d6bd-ba4c8e23b0a5@adminkuhn.ch> References: <9cb9c517-3194-908e-d181-5d6c244e6c72@gmail.com> <0c83a286-8b7a-35cb-7c0f-4b5d3170117a@gmail.com> <4f429f3b-90de-da1a-d6bd-ba4c8e23b0a5@adminkuhn.ch> Message-ID: <010601d8a185$28177d60$78467820$@dataly.gr> Hi Michael, Do you try to add items by barcode or by itemnumber ? Best Regards, George Veranis -----Original Message----- From: Koha On Behalf Of Michael Kuhn Sent: Tuesday, July 26, 2022 7:32 PM To: Andreas Roussos ; Koha Subject: Re: [Koha] Adding items to a list not possible in Koha 21.11.09 Hello Andreas > Thank you very much for taking the time to provide these details! > > I'm interested in finding what's causing this misbehaviour, so > please bear with me as I bombard you with more questions! ;-) > > Have you made any staff interface customisations with JavaScript > or jQuery? Is there anything in your instance's IntranetUserJS > system preference that refers to the .addtolist or .selection > CSS classes? No customisations. > Do you have any active browser plugins that could interfere with > your browser's JavaScript and/or LocalStorage capabilities? Personally, I'm using the webbrowser officially supported by Koha, Mozilla Firefox 91.10.0esr and I'm not aware of any plugin that would interfere or had ever interfered anywhere. > Have you tried adding a record to a list using a different browser? I just tried it with Google Chrome 103.0.5060.53 but it is the same - a small popup appears, saying "No item was selected". > Does anything helpful get printed in your browser's console? > (starting from the point in time where you perform the catalog > search, and ending when you click on "Add to list -> List name") Just after the search the following is written into the browser console: sendRemoveListener on closed conduit textern at jlebon.com.3985729651140 ConduitsChild.jsm:108 _send resource://gre/modules/ConduitsChild.jsm:108 _send self-hosted:1282 removeListener resource://gre/modules/ExtensionChild.jsm:663 removeListener resource://gre/modules/ExtensionChild.jsm:886 onChanged chrome://extensions/content/child/ext-storage.js:332 removeListener resource://gre/modules/ExtensionCommon.jsm:2534 revoke resource://gre/modules/ExtensionCommon.jsm:2556 close resource://gre/modules/ExtensionCommon.jsm:2561 unload resource://gre/modules/ExtensionCommon.jsm:922 close resource://gre/modules/ExtensionContent.jsm:934 destroyed resource://gre/modules/ExtensionContent.jsm:1012 observe resource://gre/modules/ExtensionContent.jsm:1030 But there is no further message when actually trying to add the checked record to the list. > Have you had any Koha plugins installed or enabled recently? No, there are no Koha plugins installed on this host. As the librarian has meanwhile told me it is possible to add records from the second page of a result list, but NOT from the first page of a result list - I can confirm that. It is also possible to add records from the single hit (detail view). Thus the librarian is now searching the wanted records from the first page one by one to add them to the list... 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 at adminkuhn.ch · W www.adminkuhn.ch > On 2022-07-25 10:40, Michael Kuhn wrote: >> Hi Andreas >> >> You wrote: >> >> > I've tried to reproduce the issue you describe on a development >> > 21.11.09 instance that I set up, but was not successful. >> > >> > So, I have a few questions for you to help me diagnose this ;-) >> > >> > Assuming a package installation, have you restarted the koha-common >> > service following the upgrade? >> >> Yes, we have. We have also restarted the complete host. >> >> > Have you performed a hard refresh of your web browser's cache? (hit >> > CTRL-F5) >> >> Yes, we did. >> >> > Finally, which version of Koha did you upgrade from? >> >> We have updated from Debian 9 to 10, then from Koha 19.05.02 to 21.11.09. >> >> Best wishes: Michael _______________________________________________ Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From mik at adminkuhn.ch Wed Jul 27 19:34:13 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Wed, 27 Jul 2022 09:34:13 +0200 Subject: [Koha] Adding items to a list not possible in Koha 21.11.09 In-Reply-To: <010601d8a185$28177d60$78467820$@dataly.gr> References: <9cb9c517-3194-908e-d181-5d6c244e6c72@gmail.com> <0c83a286-8b7a-35cb-7c0f-4b5d3170117a@gmail.com> <4f429f3b-90de-da1a-d6bd-ba4c8e23b0a5@adminkuhn.ch> <010601d8a185$28177d60$78467820$@dataly.gr> Message-ID: Hi George > Do you try to add items by barcode or by itemnumber ? I search for anything that gives me a result list. In this list (on the first page) I check one ore more items on the left side, then try to add it/them to an existing list. But Koha says "No item was selected" and doesn't add the item(s) to the list. 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 at adminkuhn.ch · W www.adminkuhn.ch > Do you try to add items by barcode or by itemnumber ? > > Best Regards, > George Veranis > > -----Original Message----- > From: Koha On Behalf Of Michael Kuhn > Sent: Tuesday, July 26, 2022 7:32 PM > To: Andreas Roussos ; Koha > Subject: Re: [Koha] Adding items to a list not possible in Koha 21.11.09 > > Hello Andreas > > > Thank you very much for taking the time to provide these details! > > > > I'm interested in finding what's causing this misbehaviour, so > please bear with me as I bombard you with more questions! ;-) > > Have you made any staff interface customisations with JavaScript > or jQuery? Is there anything in your instance's IntranetUserJS > system preference that refers to the .addtolist or .selection > CSS classes? > > No customisations. > > > Do you have any active browser plugins that could interfere with > your browser's JavaScript and/or LocalStorage capabilities? > > Personally, I'm using the webbrowser officially supported by Koha, Mozilla Firefox 91.10.0esr and I'm not aware of any plugin that would interfere or had ever interfered anywhere. > > > Have you tried adding a record to a list using a different browser? > > I just tried it with Google Chrome 103.0.5060.53 but it is the same - a small popup appears, saying "No item was selected". > > > Does anything helpful get printed in your browser's console? > > (starting from the point in time where you perform the catalog > search, and ending when you click on "Add to list -> List name") > > Just after the search the following is written into the browser console: > > sendRemoveListener on closed conduit textern at jlebon.com.3985729651140 > ConduitsChild.jsm:108 > _send resource://gre/modules/ConduitsChild.jsm:108 > _send self-hosted:1282 > removeListener resource://gre/modules/ExtensionChild.jsm:663 > removeListener resource://gre/modules/ExtensionChild.jsm:886 > onChanged chrome://extensions/content/child/ext-storage.js:332 > removeListener resource://gre/modules/ExtensionCommon.jsm:2534 > revoke resource://gre/modules/ExtensionCommon.jsm:2556 > close resource://gre/modules/ExtensionCommon.jsm:2561 > unload resource://gre/modules/ExtensionCommon.jsm:922 > close resource://gre/modules/ExtensionContent.jsm:934 > destroyed resource://gre/modules/ExtensionContent.jsm:1012 > observe resource://gre/modules/ExtensionContent.jsm:1030 > > But there is no further message when actually trying to add the checked record to the list. > > > Have you had any Koha plugins installed or enabled recently? > > No, there are no Koha plugins installed on this host. > > As the librarian has meanwhile told me it is possible to add records from the second page of a result list, but NOT from the first page of a result list - I can confirm that. It is also possible to add records from the single hit (detail view). Thus the librarian is now searching the wanted records from the first page one by one to add them to the list... > > 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 at adminkuhn.ch · W www.adminkuhn.ch > > >> On 2022-07-25 10:40, Michael Kuhn wrote: >>> Hi Andreas >>> >>> You wrote: >>> >>> > I've tried to reproduce the issue you describe on a development >>> > 21.11.09 instance that I set up, but was not successful. >>> > >>> > So, I have a few questions for you to help me diagnose this ;-) >>> > >>> > Assuming a package installation, have you restarted the koha-common >>> > service following the upgrade? >>> >>> Yes, we have. We have also restarted the complete host. >>> >>> > Have you performed a hard refresh of your web browser's cache? (hit >>> > CTRL-F5) >>> >>> Yes, we did. >>> >>> > Finally, which version of Koha did you upgrade from? >>> >>> We have updated from Debian 9 to 10, then from Koha 19.05.02 to 21.11.09. >>> >>> Best wishes: Michael > > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From cjf at wmu.se Wed Jul 27 19:34:17 2022 From: cjf at wmu.se (Fairlamb, Christina) Date: Wed, 27 Jul 2022 09:34:17 +0200 Subject: [Koha] 500 errors in staff mode and forcing a database update Message-ID: Hello all, We've had these issues since at least Koha 21.11 but are now on 22.05. Some links on the koha staff page result in a 500 error. Checking the plack-error.log, these are the lines linking to the page I was trying to access: *EDI accounts* DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Unknown column 'me.responses_enabled' in 'field list' at /usr/share/koha/intranet/cgi-bin/admin/edi_accounts.pl line 110 *Library EANs* DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Unknown column 'me.ee_id' in 'field list' at /usr/share/koha/intranet/cgi-bin/admin/edi_ean_accounts.pl line 93 We also still have the Patron relationship problems issue in this bug: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24263, which should have been fixed during past upgrades. (values have been used for guarantee/guarantor relationships, but do not exist in the 'borrowerRelationship') It seems as though our database schema is not updating fully during our latest koha upgrades. I've tried to run the Manual schema upgrade which results in this message only: DEV atomic update /usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/ bug_30899.pl [07:15:11]: Bug 30899 - Check borrower_attribute_types FK constraint (30449 follow-up) Which, according to this bug report: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30899 - is a none issue and means the schema is up to date. Is there a way to force a schema update to go through all updates since a specific koha version? Christina From gveranis at dataly.gr Wed Jul 27 19:36:12 2022 From: gveranis at dataly.gr (gveranis at dataly.gr) Date: Wed, 27 Jul 2022 10:36:12 +0300 Subject: [Koha] Adding items to a list not possible in Koha 21.11.09 In-Reply-To: References: <9cb9c517-3194-908e-d181-5d6c244e6c72@gmail.com> <0c83a286-8b7a-35cb-7c0f-4b5d3170117a@gmail.com> <4f429f3b-90de-da1a-d6bd-ba4c8e23b0a5@adminkuhn.ch> <010601d8a185$28177d60$78467820$@dataly.gr> Message-ID: <01b101d8a18b$8cc75770$a6560650$@dataly.gr> Could you please share some screenshots ? to give me a try to replicate that ? Thanks, George -----Original Message----- From: Michael Kuhn Sent: Wednesday, July 27, 2022 10:34 AM To: gveranis at dataly.gr; 'Andreas Roussos' ; 'Koha' Subject: Re: [Koha] Adding items to a list not possible in Koha 21.11.09 Hi George > Do you try to add items by barcode or by itemnumber ? I search for anything that gives me a result list. In this list (on the first page) I check one ore more items on the left side, then try to add it/them to an existing list. But Koha says "No item was selected" and doesn't add the item(s) to the list. 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 at adminkuhn.ch · W www.adminkuhn.ch > Do you try to add items by barcode or by itemnumber ? > > Best Regards, > George Veranis > > -----Original Message----- > From: Koha On Behalf Of Michael Kuhn > Sent: Tuesday, July 26, 2022 7:32 PM > To: Andreas Roussos ; Koha > Subject: Re: [Koha] Adding items to a list not possible in Koha 21.11.09 > > Hello Andreas > > > Thank you very much for taking the time to provide these details! > > > > I'm interested in finding what's causing this misbehaviour, so > please bear with me as I bombard you with more questions! ;-) > > Have you made any staff interface customisations with JavaScript > or jQuery? Is there anything in your instance's IntranetUserJS > system preference that refers to the .addtolist or .selection > CSS classes? > > No customisations. > > > Do you have any active browser plugins that could interfere with > your browser's JavaScript and/or LocalStorage capabilities? > > Personally, I'm using the webbrowser officially supported by Koha, Mozilla Firefox 91.10.0esr and I'm not aware of any plugin that would interfere or had ever interfered anywhere. > > > Have you tried adding a record to a list using a different browser? > > I just tried it with Google Chrome 103.0.5060.53 but it is the same - a small popup appears, saying "No item was selected". > > > Does anything helpful get printed in your browser's console? > > (starting from the point in time where you perform the catalog > search, and ending when you click on "Add to list -> List name") > > Just after the search the following is written into the browser console: > > sendRemoveListener on closed conduit textern at jlebon.com.3985729651140 > ConduitsChild.jsm:108 > _send resource://gre/modules/ConduitsChild.jsm:108 > _send self-hosted:1282 > removeListener resource://gre/modules/ExtensionChild.jsm:663 > removeListener resource://gre/modules/ExtensionChild.jsm:886 > onChanged chrome://extensions/content/child/ext-storage.js:332 > removeListener resource://gre/modules/ExtensionCommon.jsm:2534 > revoke resource://gre/modules/ExtensionCommon.jsm:2556 > close resource://gre/modules/ExtensionCommon.jsm:2561 > unload resource://gre/modules/ExtensionCommon.jsm:922 > close resource://gre/modules/ExtensionContent.jsm:934 > destroyed resource://gre/modules/ExtensionContent.jsm:1012 > observe resource://gre/modules/ExtensionContent.jsm:1030 > > But there is no further message when actually trying to add the checked record to the list. > > > Have you had any Koha plugins installed or enabled recently? > > No, there are no Koha plugins installed on this host. > > As the librarian has meanwhile told me it is possible to add records from the second page of a result list, but NOT from the first page of a result list - I can confirm that. It is also possible to add records from the single hit (detail view). Thus the librarian is now searching the wanted records from the first page one by one to add them to the list... > > 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 at adminkuhn.ch · W www.adminkuhn.ch > > >> On 2022-07-25 10:40, Michael Kuhn wrote: >>> Hi Andreas >>> >>> You wrote: >>> >>> > I've tried to reproduce the issue you describe on a development >>> > 21.11.09 instance that I set up, but was not successful. >>> > >>> > So, I have a few questions for you to help me diagnose this ;-) >>> > >>> > Assuming a package installation, have you restarted the koha-common >>> > service following the upgrade? >>> >>> Yes, we have. We have also restarted the complete host. >>> >>> > Have you performed a hard refresh of your web browser's cache? (hit >>> > CTRL-F5) >>> >>> Yes, we did. >>> >>> > Finally, which version of Koha did you upgrade from? >>> >>> We have updated from Debian 9 to 10, then from Koha 19.05.02 to 21.11.09. >>> >>> Best wishes: Michael > > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From mik at adminkuhn.ch Wed Jul 27 20:03:39 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Wed, 27 Jul 2022 10:03:39 +0200 Subject: [Koha] Adding items to a list not possible in Koha 21.11.09 In-Reply-To: <01b101d8a18b$8cc75770$a6560650$@dataly.gr> References: <9cb9c517-3194-908e-d181-5d6c244e6c72@gmail.com> <0c83a286-8b7a-35cb-7c0f-4b5d3170117a@gmail.com> <4f429f3b-90de-da1a-d6bd-ba4c8e23b0a5@adminkuhn.ch> <010601d8a185$28177d60$78467820$@dataly.gr> <01b101d8a18b$8cc75770$a6560650$@dataly.gr> Message-ID: <6deb1cac-0f9b-e42c-53a8-44ca8c6449ff@adminkuhn.ch> Hi George > Could you please share some screenshots ? to give me a try to > replicate that ? 1. Perform a search and check an item on the first page * http://adminkuhn.ch/download/list-1.png 2. Click on "Add to list" and select a list, the message "No item was selected" appears * http://adminkuhn.ch/download/list-2.png 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 at adminkuhn.ch · W www.adminkuhn.ch > -----Original Message----- > From: Michael Kuhn > Sent: Wednesday, July 27, 2022 10:34 AM > To: gveranis at dataly.gr; 'Andreas Roussos' ; 'Koha' > Subject: Re: [Koha] Adding items to a list not possible in Koha 21.11.09 > > Hi George > > > Do you try to add items by barcode or by itemnumber ? > > I search for anything that gives me a result list. > > In this list (on the first page) I check one ore more items on the left side, then try to add it/them to an existing list. But Koha says "No item was selected" and doesn't add the item(s) to the list. > > 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 at adminkuhn.ch · W www.adminkuhn.ch > > > >> Do you try to add items by barcode or by itemnumber ? >> >> Best Regards, >> George Veranis >> >> -----Original Message----- >> From: Koha On Behalf Of Michael Kuhn >> Sent: Tuesday, July 26, 2022 7:32 PM >> To: Andreas Roussos ; Koha >> Subject: Re: [Koha] Adding items to a list not possible in Koha 21.11.09 >> >> Hello Andreas >> >> > Thank you very much for taking the time to provide these details! >> > >> > I'm interested in finding what's causing this misbehaviour, so > please bear with me as I bombard you with more questions! ;-) > > Have you made any staff interface customisations with JavaScript > or jQuery? Is there anything in your instance's IntranetUserJS > system preference that refers to the .addtolist or .selection > CSS classes? >> >> No customisations. >> >> > Do you have any active browser plugins that could interfere with > your browser's JavaScript and/or LocalStorage capabilities? >> >> Personally, I'm using the webbrowser officially supported by Koha, Mozilla Firefox 91.10.0esr and I'm not aware of any plugin that would interfere or had ever interfered anywhere. >> >> > Have you tried adding a record to a list using a different browser? >> >> I just tried it with Google Chrome 103.0.5060.53 but it is the same - a small popup appears, saying "No item was selected". >> >> > Does anything helpful get printed in your browser's console? >> > (starting from the point in time where you perform the catalog > search, and ending when you click on "Add to list -> List name") >> >> Just after the search the following is written into the browser console: >> >> sendRemoveListener on closed conduit textern at jlebon.com.3985729651140 >> ConduitsChild.jsm:108 >> _send resource://gre/modules/ConduitsChild.jsm:108 >> _send self-hosted:1282 >> removeListener resource://gre/modules/ExtensionChild.jsm:663 >> removeListener resource://gre/modules/ExtensionChild.jsm:886 >> onChanged chrome://extensions/content/child/ext-storage.js:332 >> removeListener resource://gre/modules/ExtensionCommon.jsm:2534 >> revoke resource://gre/modules/ExtensionCommon.jsm:2556 >> close resource://gre/modules/ExtensionCommon.jsm:2561 >> unload resource://gre/modules/ExtensionCommon.jsm:922 >> close resource://gre/modules/ExtensionContent.jsm:934 >> destroyed resource://gre/modules/ExtensionContent.jsm:1012 >> observe resource://gre/modules/ExtensionContent.jsm:1030 >> >> But there is no further message when actually trying to add the checked record to the list. >> >> > Have you had any Koha plugins installed or enabled recently? >> >> No, there are no Koha plugins installed on this host. >> >> As the librarian has meanwhile told me it is possible to add records from the second page of a result list, but NOT from the first page of a result list - I can confirm that. It is also possible to add records from the single hit (detail view). Thus the librarian is now searching the wanted records from the first page one by one to add them to the list... >> >> 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 at adminkuhn.ch · W www.adminkuhn.ch >> >> >>> On 2022-07-25 10:40, Michael Kuhn wrote: >>>> Hi Andreas >>>> >>>> You wrote: >>>> >>>> > I've tried to reproduce the issue you describe on a development >>>> > 21.11.09 instance that I set up, but was not successful. >>>> > >>>> > So, I have a few questions for you to help me diagnose this ;-) >>>> > >>>> > Assuming a package installation, have you restarted the koha-common >>>> > service following the upgrade? >>>> >>>> Yes, we have. We have also restarted the complete host. >>>> >>>> > Have you performed a hard refresh of your web browser's cache? (hit >>>> > CTRL-F5) >>>> >>>> Yes, we did. >>>> >>>> > Finally, which version of Koha did you upgrade from? >>>> >>>> We have updated from Debian 9 to 10, then from Koha 19.05.02 to 21.11.09. >>>> >>>> Best wishes: Michael >> >> >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> > > > From fridolin.somers at biblibre.com Wed Jul 27 21:17:14 2022 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Tue, 26 Jul 2022 23:17:14 -1000 Subject: [Koha] Koha upgrade schema issue In-Reply-To: <645f924a-1b89-d3db-041b-36022294468b@web.de> References: <2062025918.2366128.1658221015968.ref@mail.yahoo.com> <2062025918.2366128.1658221015968@mail.yahoo.com> <645f924a-1b89-d3db-041b-36022294468b@web.de> Message-ID: <90f23a29-5cf3-06ac-ed2f-2ec9fafe957c@biblibre.com> This is fixed in 22.05.03, see https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30899 Le 19/07/2022 à 00:42, Katrin Fischer a écrit : > Hi, > > what error did you get? > > Katrin > > On 19.07.22 10:56, Sami M. Rasheed wrote: >> >> >> Kindly, Koha Group >> Please let me know how to correct the Koha upgrade schema issue. >> The system displays the following error while I'm using the >> (koha-upgrade-schema library) to upgrade the Koha system: >> >> >> >> DEV atomic update >> /usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/bug_30899.pl >>  [11:37:44]: Bug 30899 - Check borrower_attribute_types FK constraint >> (30449 follow-up) >> >> I'm using: >> >> Koha version: 21.11 >> >> OS version: Ubuntu 20.04.4 LTS >> >> MySQL version: mysql Ver 8.0.29 -0ubuntu0.20.04.3 for Linux on x86_64 >> ((Ubuntu)) >> >> Thanks >> Sami Abu Darbeya >> _______________________________________________ >> >> Koha mailing list  http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list  http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From fridolin.somers at biblibre.com Wed Jul 27 21:19:48 2022 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Tue, 26 Jul 2022 23:19:48 -1000 Subject: [Koha] Error message on upgrade In-Reply-To: References: Message-ID: <936ff8aa-f416-0455-f5f6-22901b2ef808@biblibre.com> There "DEV atomic update" warning is fixed in 22.05.03, see https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30899 Le 19/07/2022 à 07:49, Elaine Bradtke a écrit : > We're not sure what this means, and or what we need to do to correct it, if > anything. > > Upgrade to 22.05.02.000 [18:18:02]: Koha 22.05.02 release > DEV atomic update > /usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/ > bug_30899.pl [18:18:02]: Bug 30899 - Check borrower_attribute_types FK > constraint (30449 follow-up) > NO PLURAL FORM HEADER FOUND - DEFAULTING TO 2 > > Elaine Bradtke > VWML > English Folk Dance and Song Society > Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY > Tel +44 (0) 20 7485 2206 (This number is for the English Folk Dance and > Song Society in London, England. If you wish to phone me personally, send > an e-mail first. I work off site) > -------------------------------------------------------------------------- > Registered Company No. 297142 > Charity Registered in England and Wales No. 305999 > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From mtj at kohaaloha.com Wed Jul 27 22:06:32 2022 From: mtj at kohaaloha.com (Mason James) Date: Wed, 27 Jul 2022 22:06:32 +1200 Subject: [Koha] =?utf-8?q?Koha_packages_are_available_=F0=9F=8E=81?= Message-ID: <88ad62da-3f3c-1076-4fd1-9fedc473b665@kohaaloha.com> kia ora community, the latest Koha packages are available an installation guide is below...   https://wiki.koha-community.org/wiki/Koha_on_Debian cheers, Mason From arturo.longoria at sll.texas.gov Thu Jul 28 01:27:29 2022 From: arturo.longoria at sll.texas.gov (Arturo Longoria) Date: Wed, 27 Jul 2022 13:27:29 +0000 Subject: [Koha] Adding items to a list not possible in Koha 21.11.09 In-Reply-To: <6deb1cac-0f9b-e42c-53a8-44ca8c6449ff@adminkuhn.ch> References: <9cb9c517-3194-908e-d181-5d6c244e6c72@gmail.com> <0c83a286-8b7a-35cb-7c0f-4b5d3170117a@gmail.com> <4f429f3b-90de-da1a-d6bd-ba4c8e23b0a5@adminkuhn.ch> <010601d8a185$28177d60$78467820$@dataly.gr> <01b101d8a18b$8cc75770$a6560650$@dataly.gr> <6deb1cac-0f9b-e42c-53a8-44ca8c6449ff@adminkuhn.ch> Message-ID: Another tip for troubleshooting in case you haven't tried it - Bug 14004 added the ability to disable both custom CSS and JS by appending some parameters to your staff client's URL. This would let you load these pages without also loading your library's custom CSS and JavaScript, so that you can more definitively rule out that it isn't a local issue. You'd add ?DISABLE_SYSPREF_IntranetUserJS=1&DISABLE_SYSPREF_IntranetUserCSS=1 to the end of your URL. For example, if your staff client is accessed at http://www.mylibraryisthebest.com, you'd load http://www.mylibraryisthebest.com/?DISABLE_SYSPREF_IntranetUserJS=1&DISABLE_SYSPREF_IntranetUserCSS=1 so that it does not load your CSS and JS. Just a thought for some further troubleshooting. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14004 Arturo Longoria Reference Librarian/Web Administrator Texas State Law Library www.sll.texas.gov -----Original Message----- From: Koha On Behalf Of Michael Kuhn Sent: Wednesday, July 27, 2022 3:04 AM To: gveranis at dataly.gr; 'Andreas Roussos' ; 'Koha' Subject: Re: [Koha] Adding items to a list not possible in Koha 21.11.09 Hi George > Could you please share some screenshots ? to give me a try to > replicate that ? 1. Perform a search and check an item on the first page * https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fadminkuhn.ch%2Fdownload%2Flist-1.png&data=05%7C01%7Carturo.longoria%40sll.texas.gov%7C8191ef6467b446af61cd08da6fa6a4f3%7Caefc2264480e4d03937744890fe44e40%7C0%7C0%7C637945058803013164%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CnM2Pdg6tyvTEwiymXm6hrJwB4YTvMe5B7VnE1taWWU%3D&reserved=0 2. Click on "Add to list" and select a list, the message "No item was selected" appears * https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fadminkuhn.ch%2Fdownload%2Flist-2.png&data=05%7C01%7Carturo.longoria%40sll.texas.gov%7C8191ef6467b446af61cd08da6fa6a4f3%7Caefc2264480e4d03937744890fe44e40%7C0%7C0%7C637945058803013164%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=H3Yjq1b6ERiMixk8qBxrLJiHMjb3eSB6PWFaUiX2q%2F0%3D&reserved=0 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 at adminkuhn.ch · W https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.adminkuhn.ch%2F&data=05%7C01%7Carturo.longoria%40sll.texas.gov%7C8191ef6467b446af61cd08da6fa6a4f3%7Caefc2264480e4d03937744890fe44e40%7C0%7C0%7C637945058803013164%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9m17Dgx9Rts549tixnuh%2FDjJQmWNrWYopxRVqfXaHzw%3D&reserved=0 > -----Original Message----- > From: Michael Kuhn > Sent: Wednesday, July 27, 2022 10:34 AM > To: gveranis at dataly.gr; 'Andreas Roussos' ; 'Koha' > Subject: Re: [Koha] Adding items to a list not possible in Koha 21.11.09 > > Hi George > > > Do you try to add items by barcode or by itemnumber ? > > I search for anything that gives me a result list. > > In this list (on the first page) I check one ore more items on the left side, then try to add it/them to an existing list. But Koha says "No item was selected" and doesn't add the item(s) to the list. > > 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 at adminkuhn.ch · W https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.adminkuhn.ch%2F&data=05%7C01%7Carturo.longoria%40sll.texas.gov%7C8191ef6467b446af61cd08da6fa6a4f3%7Caefc2264480e4d03937744890fe44e40%7C0%7C0%7C637945058803013164%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9m17Dgx9Rts549tixnuh%2FDjJQmWNrWYopxRVqfXaHzw%3D&reserved=0 > > > >> Do you try to add items by barcode or by itemnumber ? >> >> Best Regards, >> George Veranis >> >> -----Original Message----- >> From: Koha On Behalf Of Michael Kuhn >> Sent: Tuesday, July 26, 2022 7:32 PM >> To: Andreas Roussos ; Koha >> Subject: Re: [Koha] Adding items to a list not possible in Koha 21.11.09 >> >> Hello Andreas >> >> > Thank you very much for taking the time to provide these details! >> > >> > I'm interested in finding what's causing this misbehaviour, so > please bear with me as I bombard you with more questions! ;-) > > Have you made any staff interface customisations with JavaScript > or jQuery? Is there anything in your instance's IntranetUserJS > system preference that refers to the .addtolist or .selection > CSS classes? >> >> No customisations. >> >> > Do you have any active browser plugins that could interfere with > your browser's JavaScript and/or LocalStorage capabilities? >> >> Personally, I'm using the webbrowser officially supported by Koha, Mozilla Firefox 91.10.0esr and I'm not aware of any plugin that would interfere or had ever interfered anywhere. >> >> > Have you tried adding a record to a list using a different browser? >> >> I just tried it with Google Chrome 103.0.5060.53 but it is the same - a small popup appears, saying "No item was selected". >> >> > Does anything helpful get printed in your browser's console? >> > (starting from the point in time where you perform the catalog > search, and ending when you click on "Add to list -> List name") >> >> Just after the search the following is written into the browser console: >> >> sendRemoveListener on closed conduit textern at jlebon.com.3985729651140 >> ConduitsChild.jsm:108 >> _send resource://gre/modules/ConduitsChild.jsm:108 >> _send self-hosted:1282 >> removeListener resource://gre/modules/ExtensionChild.jsm:663 >> removeListener resource://gre/modules/ExtensionChild.jsm:886 >> onChanged chrome://extensions/content/child/ext-storage.js:332 >> removeListener resource://gre/modules/ExtensionCommon.jsm:2534 >> revoke resource://gre/modules/ExtensionCommon.jsm:2556 >> close resource://gre/modules/ExtensionCommon.jsm:2561 >> unload resource://gre/modules/ExtensionCommon.jsm:922 >> close resource://gre/modules/ExtensionContent.jsm:934 >> destroyed resource://gre/modules/ExtensionContent.jsm:1012 >> observe resource://gre/modules/ExtensionContent.jsm:1030 >> >> But there is no further message when actually trying to add the checked record to the list. >> >> > Have you had any Koha plugins installed or enabled recently? >> >> No, there are no Koha plugins installed on this host. >> >> As the librarian has meanwhile told me it is possible to add records from the second page of a result list, but NOT from the first page of a result list - I can confirm that. It is also possible to add records from the single hit (detail view). Thus the librarian is now searching the wanted records from the first page one by one to add them to the list... >> >> 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 at adminkuhn.ch · W https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.adminkuhn.ch%2F&data=05%7C01%7Carturo.longoria%40sll.texas.gov%7C8191ef6467b446af61cd08da6fa6a4f3%7Caefc2264480e4d03937744890fe44e40%7C0%7C0%7C637945058803013164%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9m17Dgx9Rts549tixnuh%2FDjJQmWNrWYopxRVqfXaHzw%3D&reserved=0 >> >> >>> On 2022-07-25 10:40, Michael Kuhn wrote: >>>> Hi Andreas >>>> >>>> You wrote: >>>> >>>> > I've tried to reproduce the issue you describe on a development >>>> > 21.11.09 instance that I set up, but was not successful. >>>> > >>>> > So, I have a few questions for you to help me diagnose this ;-) >>>> > >>>> > Assuming a package installation, have you restarted the koha-common >>>> > service following the upgrade? >>>> >>>> Yes, we have. We have also restarted the complete host. >>>> >>>> > Have you performed a hard refresh of your web browser's cache? (hit >>>> > CTRL-F5) >>>> >>>> Yes, we did. >>>> >>>> > Finally, which version of Koha did you upgrade from? >>>> >>>> We have updated from Debian 9 to 10, then from Koha 19.05.02 to 21.11.09. >>>> >>>> Best wishes: Michael >> >> >> _______________________________________________ >> >> Koha mailing list https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkoha-community.org%2F&data=05%7C01%7Carturo.longoria%40sll.texas.gov%7C8191ef6467b446af61cd08da6fa6a4f3%7Caefc2264480e4d03937744890fe44e40%7C0%7C0%7C637945058803013164%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vC%2BhUT8C7%2Fj9AO730OmsrB3qjcicLT4PTTnTkv6z2Ww%3D&reserved=0 >> Koha at lists.katipo.co.nz >> Unsubscribe: https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.katipo.co.nz%2Fmailman%2Flistinfo%2Fkoha&data=05%7C01%7Carturo.longoria%40sll.texas.gov%7C8191ef6467b446af61cd08da6fa6a4f3%7Caefc2264480e4d03937744890fe44e40%7C0%7C0%7C637945058803013164%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FENkNUDXK1tZ4%2B7W21PhMoLQlD3Yz5jumJR5KHS7eTI%3D&reserved=0 >> > > > _______________________________________________ Koha mailing list https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkoha-community.org%2F&data=05%7C01%7Carturo.longoria%40sll.texas.gov%7C8191ef6467b446af61cd08da6fa6a4f3%7Caefc2264480e4d03937744890fe44e40%7C0%7C0%7C637945058803013164%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vC%2BhUT8C7%2Fj9AO730OmsrB3qjcicLT4PTTnTkv6z2Ww%3D&reserved=0 Koha at lists.katipo.co.nz Unsubscribe: https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.katipo.co.nz%2Fmailman%2Flistinfo%2Fkoha&data=05%7C01%7Carturo.longoria%40sll.texas.gov%7C8191ef6467b446af61cd08da6fa6a4f3%7Caefc2264480e4d03937744890fe44e40%7C0%7C0%7C637945058803013164%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FENkNUDXK1tZ4%2B7W21PhMoLQlD3Yz5jumJR5KHS7eTI%3D&reserved=0 From amutsikiwa at uzlib.uz.ac.zw Thu Jul 28 03:28:12 2022 From: amutsikiwa at uzlib.uz.ac.zw (Admire Mutsikiwa) Date: Wed, 27 Jul 2022 16:28:12 +0100 Subject: [Koha] n-Tier deployment of Koha Message-ID: My Koha implementation is sometimes overwhelmed as it is a two-tier implementation with a database on one server and a Koha application on another server. I am wondering if it is possible to have a 3 or 4 tier deployment architecture, with for instance, having a load balancer, koha application server and a clustered MySQL/Mariadb implementation. Kind Regards, -- *The information transmitted by this email is intended only for the person or entity to which it is addressed. This email may contain proprietary, business-confidential, and/or privileged material. If you are not the intended recipient of this message, be aware that any use, review, retransmission, distribution, reproduction or any action taken in reliance upon this message is strictly prohibited. If you received this in error, please contact the sender and delete the material from all computers* From mik at adminkuhn.ch Thu Jul 28 03:57:04 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Wed, 27 Jul 2022 17:57:04 +0200 Subject: [Koha] Adding items to a list not possible in Koha 21.11.09 In-Reply-To: References: <9cb9c517-3194-908e-d181-5d6c244e6c72@gmail.com> <0c83a286-8b7a-35cb-7c0f-4b5d3170117a@gmail.com> <4f429f3b-90de-da1a-d6bd-ba4c8e23b0a5@adminkuhn.ch> <010601d8a185$28177d60$78467820$@dataly.gr> <01b101d8a18b$8cc75770$a6560650$@dataly.gr> <6deb1cac-0f9b-e42c-53a8-44ca8c6449ff@adminkuhn.ch> Message-ID: <2e1503b8-0602-5a6f-94a5-b27e508dcb1d@adminkuhn.ch> Hi Arturo You wrote: > Another tip for troubleshooting in case you haven't tried it - Bug > 14004 added the ability to disable both custom CSS and JS by appending > some parameters to your staff client's URL. This would let you load > these pages without also loading your library's custom CSS and > JavaScript, so that you can more definitively rule out that it isn't > a local issue. Thanks for the tip! But in the actual case there is no custom CSS or Javascript existing. > You'd add ?DISABLE_SYSPREF_IntranetUserJS=1&DISABLE_SYSPREF_IntranetUserCSS=1 to the end of your URL. For example, > if your staff client is accessed at http://www.mylibraryisthebest.com, > you'd load http://www.mylibraryisthebest.com/?DISABLE_SYSPREF_IntranetUserJS=1&DISABLE_SYSPREF_IntranetUserCSS=1 so that it does not load your CSS and JS. > > Just a thought for some further troubleshooting. > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14004 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 at adminkuhn.ch · W www.adminkuhn.ch From dcook at prosentient.com.au Thu Jul 28 12:49:04 2022 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Thu, 28 Jul 2022 10:49:04 +1000 Subject: [Koha] n-Tier deployment of Koha In-Reply-To: References: Message-ID: <081a01d8a21b$e6d6c080$b4844180$@prosentient.com.au> Hi Admire, You'll probably have more luck asking on the dev listserv: koha-devel at lists.koha-community.org. However, I'll try to offer some insight here. I'm also CCing in Mengu who has probably the biggest horizontally scaled out Koha in the world. Off the top of my head, technically you could have a load balancer in front of multiple Koha application servers. You'd want to make sure that the cronjobs are only running on 1 application server though. You also would probably want to use an external Elasticsearch cluster since Zebra would be a bottleneck. In theory, you could use a multi-master MySQL/MariaDB database cluster, but I don't know if anyone has done that (and I'd be concerned about the "eventual consistency" of multi-master setups). If you wanted to a master-replica cluster, you'd need to patch Koha to allow for read-only connections (for things like the Reports module); at the moment, Koha can only use 1 read/write database connection. You'd also need to move your RabbitMQ server to an external server which is problematic with the koha-common package at the moment (but there are ways). (Note: I may be missing another horizontal scaling issue, but these are what come to mind at the moment. You might need to use a network share for some file system resources in /var/koha/* but I can't recall off the top of my head.) It would be much easier to scale vertically. I'd suggest you do some analysis to see where your key pain points are. - Out of the box, Koha only uses 2 Starman/Plack workers, so if it's a case where your Koha is overwhelmed by legitimate traffic, I'd recommend adding more Starman/Plack workers via koha-conf.xml (if you have the CPU and RAM to spare). - If your Koha is slow, you might want to look at your database's I/O performance as well. Using quality SSDs can make a huge difference for database driven applications. (Note also that having MySQL/MariaDB on an external server is a common practice but technically speaking it does add some latency to database transactions which you wouldn't have if you ran MySQL/MariaDB on the same server and used Unix sockets. For very large Koha databases, we've noticed that having an external DB server adds too much latency.) - If you're getting a lot of traffic, you should check to see how much traffic is from bots. You might need to implement something like fail2ban to block bots that put too much load on your system. Typically, I find when Koha is overwhelmed, it's due to bots. (You can experiment with a robots.txt file to help with this but it's not a completely effective solution.) There's lots of things to explore. In the long-term I'd love to make Koha easier to scale horizontally (and ideally deploy as a load-balanced containerized application) but there's work to do and not much demand for it from libraries, so I don't think it's a priority for devs at the moment, unfortunately. Anyway, I hope that helps! 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 -----Original Message----- Message: 10 Date: Wed, 27 Jul 2022 16:28:12 +0100 From: Admire Mutsikiwa To: koha at lists.katipo.co.nz Subject: [Koha] n-Tier deployment of Koha Message-ID: Content-Type: text/plain; charset="UTF-8" My Koha implementation is sometimes overwhelmed as it is a two-tier implementation with a database on one server and a Koha application on another server. I am wondering if it is possible to have a 3 or 4 tier deployment architecture, with for instance, having a load balancer, koha application server and a clustered MySQL/Mariadb implementation. Kind Regards, -- *The information transmitted by this email is intended only for the person or entity to which it is addressed. This email may contain proprietary, business-confidential, and/or privileged material. If you are not the intended recipient of this message, be aware that any use, review, retransmission, distribution, reproduction or any action taken in reliance upon this message is strictly prohibited. If you received this in error, please contact the sender and delete the material from all computers* From keith at thesorbos.com Thu Jul 28 14:38:29 2022 From: keith at thesorbos.com (Keith Sorbo) Date: Wed, 27 Jul 2022 21:38:29 -0500 Subject: [Koha] 500 errors in staff mode and forcing a database update Message-ID: Christina, I have had quite a few of these types of errors while attempting to upgrade from 20.05 to 21.05. What I have been forced to do is to manually add the missing fields to the tables directly. This is far from ideal, but rerunning the koha-update-schema does not seem to perform the missing changes. You need to see from the error message which field is missing and which table it is missing from. It is not too hard if you have direct access to the database and know how to edit the table structure. (I use a free software called HeidiSQL on windows which allows you to tunnel via SSH. Much easier than editing using the mysql command line.) If you have no experience editing the table structure directly, I don't have a good answer for you. Hope that helps Keith From: "Fairlamb, Christina" To: koha at lists.katipo.co.nz Cc: Bcc: Date: Wed, 27 Jul 2022 09:34:17 +0200 Subject: [Koha] 500 errors in staff mode and forcing a database update Hello all, We've had these issues since at least Koha 21.11 but are now on 22.05. Some links on the koha staff page result in a 500 error. Checking the plack-error.log, these are the lines linking to the page I was trying to access: *EDI accounts* DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Unknown column 'me.responses_enabled' in 'field list' at /usr/share/koha/intranet/cgi-bin/admin/edi_accounts.pl line 110 *Library EANs* DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Unknown column 'me.ee_id' in 'field list' at /usr/share/koha/intranet/cgi-bin/admin/edi_ean_accounts.pl line 93 We also still have the Patron relationship problems issue in this bug: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24263, which should have been fixed during past upgrades. (values have been used for guarantee/guarantor relationships, but do not exist in the 'borrowerRelationship') It seems as though our database schema is not updating fully during our latest koha upgrades. I've tried to run the Manual schema upgrade which results in this message only: DEV atomic update /usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/ bug_30899.pl [07:15:11]: Bug 30899 - Check borrower_attribute_types FK constraint (30449 follow-up) Which, according to this bug report: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30899 - is a none issue and means the schema is up to date. Is there a way to force a schema update to go through all updates since a specific koha version? Christina From noorkhalid88 at gmail.com Thu Jul 28 14:56:00 2022 From: noorkhalid88 at gmail.com (Noor Khalid) Date: Thu, 28 Jul 2022 07:56:00 +0500 Subject: [Koha] Sharing library data with others via z30.50 Message-ID: Hi everyone Can I share my books data in koha with others via Z39.50 for copy catalogue. If yes how? From mik at adminkuhn.ch Thu Jul 28 18:10:05 2022 From: mik at adminkuhn.ch (Michael Kuhn) Date: Thu, 28 Jul 2022 08:10:05 +0200 Subject: [Koha] Sharing library data with others via z30.50 In-Reply-To: References: Message-ID: <56be5e01-a4f8-9960-6930-5c2767c58e93@adminkuhn.ch> Hi Noor You wrote: > Can I share my books data in koha with others via Z39.50 for copy > catalogue. > > If yes how? Just see: https://wiki.koha-community.org/wiki/Setting_up_the_Z39.50_and_SRU_Server Fred King has made a short video to show how to do it: https://www.youtube.com/watch?v=j_XOKvq8_TI Hope this helps. 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 at adminkuhn.ch · W www.adminkuhn.ch From kohanews at gmail.com Thu Jul 28 23:00:13 2022 From: kohanews at gmail.com (Koha Newsletter) Date: Thu, 28 Jul 2022 13:00:13 +0200 Subject: [Koha] Koha Community Newsletter: July 2022 Message-ID: The Koha Community Newsletter for July 2022 is here: https://koha-community.org/koha-community-newsletter-july-2022/ 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 From jcoehoorn at york.edu Fri Jul 29 01:53:33 2022 From: jcoehoorn at york.edu (Coehoorn, Joel) Date: Thu, 28 Jul 2022 08:53:33 -0500 Subject: [Koha] n-Tier deployment of Koha In-Reply-To: <081a01d8a21b$e6d6c080$b4844180$@prosentient.com.au> References: <081a01d8a21b$e6d6c080$b4844180$@prosentient.com.au> Message-ID: In my experience, you're usually MUCH better off adding more resources to your single database server. For any given server purchase, there is a cost per performance breaking point where it starts to make more sense to buy two (or more) smaller servers for the same performance vs one large server. It's been a couple years, but the last time I checked the breaking point was something like 64GB RAM and 2 16-core CPUs. You can serve a lot of books to a lot of patrons on a machine like that. Joel Coehoorn Director of Information Technology York University of Nebraska On Wed, Jul 27, 2022 at 7:49 PM wrote: > Hi Admire, > > You'll probably have more luck asking on the dev listserv: > koha-devel at lists.koha-community.org. However, I'll try to offer some > insight here. I'm also CCing in Mengu who has probably the biggest > horizontally scaled out Koha in the world. > > Off the top of my head, technically you could have a load balancer in > front of multiple Koha application servers. You'd want to make sure that > the cronjobs are only running on 1 application server though. You also > would probably want to use an external Elasticsearch cluster since Zebra > would be a bottleneck. In theory, you could use a multi-master > MySQL/MariaDB database cluster, but I don't know if anyone has done that > (and I'd be concerned about the "eventual consistency" of multi-master > setups). If you wanted to a master-replica cluster, you'd need to patch > Koha to allow for read-only connections (for things like the Reports > module); at the moment, Koha can only use 1 read/write database connection. > You'd also need to move your RabbitMQ server to an external server which is > problematic with the koha-common package at the moment (but there are > ways). (Note: I may be missing another horizontal scaling issue, but these > are what come to mind at the moment. You might need to use a network share > for some file system resources in /var/koha/* but I can't recall off the > top of my head.) > > It would be much easier to scale vertically. I'd suggest you do some > analysis to see where your key pain points are. > - Out of the box, Koha only uses 2 Starman/Plack workers, so if it's a > case where your Koha is overwhelmed by legitimate traffic, I'd recommend > adding more Starman/Plack workers via koha-conf.xml (if you have the CPU > and RAM to spare). > - If your Koha is slow, you might want to look at your database's I/O > performance as well. Using quality SSDs can make a huge difference for > database driven applications. (Note also that having MySQL/MariaDB on an > external server is a common practice but technically speaking it does add > some latency to database transactions which you wouldn't have if you ran > MySQL/MariaDB on the same server and used Unix sockets. For very large Koha > databases, we've noticed that having an external DB server adds too much > latency.) > - If you're getting a lot of traffic, you should check to see how much > traffic is from bots. You might need to implement something like fail2ban > to block bots that put too much load on your system. Typically, I find when > Koha is overwhelmed, it's due to bots. (You can experiment with a > robots.txt file to help with this but it's not a completely effective > solution.) > > There's lots of things to explore. > > In the long-term I'd love to make Koha easier to scale horizontally (and > ideally deploy as a load-balanced containerized application) but there's > work to do and not much demand for it from libraries, so I don't think it's > a priority for devs at the moment, unfortunately. > > Anyway, I hope that helps! > > 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 > > -----Original Message----- > Message: 10 > Date: Wed, 27 Jul 2022 16:28:12 +0100 > From: Admire Mutsikiwa > To: koha at lists.katipo.co.nz > Subject: [Koha] n-Tier deployment of Koha > Message-ID: > obHtmiFt0VQ at mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > My Koha implementation is sometimes overwhelmed as it is a two-tier > implementation with a database on one server and a Koha application on > another server. I am wondering if it is possible to have a 3 or 4 tier > deployment architecture, with for instance, having a load balancer, koha > application server and a clustered MySQL/Mariadb implementation. > > Kind Regards, > > -- > > > > *The information transmitted by this email is intended only for the > person or entity to which it is addressed. This email may contain > proprietary, business-confidential, and/or privileged material. If you > are > not the intended recipient of this message, be aware that any use, > review, > retransmission, distribution, reproduction or any action taken > in reliance > upon this message is strictly prohibited. If you received > this in error, > please contact the sender and delete the material from > all computers* > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From keith at thesorbos.com Fri Jul 29 14:05:55 2022 From: keith at thesorbos.com (Keith Sorbo) Date: Thu, 28 Jul 2022 21:05:55 -0500 Subject: [Koha] /server-status?auto Message-ID: My server is getting hit once a second from 127.0.0.1 on the url /server-status?auto What is hitting the server? It is clearly internal. Is it really necessary to hit every second? Is this set from the web 127.0.0.1 - - [29/Jul/2022:01:40:27 +0000] "GET /server-status?auto HTTP/1.1" 200 1052 "-" "-" 127.0.0.1 - - [29/Jul/2022:01:40:28 +0000] "GET /server-status?auto HTTP/1.1" 200 1061 "-" "-" 127.0.0.1 - - [29/Jul/2022:01:40:29 +0000] "GET /server-status?auto HTTP/1.1" 200 1062 "-" "-" 127.0.0.1 - - [29/Jul/2022:01:40:30 +0000] "GET /server-status?auto HTTP/1.1" 200 1062 "-" "-" From victor at tuxayo.net Fri Jul 29 14:11:39 2022 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Fri, 29 Jul 2022 04:11:39 +0200 Subject: [Koha] Are there people interested by patch testing sessions? To help enhancements and bug fixes to be released. Poll to find a date for September. Message-ID: Hello:) Here is the poll: https://date.chapril.org/yTOADLpXgsU4741L You can come and leave at any time during the session. There are a lot of patches (185!) waiting for someone to test and confirm that they do what they advertise. So there need to be more people that test them. Otherwise they wait during month or years! That's one of the easiest way to contribute to Koha. No need for particular skills, just basic Koha usage. We will use a VoIP call + chat tool [1] to speak and eventually screenshare. It's possible to join without sound and only use chat. So if you are at the front desk and there are not much patrons you can still test patches ^^ And also it's easier if you aren't comfortable with oral english. No need to have a local Koha instance. Just with a web browser we can use the sandboxes [2] to have temporary Kohas to test most of patches and do whatever we want without bad consequences. The hours are large to try to accommodate a much people as possible in the Americas 🌎, Africa & Europe 🌍. People from Asia 🌏 or other parts of the world 🌐: tell me if you are interested as well. So we can plan together another session with hours better for your timezone :) Cheers, [1] Libre of course (Jitsi Meet or eventually Big Blue Button) [2] https://wiki.koha-community.org/wiki/Sandboxes -- Victor Grousset/tuxayo From victor at tuxayo.net Fri Jul 29 14:44:48 2022 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Fri, 29 Jul 2022 04:44:48 +0200 Subject: [Koha] To companies selling Koha but rarely contributing or self-hosted libraries: testing enhancements or bug fixes is one of the easiest ways to give back and keep your product relevant in the future Message-ID: <3238f7f3-e1c7-94bf-2e47-3fb662c80b86@tuxayo.net> Hello :) To companies in Asia, like India or Pakistan (Koha seems very popular there :D) or any other country, be it in the Americas, Europe or Africa: If you are making a living out of Koha, it's a good and cheap business decision to test one or two patches from time to time. So you take part in keeping Koha competitive on the long run and secure all the time you invested in learning how to deploy and use it. That will help to ensure your customers will stay satisfied with Koha staying a state of the art ILS. Maybe there are bugfixes or enhancements that you are waiting to be released? There are more than 180 enhancements or bug fixes waiting and that means most of them wait months and some years to be released. It wastes a lot of developer time to keep the proposed patches working when the rest of Koha changes. So there is a big need to have more people test patches to rebalance the Koha development process and remove this big bottleneck. Again, cheap in time, it's doing your part in exchange for the software you got for free ready to be sold/use, and a long run investment to keep it a good sellable product. See my previous email about planning testing sessions: https://lists.katipo.co.nz/pipermail/koha/2022-July/058259.html Don't hesitate to message me if you want to try on your own outside the testing sessions. I will be very happy to help anyone that want to start testing patches from time to time. Cheers, -- Victor Grousset/tuxayo Just some Koha contributor. From victor at tuxayo.net Sat Jul 30 04:12:56 2022 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Fri, 29 Jul 2022 18:12:56 +0200 Subject: [Koha] n-Tier deployment of Koha In-Reply-To: <081a01d8a21b$e6d6c080$b4844180$@prosentient.com.au> References: <081a01d8a21b$e6d6c080$b4844180$@prosentient.com.au> Message-ID: <8aa72ec1-3cac-0fc4-d96f-3c16f9967d62@tuxayo.net> Hi :) On 22-07-28 02:49, dcook at prosentient.com.au wrote: > Off the top of my head, technically you could have a load balancer in front of multiple Koha application servers. You'd want to make sure that the cronjobs are only running on 1 application server though. You also would probably want to use an external Elasticsearch cluster since Zebra would be a bottleneck. In theory, you could use a multi-master MySQL/MariaDB database cluster, but I don't know if anyone has done that (and I'd be concerned about the "eventual consistency" of multi-master setups). If you wanted to a master-replica cluster, you'd need to patch Koha to allow for read-only connections (for things like the Reports module); at the moment, Koha can only use 1 read/write database connection. Are there MariaDB front end/load balancers than could route the read queries to one of the multiple read only replicas? And the write queries to the main server. That would allow to not change apps. So in the end the only non-horizontally-scalable thing would be DB writes? (unless multi-master eventual consistency works) > In the long-term I'd love to make Koha easier to scale horizontally (and ideally deploy as a load-balanced containerized application) but there's work to do and not much demand for it from libraries, so I don't think it's a priority for devs at the moment, unfortunately. Ideally the largest Koha installations would have contributed back/funded scalability improvement. Maybe they did, I don't know the history. So it's a matter of priority of upstreaming changes while having already a lot to deal with. That might show the largest installations are underfunded and have no margin for upstreaming :( Cheers, -- Victor Grousset/tuxayo From mtj at kohaaloha.com Sat Jul 30 15:54:54 2022 From: mtj at kohaaloha.com (Mason James) Date: Sat, 30 Jul 2022 15:54:54 +1200 Subject: [Koha] /server-status?auto In-Reply-To: References: Message-ID: <351606ca-6bf1-af46-601b-1a65285afac7@kohaaloha.com> On 29/07/22 2:05 pm, Keith Sorbo wrote: > My server is getting hit once a second from 127.0.0.1 on the url > /server-status?auto > > What is hitting the server? It is clearly internal. hi Keith i'm not sure what is hitting your server, but it is not koha you possibly have a local monitoring tool that's causing the requests, and is not identifying itself From victor at tuxayo.net Sat Jul 30 16:06:32 2022 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Sat, 30 Jul 2022 06:06:32 +0200 Subject: [Koha] To companies selling Koha but rarely contributing or self-hosted libraries: testing enhancements or bug fixes is one of the easiest ways to give back and keep your product relevant in the future In-Reply-To: <3238f7f3-e1c7-94bf-2e47-3fb662c80b86@tuxayo.net> References: <3238f7f3-e1c7-94bf-2e47-3fb662c80b86@tuxayo.net> Message-ID: Also, for the companies: trying to get the librarians from your customers to test patches would be super great! Like forwarding the email about planning testing sessions: https://lists.katipo.co.nz/pipermail/koha/2022-July/058259.html They can choose to test what they are interested in so they get it in the next version. Isn't that cool? :D Cheers, -- Victor Grousset/tuxayo From indradg at gmail.com Sat Jul 30 17:58:38 2022 From: indradg at gmail.com (Indranil Das Gupta) Date: Sat, 30 Jul 2022 11:28:38 +0530 Subject: [Koha] /server-status?auto In-Reply-To: <351606ca-6bf1-af46-601b-1a65285afac7@kohaaloha.com> References: <351606ca-6bf1-af46-601b-1a65285afac7@kohaaloha.com> Message-ID: Hi Mason, Sounds like he prolly has mod_status enabled on his Apache Cheers Indranil On Sat, 30 Jul, 2022, 9:25 am Mason James, wrote: > On 29/07/22 2:05 pm, Keith Sorbo wrote: > > My server is getting hit once a second from 127.0.0.1 on the url > > /server-status?auto > > > > What is hitting the server? It is clearly internal. > > hi Keith > > i'm not sure what is hitting your server, but it is not koha > > you possibly have a local monitoring tool that's causing the requests, and > is not identifying itself > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From loveandmarigold at gmail.com Sun Jul 31 15:57:48 2022 From: loveandmarigold at gmail.com (Sanjay Uchcharia) Date: Sun, 31 Jul 2022 09:27:48 +0530 Subject: [Koha] Set one particular library in OPAC drop down menu Message-ID: I have so many libraries in Koha and I have already moved some books to their related library Now, I want to set only one particular library as default library in OPAC (in drop down menu for libraries) and I want search result must be shown from this particular library as well. . From katrin.fischer.83 at web.de Sun Jul 31 22:22:50 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sun, 31 Jul 2022 12:22:50 +0200 Subject: [Koha] Patron search not working after upgrade to version 22 In-Reply-To: References: <72c4b0e3-29af-f2a6-6191-85108d126eb8@web.de> Message-ID: Hi Kyle, did you solve you error yet? If not, you could check if you see any error with the developer tools in your browser. Sometimes bad data can break the patron search and the error might give a clue. Hope this helps, Katrin On 26.07.22 01:55, Kyle Noakes wrote: > Hi Katrin, > > I am able to see all libraries under administration. I did put that in > my original email, but I was not clear in my wording. > > On Mon, Jul 25, 2022, 4:29 PM Katrin Fischer > wrote: > > Hi Kyle, > > did you do the check with the Administration > Libraries table I > suggested? If the table doesn't show your configured libraries, > it's pointing to the API not working correctly. > > I can imagine because cardnumber gives only one result, this > bypasses the API and goes to the account directly. > > Hope this helps, > > Katrin > > On 25.07.22 18:03, Kyle Noakes wrote: >> Thanks for those ideas Evan. I did already find those not up to >> date before posting, yet still deal with the problem. >> >> I did find that we are able to search for patrons using the card >> number instead of the last name. I thought I was going to be fine >> just rolling back to my old server version and database since I >> am at a school during the summer, but then noticed in the logs >> that my staff have been checking things out using ID so I am >> unable to just go back to that old version as easily as I thought. >> >> Maybe someone will have an idea of why I can search by card >> number, but not last name. >> >> Thank you, >> >> Kyle Noakes >> Manager of Information Systems >> East Grand Rapids Public Schools >> 616-974-0157 >> >> >> On Mon, Jul 11, 2022 at 3:05 PM Evan Stewart >> wrote: >> >> Correction to my apt install command in the previous reply. >> >> To fix, I upgraded "libmojolicious-perl" and " >> libmojolicious-plugin-openapi-perl" upgraded with it. >> >> I ran:  sudo apt install libmojolicious-perl >> >> -Evan >> >> On Sun, Jul 10, 2022 at 9:48 PM Evan Stewart >> >> wrote: >> >> > Hi, >> > >> > I found the solution on Raspberry Pi OS (based on Debian >> 10). I noticed >> > that after running apt upgrade two packages were held back: >> > >> >    - libmojolicious-perl >> >    - libmojolicious-plugin-openapi-perl >> > >> > I didn't notice them before and probably wouldn't have >> noticed them had I >> > not learned about the REST API and then read a little about >> it in the Koha >> > documentation (thanks Katrin!). Once I saw the REST API >> references the >> > OpenAPI format I figured these packages were the culprit.  >> Also, I >> > confirmed in my About Koha settings page that the Open API >> module was >> > flagged as "not installed" after I upgraded to Koha 22. >> > >> > The solution for me was to install the two packages with >> apt.  Not sure >> > why they were held back using "apt upgrade", but running >> "sudo apt install >> > libmojolicious-plugin-openapi-perl" called in all other >> dependent packages; >> > including the upgrade for libmojolicious-perl and nine >> other new packages. >> > >> > I rebooted my Raspberry Pi, logged into Koha and all is >> good.  The Open >> > API module is listed as "Installed" in the About Koha >> settings page and the >> > patron search and library listing is working. >> > >> > Kyle, hopefully this helps your machine. >> > >> > -Evan Stewart >> > >> > >> > >> > On Fri, Jul 8, 2022 at 12:37 PM Katrin Fischer >> >> > wrote: >> > >> >> Hi Kyle, >> >> >> >> the API settings in administration are not related to >> Koha's internal >> >> use of the API, so if you are not using the API >> exeternally, you can >> >> turn these off again. >> >> >> >> Did you test if the list of libraries is visible for you in >> >> administration? If the list doesn't show, your problem is >> probably not >> >> the bug Tomas mentioned. >> >> >> >> What does your /etc/apt/sources.list.d/koha.list entry >> look like? >> >> >> >> Hope this helps, >> >> >> >> Katrin >> >> >> >> >> >> On 08.07.22 17:15, Kyle Noakes wrote: >> >> > I am having the same problem as Evan on Debian 10 >> (Buster) after the >> >> > upgrade to 22.05.00 that has continued to 22.05.02. I >> did attempt to add >> >> > Tomas's patch to my pagination file manually, but it did >> not work, >> >> > although admittedly I have rarely needed to hand add any >> patch so I >> >> could >> >> > have done something wrong. I was also unable to find any >> errors in the >> >> logs >> >> > that mention long search strings before I tried the >> pagination fix >> >> anyway. >> >> > I am unable to search for any patron string, not just >> long ones. I can't >> >> > even click on a letter in the alphabet to search and >> receive any >> >> results. >> >> > >> >> > I did enable the API in administration. I can also see >> my branches in >> >> > libraries. >> >> > >> >> > Thank you, >> >> > >> >> > Kyle Noakes >> >> > Manager of Information Systems >> >> > East Grand Rapids Public Schools >> >> > 616-974-0157 >> >> > >> >> > >> >> > On Wed, Jul 6, 2022 at 1:20 PM Tomas Cohen Arazi >> >> >> > wrote: >> >> > >> >> >> This is certainly caused by a Koha bug I'm about to >> submit a patch for >> >> [1]. >> >> >> The 22.05 release maintainer is AFK this week so he >> cannot release a >> >> new >> >> >> version yet. >> >> >> >> >> >> Best regards. >> >> >> >> >> >> [1] >> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31104 >> >> >> >> >> >> El mié, 6 jul 2022 a las 13:43, Evan Stewart (< >> >> evanstewart406 at gmail.com>) >> >> >> escribió: >> >> >> >> >> >>> Hello, >> >> >>> >> >> >>> I recently upgraded my Koka 21 to 22.  Everything >> seemed to be working >> >> >> fine >> >> >>> until I tried searching for patrons.  Using the >> intranet portal to >> >> search >> >> >>> for patrons provides zero results.  I see my patrons >> in the borrowers >> >> >>> table, but the GUI won't display them.  It's like the >> search function >> >> >> sees >> >> >>> no results. >> >> >>> >> >> >>> I upgraded to version 22.05.02, but the same problem >> still occurs. >> >> >>> >> >> >>> I'm using Raspberry Pi OS (Buster). >> >> >>> >> >> >>> I can add a new patron, but even the new patron does >> not show in the >> >> >> search >> >> >>> results. >> >> >>> >> >> >>> Is there a way to refresh the indexer that handles >> patron searching? >> >> Any >> >> >>> other suggestions? >> >> >>> >> >> >>> -Evan Stewart >> >> >>> Africa's Hope, USA >> >> >>> _______________________________________________ >> >> >>> >> >> >>> Koha mailing list http://koha-community.org >> >> >>> Koha at lists.katipo.co.nz >> >> >>> Unsubscribe: >> https://lists.katipo.co.nz/mailman/listinfo/koha >> >> >>> >> >> >> >> >> >> -- >> >> >> Tomás Cohen Arazi >> >> >> Theke Solutions (http://theke.io) >> >> >> ✆ +54 9351 3513384 >> >> >> GPG: B2F3C15F >> >> >> _______________________________________________ >> >> >> >> >> >> Koha mailing list http://koha-community.org >> >> >> Koha at lists.katipo.co.nz >> >> >> Unsubscribe: >> https://lists.katipo.co.nz/mailman/listinfo/koha >> >> >> >> >> > _______________________________________________ >> >> > >> >> > Koha mailing list http://koha-community.org >> >> > Koha at lists.katipo.co.nz >> >> > Unsubscribe: >> https://lists.katipo.co.nz/mailman/listinfo/koha >> >> _______________________________________________ >> >> >> >> Koha mailing list http://koha-community.org >> >> Koha at lists.katipo.co.nz >> >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> >> >> > >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> From katrin.fischer.83 at web.de Sun Jul 31 22:33:56 2022 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sun, 31 Jul 2022 12:33:56 +0200 Subject: [Koha] Set one particular library in OPAC drop down menu In-Reply-To: References: Message-ID: <856b7a18-e408-f63e-da99-a311dfaccbc0@web.de> Hi Sanjay, maybe have a look at the OpacAddMastheadLibraryPulldown and SearchMyLibraryFirst system preferences. With some jQuery in OpacUserJs you could also pre-select a specific library in the pull-downs. Something like this could maybe be modified/reused: https://wiki.koha-community.org/wiki/JQuery_Library#Set_all_library_pulldowns_to_the_logged_in_library Hope this helps, Katrin |||| || || |||| On 31.07.22 05:57, Sanjay Uchcharia wrote: > I have so many libraries in Koha and I have already moved some books to > their related library > > Now, I want to set only one particular library as default library in OPAC > (in drop down menu for libraries) and I want search result must be shown > from this particular library as well. > > > > . > _______________________________________________ > > Koha mailing listhttp://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe:https://lists.katipo.co.nz/mailman/listinfo/koha