Test navigator bar staff client

From vbovictor at gmail.com Wed Sep 1 04:42:24 2021 From: vbovictor at gmail.com (Victor Barroso Oliveira) Date: Tue, 31 Aug 2021 13:42:24 -0300 Subject: [Koha] How can I temporarily disable the visibility of an OPAC Library? Message-ID: Good afternoon, I have a Koha installation with multiple libraries. How can I temporarily disable the visibility of an OPAC Library? From indradg at gmail.com Wed Sep 1 04:50:11 2021 From: indradg at gmail.com (Indranil Das Gupta) Date: Tue, 31 Aug 2021 22:20:11 +0530 Subject: [Koha] How can I temporarily disable the visibility of an OPAC Library? In-Reply-To: References: Message-ID: Hi Victor, Easy way: Setting OpacPublic system preference. That will set the OPAC as password protected. More technically complex way: uncomment the disable segment in the shared opac apache config of your Koha instance. Hope this helps Indranil Das Gupta L2C2 Technologies On Tue, 31 Aug, 2021, 10:13 pm Victor Barroso Oliveira, wrote: > Good afternoon, > I have a Koha installation with multiple libraries. > How can I temporarily disable the visibility of an OPAC Library? > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From indradg at gmail.com Wed Sep 1 05:15:09 2021 From: indradg at gmail.com (Indranil Das Gupta) Date: Tue, 31 Aug 2021 22:45:09 +0530 Subject: [Koha] How can I temporarily disable the visibility of an OPAC Library? In-Reply-To: References:

Message-ID: Hi, On Tue, 31 Aug, 2021, 10:34 pm Victor Barroso Oliveira, wrote: > I don't want to enable login and password to access opac. > I just want to temporarily disable access to a library in OPAC. > In that case: https://koha-community.org/manual/18.11/en/html/systempreferences.html#opacmaintenance Regards, Indranil Das Gupta L2C2 Technologies. > > From eb at efdss.org Wed Sep 1 05:45:41 2021 From: eb at efdss.org (Elaine Bradtke) Date: Tue, 31 Aug 2021 10:45:41 -0700 Subject: [Koha] Display issue: IntranetNav in 21.05.02.003 In-Reply-To: References: Message-ID: Here's what we have at the moment: Test navigator bar staff client Manual | OPAC | New Biblio | Authorities | Main site | Classification Scheme |
It was longer - I cut out the part that said* THIS IS THE TEST SITE* With that there, it pushed the More menu right off the edge of the window. It seems to me the IntranetNav window is a tad too small, and or it doesn't adapt to the size of the window. Elaine VWML On Tue, Aug 31, 2021 at 1:41 AM Jonathan Druart < jonathan.druart at bugs.koha-community.org> wrote: > Hi Elaine, > > How many links do you have? Can you share your IntranetNav content? > I do see the overlap described on 23840 but the "More" moving all around. > It appears on a separate line if the line is too long for the window, > but it's the best we can do, in my opinion. > > Regards, > Jonathan > > > Le lun. 30 août 2021 à 20:35, Elaine Bradtke a écrit : > > > > Our test site is on 21.05.02.003 . Our production site is 21.05.00 The > > problem is in 21.05.02.003 > > We have some extra links in the IntranetNav There seems to be a limit to > > how much you can put to the left of the More menu. > > Once exceeded, the More menu ends up on the next line, but in an odd > place. > > In this case on the very far left of the page: > > > https://drive.google.com/file/d/1AWF36xmnYSkvsxT-n7a9a4N6W2kGPFNn/view?usp=sharing > > When the More menu is clicked, it actually falls off the edge of the > page - > > there's no way to bring it into view. > > > https://drive.google.com/file/d/19fb6nR21jWKJG1-4WObawP4vBrCGoOX-/view?usp=sharing > > By cutting down on the number of characters that display, I managed to > > bring it into view, More is still on the next line, despite the fact that > > there is plenty of room for it above. > > Weirdly (and I struggle with left and right, so I never thought about it > > before), the production site running the older version puts our added > links > > to the RIGHT of the More menu, but on the same line. > > > > I'm not sure if it's related to bug 23840 > > or if > > it's a new problem. > > > > 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 jcoehoorn at york.edu Wed Sep 1 05:54:11 2021 From: jcoehoorn at york.edu (Coehoorn, Joel) Date: Tue, 31 Aug 2021 12:54:11 -0500 Subject: [Koha] How can I temporarily disable the visibility of an OPAC Library? In-Reply-To: References:

Message-ID: That's ALL libraries. Sounds like he just wants to hide one. Joel Coehoorn Director of Information Technology York College of Nebraska On Tue, Aug 31, 2021 at 12:15 PM Indranil Das Gupta wrote: > Hi, > > On Tue, 31 Aug, 2021, 10:34 pm Victor Barroso Oliveira, < > vbovictor at gmail.com> > wrote: > > > I don't want to enable login and password to access opac. > > I just want to temporarily disable access to a library in OPAC. > > > > In that case: > > > https://koha-community.org/manual/18.11/en/html/systempreferences.html#opacmaintenance > > Regards, > Indranil Das Gupta > L2C2 Technologies. > > > > > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From lucas at bywatersolutions.com Wed Sep 1 06:07:12 2021 From: lucas at bywatersolutions.com (Lucas Gass) Date: Tue, 31 Aug 2021 12:07:12 -0600 Subject: [Koha] Display issue: IntranetNav in 21.05.02.003 In-Reply-To: References: Message-ID: Hi Elaine, In the IntranetNav system pref the , , and tags are all unnecessary. It is also best if you wrap your links in HTML

elements. I would try replacing your current HTML with this: http://paste.koha-community.org/2551 Cheers, On Tue, Aug 31, 2021 at 11:46 AM Elaine Bradtke wrote: > Here's what we have at the moment: > > > > Test navigator bar staff client > > > href="https://sites.google.com/a/efdss.org/library-staff-koha-manual/ > ">Manual > | OPAC > | href=" > http://kohaadmin.randomnotes.org/cgi-bin/koha/cataloguing/addbooks.pl > ">New > Biblio > | href=" > > http://kohaadmin.randomnotes.org/cgi-bin/koha/authorities/authorities-home.pl > ">Authorities > | Main site | > href=" > > https://sites.google.com/a/efdss.org/library-staff-koha-manual/home/cataloguing/classification-scheme > ">Classification > Scheme > |
> > > > It was longer - I cut out the part that said* THIS IS THE TEST SITE* > With that there, it pushed the More menu right off the edge of the window. > It seems to me the IntranetNav window is a tad too small, and or it doesn't > adapt to the size of the window. > Elaine > VWML > > > > On Tue, Aug 31, 2021 at 1:41 AM Jonathan Druart < > jonathan.druart at bugs.koha-community.org> wrote: > > > Hi Elaine, > > > > How many links do you have? Can you share your IntranetNav content? > > I do see the overlap described on 23840 but the "More" moving all around. > > It appears on a separate line if the line is too long for the window, > > but it's the best we can do, in my opinion. > > > > Regards, > > Jonathan > > > > > > Le lun. 30 août 2021 à 20:35, Elaine Bradtke a écrit : > > > > > > Our test site is on 21.05.02.003 . Our production site is 21.05.00 > The > > > problem is in 21.05.02.003 > > > We have some extra links in the IntranetNav There seems to be a limit > to > > > how much you can put to the left of the More menu. > > > Once exceeded, the More menu ends up on the next line, but in an odd > > place. > > > In this case on the very far left of the page: > > > > > > https://drive.google.com/file/d/1AWF36xmnYSkvsxT-n7a9a4N6W2kGPFNn/view?usp=sharing > > > When the More menu is clicked, it actually falls off the edge of the > > page - > > > there's no way to bring it into view. > > > > > > https://drive.google.com/file/d/19fb6nR21jWKJG1-4WObawP4vBrCGoOX-/view?usp=sharing > > > By cutting down on the number of characters that display, I managed to > > > bring it into view, More is still on the next line, despite the fact > that > > > there is plenty of room for it above. > > > Weirdly (and I struggle with left and right, so I never thought about > it > > > before), the production site running the older version puts our added > > links > > > to the RIGHT of the More menu, but on the same line. > > > > > > I'm not sure if it's related to bug 23840 > > > or > if > > > it's a new problem. > > > > > > 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 > > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > -- Lucas Gass Web Developer From lennon at kohasupport.com Wed Sep 1 23:24:55 2021 From: lennon at kohasupport.com (Lennon Mazonde) Date: Wed, 1 Sep 2021 13:24:55 +0200 Subject: [Koha] How can I temporarily disable the visibility of an OPAC Library? In-Reply-To: References: Message-ID: <38cd9c2d-efaf-4365-1cc5-dade8242d927@kohasupport.com> Hi Victor, Can you clarify how your installation is setup? Do you have multiple Koha instances running on one server or one Koha instance with multiple branches? If it's the former, then you can comment out (put a # in front of every line) the OPAC VirtualHosts section in your config file and restart your Apache web server (or whatever webserver you're running). This will stop Apache from serving requests to your OPAC. When you are ready to enable your OPAC again, simply uncomment the VirtualHosts and restart your web server. Hope this helps! On 8/31/21 6:42 PM, Victor Barroso Oliveira wrote: > Good afternoon, > I have a Koha installation with multiple libraries. > How can I temporarily disable the visibility of an OPAC Library? > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha -- Lennon Mazonde www.kohasupport.com lennon at kohasupport.com WhatsApp @ (+1) 717.489.0195 From martin.renvoize at ptfs-europe.com Thu Sep 2 02:30:48 2021 From: martin.renvoize at ptfs-europe.com (Renvoize, Martin) Date: Wed, 1 Sep 2021 15:30:48 +0100 Subject: [Koha] Monthly Community Meeting Message-ID: Hi all, We had our monthly general meeting today, as usual, hosted on IRC. Attendance has been very low for a while now and we mooted the idea of dropping it from our schedule and instead just having perhaps two meetings a year, one for Kohacon votes and a second for a broader annual general meeting should anyone want to raise any points in that formal setting. The next meeting is scheduled for 13th October 2021 at 1400 UTC where we will vote on the new reduced format. We're open to new idea's at any time and I'd be happy to try a video meeting or something if people would prefer. But at this point, we're not discussing much and I don't know if we're missing peoples views or people just don't have many or they have other ways of communicating with the community at large. Hope everyone is well, *Martin Renvoize, MPhys (Hons)* Head of Development and Community Engagement *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize at ptfs-europe.com www.ptfs-europe.com *Sign up for our newsletters here or by scanning the QR code* Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info at ptfs-europe.com From Heather_Hernandez at nps.gov Thu Sep 2 03:44:45 2021 From: Heather_Hernandez at nps.gov (Hernandez, Heather H) Date: Wed, 1 Sep 2021 15:44:45 +0000 Subject: [Koha] Two CatSIGs this month! In-Reply-To: References: Message-ID: Hi, all! The next Koha-US Cataloging Special Interest Group ("Cat SIG") meeting is Thursday, September 2, 2021, at 8 PT, 9 MT, 10 CT, 11 ET, 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. Actual catalogers do attend, as well as the cataloging curious and those who have had cataloging thrust upon them! And this month there's a bonus CatSIG at the Koha-US Conference that is also free to attend to for all on Thursday, September 23rd at 1:00pm/13:00 PT, 2:00pm/14:00 MT, 3:00pm/15:00 CT, 4:00pm/16:00 ET. Information on joining us on September 2 is on the Koha-US calendar: https://koha-us.org/calendar/ And info on joining on September 23rd will be on the Conference website (and why not register for the conference? it's free for remote attendees!) https://koha-us.org/conference2021/ 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 San Francisco Maritime National Historical Park Research Center 2 Marina Blvd., Bldg. E, 3rd floor, San Francisco, CA 94123-1284 415-561-7032, heather_hernandez at nps.gov Library catalog: http://keys.bywatersolutions.com/ From eb at efdss.org Thu Sep 2 05:59:09 2021 From: eb at efdss.org (Elaine Bradtke) Date: Wed, 1 Sep 2021 10:59:09 -0700 Subject: [Koha] Display issue: IntranetNav in 21.05.02.003 In-Reply-To: References: Message-ID: Thanks! That works brilliantly. My HTML skills date from the last century. . . .and I think I forgot most of what I knew. Elaine VWML On Tue, Aug 31, 2021 at 11:07 AM Lucas Gass wrote: > Hi Elaine, > > In the IntranetNav system pref the , , and tags are all > unnecessary. > It is also best if you wrap your links in HTML

elements. I would try > replacing your current HTML with this: > > http://paste.koha-community.org/2551 > > Cheers, > > On Tue, Aug 31, 2021 at 11:46 AM Elaine Bradtke wrote: > >> Here's what we have at the moment: >> >> >> >> Test navigator bar staff client >> >> >> > href="https://sites.google.com/a/efdss.org/library-staff-koha-manual/ >> ">Manual >> | OPAC >> | > href=" >> http://kohaadmin.randomnotes.org/cgi-bin/koha/cataloguing/addbooks.pl >> ">New >> Biblio >> | > href=" >> >> http://kohaadmin.randomnotes.org/cgi-bin/koha/authorities/authorities-home.pl >> ">Authorities >> | Main site | >> > href=" >> >> https://sites.google.com/a/efdss.org/library-staff-koha-manual/home/cataloguing/classification-scheme >> ">Classification >> Scheme >> |
>> >> >> >> It was longer - I cut out the part that said* THIS IS THE TEST SITE* >> With that there, it pushed the More menu right off the edge of the window. >> It seems to me the IntranetNav window is a tad too small, and or it >> doesn't >> adapt to the size of the window. >> Elaine >> VWML >> >> >> >> On Tue, Aug 31, 2021 at 1:41 AM Jonathan Druart < >> jonathan.druart at bugs.koha-community.org> wrote: >> >> > Hi Elaine, >> > >> > How many links do you have? Can you share your IntranetNav content? >> > I do see the overlap described on 23840 but the "More" moving all >> around. >> > It appears on a separate line if the line is too long for the window, >> > but it's the best we can do, in my opinion. >> > >> > Regards, >> > Jonathan >> > >> > >> > Le lun. 30 août 2021 à 20:35, Elaine Bradtke a écrit : >> > > >> > > Our test site is on 21.05.02.003 . Our production site is 21.05.00 >> The >> > > problem is in 21.05.02.003 >> > > We have some extra links in the IntranetNav There seems to be a limit >> to >> > > how much you can put to the left of the More menu. >> > > Once exceeded, the More menu ends up on the next line, but in an odd >> > place. >> > > In this case on the very far left of the page: >> > > >> > >> https://drive.google.com/file/d/1AWF36xmnYSkvsxT-n7a9a4N6W2kGPFNn/view?usp=sharing >> > > When the More menu is clicked, it actually falls off the edge of the >> > page - >> > > there's no way to bring it into view. >> > > >> > >> https://drive.google.com/file/d/19fb6nR21jWKJG1-4WObawP4vBrCGoOX-/view?usp=sharing >> > > By cutting down on the number of characters that display, I managed to >> > > bring it into view, More is still on the next line, despite the fact >> that >> > > there is plenty of room for it above. >> > > Weirdly (and I struggle with left and right, so I never thought about >> it >> > > before), the production site running the older version puts our added >> > links >> > > to the RIGHT of the More menu, but on the same line. >> > > >> > > I'm not sure if it's related to bug 23840 >> > > or >> if >> > > it's a new problem. >> > > >> > > 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 >> > >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> > > > -- > Lucas Gass > Web Developer > > From secretary at koha-us.org Thu Sep 2 06:05:39 2021 From: secretary at koha-us.org (Jason Robb) Date: Wed, 1 Sep 2021 13:05:39 -0500 Subject: [Koha] koha-US September 2021 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/. *Meetings* Board Meeting - Wednesday, September 8 @ 8:30a PT / 11:30a ET / 15:30 UTC - Meeting Link - https://us02web.zoom.us/j/293750042?pwd=SGQzS2pmU3prNFhYRHNaeTFhOHN4QT09 - Agenda - https://docs.google.com/document/d/1UKEg2VjrHP-WV3xnLBP4ReNynqOeQWZ8_YgYjomQq7E/edit?usp=sharing General Meeting - Wednesday, September 22 @ 8:45a PT / 11:45a ET / 15:45 UTC *koha-US Annual Conference* Tuesday, September 21 - Friday, September 24 This year's conference will be held in-person and live streamed to YouTube -- register and view the full schedule here: https://koha-us.org/conference2021/ *Special Interest Groups* *Note: Most groups will be meeting during the conference this month* Cataloging - Thursday, September 2 @ 8:00a PT / 11:00a ET / 15:00 UTC Acquisitions - Thursday, September 23 @ 8:00a PT / 11:00p ET / 15:00 UTC Circulation - Thursday, September 23 @ 12:00p PT / 3:00p ET / 19:00 UTC Cataloging - Thursday, September 23 @ 1:00p PT / 4:00p ET / 20:00 UTC Consortia - Friday, September 24 @ 12:00p PT / 3:00p ET / 19:00 UTC Sys Admin + Web Development - September 24 @ 1:00p PT / 4:00p ET / 20: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 Jason Robb koha-US Secretary secretary at koha-us.org From amutsikiwa at uzlib.uz.ac.zw Thu Sep 2 10:42:18 2021 From: amutsikiwa at uzlib.uz.ac.zw (Admire Mutsikiwa) Date: Thu, 2 Sep 2021 00:42:18 +0200 Subject: [Koha] Error upgrading Koha from version 18.06 to Koha 21.05 Message-ID: Good day. I was trying to upgrade Koha from version 18.06 to 21.05 on Ubuntu 20.05. I installed Ubuntu 20.04 and then installed Koha 20.05. I then used the Koha 18.06 database dump to restore the Koha database after dropping the Koha 20.05 database. On trying to do the database schema upgrade, I am getting the following error: The following error occurred while importing the database structure: DBD::mysql::st execute failed: Referencing column 'message_transport_type' and referenced column 'message_transport_type' in foreign key constraint 'borrower_message_transport_preferences_ibfk_2' are incompatible. at /usr/share/perl5/DBIx/RunSQL.pm line 279, <$args{...}> line 1. Something went wrong loading file /usr/share/koha/intranet/cgi-bin/installer/data/mysql/kohastructure.sql ([SQL ERROR]: CREATE TABLE `borrower_message_transport_preferences` ( `borrower_message_preference_id` int(11) NOT NULL DEFAULT 0, `message_transport_type` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '0', PRIMARY KEY (`borrower_message_preference_id`,`message_transport_type`), KEY `message_transport_type` (`message_transport_type`), CONSTRAINT `borrower_message_transport_preferences_ibfk_1` FOREIGN KEY (`borrower_message_preference_id`) REFERENCES `borrower_message_preferences` (`borrower_message_preference_id`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `borrower_message_transport_preferences_ibfk_2` FOREIGN KEY (`message_transport_type`) REFERENCES `message_transport_types` (`message_transport_type`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci ) at /usr/share/koha/lib/C4/Installer.pm line 580. Any pointers will be greatly appreciated. Kind Regards, From rooy.de.m at gmail.com Thu Sep 2 18:24:14 2021 From: rooy.de.m at gmail.com (Marcel de Rooy) Date: Thu, 2 Sep 2021 08:24:14 +0200 Subject: [Koha] [Koha-devel] Monthly Community Meeting In-Reply-To: References: Message-ID: Semi annual voting on new roles too ? Op wo 1 sep. 2021 om 16:31 schreef Renvoize, Martin < martin.renvoize at ptfs-europe.com>: > Hi all, > > We had our monthly general meeting today, as usual, hosted on IRC. > Attendance has been very low for a while now and we mooted the idea of > dropping it from our schedule and instead just having perhaps two meetings > a year, one for Kohacon votes and a second for a broader annual general > meeting should anyone want to raise any points in that formal setting. > > The next meeting is scheduled for 13th October 2021 at 1400 UTC where we > will vote on the new reduced format. > > We're open to new idea's at any time and I'd be happy to try a video > meeting or something if people would prefer. But at this point, we're not > discussing much and I don't know if we're missing peoples views or people > just don't have many or they have other ways of communicating with the > community at large. > > Hope everyone is well, > > *Martin Renvoize, MPhys (Hons)* > > > > Head of Development and Community Engagement > > > > *Phone:* +44 (0) 1483 378728 > > *Mobile:* +44 (0) 7725 985 636 > > *Email:* martin.renvoize at ptfs-europe.com > > www.ptfs-europe.com > > > *Sign up for our newsletters here or by > scanning the QR code* > > > > Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 > > The information contained in this email message may be privileged, > confidential and protected from disclosure. If you are not the intended > recipient, any dissemination, distribution or copying is strictly > prohibited. If you think that you have received this email message in > error, please email the sender at info at ptfs-europe.com > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ > git : https://git.koha-community.org/ > bugs : https://bugs.koha-community.org/ > From jonathan.druart at bugs.koha-community.org Thu Sep 2 18:45:13 2021 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Thu, 2 Sep 2021 08:45:13 +0200 Subject: [Koha] Error upgrading Koha from version 18.06 to Koha 21.05 In-Reply-To: References: Message-ID: Hello Admire, 18.06 is a development version, did you mean 18.05? Do you have a line number from updatedatabase.pl? Or the version number where it explodes? At first glance I'd say it tried to run a very old version during the upgrade, which would mean you should restart memcached, apache2 then koha-common. And try again. Regards, Jonathan Le jeu. 2 sept. 2021 à 00:42, Admire Mutsikiwa a écrit : > > Good day. I was trying to upgrade Koha from version 18.06 to 21.05 on > Ubuntu 20.05. I installed Ubuntu 20.04 and then installed Koha 20.05. I > then used the Koha 18.06 database dump to restore the Koha database after > dropping the Koha 20.05 database. On trying to do the database schema > upgrade, I am getting the following error: > > > The following error occurred while importing the database structure: > > DBD::mysql::st execute failed: Referencing column 'message_transport_type' > and referenced column 'message_transport_type' in foreign key constraint > 'borrower_message_transport_preferences_ibfk_2' are incompatible. at > /usr/share/perl5/DBIx/RunSQL.pm line 279, <$args{...}> line 1. Something > went wrong loading file > /usr/share/koha/intranet/cgi-bin/installer/data/mysql/kohastructure.sql > ([SQL ERROR]: CREATE TABLE `borrower_message_transport_preferences` ( > `borrower_message_preference_id` int(11) NOT NULL DEFAULT 0, > `message_transport_type` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL > DEFAULT '0', PRIMARY KEY > (`borrower_message_preference_id`,`message_transport_type`), KEY > `message_transport_type` (`message_transport_type`), CONSTRAINT > `borrower_message_transport_preferences_ibfk_1` FOREIGN KEY > (`borrower_message_preference_id`) REFERENCES > `borrower_message_preferences` (`borrower_message_preference_id`) ON DELETE > CASCADE ON UPDATE CASCADE, CONSTRAINT > `borrower_message_transport_preferences_ibfk_2` FOREIGN KEY > (`message_transport_type`) REFERENCES `message_transport_types` > (`message_transport_type`) ON DELETE CASCADE ON UPDATE CASCADE ) > ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci ) at > /usr/share/koha/lib/C4/Installer.pm line 580. > > > Any pointers will be greatly appreciated. > > > Kind Regards, > _______________________________________________ > > 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 Fri Sep 3 07:17:40 2021 From: vbovictor at gmail.com (Victor Barroso Oliveira) Date: Thu, 2 Sep 2021 16:17:40 -0300 Subject: [Koha] List of all cataloged items and the users who inserted the item. Message-ID: Good afternoon, What would be the sql code to generate a report with a list of all cataloged items and the users who inserted the item. From vbovictor at gmail.com Fri Sep 3 23:28:05 2021 From: vbovictor at gmail.com (Victor Barroso Oliveira) Date: Fri, 3 Sep 2021 08:28:05 -0300 Subject: [Koha] report to show the listing of titles entered by each Librarian Message-ID: Good morning, This report allows you to view the number of items entered for each Librarian. SELECT concat(p.firstname, ' ', p.surname) AS Operador, concat(a.action, ' ', a.info) AS Ação, count(a.timestamp) AS Quantidade FROM action_logs a LEFT JOIN borrowers p ON (a.user=p.borrowernumber) WHERE a.module='CATALOGUING' AND a.timestamp BETWEEN <> AND <> AND a.info IN ('item','biblio') GROUP BY p.borrowernumber, concat(a.action, ' ', a.info) How can I change this report to show the listing of titles entered by each Librarian? From sheralynb at latahlibrary.org Sat Sep 4 12:00:48 2021 From: sheralynb at latahlibrary.org (sheralynb) Date: Fri, 3 Sep 2021 17:00:48 -0700 Subject: [Koha] Out Of Office until 21 September 2021 Message-ID: <12109031700.AA3094744805@latahlibrary.org> Thank you for contacting me. I will be out of the office until 21 September 2021 and not checking email. In the event of an emergency, please contact kimc at latahlibrary.org. Sheralyn Bassett She/Her/Hers Manager of Technical Services Latah County Library District 110 S. Jefferson, Moscow ID 83843 208-882-3925 ext 120 From jonathan.druart at bugs.koha-community.org Tue Sep 7 00:00:00 2021 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Mon, 6 Sep 2021 14:00:00 +0200 Subject: [Koha] Security releases for all stable branches - UPGRADE! Message-ID: Hello everybody, Don't ignore this email! Last week a critical security bug was reported on our bug tracker. We fixed it and built debian packages for the four stable releases we currently support. The security flaw can cause a privilege escalation from OPAC users. It can be highly damaging, especially if your staff interface is accessible via login from everywhere without further security measures like IP restrictions in place. How to fix the problem? If you are using a debian-based system you should upgrade using the debian packages: % apt update % apt install koha-common If you are using an older version of Koha (<19.11) you should either upgrade to a newer version, or apply those two patches (they should apply on older versions as well): https://paste.debian.net/hidden/885fb5ec/ https://paste.debian.net/hidden/1184f523/ https://paste.debian.net/plainh/ae9f9f25 You can apply them using the following command: % wget "https://paste.debian.net/plainh/885fb5ec" -O 28929_1.patch % wget "https://paste.debian.net/plainh/1184f523" -O 28929_2.patch % wget "https://paste.debian.net/plainh/ae9f9f25" -O 28947.patch % patch -p1 -d /usr/share/koha/intranet/cgi-bin/ < /kohadevbox/koha/28929_1.patch % patch -p1 -d /usr/share/koha/opac/cgi-bin/ < /kohadevbox/koha/28929_2.patch % patch -d /usr/share/koha/opac/cgi-bin/opac/ < /kohadevbox/koha/28947.patch The two bugs are 28929 and 28947. As they contain information about how to recreate the vulnerability they will stay hidden two more days to let you upgrade your systems. Let us know if you have any questions! Regards, Jonathan From mtj at kohaaloha.com Tue Sep 7 00:57:43 2021 From: mtj at kohaaloha.com (Mason James) Date: Tue, 7 Sep 2021 00:57:43 +1200 Subject: [Koha] [Koha-devel] Security releases for all stable branches - UPGRADE! In-Reply-To: References: Message-ID: hi folks i think there might be a small typo in the patch commands - but this worked OK for me... cd /tmp wget "https://paste.debian.net/plainh/885fb5ec" -O 28929_1.patch wget "https://paste.debian.net/plainh/1184f523" -O 28929_2.patch wget "https://paste.debian.net/plainh/ae9f9f25" -O 28947.patch sudo patch -p1 -d /usr/share/koha/intranet/cgi-bin/ < 28929_1.patch sudo patch -p1 -d /usr/share/koha/opac/cgi-bin/ < 28929_2.patch sudo patch -p1 -d /usr/share/koha/opac/cgi-bin/ < 28947.patch output looks like... ------------------ mason at xen1:/tmp$ sudo patch -p1 -d /usr/share/koha/intranet/cgi-bin/ < 28929_1.patch patching file members/memberentry.pl Hunk #1 succeeded at 225 (offset 10 lines). mason at xen1:/tmp$ sudo patch -p1 -d /usr/share/koha/opac/cgi-bin/ < 28929_2.patch patching file opac/opac-memberentry.pl Hunk #1 succeeded at 523 (offset 1 line). mason at xen1:/tmp$ sudo patch -p1 -d /usr/share/koha/opac/cgi-bin/ < 28947.patch patching file opac/opac-memberentry.pl patch unexpectedly ends in middle of line ------------------ it seems you can ignore the 'patch unexpectedly ends' message On 7/09/21 12:00 am, Jonathan Druart wrote: > Hello everybody, > > Don't ignore this email! > > Last week a critical security bug was reported on our bug tracker. We > fixed it and built debian packages for the four stable releases we > currently support. > > The security flaw can cause a privilege escalation from OPAC users. It > can be highly damaging, especially if your staff interface is > accessible via login from everywhere without further security measures > like IP restrictions in place. > > > How to fix the problem? > If you are using a debian-based system you should upgrade using the > debian packages: > % apt update > % apt install koha-common > > If you are using an older version of Koha (<19.11) you should either > upgrade to a newer version, or apply those two patches (they should > apply on older versions as well): > https://paste.debian.net/hidden/885fb5ec/ > https://paste.debian.net/hidden/1184f523/ > https://paste.debian.net/plainh/ae9f9f25 > > You can apply them using the following command: > % wget "https://paste.debian.net/plainh/885fb5ec" -O 28929_1.patch > % wget "https://paste.debian.net/plainh/1184f523" -O 28929_2.patch > % wget "https://paste.debian.net/plainh/ae9f9f25" -O 28947.patch > % patch -p1 -d /usr/share/koha/intranet/cgi-bin/ < > /kohadevbox/koha/28929_1.patch > % patch -p1 -d /usr/share/koha/opac/cgi-bin/ < /kohadevbox/koha/28929_2.patch > % patch -d /usr/share/koha/opac/cgi-bin/opac/ < /kohadevbox/koha/28947.patch > > The two bugs are 28929 and 28947. As they contain information about > how to recreate the vulnerability they will stay hidden two more days to let > you upgrade your systems. > > Let us know if you have any questions! > > Regards, > Jonathan > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ > git : https://git.koha-community.org/ > bugs : https://bugs.koha-community.org/ From tasha.r.bales at boeing.com Wed Sep 8 01:48:58 2021 From: tasha.r.bales at boeing.com (Bales (US), Tasha R) Date: Tue, 7 Sep 2021 13:48:58 +0000 Subject: [Koha] Elasticsearch error stops bulkmarcimport Message-ID: <78d3e68a9c13411cabb42e4bebc2056f@boeing.com> I've occasionally seen this error when loading MARC record on the command line using bulkmarcimport.pl: Bad response received when submitting request to Elasticsearch. When it occurs, the bulkmarcimport ceases, interrupting the load. I've found nothing else in any other logs on the Koha server that help explain the error. I'm not sure what Elasticsearch has to do with my bulkmarcimport, unless it is Elasticsearch trying to index records on-the-fly after they are loaded? Is there an easy way to prevent this error from happening? Perhaps I should stop the Elasticsearch process while doing a bulkmarcimport? My Elasticsearch servers are external to the Koha environment, and I don't see any obvious indexing processes running on my local machine, so I'm not sure how best to intervene to prevent the above issue. I'm currently working my way through loading 1.3 million records, and I've had several redo's already as a result of loads being interrupted partway through (running bulkmarcimport via a cronjob helped *a lot*, but now I've had two ES errors/interruptions in the last day, which has put me a day behind). I am currently working with batches of 200K records or less. Thanks for any tips you may have! In the meantime, I will modify my latest MARC file to try to remove records already loaded and then resubmit the job (in order to save additional hours spent reloading 98K records). Tasha Bales Enterprise Services http://isesi.web.boeing.com/ From Boze.1 at nd.edu Thu Sep 9 01:57:21 2021 From: Boze.1 at nd.edu (Andy Boze) Date: Wed, 8 Sep 2021 09:57:21 -0400 Subject: [Koha] Security releases for all stable branches - UPGRADE! In-Reply-To: References: Message-ID: Hi, all. We applied the patch on our test server running v20.11. In testing, I've run into a problem. After I log in to the OPAC and click on "Your account", when I click on the "your personal details" tab, I get a page that states in part Sorry, the requested page is not available Error 500 This message can have the following reason(s): An error occurred while processing your request. On our production server, following the same steps, I get a page with my account details. Is anyone else who has applied the patch seeing the same error? Andy On 9/6/2021 8:00 AM, Jonathan Druart wrote: > Hello everybody, > > Don't ignore this email! > > Last week a critical security bug was reported on our bug tracker. We > fixed it and built debian packages for the four stable releases we > currently support. > > The security flaw can cause a privilege escalation from OPAC users. It > can be highly damaging, especially if your staff interface is > accessible via login from everywhere without further security measures > like IP restrictions in place. > > > How to fix the problem? > If you are using a debian-based system you should upgrade using the > debian packages: > % apt update > % apt install koha-common > > If you are using an older version of Koha (<19.11) you should either > upgrade to a newer version, or apply those two patches (they should > apply on older versions as well): > https://paste.debian.net/hidden/885fb5ec/ > https://paste.debian.net/hidden/1184f523/ > https://paste.debian.net/plainh/ae9f9f25 > > You can apply them using the following command: > % wget "https://paste.debian.net/plainh/885fb5ec" -O 28929_1.patch > % wget "https://paste.debian.net/plainh/1184f523" -O 28929_2.patch > % wget "https://paste.debian.net/plainh/ae9f9f25" -O 28947.patch > % patch -p1 -d /usr/share/koha/intranet/cgi-bin/ < > /kohadevbox/koha/28929_1.patch > % patch -p1 -d /usr/share/koha/opac/cgi-bin/ < /kohadevbox/koha/28929_2.patch > % patch -d /usr/share/koha/opac/cgi-bin/opac/ < /kohadevbox/koha/28947.patch > > The two bugs are 28929 and 28947. As they contain information about > how to recreate the vulnerability they will stay hidden two more days to let > you upgrade your systems. > > Let us know if you have any questions! > > Regards, > Jonathan > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > -- Andy Boze, Associate Librarian University of Notre Dame 271H Hesburgh Library (574) 631-8708 From stefan.scoala9 at gmail.com Thu Sep 9 02:55:28 2021 From: stefan.scoala9 at gmail.com (stefan) Date: Wed, 8 Sep 2021 17:55:28 +0300 Subject: [Koha] install koha Message-ID: <03363f8d-f9b7-caeb-f8f5-af653850a292@gmail.com> Hi, I'm from Romania, I'm a librarian and I want to install koha on the library computer. I tried using the instructions at https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#Install_Ubuntu but without success. On the computer i have ubuntu 20.04.3. I want to install koha and then get in the system all the books in the library and all the students that come to the library. I want to get koha up and running individually on this local computer. I don't have a system admin at the school. The computer is connected to the internet. Can somebody explain to me how i configure /etc/koha/koha-sites.conf? Also, what is the difference between web install and IP install. What would be best form me? I don't know about domain names and INTRAPORT AND OPACPORT... From Fred.King at Medstar.net Thu Sep 9 03:17:14 2021 From: Fred.King at Medstar.net (King, Fred) Date: Wed, 8 Sep 2021 15:17:14 +0000 Subject: [Koha] [EXTERNAL] install koha In-Reply-To: <03363f8d-f9b7-caeb-f8f5-af653850a292@gmail.com> References: <03363f8d-f9b7-caeb-f8f5-af653850a292@gmail.com> Message-ID: This won't tell you everything you need to know, but I did a video that takes you from the Ubuntu command line through a complete Koha system, ready to go, in half an hour. See https://youtu.be/plzFqqy1iPs. I'm working on part 2, where I set up the library, item types, OPAC home page, etc., which I hope to have ready in time for the koha-US conference, starting on September 21st. Free registration if you attend online! See https://koha-us.org/. As for koha-sites.conf, I'd recommend setting intraport to 8080 and opacport to 80. Then you can get to your staff interface as 123.123.123.123:8080 (assuming your IP address is 123.123.123.123) and the catalog as 123.123.123.123. You don't need an actual domain name for Koha, though it does make things easier. NOTE: Some of you might be rather alarmed at my barebones approach to setting up Koha. No, my directions don't produce something pretty looking. My intended audience is libraries that don't have a lot of money to hire someone to design and set up their ILS. You'll end up with something that works, but look like something designed in somebody's basement. And if you find any errors in my video, please tell me! 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 All right, but apart from sanitation, medicine, education, wine, public order, irrigation, roads, the fresh water system and public health, what have the Romans ever done for us? --John Cleese -----Original Message----- From: Koha On Behalf Of stefan Sent: Wednesday, September 08, 2021 10:55 AM To: koha Subject: [EXTERNAL] [Koha] install koha **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, I'm from Romania, I'm a librarian and I want to install koha on the library computer. I tried using the instructions at https://urldefense.com/v3/__https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages*Install_Ubuntu__;Iw!!D7IIWT94AA!r8Im6_gLUsp-6SdXI2zDtDwSvLDj2no5iuW9d1zDfvYQB-zL1TCtaBcbg4EROE1Dlw$ but without success. On the computer i have ubuntu 20.04.3. I want to install koha and then get in the system all the books in the library and all the students that come to the library. I want to get koha up and running individually on this local computer. I don't have a system admin at the school. The computer is connected to the internet. Can somebody explain to me how i configure /etc/koha/koha-sites.conf? Also, what is the difference between web install and IP install. What would be best form me? I don't know about domain names and INTRAPORT AND OPACPORT... _______________________________________________ Koha mailing list https://urldefense.com/v3/__http://koha-community.org__;!!D7IIWT94AA!r8Im6_gLUsp-6SdXI2zDtDwSvLDj2no5iuW9d1zDfvYQB-zL1TCtaBcbg4FEEZLGOg$ Koha at lists.katipo.co.nz Unsubscribe: https://urldefense.com/v3/__https://lists.katipo.co.nz/mailman/listinfo/koha__;!!D7IIWT94AA!r8Im6_gLUsp-6SdXI2zDtDwSvLDj2no5iuW9d1zDfvYQB-zL1TCtaBcbg4FV8B4UYg$ ---------------------------------------------------------------------- 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 mrosu at rschicago.org Thu Sep 9 10:55:59 2021 From: mrosu at rschicago.org (Mihai Rosu) Date: Wed, 8 Sep 2021 17:55:59 -0500 Subject: [Koha] Cannot see Google Login Link In-Reply-To: References:

Message-ID: Hi Owen, I just wanted to give an update that I upgraded our Koha installation to 21.05.03.001 and the Google Authentication link does not display on the staff nor the public login. Mihai Rosu Rudolf Steiner Branch Chicago 4249 N. Lincoln Ave Chicago, IL 60618-1953 mrosu at rschicago.org 773.562.6254 www.rschicago.org On Fri, Aug 20, 2021 at 12:12 PM Mihai Rosu wrote: > Thank you Owen! > > Mihai Rosu > Rudolf Steiner Branch Chicago > 4249 N. Lincoln Ave > Chicago, IL 60618-1953 > mrosu at rschicago.org > 773.562.6254 > www.rschicago.org > > > On Fri, Aug 20, 2021 at 7:53 AM Owen Leonard wrote: > >> > We are running the latest Koha stable release 21.05.02-1 >> >> It sounds like may be seeing this bug: >> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28679 >> >> It is fixed in 21.05.03 which will be released soon. >> >> -- Owen >> > From mtj at kohaaloha.com Thu Sep 9 15:04:00 2021 From: mtj at kohaaloha.com (Mason James) Date: Thu, 9 Sep 2021 15:04:00 +1200 Subject: [Koha] Security releases for all stable branches - UPGRADE! In-Reply-To: References:

Message-ID: hi Andy i'm not sure why you are getting the error on your testing koha, it works ok for me - are your testing and prod systems running the same koha version - are they both running the latest 20.11.x koha version (20.11.09)? - do you get the error if you revert the patches? - do you have additional code modifications to your testing system? the 500 error is often caused by a perl syntax error, so perhaps the patching has caused a syntax error in your koha check your error logs for more info about the error... tail -f /var/log/koha/mykoha/*err*.log /var/log/apache/*err*.log On 9/09/21 1:57 am, Andy Boze wrote: > Hi, all. > > We applied the patch on our test server running v20.11. In testing, I've run into a problem. After I log in to the OPAC and click on "Your account", when I click on the "your personal details" tab, I get a page that states in part > > Sorry, the requested page is not available > Error 500 > This message can have the following reason(s): > > An error occurred while processing your request. > > On our production server, following the same steps, I get a page with my account details. > > Is anyone else who has applied the patch seeing the same error? > > Andy > > On 9/6/2021 8:00 AM, Jonathan Druart wrote: >> Hello everybody, >> >> Don't ignore this email! >> >> Last week a critical security bug was reported on our bug tracker. We >> fixed it and built debian packages for the four stable releases we >> currently support. >> >> The security flaw can cause a privilege escalation from OPAC users. It >> can be highly damaging, especially if your staff interface is >> accessible via login from everywhere without further security measures >> like IP restrictions in place. >> >> >> How to fix the problem? >> If you are using a debian-based system you should upgrade using the >> debian packages: >> % apt update >> % apt install koha-common >> >> If you are using an older version of Koha (<19.11) you should either >> upgrade to a newer version, or apply those two patches (they should >> apply on older versions as well): >> https://paste.debian.net/hidden/885fb5ec/ >> https://paste.debian.net/hidden/1184f523/ >> https://paste.debian.net/plainh/ae9f9f25 >> >> You can apply them using the following command: >> % wget "https://paste.debian.net/plainh/885fb5ec" -O 28929_1.patch >> % wget "https://paste.debian.net/plainh/1184f523" -O 28929_2.patch >> % wget "https://paste.debian.net/plainh/ae9f9f25" -O 28947.patch >> % patch -p1 -d /usr/share/koha/intranet/cgi-bin/ < >> /kohadevbox/koha/28929_1.patch >> % patch -p1 -d /usr/share/koha/opac/cgi-bin/ < /kohadevbox/koha/28929_2.patch >> % patch -d /usr/share/koha/opac/cgi-bin/opac/ < /kohadevbox/koha/28947.patch >> >> The two bugs are 28929 and 28947. As they contain information about >> how to recreate the vulnerability they will stay hidden two more days to let >> you upgrade your systems. >> >> Let us know if you have any questions! >> >> Regards, >> Jonathan >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> > From jstallings at tsas.org Thu Sep 9 15:18:57 2021 From: jstallings at tsas.org (Jesse Stallings) Date: Wed, 8 Sep 2021 22:18:57 -0500 Subject: [Koha] 500 error when choosing patron for purchase suggestion Message-ID: Running 21.05.02 on Debian stretch 9.13. When selecting "set to patron" or "select manager" while entering a purchase suggestion from the staff console, a 500 error rather than a patron search box appears in the popup. This issue seems related to bug 26738 , where suggestion managers and patrons were unable to be saved, but I'm unable to get even that far. I'm not sure how to troubleshoot this—has anyone else run into this issue? Created bug report 28946 last week, but hasn't received any attention. Thanks! From mamcet.library10 at gmail.com Thu Sep 9 16:06:45 2021 From: mamcet.library10 at gmail.com (MASTeR Library) Date: Thu, 9 Sep 2021 09:36:45 +0530 Subject: [Koha] [EXTERNAL] install koha In-Reply-To: References: <03363f8d-f9b7-caeb-f8f5-af653850a292@gmail.com> Message-ID: Visit the link Koha Full tutorial. basic koha installation and koha customization etc.. https://www.youtube.com/c/LibPowerTech On Wed, Sep 8, 2021 at 8:48 PM King, Fred wrote: > This won't tell you everything you need to know, but I did a video that > takes you from the Ubuntu command line through a complete Koha system, > ready to go, in half an hour. See https://youtu.be/plzFqqy1iPs. I'm > working on part 2, where I set up the library, item types, OPAC home page, > etc., which I hope to have ready in time for the koha-US conference, > starting on September 21st. Free registration if you attend online! See > https://koha-us.org/. > > As for koha-sites.conf, I'd recommend setting intraport to 8080 and > opacport to 80. Then you can get to your staff interface as > 123.123.123.123:8080 (assuming your IP address is 123.123.123.123) and > the catalog as 123.123.123.123. You don't need an actual domain name for > Koha, though it does make things easier. > > NOTE: Some of you might be rather alarmed at my barebones approach to > setting up Koha. No, my directions don't produce something pretty looking. > My intended audience is libraries that don't have a lot of money to hire > someone to design and set up their ILS. You'll end up with something that > works, but look like something designed in somebody's basement. > > And if you find any errors in my video, please tell me! > > 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 > > All right, but apart from sanitation, medicine, education, wine, public > order, irrigation, roads, the fresh water system and public health, what > have the Romans ever done for us? > --John Cleese > > -----Original Message----- > From: Koha On Behalf Of stefan > Sent: Wednesday, September 08, 2021 10:55 AM > To: koha > Subject: [EXTERNAL] [Koha] install koha > > > > **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, > > I'm from Romania, I'm a librarian and I want to install koha on the > library computer. I tried using the instructions at > https://urldefense.com/v3/__https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages*Install_Ubuntu__;Iw!!D7IIWT94AA!r8Im6_gLUsp-6SdXI2zDtDwSvLDj2no5iuW9d1zDfvYQB-zL1TCtaBcbg4EROE1Dlw$ > but without success. > > On the computer i have ubuntu 20.04.3. > > I want to install koha and then get in the system all the books in the > library and all the students that come to the library. I want to get koha > up and running individually on this local computer. > > I don't have a system admin at the school. > > The computer is connected to the internet. > > Can somebody explain to me how i configure /etc/koha/koha-sites.conf? > Also, what is the difference between web install and IP install. What > would be best form me? I don't know about domain names and INTRAPORT AND > OPACPORT... > > _______________________________________________ > > Koha mailing list > https://urldefense.com/v3/__http://koha-community.org__;!!D7IIWT94AA!r8Im6_gLUsp-6SdXI2zDtDwSvLDj2no5iuW9d1zDfvYQB-zL1TCtaBcbg4FEEZLGOg$ > Koha at lists.katipo.co.nz > Unsubscribe: > https://urldefense.com/v3/__https://lists.katipo.co.nz/mailman/listinfo/koha__;!!D7IIWT94AA!r8Im6_gLUsp-6SdXI2zDtDwSvLDj2no5iuW9d1zDfvYQB-zL1TCtaBcbg4FV8B4UYg$ > > ---------------------------------------------------------------------- > 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. > > > _______________________________________________ > > 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 Boze.1 at nd.edu Fri Sep 10 02:15:11 2021 From: Boze.1 at nd.edu (Andy Boze) Date: Thu, 9 Sep 2021 10:15:11 -0400 Subject: [Koha] Security releases for all stable branches - UPGRADE! In-Reply-To: References:

Message-ID: <9b878d79-1cd3-6d4e-8965-02ae8f33905f@nd.edu> Hi, Mason. Thanks for your e-mail. We're running v 20.11.04 on both test and prod servers. They are essentially identical and the only changes we've made to any files is to alter a text string in a couple of .inc and .tt files and one javascript file. We haven't tried reverting the patches, but that's the next thing we'll do. Andy On 9/8/2021 11:04 PM, Mason James wrote: > hi Andy > i'm not sure why you are getting the error on your testing koha, it > works ok for me > > - are your testing and prod systems running the same koha version > - are they both running the latest 20.11.x koha version (20.11.09)? > - do you get the error if you revert the patches? > - do you have additional code modifications to your testing system? > > the 500 error is often caused by a perl syntax error, so perhaps the > patching has caused a syntax error in your koha > > check your error logs for more info about the error... > > tail -f /var/log/koha/mykoha/*err*.log /var/log/apache/*err*.log > > > On 9/09/21 1:57 am, Andy Boze wrote: >> Hi, all. >> >> We applied the patch on our test server running v20.11. In testing, >> I've run into a problem. After I log in to the OPAC and click on "Your >> account", when I click on the "your personal details" tab, I get a >> page that states in part >> >> Sorry, the requested page is not available >> Error 500 >> This message can have the following reason(s): >> >> An error occurred while processing your request. >> >> On our production server, following the same steps, I get a page with >> my account details. >> >> Is anyone else who has applied the patch seeing the same error? >> >> Andy >> >> On 9/6/2021 8:00 AM, Jonathan Druart wrote: >>> Hello everybody, >>> >>> Don't ignore this email! >>> >>> Last week a critical security bug was reported on our bug tracker. We >>> fixed it and built debian packages for the four stable releases we >>> currently support. >>> >>> The security flaw can cause a privilege escalation from OPAC users. It >>> can be highly damaging, especially if your staff interface is >>> accessible via login from everywhere without further security measures >>> like IP restrictions in place. >>> >>> >>> How to fix the problem? >>> If you are using a debian-based system you should upgrade using the >>> debian packages: >>> % apt update >>> % apt install koha-common >>> >>> If you are using an older version of Koha (<19.11) you should either >>> upgrade to a newer version, or apply those two patches (they should >>> apply on older versions as well): >>> https://paste.debian.net/hidden/885fb5ec/ >>> https://paste.debian.net/hidden/1184f523/ >>> https://paste.debian.net/plainh/ae9f9f25 >>> >>> You can apply them using the following command: >>> % wget "https://paste.debian.net/plainh/885fb5ec" -O 28929_1.patch >>> % wget "https://paste.debian.net/plainh/1184f523" -O 28929_2.patch >>> % wget "https://paste.debian.net/plainh/ae9f9f25" -O 28947.patch >>> % patch -p1 -d /usr/share/koha/intranet/cgi-bin/ < >>> /kohadevbox/koha/28929_1.patch >>> % patch -p1 -d /usr/share/koha/opac/cgi-bin/ < >>> /kohadevbox/koha/28929_2.patch >>> % patch -d /usr/share/koha/opac/cgi-bin/opac/ < >>> /kohadevbox/koha/28947.patch >>> >>> The two bugs are 28929 and 28947. As they contain information about >>> how to recreate the vulnerability they will stay hidden two more days >>> to let >>> you upgrade your systems. >>> >>> Let us know if you have any questions! >>> >>> Regards, >>> Jonathan >>> _______________________________________________ >>> >>> Koha mailing list http://koha-community.org >>> Koha at lists.katipo.co.nz >>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >>> >> > > -- Andy Boze, Associate Librarian University of Notre Dame 271H Hesburgh Library (574) 631-8708 From matthew.lindfield-seager at hope.edu.kh Fri Sep 10 16:03:05 2021 From: matthew.lindfield-seager at hope.edu.kh (Matthew Lindfield Seager) Date: Fri, 10 Sep 2021 11:03:05 +0700 Subject: [Koha] Batch check outs timing out after upgrade and migration Message-ID: Hi All, I'm a Koha newbie so I hope this is the appropriate forum for this question, please let me know if not! I'm the ICT Manager in a small school in Phnom Penh that had a working Koha installation. One of our physical servers died and, rather than replace it to get back up to full redundancy, we decided to move our on-prem servers to an IaaS provider (Linode). In the process of restoring Koha onto the new server I discovered we were running Koha 20.05 on the old server and 21.05 on the new server. I then made the fateful mistake of proceeding with both changes at once (despite knowing better 😔). I upgraded the old server to 21.05 and then backed up and restored onto the new server (both Ubuntu 20.04 LTS). I also added TLS using Let's Encrypt at the same time. It all seemed to go smoothly but we're now experiencing slow performance when checking out and looking up patrons and we're getting gateway timeouts when we try to use Batch Check Out. Does anyone have any tips on how to troubleshoot this? So far I've: - checked specs (new server is a "dedicated" 4GB VM with specs equivalent to or better than the old server) - tried to find any configuration differences between the old server and the new server - looked through the wiki pages on performance and tuning to see if there's anything we'd done on the old server but not on the new In the process I discovered that the old server was running on MariaDB 10.3.31 whereas I installed MySQL 8.0.26 on the new server. Could that be the source of all our issues or is that a red herring? To rule out MariaDB as the issue I've tried backing up the new server and restoring it on to an even newer server with MariaDB installed but so far I've not been successful in getting Koha running on MariaDB, despite successfully running the restore (after adjusting the SQL dump to change from MySQL's `utf8mb4_0900_ai_ci` collation to MariaDB's `utf8mb4_general_ci `). Has anyone got any nuggets of wisdom? I fear our next best option might be to create a new (MariaDB) server from the original back ups and manually re-enter the past 4 days worth of borrowing and returns 😔 Regards, Matt From tadas.kaupa at gmail.com Fri Sep 10 20:45:50 2021 From: tadas.kaupa at gmail.com (Tadas G) Date: Fri, 10 Sep 2021 11:45:50 +0300 Subject: [Koha] Import in koha 21.05 all users from LDAP Message-ID: Hello, We have Koha 21.05 installed and configured to work with AD. Everything is fine, users can login to Koha using AD credentials, but in Patron list they appear only after successful authorisation. It is quite annoying, because if you want to assign book to the reader, he/she has to be in patron list. Is it possible to create Cron job to import users to patron list automatically from AD (it is enough to import only a few fields, all other fields can be updated after user login)? Thanks for the answers From javi at legido.com Fri Sep 10 20:52:40 2021 From: javi at legido.com (Javi Legido) Date: Fri, 10 Sep 2021 10:52:40 +0200 Subject: [Koha] Import in koha 21.05 all users from LDAP In-Reply-To: References: Message-ID: Hi there. I'm not an expert on the subject, maybe others can reply, but this is the classical behaviour of applications integrating with LDAP for authentication (and sometimes also authorization): after first login the application creates data in its database, in this example as "Patron". No idea if there's anything out there, but a high level approach would be: 1. Create a test account in LDAP (Active Directory in your case) 2. Dump Koha database (one insert per line is useful) mysqldump --extended-insert=FALSE my_koha_database -u root -psecret > koha.sql 3. Perform first login with user created at step 1. 4. Repeat step 2: mysqldump --extended-insert=FALSE my_koha_database -u root -psecret > koha.after.sql 5. See differences diff koha.sql koha_after.sql Now you are very close to build the SQL statements to add a new Patron once authenticated. Cheers. Javier On Fri, 10 Sept 2021 at 10:46, Tadas G wrote: > Hello, > > We have Koha 21.05 installed and configured to work with AD. Everything is > fine, users can login to Koha using AD credentials, but in Patron list they > appear only after successful authorisation. It is quite annoying, because > if you want to assign book to the reader, he/she has to be in patron list. > Is it possible to create Cron job to import users to patron list > automatically from AD (it is enough to import only a few fields, all other > fields can be updated after user login)? > > Thanks for the answers > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From pradhmohan at gmail.com Sat Sep 11 02:36:22 2021 From: pradhmohan at gmail.com (mohan pradhan) Date: Fri, 10 Sep 2021 20:21:22 +0545 Subject: [Koha] VuFind Summit 2021 Message-ID: Central Department of Library and Information Science, TU in partnership with Villanova University’s Falvey Memorial Library, the VuFind Summit 2021 is going to be organized on November 15-17, 2021. Welcome you all for presenting your paper and participation. For details click the link: VuFind Summit 2021 Prof. Mohan Raj Pradhan, Ph. D. Secretary VuFind Software From david at penkler.net Sat Sep 11 03:50:16 2021 From: david at penkler.net (david at penkler.net) Date: Fri, 10 Sep 2021 17:50:16 +0200 Subject: [Koha] New community member introduction and question Message-ID: <0151b74c5ad3ed6f5004ccda527f5df0@penkler.net> Hi, I work as a volunteer in a non-profit association that runs the library for culture and religion at the Theological Centre in Meylan near Grenoble in France. My main task is cataloguing. We receive many books through book donations and bequests with the result that we have a large number of duplicates (circa 2500 books out of some 40000). We are setting up a framework to sell the duplicates for a token amount. To this end we have added a item.notforloan value "For Sale" which we use to generate a report of books for sale from which we create a virtual shelf that can be consulted by the patrons. I am trying to figure out how to add a "Price" column with items.price to the Holdings tab of the opac details page for folks viewing the "For Sale" virtual shelf in the "Normal View". The price is shown in the "Marc view". Any advice is gratefully accepted. Thanks, -David Penkler From katrin.fischer.83 at web.de Sun Sep 12 22:45:05 2021 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sun, 12 Sep 2021 12:45:05 +0200 Subject: [Koha] [EXTERNAL] Re: Search/List RSS feeds (trigger? add call number?) In-Reply-To: <80f0f4ed02c347ceb09b5c3f85684572@boeing.com> References: <218ad6fd61d74bc29ab93a5e2e2bf972@boeing.com> <80f0f4ed02c347ceb09b5c3f85684572@boeing.com> Message-ID: <3a8c7237-196e-c085-59df-b228069252f7@web.de> Hi Tasha, sorry for my late reply. I am sorry, I don't have the time to take a closer look at the templates, but usually it will not be possible to display arbitrary MARC fields. You could try the column names from biblio and biblioitems, but it might not work, as it depends on what was made available to the template as variables. An enhancement request is a bug on bugzilla with importance "enhancement" selected. For Koha the term bug is also used for new features and improvements. Hope this helps, Katrin On 23.08.21 16:18, Bales (US), Tasha R wrote: > Thanks for your reply, Katrin. > > Your comments on including a call number in an RSS make perfect sense. We could use a bibliographic attribute instead, such as technical report number in 027, thus my attempt to sub in "report-number" for isbn. I don't know if I'm on the right track with respect to syntax (i.e., what are the possible terms that could be subbed in for isbn?), but I haven't tried 001 or 035 yet; I will give those a try too. > > I am surprised by the behavior of the "Subscribe to this list" RSS. I was really hoping that would allow for reappearance in the feed if an item in the list was edited. Thanks for your suggestion to file an enhancement request (is that just a bug report, or is there a separate option for enhancement requests?). > > If anyone has knowledge of what code we would look at in addition to opac-opensearch.tt and opac-search.pl, please advise. Maybe there is something we can tweak fundamental to RSS to allow for reporting on records with an 005 that is >= a specified value. I believe we could use a custom feed, but I think that would only work for users on a case-by-case basis, which would be unmanageable. Thanks again for your time. > > > Tasha Bales > Enterprise Services > http://isesi.web.boeing.com/ > > -----Original Message----- > From: Koha [mailto:koha-bounces at lists.katipo.co.nz] On Behalf Of Katrin Fischer > Sent: Monday, August 23, 2021 5:38 AM > To:koha at lists.katipo.co.nz > Subject: [EXTERNAL] Re: [Koha] Search/List RSS feeds (trigger? add call number?) > > EXT email: be mindful of links/attachments. > > > > Hi Tasha, > > I can't answer all your questions, but maybe I can provide a bit of information. > > I think that for the RSS feed on lists the date the record is added to a list is used. Would that match with what you see? > > I think adding the call number to the RSS feed might not be straight forward, because this information would have to be taken from the items instead of the record. As there can be many items per record and the call numbers can vary between the different branches and locations of a library system, the task of displaying this information in a useful and nice way is not an easy one. Maybe filing an enhancement request on bugzilla to discuss this more would be a good first step to discuss this further. > > Hope this helps, > > Katrin > > On 19.08.21 15:51, Bales (US), Tasha R wrote: >> Good morning, >> >> I'm writing with a couple questions about out-of-the-box RSS feeds for searches. I'm interested in how to modify them (I really need one or more of our call numbers/classification numbers to be included), and how they are triggered. I see two types of feeds, below. >> >> "Subscribe to this search" >> >> * The manual says this feed "will allow you to see when a new item is added to the catalog". >> >> * How is a "new item" defined? I've taken a look at opac-opensearch.tt and opac-search.pl, in order to under how date limiting is coming in to play, specifically (which dates, what comparison, what fields, etc.). I do see reference to an 005 date "hack" for Atom, but it seems like only the RSS portions of the code are relevant. I'd like to determine if I can only ever expect newly added records to be returned, or would/could updated records also be returned? >> >> "Subscribe to this list" >> >> * I don't see information about this feed in the manual. >> >> * Since this is a search about already-cataloged, known items, it wouldn't make sense for the RSS to retrieve only newly cataloged records. Therefore, what should trigger a subscriber to receive an update about their list if an item has been updated? Is it the bib 005, or something else? I've tried editing a few records in a list I am subscribed to, expecting to get a new email, but I didn't receive a message. Although this last part may sound confusing, I'm leaving as is, as it may help explain context-I've added the feeds to my Microsoft Outlook, where each matching item shows up as a discrete "email" message in my RSS Feeds folder. >> >> Maybe the problem here is my understanding of RSS. My feeds appear to be refreshed every time I check my mail, but I'm only receiving RSS for newly added records. I didn't receive a new feed today of records in my "list" that I edited yesterday. >> >> Finally, I find that the RSS output is not usable for my patrons. We really need call number to be included in the RSS. It looks like we could modify the template line below to swap out isbn with another identifier, but I'm not sure how to know what term to swap in after "SEARCH_RESULT.": >> >> ISBN:[% SEARCH_RESULT.isbn | html %] >> >> I've tried "report-number", "callnum", "lcn", and "local-classification", which all failed to produce results. >> >> Please advise if there are any known examples about customizing the RSS templates for the basic searches above (I didn't see anything promising in the Wiki, when I searched for "RSS" or "opensearch.tt"). >> >> Thanks so much for your time, >> >> >> Tasha Bales >> Enterprise Services >> http://isesi.web.boeing.com/ >> >> _______________________________________________ >> >> 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 From katrin.fischer.83 at web.de Sun Sep 12 22:46:57 2021 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sun, 12 Sep 2021 12:46:57 +0200 Subject: [Koha] Batch check outs timing out after upgrade and migration In-Reply-To: References: Message-ID: <219ecc3c-ed9a-d27c-7074-962422505f80@web.de> Hi Matthew, is there anything on the "About Koha" page that might give a clue? * Is Memcached running? * Is Plack configured and running? * Is there any error or warning displayed on the System information tab? Hope this helps, Katrin On 10.09.21 06:03, Matthew Lindfield Seager wrote: > Hi All, > > I'm a Koha newbie so I hope this is the appropriate forum for this > question, please let me know if not! > > I'm the ICT Manager in a small school in Phnom Penh that had a working Koha > installation. One of our physical servers died and, rather than replace it > to get back up to full redundancy, we decided to move our on-prem servers > to an IaaS provider (Linode). > > In the process of restoring Koha onto the new server I discovered we were > running Koha 20.05 on the old server and 21.05 on the new server. I then > made the fateful mistake of proceeding with both changes at once (despite > knowing better 😔). I upgraded the old server to 21.05 and then backed up > and restored onto the new server (both Ubuntu 20.04 LTS). I also added TLS > using Let's Encrypt at the same time. > > It all seemed to go smoothly but we're now experiencing slow performance > when checking out and looking up patrons and we're getting gateway timeouts > when we try to use Batch Check Out. > > Does anyone have any tips on how to troubleshoot this? So far I've: > > - checked specs (new server is a "dedicated" 4GB VM with specs > equivalent to or better than the old server) > - tried to find any configuration differences between the old server and > the new server > - looked through the wiki pages on performance > and tuning > to see if > there's anything we'd done on the old server but not on the new > > In the process I discovered that the old server was running on > MariaDB 10.3.31 whereas I installed MySQL 8.0.26 on the new server. Could > that be the source of all our issues or is that a red herring? > > To rule out MariaDB as the issue I've tried backing up the new server and > restoring it on to an even newer server with MariaDB installed but so far > I've not been successful in getting Koha running on MariaDB, despite > successfully running the restore (after adjusting the SQL dump to change > from MySQL's `utf8mb4_0900_ai_ci` collation to MariaDB's > `utf8mb4_general_ci `). > > Has anyone got any nuggets of wisdom? I fear our next best option might be > to create a new (MariaDB) server from the original back ups and manually > re-enter the past 4 days worth of borrowing and returns 😔 > > Regards, > Matt > _______________________________________________ > > 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 Sun Sep 12 22:48:07 2021 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sun, 12 Sep 2021 12:48:07 +0200 Subject: [Koha] Import in koha 21.05 all users from LDAP In-Reply-To: References: Message-ID: <56997c80-af16-5ec0-bcce-80dfe8dfdcc6@web.de> Hi, as others have pointed out, there is no way to do this via LDAP in Koha at the moment. What you could do is maybe get a list of patron information from your AD to use with the patron import tool. You could regularly import the new patrons manually or automated via the available command line tools. There are also REST API endpoints for patron data that might be useful. Hope this helps, Katrin On 10.09.21 10:45, Tadas G wrote: > Hello, > > We have Koha 21.05 installed and configured to work with AD. Everything is > fine, users can login to Koha using AD credentials, but in Patron list they > appear only after successful authorisation. It is quite annoying, because > if you want to assign book to the reader, he/she has to be in patron list. > Is it possible to create Cron job to import users to patron list > automatically from AD (it is enough to import only a few fields, all other > fields can be updated after user login)? > > Thanks for the answers > _______________________________________________ > > 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 Sun Sep 12 22:48:33 2021 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sun, 12 Sep 2021 12:48:33 +0200 Subject: [Koha] New community member introduction and question In-Reply-To: <0151b74c5ad3ed6f5004ccda527f5df0@penkler.net> References: <0151b74c5ad3ed6f5004ccda527f5df0@penkler.net> Message-ID: <5cc46e37-467b-4080-94ab-5d78f43df6e6@web.de> Hi David, welcome! Currently it's not possible to make the Price field visible in the OPAC normal view. If you go to Administration > Table settings > OPAC > holdingst you can see all columns that can be made visible/be hidden from the table. Maybe putting/copying the price to OPAC note (item_notes) could work for your use case? Hope this helps, Katrin On 10.09.21 17:50, david at penkler.net wrote: > Hi, > I work as a volunteer in a non-profit association that runs the > library for culture and religion at the Theological Centre in Meylan > near Grenoble in France. My main task is cataloguing. > > We receive many books through book donations and bequests with the > result that we have a large number of duplicates (circa 2500 books out > of some 40000). We are setting up a framework to sell the duplicates > for a token amount. To this end we have added a item.notforloan value > "For Sale" which we use to generate a report of books for sale from > which we create a virtual shelf that can be consulted by the patrons. > I am trying to figure out how to add a "Price" column with items.price > to the Holdings tab of the opac details page for folks viewing the > "For Sale" virtual shelf in the "Normal View". The price is shown in > the "Marc view". Any advice is gratefully accepted. > Thanks, > -David Penkler > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From jwitts at queenmargarets.com Mon Sep 13 22:43:32 2021 From: jwitts at queenmargarets.com (Jon Witts) Date: Mon, 13 Sep 2021 11:43:32 +0100 Subject: [Koha] Import in koha 21.05 all users from LDAP In-Reply-To: <56997c80-af16-5ec0-bcce-80dfe8dfdcc6@web.de> References: <56997c80-af16-5ec0-bcce-80dfe8dfdcc6@web.de> Message-ID: Hi list, This functionality is something that we would love to see added to Koha in our school too. We use LDAP and / or Google oAuth login for most of our systems to ensure that usernames and passwords are consistent across our systems. We use Moodle as our school's Virtual Learning Environment, and this system has the ability to create / synchronise users from LDAP into the system. I would love to be able to do this for our patrons in Koha too. We self-check out modules that use a Mifare card to log the user in; the card number is copied across from LDAP at user login to OPAC. This means that before a user can use the self-check units they have to have first logged into the OPAC. A user sync script with LDAP would remove this requirement... Jon ----------------------------------------------------- Jon Witts Director of Digital Strategy On Sun, 12 Sept 2021 at 11:48, Katrin Fischer wrote: > Hi, > > as others have pointed out, there is no way to do this via LDAP in Koha > at the moment. > > What you could do is maybe get a list of patron information from your AD > to use with the patron import tool. You could regularly import the new > patrons manually or automated via the available command line tools. > There are also REST API endpoints for patron data that might be useful. > > Hope this helps, > > Katrin > > On 10.09.21 10:45, Tadas G wrote: > > Hello, > > > > We have Koha 21.05 installed and configured to work with AD. Everything > is > > fine, users can login to Koha using AD credentials, but in Patron list > they > > appear only after successful authorisation. It is quite annoying, because > > if you want to assign book to the reader, he/she has to be in patron > list. > > Is it possible to create Cron job to import users to patron list > > automatically from AD (it is enough to import only a few fields, all > other > > fields can be updated after user login)? > > > > Thanks for the answers > > _______________________________________________ > > > > 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 > -- 01904 727600 queenmargarets.com Queen Margaret's, Escrick Park, York YO19 6EU *Come and be inspired... * Let us arrange a personalised virtual tour tailored to your requirements and chat to our Head and find out what a QM education can offer your daughter. Visit *queenmargarets.com/admissions/book-a-visit *, call 01904 727630 or email admissions at queenmargarets.com to find out more. From oleonard at myacpl.org Mon Sep 13 23:40:12 2021 From: oleonard at myacpl.org (Owen Leonard) Date: Mon, 13 Sep 2021 07:40:12 -0400 Subject: [Koha] Cannot see Google Login Link In-Reply-To: References:

Message-ID: > I just wanted to give an update that I upgraded our Koha installation to 21.05.03.001 > and the Google Authentication link does not display on the staff nor the public login. In my test the Google Authentication link doesn't appear on the staff interface login screen. I don't know if the feature is supposed to be working there or if it's only for the OPAC. In the OPAC, the Google Authentication link doesn't appear on the home page but clicking the "Log in to your account" link at the top takes you to a Google sign-in form. This makes me think that it's working, but that we need to add a "Log in with Google" button to the sign-in form on the OPAC home page. -- Owen From kohanews at gmail.com Mon Sep 13 23:44:12 2021 From: kohanews at gmail.com (Koha Newsletter) Date: Mon, 13 Sep 2021 13:44:12 +0200 Subject: [Koha] Call for news - Newsletter September 2021 Message-ID: Hi I'm collecting news for the September 2021 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 From mrosu at rschicago.org Tue Sep 14 00:51:08 2021 From: mrosu at rschicago.org (Mihai Rosu) Date: Mon, 13 Sep 2021 07:51:08 -0500 Subject: [Koha] Cannot see Google Login Link In-Reply-To: References:

Message-ID: Hi Owen, I can confirm what you are saying. I did find the Google Authentication via the "Log in to your account". I agree that it would be much less confusing if the Google Login link is located on the front page somewhere near the regular login. Ideally it would exist on both sites, thank you! Mihai Rosu Rudolf Steiner Branch Chicago 4249 N. Lincoln Ave Chicago, IL 60618-1953 mrosu at rschicago.org 773.562.6254 www.rschicago.org On Mon, Sep 13, 2021 at 6:40 AM Owen Leonard wrote: > > I just wanted to give an update that I upgraded our Koha installation to > 21.05.03.001 > > and the Google Authentication link does not display on the staff nor the > public login. > > In my test the Google Authentication link doesn't appear on the staff > interface login screen. I don't know if the feature is supposed to be > working there or if it's only for the OPAC. > > In the OPAC, the Google Authentication link doesn't appear on the home > page but clicking the "Log in to your account" link at the top takes > you to a Google sign-in form. This makes me think that it's working, > but that we need to add a "Log in with Google" button to the sign-in > form on the OPAC home page. > > > -- Owen > From loveandmarigold at gmail.com Tue Sep 14 05:06:13 2021 From: loveandmarigold at gmail.com (Sanjay Uchcharia) Date: Mon, 13 Sep 2021 22:36:13 +0530 Subject: [Koha] Unable to login in Web Installer 21.5 Message-ID: Sir, I've installed Koha on Ubuntu 20.04 but I'm unable to login in Web Installer 21.5 with the username & password. From lennon at kohasupport.com Tue Sep 14 18:36:14 2021 From: lennon at kohasupport.com (Lennon Mazonde) Date: Tue, 14 Sep 2021 08:36:14 +0200 Subject: [Koha] Unable to login in Web Installer 21.5 In-Reply-To: References: Message-ID: <645098de-e088-9b34-72e8-7d8bf00faeec@kohasupport.com> Hi Sanjay, Can you provide more information? Are you getting an error message when you try to login? And what username and password are you using - your default username is koha_library (where 'library' is the name of your instance). To get your password run 'sudo koha-passwd library' in your commandline, where 'library' is again the name of your instance. For more steps on installing Koha on Ubuntu, check out this tutorial . Regards -- Lennon Mazonde www.kohasupport.com lennon at kohasupport.com WhatsApp @ (+1) 717.489.0195 On 9/13/21 7:06 PM, Sanjay Uchcharia wrote: > Sir, > > I've installed Koha on Ubuntu 20.04 but I'm unable to login in Web > Installer 21.5 with the username & password. > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From matthew.lindfield-seager at hope.edu.kh Tue Sep 14 18:55:22 2021 From: matthew.lindfield-seager at hope.edu.kh (Matthew Lindfield Seager) Date: Tue, 14 Sep 2021 13:55:22 +0700 Subject: [Koha] Batch check outs timing out after upgrade and migration In-Reply-To: References: Message-ID: Hi Katrin, Memcached is installed and running according to the About Koha page. Following the second lot of instructions at https://wiki.koha-community.org/wiki/Troubleshooting_memcached I can see that it has been handling requests. I also compared the old server (post upgrade to 21.05) with the new server and both have the same configuration in `/etc/memcached.conf`. According to the about page configuration is coming from koha-conf.xml but I'm not sure where to find that file (and it doesn't seem like Memcached is the culprit so I didn't bother installing mlocate to find it). The only mentions of Plack I can see are on the Perl Modules info page: - Plack::Middleware::ReverseProxy (0.14) - 0.16 - Plack::Middleware::LogWarn (0.001002) - 0.001002 I could not find any info in the Wiki about Plack other than the ~2017 Plack page and a brief mention on the Performance page . Is there anything I need to do to enable it? Both old and new server have a single warning on the System information tab: "System preference 'KohaAdminEmailAddress' does not contain a valid email address. Emails will not be sent." Comparing the Server Information page for the old server (which is super slow after the 21.05 upgrade but doesn't time out) with the new server (which is super slow AND times out), the only differences are: - Minor Koha version (old server is 21.05.02.003, new server is 21.05.03.001) - Slightly different kernel release and version (old is 5.4.0-84-generic, #94-Ubuntu; new is 5.4.0-81-generic, #91-Ubuntu) - Different MySQL versions (old is "mysql Ver 15.1 Distrib 10.3.31-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2", new is "mysql Ver 8.0.26-0ubuntu0.20.04.2 for Linux on x86_64 ((Ubuntu))" Thanks so much for some additional places to look for issues! If something in there gives a clue or if anyone has any other suggestions for things to check I'm all ears! Matt On Mon, 13 Sept 2021 at 07:01, wrote: > Date: Sun, 12 Sep 2021 12:46:57 +0200 > From: Katrin Fischer > To: koha at lists.katipo.co.nz > Subject: Re: [Koha] Batch check outs timing out after upgrade and > migration > Message-ID: <219ecc3c-ed9a-d27c-7074-962422505f80 at web.de> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi Matthew, > > is there anything on the "About Koha" page that might give a clue? > > * Is Memcached running? > * Is Plack configured and running? > * Is there any error or warning displayed on the System information tab? > > Hope this helps, > > Katrin > From lennon at kohasupport.com Tue Sep 14 19:10:18 2021 From: lennon at kohasupport.com (Lennon Mazonde) Date: Tue, 14 Sep 2021 09:10:18 +0200 Subject: [Koha] Batch check outs timing out after upgrade and migration In-Reply-To: References:

Message-ID: <7e340723-ab6d-d615-280a-d2a1a73b2840@kohasupport.com> Hi Matthew, 1. To enable Plack you need to run sudo koha-plack --enable instancename then sudo koha-plack --start instancename 2. To resolve the admin email warning, go to Home > Administration > System preferences > Interface options > KohaAdminEmailAddress and enter your admin email. You may have to do some additional configuration on your back-end server to setup an email server such as Postfix to enable your Koha instance to send out emails. I hope this helps! -- Lennon Mazonde www.kohasupport.com lennon at kohasupport.com WhatsApp @ (+1) 717.489.0195 On 9/14/21 8:55 AM, Matthew Lindfield Seager wrote: > Hi Katrin, > > Memcached is installed and running according to the About Koha page. > Following the second lot of instructions at > https://wiki.koha-community.org/wiki/Troubleshooting_memcached I can see > that it has been handling requests. I also compared the old server (post > upgrade to 21.05) with the new server and both have the same configuration > in `/etc/memcached.conf`. According to the about page configuration is > coming from koha-conf.xml but I'm not sure where to find that file (and it > doesn't seem like Memcached is the culprit so I didn't bother installing > mlocate to find it). > > The only mentions of Plack I can see are on the Perl Modules info page: > > - Plack::Middleware::ReverseProxy (0.14) - 0.16 > - Plack::Middleware::LogWarn (0.001002) - 0.001002 > > I could not find any info in the Wiki about Plack other than the ~2017 Plack > page and a brief mention on > the Performance page . Is > there anything I need to do to enable it? > > Both old and new server have a single warning on the System information tab: > "System preference 'KohaAdminEmailAddress' does not contain a valid email > address. Emails will not be sent." > > Comparing the Server Information page for the old server (which is super > slow after the 21.05 upgrade but doesn't time out) with the new server > (which is super slow AND times out), the only differences are: > > - Minor Koha version (old server is 21.05.02.003, new server is > 21.05.03.001) > - Slightly different kernel release and version (old is > 5.4.0-84-generic, #94-Ubuntu; new is 5.4.0-81-generic, #91-Ubuntu) > - Different MySQL versions (old is "mysql Ver 15.1 Distrib > 10.3.31-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2", new is > "mysql Ver 8.0.26-0ubuntu0.20.04.2 for Linux on x86_64 ((Ubuntu))" > > Thanks so much for some additional places to look for issues! If something > in there gives a clue or if anyone has any other suggestions for things to > check I'm all ears! > > Matt > > On Mon, 13 Sept 2021 at 07:01, wrote: > >> Date: Sun, 12 Sep 2021 12:46:57 +0200 >> From: Katrin Fischer >> To: koha at lists.katipo.co.nz >> Subject: Re: [Koha] Batch check outs timing out after upgrade and >> migration >> Message-ID: <219ecc3c-ed9a-d27c-7074-962422505f80 at web.de> >> Content-Type: text/plain; charset=utf-8; format=flowed >> >> Hi Matthew, >> >> is there anything on the "About Koha" page that might give a clue? >> >> * Is Memcached running? >> * Is Plack configured and running? >> * Is there any error or warning displayed on the System information tab? >> >> Hope this helps, >> >> Katrin >> > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From sebastian.krieg at tuz-eisenach.de Tue Sep 14 19:22:19 2021 From: sebastian.krieg at tuz-eisenach.de (Sebastian Krieg) Date: Tue, 14 Sep 2021 07:22:19 +0000 Subject: [Koha] Unable to login in Web Installer 21.5 In-Reply-To: References: Message-ID: Hello Sanjay, there are two ways: 1. Please login in a shell at your koha server, change to the superuser 'root' and execute 'koha-passwd [libraryname]' where [libraryname] is the given instance name during the installation. You will get the database password for the instance user. Note, that the command will make a 'clear' with next click. 2. Look into the file '/etc/koha/sites/[libraryname]/koha-conf.xml'. You will get the informations about the instance user in line 270 and the password in line 271. These are the login informations. Greets Sebastian --- mailto: sebastian.krieg at tuz-eisenach.de 13. September 2021 19:06, "Sanjay Uchcharia" schrieb: > Sir, > > I've installed Koha on Ubuntu 20.04 but I'm unable to login in Web > Installer 21.5 with the username & password. > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From david at penkler.net Tue Sep 14 19:38:29 2021 From: david at penkler.net (david at penkler.net) Date: Tue, 14 Sep 2021 09:38:29 +0200 Subject: [Koha] How to make the Price field visible in the OPAC normal view. In-Reply-To: <5cc46e37-467b-4080-94ab-5d78f43df6e6@web.de> References: <0151b74c5ad3ed6f5004ccda527f5df0@penkler.net> <5cc46e37-467b-4080-94ab-5d78f43df6e6@web.de> Message-ID: <9b24238615df6a824e1411c8a4c00f44@penkler.net> Hi Katrin, Thank you very much for the suggestion to use the item_notes field. That works perfectly for our needs. Is there a way to use the batch operations to add the note from the items.price field ? Many thanks, -David On 2021-09-12 12:48, Katrin Fischer wrote: > Hi David, > > welcome! > > Currently it's not possible to make the Price field visible in the OPAC > normal view. If you go to Administration > Table settings > OPAC > > holdingst you can see all columns that can be made visible/be hidden > from the table. > > Maybe putting/copying the price to OPAC note (item_notes) could work > for > your use case? > > Hope this helps, > > Katrin From matthew.lindfield-seager at hope.edu.kh Tue Sep 14 20:02:13 2021 From: matthew.lindfield-seager at hope.edu.kh (Matthew Lindfield Seager) Date: Tue, 14 Sep 2021 15:02:13 +0700 Subject: [Koha] Batch check outs timing out after upgrade and migration In-Reply-To: <7e340723-ab6d-d615-280a-d2a1a73b2840@kohasupport.com> References:

<7e340723-ab6d-d615-280a-d2a1a73b2840@kohasupport.com> Message-ID: Thanks Lennon! I enabled and started Plack (with one extra command needed): - sudo koha-plack --enable library - sudo a2enmod headers proxy_http - sudo koha-plack --start library After doing so I was hoping the problem would be magically* fixed but alas batch check outs still aren't working reliably: - Choose a patron - Switch to batch check out - Paste in 88 barcodes - Click "check out" - Wait over 10 minutes for a "Gateway Timeout: The gateway did not receive a timely response from the upstream server or application." While it was running I ran htop to see if memory or processor was causing a bottleneck but neither processor was maxed out and the RAM was hovering around 1.44G of 3.84G. My plan for tomorrow is to try profiling circulation.pl using Devel::NYTProf ( https://wiki.koha-community.org/wiki/Profiling_with_DevelNYTProf) and see if that gives me any clues. Matt On Tue, 14 Sept 2021 at 14:10, Lennon Mazonde wrote: > Hi Matthew, > > 1. To enable Plack you need to run > > sudo koha-plack --enable instancename > > then > > sudo koha-plack --start instancename > > 2. To resolve the admin email warning, go to Home > Administration > > System preferences > Interface options > KohaAdminEmailAddress and enter > your admin email. You may have to do some additional configuration on > your back-end server to setup an email server such as Postfix to enable > your Koha instance to send out emails. > > I hope this helps! > > -- > Lennon Mazonde > www.kohasupport.com > lennon at kohasupport.com > WhatsApp @ (+1) 717.489.0195 > > On 9/14/21 8:55 AM, Matthew Lindfield Seager wrote: > > Hi Katrin, > > > > Memcached is installed and running according to the About Koha page. > > Following the second lot of instructions at > > https://wiki.koha-community.org/wiki/Troubleshooting_memcached I can see > > that it has been handling requests. I also compared the old server (post > > upgrade to 21.05) with the new server and both have the same > configuration > > in `/etc/memcached.conf`. According to the about page configuration is > > coming from koha-conf.xml but I'm not sure where to find that file (and > it > > doesn't seem like Memcached is the culprit so I didn't bother installing > > mlocate to find it). > > > > The only mentions of Plack I can see are on the Perl Modules info page: > > > > - Plack::Middleware::ReverseProxy (0.14) - 0.16 > > - Plack::Middleware::LogWarn (0.001002) - 0.001002 > > > > I could not find any info in the Wiki about Plack other than the ~2017 > Plack > > page and a brief mention on > > the Performance page . > Is > > there anything I need to do to enable it? > > > > Both old and new server have a single warning on the System information > tab: > > "System preference 'KohaAdminEmailAddress' does not contain a valid email > > address. Emails will not be sent." > > > > Comparing the Server Information page for the old server (which is super > > slow after the 21.05 upgrade but doesn't time out) with the new server > > (which is super slow AND times out), the only differences are: > > > > - Minor Koha version (old server is 21.05.02.003, new server is > > 21.05.03.001) > > - Slightly different kernel release and version (old is > > 5.4.0-84-generic, #94-Ubuntu; new is 5.4.0-81-generic, #91-Ubuntu) > > - Different MySQL versions (old is "mysql Ver 15.1 Distrib > > 10.3.31-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2", > new is > > "mysql Ver 8.0.26-0ubuntu0.20.04.2 for Linux on x86_64 ((Ubuntu))" > > > > Thanks so much for some additional places to look for issues! If > something > > in there gives a clue or if anyone has any other suggestions for things > to > > check I'm all ears! > > > > Matt > > > > On Mon, 13 Sept 2021 at 07:01, wrote: > > > >> Date: Sun, 12 Sep 2021 12:46:57 +0200 > >> From: Katrin Fischer > >> To: koha at lists.katipo.co.nz > >> Subject: Re: [Koha] Batch check outs timing out after upgrade and > >> migration > >> Message-ID: <219ecc3c-ed9a-d27c-7074-962422505f80 at web.de> > >> Content-Type: text/plain; charset=utf-8; format=flowed > >> > >> Hi Matthew, > >> > >> is there anything on the "About Koha" page that might give a clue? > >> > >> * Is Memcached running? > >> * Is Plack configured and running? > >> * Is there any error or warning displayed on the System information tab? > >> > >> Hope this helps, > >> > >> Katrin > >> > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha at lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > From lmmazonde at gmail.com Tue Sep 14 20:51:18 2021 From: lmmazonde at gmail.com (Lennon Mazonde) Date: Tue, 14 Sep 2021 10:51:18 +0200 Subject: [Koha] Batch check outs timing out after upgrade and migration In-Reply-To: References:

<7e340723-ab6d-d615-280a-d2a1a73b2840@kohasupport.com> Message-ID: <82bbf459-7a44-634a-0a6f-65cc05f74868@gmail.com> And are you getting any additional errors in your log files - esp. MySQL, Apache and Koha logs? I'm groping in the dark here but I wonder if you need change the limits in your apache2.conf (maybe increase your timeout value?) or increase the max input and execution time in php.ini? This sounds pretty basic but you could also try using a different browser after clearing your cache and cookies, and see if that makes a difference. 88 barcodes in batch checkout seems quite a lot to me, do you have the same issues when checking out fewer barcodes, e.g. 10? In your first email you said: > I fear our next best option might be to create a new (MariaDB) server from the original back ups and manually re-enter the past 4 days worth of borrowing and returns 😔 Have you considered setting up offline circulation so you can at least continue serving your patrons (I assume you're in a production environment) until you can resolve the issue? On 9/14/21 10:02 AM, Matthew Lindfield Seager wrote: > Thanks Lennon! > > I enabled and started Plack (with one extra command needed): > > - sudo koha-plack --enable library > - sudo a2enmod headers proxy_http > - sudo koha-plack --start library > > After doing so I was hoping the problem would be magically* fixed but alas > batch check outs still aren't working reliably: > > - Choose a patron > - Switch to batch check out > - Paste in 88 barcodes > - Click "check out" > - Wait over 10 minutes for a "Gateway Timeout: The gateway did not > receive a timely response from the upstream server or application." > > While it was running I ran htop to see if memory or processor was causing a > bottleneck but neither processor was maxed out and the RAM was hovering > around 1.44G of 3.84G. > > My plan for tomorrow is to try profiling circulation.pl using > Devel::NYTProf ( > https://wiki.koha-community.org/wiki/Profiling_with_DevelNYTProf) and see > if that gives me any clues. > > Matt > > > > On Tue, 14 Sept 2021 at 14:10, Lennon Mazonde > wrote: > >> Hi Matthew, >> >> 1. To enable Plack you need to run >> >> sudo koha-plack --enable instancename >> >> then >> >> sudo koha-plack --start instancename >> >> 2. To resolve the admin email warning, go to Home > Administration > >> System preferences > Interface options > KohaAdminEmailAddress and enter >> your admin email. You may have to do some additional configuration on >> your back-end server to setup an email server such as Postfix to enable >> your Koha instance to send out emails. >> >> I hope this helps! >> >> -- >> Lennon Mazonde >> www.kohasupport.com >> lennon at kohasupport.com >> WhatsApp @ (+1) 717.489.0195 >> >> On 9/14/21 8:55 AM, Matthew Lindfield Seager wrote: >>> Hi Katrin, >>> >>> Memcached is installed and running according to the About Koha page. >>> Following the second lot of instructions at >>> https://wiki.koha-community.org/wiki/Troubleshooting_memcached I can see >>> that it has been handling requests. I also compared the old server (post >>> upgrade to 21.05) with the new server and both have the same >> configuration >>> in `/etc/memcached.conf`. According to the about page configuration is >>> coming from koha-conf.xml but I'm not sure where to find that file (and >> it >>> doesn't seem like Memcached is the culprit so I didn't bother installing >>> mlocate to find it). >>> >>> The only mentions of Plack I can see are on the Perl Modules info page: >>> >>> - Plack::Middleware::ReverseProxy (0.14) - 0.16 >>> - Plack::Middleware::LogWarn (0.001002) - 0.001002 >>> >>> I could not find any info in the Wiki about Plack other than the ~2017 >> Plack >>> page and a brief mention on >>> the Performance page . >> Is >>> there anything I need to do to enable it? >>> >>> Both old and new server have a single warning on the System information >> tab: >>> "System preference 'KohaAdminEmailAddress' does not contain a valid email >>> address. Emails will not be sent." >>> >>> Comparing the Server Information page for the old server (which is super >>> slow after the 21.05 upgrade but doesn't time out) with the new server >>> (which is super slow AND times out), the only differences are: >>> >>> - Minor Koha version (old server is 21.05.02.003, new server is >>> 21.05.03.001) >>> - Slightly different kernel release and version (old is >>> 5.4.0-84-generic, #94-Ubuntu; new is 5.4.0-81-generic, #91-Ubuntu) >>> - Different MySQL versions (old is "mysql Ver 15.1 Distrib >>> 10.3.31-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2", >> new is >>> "mysql Ver 8.0.26-0ubuntu0.20.04.2 for Linux on x86_64 ((Ubuntu))" >>> >>> Thanks so much for some additional places to look for issues! If >> something >>> in there gives a clue or if anyone has any other suggestions for things >> to >>> check I'm all ears! >>> >>> Matt >>> >>> On Mon, 13 Sept 2021 at 07:01, wrote: >>> >>>> Date: Sun, 12 Sep 2021 12:46:57 +0200 >>>> From: Katrin Fischer >>>> To: koha at lists.katipo.co.nz >>>> Subject: Re: [Koha] Batch check outs timing out after upgrade and >>>> migration >>>> Message-ID: <219ecc3c-ed9a-d27c-7074-962422505f80 at web.de> >>>> Content-Type: text/plain; charset=utf-8; format=flowed >>>> >>>> Hi Matthew, >>>> >>>> is there anything on the "About Koha" page that might give a clue? >>>> >>>> * Is Memcached running? >>>> * Is Plack configured and running? >>>> * Is there any error or warning displayed on the System information tab? >>>> >>>> Hope this helps, >>>> >>>> Katrin >>>> >>> _______________________________________________ >>> >>> 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 lennon at kohasupport.com Tue Sep 14 20:53:08 2021 From: lennon at kohasupport.com (Lennon Mazonde) Date: Tue, 14 Sep 2021 10:53:08 +0200 Subject: [Koha] Batch check outs timing out after upgrade and migration In-Reply-To: References:

<7e340723-ab6d-d615-280a-d2a1a73b2840@kohasupport.com> Message-ID: Are you getting any additional errors in your log files - esp. MySQL, Apache and Koha logs? I'm groping in the dark here but I wonder if you need change the limits in your apache2.conf (maybe increase your timeout value?) or increase the max input and execution time in php.ini? This sounds pretty basic but you could also try using a different browser after clearing your cache and cookies, and see if that makes a difference. 88 barcodes in batch checkout seems quite a lot to me, do you have the same issues when checking out fewer barcodes, e.g. 10? In your first email you said: > I fear our next best option might be to create a new (MariaDB) server from the original back ups and manually re-enter the past 4 days worth of borrowing and returns 😔 Have you considered setting up offline circulation so you can at least continue serving your patrons (I assume you're in a production environment) until you can resolve the issue? Lennon Mazonde www.kohasupport.com lennon at kohasupport.com WhatsApp @ (+1) 717.489.0195 On 9/14/21 10:02 AM, Matthew Lindfield Seager wrote: > Thanks Lennon! > > I enabled and started Plack (with one extra command needed): > > - sudo koha-plack --enable library > - sudo a2enmod headers proxy_http > - sudo koha-plack --start library > > After doing so I was hoping the problem would be magically* fixed but alas > batch check outs still aren't working reliably: > > - Choose a patron > - Switch to batch check out > - Paste in 88 barcodes > - Click "check out" > - Wait over 10 minutes for a "Gateway Timeout: The gateway did not > receive a timely response from the upstream server or application." > > While it was running I ran htop to see if memory or processor was causing a > bottleneck but neither processor was maxed out and the RAM was hovering > around 1.44G of 3.84G. > > My plan for tomorrow is to try profiling circulation.pl using > Devel::NYTProf ( > https://wiki.koha-community.org/wiki/Profiling_with_DevelNYTProf) and see > if that gives me any clues. > > Matt > > > > On Tue, 14 Sept 2021 at 14:10, Lennon Mazonde > wrote: > >> Hi Matthew, >> >> 1. To enable Plack you need to run >> >> sudo koha-plack --enable instancename >> >> then >> >> sudo koha-plack --start instancename >> >> 2. To resolve the admin email warning, go to Home > Administration > >> System preferences > Interface options > KohaAdminEmailAddress and enter >> your admin email. You may have to do some additional configuration on >> your back-end server to setup an email server such as Postfix to enable >> your Koha instance to send out emails. >> >> I hope this helps! >> >> -- >> Lennon Mazonde >> www.kohasupport.com >> lennon at kohasupport.com >> WhatsApp @ (+1) 717.489.0195 >> >> On 9/14/21 8:55 AM, Matthew Lindfield Seager wrote: >>> Hi Katrin, >>> >>> Memcached is installed and running according to the About Koha page. >>> Following the second lot of instructions at >>> https://wiki.koha-community.org/wiki/Troubleshooting_memcached I can see >>> that it has been handling requests. I also compared the old server (post >>> upgrade to 21.05) with the new server and both have the same >> configuration >>> in `/etc/memcached.conf`. According to the about page configuration is >>> coming from koha-conf.xml but I'm not sure where to find that file (and >> it >>> doesn't seem like Memcached is the culprit so I didn't bother installing >>> mlocate to find it). >>> >>> The only mentions of Plack I can see are on the Perl Modules info page: >>> >>> - Plack::Middleware::ReverseProxy (0.14) - 0.16 >>> - Plack::Middleware::LogWarn (0.001002) - 0.001002 >>> >>> I could not find any info in the Wiki about Plack other than the ~2017 >> Plack >>> page and a brief mention on >>> the Performance page . >> Is >>> there anything I need to do to enable it? >>> >>> Both old and new server have a single warning on the System information >> tab: >>> "System preference 'KohaAdminEmailAddress' does not contain a valid email >>> address. Emails will not be sent." >>> >>> Comparing the Server Information page for the old server (which is super >>> slow after the 21.05 upgrade but doesn't time out) with the new server >>> (which is super slow AND times out), the only differences are: >>> >>> - Minor Koha version (old server is 21.05.02.003, new server is >>> 21.05.03.001) >>> - Slightly different kernel release and version (old is >>> 5.4.0-84-generic, #94-Ubuntu; new is 5.4.0-81-generic, #91-Ubuntu) >>> - Different MySQL versions (old is "mysql Ver 15.1 Distrib >>> 10.3.31-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2", >> new is >>> "mysql Ver 8.0.26-0ubuntu0.20.04.2 for Linux on x86_64 ((Ubuntu))" >>> >>> Thanks so much for some additional places to look for issues! If >> something >>> in there gives a clue or if anyone has any other suggestions for things >> to >>> check I'm all ears! >>> >>> Matt >>> >>> On Mon, 13 Sept 2021 at 07:01, wrote: >>> >>>> Date: Sun, 12 Sep 2021 12:46:57 +0200 >>>> From: Katrin Fischer >>>> To: koha at lists.katipo.co.nz >>>> Subject: Re: [Koha] Batch check outs timing out after upgrade and >>>> migration >>>> Message-ID: <219ecc3c-ed9a-d27c-7074-962422505f80 at web.de> >>>> Content-Type: text/plain; charset=utf-8; format=flowed >>>> >>>> Hi Matthew, >>>> >>>> is there anything on the "About Koha" page that might give a clue? >>>> >>>> * Is Memcached running? >>>> * Is Plack configured and running? >>>> * Is there any error or warning displayed on the System information tab? >>>> >>>> Hope this helps, >>>> >>>> Katrin >>>> >>> _______________________________________________ >>> >>> 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 oleonard at myacpl.org Wed Sep 15 02:40:41 2021 From: oleonard at myacpl.org (Owen Leonard) Date: Tue, 14 Sep 2021 10:40:41 -0400 Subject: [Koha] Cannot see Google Login Link In-Reply-To: References:

Message-ID: > I agree that it would be much less confusing if the Google Login link is > located on the front page somewhere near the regular login. I have submitted a patch for this under Bug 29006, "Make GoogleOpenIDConnect options consistent in the OPAC" https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29006 I have also submitted a patch to add to the system preference description that it is only for the OPAC: Bug 29004, "Update GoogleOpenIDConnect preference to make it clear that it is OPAC-only" https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29004 > Ideally it would exist on both sites That would be ideal, but is a change large enough that it will probably have to be sponsored. -- Owen From mamcet.library10 at gmail.com Wed Sep 15 02:58:03 2021 From: mamcet.library10 at gmail.com (MASTeR Library) Date: Tue, 14 Sep 2021 20:28:03 +0530 Subject: [Koha] Unable to login in Web Installer 21.5 In-Reply-To: References:

Message-ID: Koha installation https://libpowertech.blogspot.com/2021/03/how-to-install-koha-on-ubuntu-mate-2004.html?m=1 On Tue, 14 Sep 2021, 12:52 pm Sebastian Krieg, < sebastian.krieg at tuz-eisenach.de> wrote: > Hello Sanjay, > > there are two ways: > > 1. Please login in a shell at your koha server, change to the superuser > 'root' and execute 'koha-passwd [libraryname]' where [libraryname] is the > given instance name during the installation. You will get the database > password for the instance user. Note, that the command will make a 'clear' > with next click. > > 2. Look into the file '/etc/koha/sites/[libraryname]/koha-conf.xml'. You > will get the informations about the instance user in line 270 and the > password in line 271. > > These are the login informations. > > Greets > > Sebastian > > > > --- > mailto: sebastian.krieg at tuz-eisenach.de > > 13. September 2021 19:06, "Sanjay Uchcharia" > schrieb: > > > Sir, > > > > I've installed Koha on Ubuntu 20.04 but I'm unable to login in Web > > Installer 21.5 with the username & password. > > _______________________________________________ > > > > 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 Wed Sep 15 04:43:23 2021 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Tue, 14 Sep 2021 18:43:23 +0200 Subject: [Koha] Unable to login in Web Installer 21.5 In-Reply-To: References:

Message-ID: Please link to the official Koha community documentation page when it's available. https://wiki.koha-community.org/wiki/Koha_on_Debian Le mar. 14 sept. 2021 à 16:58, MASTeR Library a écrit : > > Koha installation > https://libpowertech.blogspot.com/2021/03/how-to-install-koha-on-ubuntu-mate-2004.html?m=1 > > On Tue, 14 Sep 2021, 12:52 pm Sebastian Krieg, < > sebastian.krieg at tuz-eisenach.de> wrote: > > > Hello Sanjay, > > > > there are two ways: > > > > 1. Please login in a shell at your koha server, change to the superuser > > 'root' and execute 'koha-passwd [libraryname]' where [libraryname] is the > > given instance name during the installation. You will get the database > > password for the instance user. Note, that the command will make a 'clear' > > with next click. > > > > 2. Look into the file '/etc/koha/sites/[libraryname]/koha-conf.xml'. You > > will get the informations about the instance user in line 270 and the > > password in line 271. > > > > These are the login informations. > > > > Greets > > > > Sebastian > > > > > > > > --- > > mailto: sebastian.krieg at tuz-eisenach.de > > > > 13. September 2021 19:06, "Sanjay Uchcharia" > > schrieb: > > > > > Sir, > > > > > > I've installed Koha on Ubuntu 20.04 but I'm unable to login in Web > > > Installer 21.5 with the username & password. > > > _______________________________________________ > > > > > > 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 mrosu at rschicago.org Wed Sep 15 05:40:46 2021 From: mrosu at rschicago.org (Mihai Rosu) Date: Tue, 14 Sep 2021 12:40:46 -0500 Subject: [Koha] Cannot see Google Login Link In-Reply-To: References:

Message-ID: Ahh I see, well thank you very much for all your assistance! Now I understand the situation much better. We'll stick with local accounts for staff. Mihai Rosu Rudolf Steiner Branch Chicago 4249 N. Lincoln Ave Chicago, IL 60618-1953 mrosu at rschicago.org 773.562.6254 www.rschicago.org On Tue, Sep 14, 2021 at 9:40 AM Owen Leonard wrote: > > I agree that it would be much less confusing if the Google Login link is > > located on the front page somewhere near the regular login. > > I have submitted a patch for this under Bug 29006, "Make > GoogleOpenIDConnect options consistent in the OPAC" > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29006 > > I have also submitted a patch to add to the system preference > description that it is only for the OPAC: Bug 29004, "Update > GoogleOpenIDConnect preference to make it clear that it is OPAC-only" > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29004 > > > Ideally it would exist on both sites > > That would be ideal, but is a change large enough that it will > probably have to be sponsored. > > -- Owen > From stevenanickerson at gmail.com Wed Sep 15 06:28:25 2021 From: stevenanickerson at gmail.com (Steve Nickerson) Date: Tue, 14 Sep 2021 14:28:25 -0400 Subject: [Koha] Upgrading from 17.05.00.00 to "current" Message-ID: <146101d7a996$4ed4b3b0$ec7e1b10$@gmail.com> Does anyone have any tips on how to successfully go from Koha 17.05 to anything more current on Debian 8 (Jessie) package install? I've tried the process I've used in the past and the other OS packages upgrade but Koha keeps getting "held back" no matter what I've tried (various 'koha.list' sources, apt-get full-upgrade, apt-get dist-upgrade, etc.). What is the latest version that will run on Debian 8 and what should I put in my koha.list source file? Thanks! Steve From JBoyer at equinoxOLI.org Wed Sep 15 06:44:24 2021 From: JBoyer at equinoxOLI.org (Jason Boyer) Date: Tue, 14 Sep 2021 14:44:24 -0400 Subject: [Koha] Upgrading from 17.05.00.00 to "current" In-Reply-To: <146101d7a996$4ed4b3b0$ec7e1b10$@gmail.com> References: <146101d7a996$4ed4b3b0$ec7e1b10$@gmail.com> Message-ID: Hi Steve, koha-common and associated packages won’t be upgraded on regular apt-get (dist-)upgrade. Once your regular OS packages are up to date you can upgrade koha with 'apt-get install koha-common' to install the version pointed to by your koha.list file. I’m not sure what the latest supported version on Jessie is, but you likely should specify a specific version in your koha.list rather than using “current". Jason -- Jason Boyer Senior System Administrator Equinox Open Library Initiative JBoyer at equinoxOLI.org +1 (877) Open-ILS (673-6457) https://equinoxOLI.org/ > On Sep 14, 2021, at 2:28 PM, Steve Nickerson wrote: > > Does anyone have any tips on how to successfully go from Koha 17.05 to > anything more current on Debian 8 (Jessie) package install? I've tried the > process I've used in the past and the other OS packages upgrade but Koha > keeps getting "held back" no matter what I've tried (various 'koha.list' > sources, apt-get full-upgrade, apt-get dist-upgrade, etc.). What is the > latest version that will run on Debian 8 and what should I put in my > koha.list source file? > > > > Thanks! > > Steve > > _______________________________________________ > > 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 Wed Sep 15 09:23:55 2021 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Tue, 14 Sep 2021 23:23:55 +0200 Subject: [Koha] How to make the Price field visible in the OPAC normal view. In-Reply-To: <9b24238615df6a824e1411c8a4c00f44@penkler.net> References: <0151b74c5ad3ed6f5004ccda527f5df0@penkler.net> <5cc46e37-467b-4080-94ab-5d78f43df6e6@web.de> <9b24238615df6a824e1411c8a4c00f44@penkler.net> Message-ID: <659e9fd6-16f5-bd8b-270c-fbc1aee95a4b@web.de> Hi David, I believe currently copying from one field into another is not an option with the batch edit tool for items. Katrin On 14.09.21 09:38, david at penkler.net wrote: > Hi Katrin, > Thank you very much for the suggestion to use the item_notes field. > That works perfectly for our needs. > Is there a way to use the batch operations to add the note from the > items.price field ? > Many thanks, > -David > > On 2021-09-12 12:48, Katrin Fischer wrote: >> Hi David, >> >> welcome! >> >> Currently it's not possible to make the Price field visible in the OPAC >> normal view. If you go to Administration > Table settings > OPAC > >> holdingst you can see all columns that can be made visible/be hidden >> from the table. >> >> Maybe putting/copying the price to OPAC note (item_notes) could work for >> your use case? >> >> Hope this helps, >> >> Katrin From bibliwho at gmail.com Wed Sep 15 19:07:46 2021 From: bibliwho at gmail.com (Cab Vinton) Date: Wed, 15 Sep 2021 03:07:46 -0400 Subject: [Koha] How to make the Price field visible in the OPAC normal view. In-Reply-To: <659e9fd6-16f5-bd8b-270c-fbc1aee95a4b@web.de> References: <0151b74c5ad3ed6f5004ccda527f5df0@penkler.net> <5cc46e37-467b-4080-94ab-5d78f43df6e6@web.de> <9b24238615df6a824e1411c8a4c00f44@penkler.net> <659e9fd6-16f5-bd8b-270c-fbc1aee95a4b@web.de> Message-ID: >> Is there a way to use the batch operations to add the note from the items.price field ? This would work w/ the Batch record modification tool if it had access to the 952 tag & subfields. Unfortunately, it doesn't, at least in 20.05. Perhaps a good enhancement for down the road? This type of operation is trivial using a tool such as MarcEdit, though. Exporting & re-importing is obviously less time-consuming w/ smaller catalogs. All best, Cab Vinton, Director Plaistow Public Library Plaistow, NH From mtj at kohaaloha.com Thu Sep 16 00:10:07 2021 From: mtj at kohaaloha.com (Mason James) Date: Thu, 16 Sep 2021 00:10:07 +1200 Subject: [Koha] Upgrading from 17.05.00.00 to "current" In-Reply-To: <146101d7a996$4ed4b3b0$ec7e1b10$@gmail.com> References: <146101d7a996$4ed4b3b0$ec7e1b10$@gmail.com> Message-ID: |hi ||Steve the 19.11 series is still supported on jessie the following apt line should get you the latest 19.11.x release (||||currently koha 19.11.21) ||echo "deb http://debian.koha-community.org/koha 19.11 main jessie" > /etc/apt/sources.list.d/koha.list more info... https://wiki.koha-community.org/wiki/Koha_on_Debian ||cheers, Mason ||||| On 15/09/21 6:28 am, Steve Nickerson wrote: > Does anyone have any tips on how to successfully go from Koha 17.05 to > anything more current on Debian 8 (Jessie) package install? I've tried the > process I've used in the past and the other OS packages upgrade but Koha > keeps getting "held back" no matter what I've tried (various 'koha.list' > sources, apt-get full-upgrade, apt-get dist-upgrade, etc.). What is the > latest version that will run on Debian 8 and what should I put in my > koha.list source file? > > > > Thanks! > > Steve > > _______________________________________________ > > 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 Sep 16 11:04:26 2021 From: cmkelleymls at gmail.com (Charles Kelley) Date: Thu, 16 Sep 2021 08:04:26 +0900 Subject: [Koha] How to Update and Upgrade Koha Message-ID: Hi, all! I think I have asked about this before, but I don't recall getting a definitive answer. But it's awhile, so here goes. I have seen announcements about updates and upgrades to Koha. ("Come and get it!") Alas, I don't find instructions for installing updates and upgrades. There are initial installation instructions aplenty, but alas, if there are ones for updates and upgrades, I don't see them. So I ask: How does one update or upgrades Koha? Thanks for your help, everyone. -- 気を付けて。 /ki wo tukete/ = Take care. -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk at aol.com [h] cmkelleymls at gmail.com [p] linkedin.com/in/cmkelleymls Meeting Your Information Needs. Virtually. From cacho at genac.org Thu Sep 16 11:25:40 2021 From: cacho at genac.org (Hector Gonzalez Jaime) Date: Wed, 15 Sep 2021 18:25:40 -0500 Subject: [Koha] How to Update and Upgrade Koha In-Reply-To: References: Message-ID: Hi, as with anything else, you should first have a good (tested) backup of everything. Koha, server software, and database. Then, if you used the debian packages, you should check which version you are "tracking", something like: grep -Ri koha /etc/apt/* would return something like: /etc/apt/sources.list.d/koha.list:deb http://debian.koha-community.org/koha 19.11 main That means there is a file /etc/apt/sources.list.d/koha.list which you should edit and change to the version you want to track now. The content of the file would be: deb http://debian.koha-community.org/koha 21.05 main if you want to track koha 21.05 Then you would: apt-get update apt-get upgrade and it should do the upgrade. With the following exception, if apt-get upgrade says it would need to update mariadb-server or mysql-server, then you should upgrade that first and separately, like this: apt-get update apt-get install mariadb-server-10.3 apt-get upgrade If you don't upgrade mariadb first, it will be DOWN when koha wants to upgrade the database, leaving you with a half upgraded system. (And using that backup). Hope this helps. On 9/15/21 6:04 PM, Charles Kelley wrote: > Hi, all! > > I think I have asked about this before, but I don't recall getting a > definitive answer. But it's awhile, so here goes. > > I have seen announcements about updates and upgrades to Koha. ("Come > and get it!") Alas, I don't find instructions for installing updates and > upgrades. There are initial installation instructions aplenty, but alas, if > there are ones for updates and upgrades, I don't see them. So I ask: > > How does one update or upgrades Koha? > > Thanks for your help, everyone. > -- Hector Gonzalez cacho at genac.org From cacho at genac.org Thu Sep 16 11:44:58 2021 From: cacho at genac.org (Hector Gonzalez Jaime) Date: Wed, 15 Sep 2021 18:44:58 -0500 Subject: [Koha] How to Update and Upgrade Koha In-Reply-To: References:

Message-ID: I forgot something, if koha requires additional software to be installed, when you run apt-get upgrade it will say something like this: The following packages have been kept back: koha-common In this case, you will need to do: apt-get dist-upgrade which will install the needed packages and then it will upgrade koha. On 9/15/21 6:25 PM, Hector Gonzalez Jaime wrote: > Hi, as with anything else, you should first have a good (tested) > backup of everything. Koha, server software, and database. > > Then, if you used the debian packages, you should check which version > you are "tracking", something like: > > grep -Ri koha /etc/apt/* > > would return something like: > > /etc/apt/sources.list.d/koha.list:deb > http://debian.koha-community.org/koha 19.11 main > > That means there is a file /etc/apt/sources.list.d/koha.list which you > should edit and change to the version you want to track now. The > content of the file would be: > > deb http://debian.koha-community.org/koha 21.05 main > > if you want to track koha 21.05 > > Then you would: > > apt-get update > apt-get upgrade > > and it should do the upgrade. With the following exception, if > apt-get upgrade says it would need to update mariadb-server or > mysql-server, then you should upgrade that first and separately, like > this: > > apt-get update > apt-get install mariadb-server-10.3 > apt-get upgrade > > If you don't upgrade mariadb first, it will be DOWN when koha wants to > upgrade the database, leaving you with a half upgraded system. (And > using that backup). > > Hope this helps. > > On 9/15/21 6:04 PM, Charles Kelley wrote: >> Hi, all! >> >> I think I have asked about this before, but I don't recall >> getting a >> definitive answer. But it's awhile, so here goes. >> >> I have seen announcements about updates and upgrades to Koha. >> ("Come >> and get it!") Alas, I don't find instructions for installing updates and >> upgrades. There are initial installation instructions aplenty, but >> alas, if >> there are ones for updates and upgrades, I don't see them. So I ask: >> >> How does one update or upgrades Koha? >> >> Thanks for your help, everyone. >> -- Hector Gonzalez cacho at genac.org From cmkelleymls at gmail.com Thu Sep 16 12:49:42 2021 From: cmkelleymls at gmail.com (Charles Kelley) Date: Thu, 16 Sep 2021 09:49:42 +0900 Subject: [Koha] =?utf-8?q?=E2=80=8BHow_to_Update_and_Upgrade_Koha?= Message-ID: Hello, all! In our latest exchange, on 16 Sept. 2021 at 09:00 [JST], I received the following from Hector Gonzalez Jaime : [Originally 15 Sept. 2021 at 18:25]: Hi, as with anything else, you should first have a good (tested) backup of > everything. Koha, server software, and database. > > Then, if you used the debian packages, you should check which version you > are "tracking", something like: > > grep -Ri koha /etc/apt/* > > would return something like: > > /etc/apt/sources.list.d/koha.list:deb > http://debian.koha-community.org/koha 19.11 main > > That means there is a file /etc/apt/sources.list.d/koha.list which you > should edit and change to the version you want to track now. The content > of the file would be: > > deb http://debian.koha-community.org/koha 21.05 main > > if you want to track koha 21.05 > > Then you would: > > apt-get update > apt-get upgrade > > and it should do the upgrade. With the following exception, if apt-get > upgrade says it would need to update mariadb-server or mysql-server, then > you should upgrade that first and separately, like this: > > apt-get update > apt-get install mariadb-server-10.3 > apt-get upgrade > > If you don't upgrade mariadb first, it will be DOWN when koha wants to > upgrade the database, leaving you with a half upgraded system. (And using > that backup). > > Hope this helps. > [A few minutes later, at 18:44, he sent this:] I forgot something, if koha requires additional software to be installed, > when you run apt-get upgrade it will say something like this: > > The following packages have been kept back: > koha-common > > In this case, you will need to do: > > apt-get dist-upgrade > > which will install the needed packages and then it will upgrade koha. > Many thanks! This will help enormously. We will be upgrading on a test/demonstration/development machine before we do so to the production machine. I've been involved in upgrades and updates of too many other software packages to know not to do so on the production machine right off. Only after the staff are satisfied that the test machine functions properly is the production machine updated or upgraded. Thanks again! -- 気を付けて。 /ki wo tukete/ = Take care. -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk at aol.com [h] cmkelleymls at gmail.com [p] linkedin.com/in/cmkelleymls Meeting Your Information Needs. Virtually. From cmkelleymls at gmail.com Thu Sep 16 13:37:11 2021 From: cmkelleymls at gmail.com (Charles Kelley) Date: Thu, 16 Sep 2021 10:37:11 +0900 Subject: [Koha] Open Ended Due Dates, Permanent Loans, Etc. Message-ID: Hi, all! Is there a way to make an open ended due date? That is, if a person checks out a book, Koha does not assign a due date, *per se*, rather it merely marks it checked-out. I guess this be might be considered a permanent or semi-permanent loan but it would not be a transfer. Mind you, if a patron puts a hold on such a book, the patron who checked out the book would have to surrender it. The book would still be one of the library's holdings so that the library can avail it to the patrons and track it for property management reasons. (The OPAC would list it only *CHECKED OUT* or *BORROWED*.) Mind you, I am trying to avoid a proliferation and plethora of LOCs and CCODEs. I know this is a nightmare and it defeats the purpose of a library of shareable works. It would be rarely used, of course, but I can imagine a scenario in which it would arise. Many thanks, all! -- 気を付けて。 /ki wo tukete/ = Take care. -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk at aol.com [h] cmkelleymls at gmail.com [p] linkedin.com/in/cmkelleymls Meeting Your Information Needs. Virtually. From mtj at kohaaloha.com Thu Sep 16 15:37:23 2021 From: mtj at kohaaloha.com (Mason James) Date: Thu, 16 Sep 2021 15:37:23 +1200 Subject: [Koha] Upgrading from 17.05.00.00 to "current" In-Reply-To: References: <146101d7a996$4ed4b3b0$ec7e1b10$@gmail.com> Message-ID: <99dc19f4-39e4-46fe-5a9a-65662b2c2720@kohaaloha.com> oops, that apt line should be echo "deb http://debian.koha-community.org/koha 19.11 main jessie" > /etc/apt/sources.list.d/koha.list On 16/09/21 12:10 am, Mason James wrote: > |hi ||Steve > the 19.11 series is still supported on jessie > > the following apt line should get you the latest 19.11.x release (||||currently koha 19.11.21) > ||echo "deb http://debian.koha-community.org/koha 19.11 main jessie" > /etc/apt/sources.list.d/koha.list > > more info... > https://wiki.koha-community.org/wiki/Koha_on_Debian > > > ||cheers, Mason > > ||||| > On 15/09/21 6:28 am, Steve Nickerson wrote: >> Does anyone have any tips on how to successfully go from Koha 17.05 to >> anything more current on Debian 8 (Jessie) package install? I've tried the >> process I've used in the past and the other OS packages upgrade but Koha >> keeps getting "held back" no matter what I've tried (various 'koha.list' >> sources, apt-get full-upgrade, apt-get dist-upgrade, etc.). What is the >> latest version that will run on Debian 8 and what should I put in my >> koha.list source file? >> >> >> Thanks! >> >> Steve >> >> _______________________________________________ >> >> 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 Thu Sep 16 19:50:06 2021 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Wed, 15 Sep 2021 21:50:06 -1000 Subject: [Koha] Time to translate: string freeze to prepare 20.11.10 release Message-ID: Hi, String freeze is into effect 🥶 The 20.11.x maintenance branch is preparing for 20.11.10 release 📦 This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Keep in mind that translations must be done with priority on higher version 21.05 🔥 Happy translating 🌎🌍🌏 -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From caroline.cyr-la-rose at inlibro.com Fri Sep 17 00:56:39 2021 From: caroline.cyr-la-rose at inlibro.com (Caroline Cyr-La-Rose) Date: Thu, 16 Sep 2021 08:56:39 -0400 Subject: [Koha] Open Ended Due Dates, Permanent Loans, Etc. In-Reply-To: References: Message-ID: Hi Charles, Maybe you could do something like that with automatic renewals? In circulation rules, you could have a "regular" loan period, but many renewals, e.g. 99. Set up automatic renewals. Koha will renew automatically, as long as the item is not on hold, the patron's membership is not expired, etc. Caroline On 2021-09-15 21 h 37, Charles Kelley wrote: > Hi, all! > > Is there a way to make an open ended due date? That is, if a person > checks out a book, Koha does not assign a due date, *per se*, rather it > merely marks it checked-out. I guess this be might be considered a > permanent or semi-permanent loan but it would not be a transfer. > > Mind you, if a patron puts a hold on such a book, the patron who > checked out the book would have to surrender it. The book would still be > one of the library's holdings so that the library can avail it to the > patrons and track it for property management reasons. > > (The OPAC would list it only *CHECKED OUT* or *BORROWED*.) > > Mind you, I am trying to avoid a proliferation and plethora of LOCs and > CCODEs. > > I know this is a nightmare and it defeats the purpose of a library of > shareable works. It would be rarely used, of course, but I can imagine a > scenario in which it would arise. > > Many thanks, all! > 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 Technology Specialists | www.inLibro.com From tasha.r.bales at boeing.com Fri Sep 17 06:48:44 2021 From: tasha.r.bales at boeing.com (Bales (US), Tasha R) Date: Thu, 16 Sep 2021 18:48:44 +0000 Subject: [Koha] JSON report only contains partial results Message-ID: <52edc8b1786d4f9ebe44923c4e049921@boeing.com> Any idea why my public report would return almost 2000 results, but the JSON URL for that report (accessed right after I ran the report), would only display a list of 9 results? I've tried reindexing to no avail. I've also tried duplicating and rerunning the report, as well as changing the report category back to "Cataloging" instead of the custom category I'd added. In my initial experimentation with reports and their JSON URL's, everything worked perfectly. Now, besides the above, I'm noticing odd behavior with the "&annotated=1" parameter, in that if I access the annotated report, then subsequently strip off that parameter and navigate again to the report, the output is still annotated. I attributed this to caching, but I get this behavior even if I try to access the not annotated URL in a different browser. That doesn't seem possible; I presume there is something about JSON I just don't understand. Tasha Bales Enterprise Services http://isesi.web.boeing.com/ From cornejo.alvaro at gmail.com Fri Sep 17 07:11:06 2021 From: cornejo.alvaro at gmail.com (Alvaro Cornejo) Date: Thu, 16 Sep 2021 14:11:06 -0500 Subject: [Koha] JSON report only contains partial results In-Reply-To: <52edc8b1786d4f9ebe44923c4e049921@boeing.com> References: <52edc8b1786d4f9ebe44923c4e049921@boeing.com> Message-ID: Hi Tasha This is because public reports default to 10 results. If you need more lines, you should add "LIMIT xxxx" to the end of your query. Where xxx is the maximum lines you want to get. 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. 16 sept. 2021 à 13:49, Bales (US), Tasha R a écrit : > Any idea why my public report would return almost 2000 results, but the > JSON URL for that report (accessed right after I ran the report), would > only display a list of 9 results? > > I've tried reindexing to no avail. I've also tried duplicating and > rerunning the report, as well as changing the report category back to > "Cataloging" instead of the custom category I'd added. > > In my initial experimentation with reports and their JSON URL's, > everything worked perfectly. Now, besides the above, I'm noticing odd > behavior with the "&annotated=1" parameter, in that if I access the > annotated report, then subsequently strip off that parameter and navigate > again to the report, the output is still annotated. I attributed this to > caching, but I get this behavior even if I try to access the not annotated > URL in a different browser. That doesn't seem possible; I presume there is > something about JSON I just don't understand. > > > Tasha Bales > Enterprise Services > http://isesi.web.boeing.com/ > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From tasha.r.bales at boeing.com Fri Sep 17 08:06:43 2021 From: tasha.r.bales at boeing.com (Bales (US), Tasha R) Date: Thu, 16 Sep 2021 20:06:43 +0000 Subject: [Koha] [EXTERNAL] Re: JSON report only contains partial results In-Reply-To: References: <52edc8b1786d4f9ebe44923c4e049921@boeing.com> Message-ID: <6bdcb5b78fca4a79a6fdf0d0a839fc1e@boeing.com> Alvaro, thank you so much! Adding the LIMIT fixed my issue. Tasha Bales Enterprise Services http://isesi.web.boeing.com/ From: Alvaro Cornejo [mailto:cornejo.alvaro at gmail.com] Sent: Thursday, September 16, 2021 12:11 To: Bales (US), Tasha R Cc: koha at lists.katipo.co.nz Subject: [EXTERNAL] Re: [Koha] JSON report only contains partial results Importance: High EXT email: be mindful of links/attachments. Hi Tasha This is because public reports default to 10 results. If you need more lines, you should add "LIMIT xxxx" to the end of your query. Where xxx is the maximum lines you want to get. Regards, Alvaro |----------------------------------------------------------------------------------------| [https://drive.google.com/uc?id=1lpgSKUunPpKrvmS1rja7umnEgiqBa_vD&export=download] 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. 16 sept. 2021 à 13:49, Bales (US), Tasha R > a écrit : Any idea why my public report would return almost 2000 results, but the JSON URL for that report (accessed right after I ran the report), would only display a list of 9 results? I've tried reindexing to no avail. I've also tried duplicating and rerunning the report, as well as changing the report category back to "Cataloging" instead of the custom category I'd added. In my initial experimentation with reports and their JSON URL's, everything worked perfectly. Now, besides the above, I'm noticing odd behavior with the "&annotated=1" parameter, in that if I access the annotated report, then subsequently strip off that parameter and navigate again to the report, the output is still annotated. I attributed this to caching, but I get this behavior even if I try to access the not annotated URL in a different browser. That doesn't seem possible; I presume there is something about JSON I just don't understand. Tasha Bales Enterprise Services http://isesi.web.boeing.com/ _______________________________________________ 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 Fri Sep 17 10:22:50 2021 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Fri, 17 Sep 2021 00:22:50 +0200 Subject: [Koha] Time to translate: string freeze to prepare Koha 20.05.16 has begun Message-ID: Hi, saluton, hola, bonjour, String freeze is into effect as of now for the 20.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 20.05, then you must also copy it to 20.11 and 21.05. Otherwise your work will be lost for future versions. Happy translating :) -- Victor Grousset/tuxayo From ephetteplace at cca.edu Fri Sep 17 12:18:36 2021 From: ephetteplace at cca.edu (Eric Phetteplace) Date: Thu, 16 Sep 2021 17:18:36 -0700 Subject: [Koha] [EXTERNAL] Re: JSON report only contains partial results In-Reply-To: <6bdcb5b78fca4a79a6fdf0d0a839fc1e@boeing.com> References: <52edc8b1786d4f9ebe44923c4e049921@boeing.com> <6bdcb5b78fca4a79a6fdf0d0a839fc1e@boeing.com> Message-ID: Hi all, Is this true about the limit of 10 for public report results? Is it documented somewhere? I don't see a mention of it in the manual . We use public reports in a couple of integrations and I've never noticed a limit. I tested just now and was able to over a thousand rows in a public report with no LIMIT statement. I'm just worried that one day my integrations are going to break because of this but right now we're definitely not seeing a limit, or if there is one it's much larger than 10. 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, Sep 16, 2021 at 1:07 PM Bales (US), Tasha R < tasha.r.bales at boeing.com> wrote: > Alvaro, thank you so much! Adding the LIMIT fixed my issue. > > Tasha Bales > Enterprise Services > http://isesi.web.boeing.com/ > > From: Alvaro Cornejo [mailto:cornejo.alvaro at gmail.com] > Sent: Thursday, September 16, 2021 12:11 > To: Bales (US), Tasha R > Cc: koha at lists.katipo.co.nz > Subject: [EXTERNAL] Re: [Koha] JSON report only contains partial results > Importance: High > > > EXT email: be mindful of links/attachments. > > > > > Hi Tasha > > This is because public reports default to 10 results. > > If you need more lines, you should add "LIMIT xxxx" to the end of your > query. Where xxx is the maximum lines you want to get. > > Regards, > > Alvaro > > |----------------------------------------------------------------------------------------| > [ > https://drive.google.com/uc?id=1lpgSKUunPpKrvmS1rja7umnEgiqBa_vD&export=download] > 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. 16 sept. 2021 à 13:49, Bales (US), Tasha R < > tasha.r.bales at boeing.com> a écrit : > Any idea why my public report would return almost 2000 results, but the > JSON URL for that report (accessed right after I ran the report), would > only display a list of 9 results? > > I've tried reindexing to no avail. I've also tried duplicating and > rerunning the report, as well as changing the report category back to > "Cataloging" instead of the custom category I'd added. > > In my initial experimentation with reports and their JSON URL's, > everything worked perfectly. Now, besides the above, I'm noticing odd > behavior with the "&annotated=1" parameter, in that if I access the > annotated report, then subsequently strip off that parameter and navigate > again to the report, the output is still annotated. I attributed this to > caching, but I get this behavior even if I try to access the not annotated > URL in a different browser. That doesn't seem possible; I presume there is > something about JSON I just don't understand. > > > Tasha Bales > Enterprise Services > http://isesi.web.boeing.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 cmkelleymls at gmail.com Fri Sep 17 16:23:33 2021 From: cmkelleymls at gmail.com (Charles Kelley) Date: Fri, 17 Sep 2021 13:23:33 +0900 Subject: [Koha] Open Ended Due Dates, Permanent Loans, Etc. In-Reply-To: References: Message-ID: Hello, Caroline! In our latest exchange, on 17 Sept. 2021 at 09:01 [JST], I received the following from you through the Koha Digest, to wit: Maybe you could do something like that with automatic renewals? > > In circulation rules, you could have a "regular" loan period, but many > renewals, e.g. 99. > > Set up automatic renewals. Koha will renew automatically, as long as the > item is not on hold, the patron's membership is not expired, etc. > What an excellent idea! Thanks for the suggestion! -- 気を付けて。 /ki wo tukete/ = Take care. -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk at aol.com [h] cmkelleymls at gmail.com [p] linkedin.com/in/cmkelleymls Meeting Your Information Needs. Virtually. From katrin.fischer.83 at web.de Sat Sep 18 21:09:13 2021 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sat, 18 Sep 2021 11:09:13 +0200 Subject: [Koha] JSON report only contains partial results In-Reply-To: <52edc8b1786d4f9ebe44923c4e049921@boeing.com> References: <52edc8b1786d4f9ebe44923c4e049921@boeing.com> Message-ID: <27abddde-034f-6a87-b9ac-e56719c6872c@web.de> Hi Tasha, the caching is done server side, so switching the browser would not make a difference. Try reducing the time the results are cached maybe. There is also a limit on how many results the JSON reports will show. This is set by the SvcMaxreportRows system preference. The default is 10 so that can also explain surprising results. I think changing the LIMIT is just a way to overwrite that preference, so you could do that for individual reports or up the global limit. Hope that helps, Katrin | | On 16.09.21 20:48, Bales (US), Tasha R wrote: > Any idea why my public report would return almost 2000 results, but the JSON URL for that report (accessed right after I ran the report), would only display a list of 9 results? > > I've tried reindexing to no avail. I've also tried duplicating and rerunning the report, as well as changing the report category back to "Cataloging" instead of the custom category I'd added. > > In my initial experimentation with reports and their JSON URL's, everything worked perfectly. Now, besides the above, I'm noticing odd behavior with the "&annotated=1" parameter, in that if I access the annotated report, then subsequently strip off that parameter and navigate again to the report, the output is still annotated. I attributed this to caching, but I get this behavior even if I try to access the not annotated URL in a different browser. That doesn't seem possible; I presume there is something about JSON I just don't understand. > > > Tasha Bales > Enterprise Services > http://isesi.web.boeing.com/ > > _______________________________________________ > > 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 Sep 20 21:47:00 2021 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Mon, 20 Sep 2021 11:47:00 +0200 Subject: [Koha] How to Update and Upgrade Koha In-Reply-To: References:

Message-ID: Hi Hector, Well detailed instructions, it would help to have them on the wiki page :) Would you mind updating the existing section? https://wiki.koha-community.org/wiki/Koha_on_Debian#Upgrade Le jeu. 16 sept. 2021 à 01:44, Hector Gonzalez Jaime a écrit : > > I forgot something, if koha requires additional software to be > installed, when you run apt-get upgrade it will say something like this: > > The following packages have been kept back: > koha-common > > In this case, you will need to do: > > apt-get dist-upgrade > > which will install the needed packages and then it will upgrade koha. > > > On 9/15/21 6:25 PM, Hector Gonzalez Jaime wrote: > > Hi, as with anything else, you should first have a good (tested) > > backup of everything. Koha, server software, and database. > > > > Then, if you used the debian packages, you should check which version > > you are "tracking", something like: > > > > grep -Ri koha /etc/apt/* > > > > would return something like: > > > > /etc/apt/sources.list.d/koha.list:deb > > http://debian.koha-community.org/koha 19.11 main > > > > That means there is a file /etc/apt/sources.list.d/koha.list which you > > should edit and change to the version you want to track now. The > > content of the file would be: > > > > deb http://debian.koha-community.org/koha 21.05 main > > > > if you want to track koha 21.05 > > > > Then you would: > > > > apt-get update > > apt-get upgrade > > > > and it should do the upgrade. With the following exception, if > > apt-get upgrade says it would need to update mariadb-server or > > mysql-server, then you should upgrade that first and separately, like > > this: > > > > apt-get update > > apt-get install mariadb-server-10.3 > > apt-get upgrade > > > > If you don't upgrade mariadb first, it will be DOWN when koha wants to > > upgrade the database, leaving you with a half upgraded system. (And > > using that backup). > > > > Hope this helps. > > > > On 9/15/21 6:04 PM, Charles Kelley wrote: > >> Hi, all! > >> > >> I think I have asked about this before, but I don't recall > >> getting a > >> definitive answer. But it's awhile, so here goes. > >> > >> I have seen announcements about updates and upgrades to Koha. > >> ("Come > >> and get it!") Alas, I don't find instructions for installing updates and > >> upgrades. There are initial installation instructions aplenty, but > >> alas, if > >> there are ones for updates and upgrades, I don't see them. So I ask: > >> > >> How does one update or upgrades Koha? > >> > >> Thanks for your help, everyone. > >> > -- > Hector Gonzalez > cacho at genac.org > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From tasha.r.bales at boeing.com Tue Sep 21 01:41:22 2021 From: tasha.r.bales at boeing.com (Bales (US), Tasha R) Date: Mon, 20 Sep 2021 13:41:22 +0000 Subject: [Koha] Conference registration, who to contact for help? Message-ID: Good morning, I registered for the virtual conference and received a confirmation from the Google from. However, I never received a payment link, or materials indicating how to attend the conference. On my end, the Koha US site appears to be down at the moment. Although this isn't a technical question, I'm writing in hopes someone might know of the proper avenue to get help with conference registration follow-up. Thank you! Tasha Bales Enterprise Services http://isesi.web.boeing.com/ From Heather_Hernandez at nps.gov Tue Sep 21 03:34:44 2021 From: Heather_Hernandez at nps.gov (Hernandez, Heather H) Date: Mon, 20 Sep 2021 15:34:44 +0000 Subject: [Koha] Conference registration, who to contact for help? In-Reply-To: References: Message-ID: Hi, Tasha-- The Koha-US Conference is going to be livestreamed via YouTube, e.g. here: https://youtu.be/H5HshJDn8GU Attending remotely is free, but registering as a remote attendee is appreciated, I believe, because it helps the planning. And you could probably get some assistance via info at koha-us.org or secretary at koha-us.org. (Yes, the Koha-US website seems down right now.) Cheers, h2 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ms. Heather Hernandez (she, her, hers) Technical Services Librarian San Francisco Maritime National Historical Park Research Center 2 Marina Blvd., Bldg. E, 3rd floor, San Francisco, CA 94123-1284 415-561-7032, heather_hernandez at nps.gov Library catalog: http://keys.bywatersolutions.com/ From jzairo at bywatersolutions.com Tue Sep 21 04:11:45 2021 From: jzairo at bywatersolutions.com (Jessica Zairo) Date: Mon, 20 Sep 2021 12:11:45 -0400 Subject: [Koha] Conference registration, who to contact for help? In-Reply-To: References: Message-ID: Hi Tasha, Here's an alternate link to the schedule: https://docs.google.com/spreadsheets/d/1sbJJgo1DTZsnMftH2_hae7uzqHz3JaEQiK9sKzbqTiM/edit?usp=sharing The site should be back up shortly. Jessie > On Sep 20, 2021, at 9:42 AM, Bales (US), Tasha R wrote: > > Good morning, > > I registered for the virtual conference and received a confirmation from the Google from. However, I never received a payment link, or materials indicating how to attend the conference. On my end, the Koha US site appears to be down at the moment. > > Although this isn't a technical question, I'm writing in hopes someone might know of the proper avenue to get help with conference registration follow-up. > > Thank you! > > > Tasha Bales > Enterprise Services > http://isesi.web.boeing.com/ > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha From tasha.r.bales at boeing.com Tue Sep 21 04:30:39 2021 From: tasha.r.bales at boeing.com (Bales (US), Tasha R) Date: Mon, 20 Sep 2021 16:30:39 +0000 Subject: [Koha] Conference registration, who to contact for help? In-Reply-To: References: Message-ID: <281e48de824644478492a6c8f78db759@boeing.com> Thank you very much to those who replied. It had not been clear to me that attendance was free. I've since received a follow-up email with more information about the channels for each track. Please pardon my ignorance. Tasha Bales Enterprise Services http://isesi.web.boeing.com/ From: Hernandez, Heather H [mailto:Heather_Hernandez at nps.gov] Sent: Monday, September 20, 2021 08:35 To: Bales (US), Tasha R ; koha at lists.katipo.co.nz Subject: [EXTERNAL] Re: [Koha] Conference registration, who to contact for help? Importance: High EXT email: be mindful of links/attachments. Hi, Tasha-- The Koha-US Conference is going to be livestreamed via YouTube, e.g. here: https://youtu.be/H5HshJDn8GU Attending remotely is free, but registering as a remote attendee is appreciated, I believe, because it helps the planning. And you could probably get some assistance via info at koha-us.org or secretary at koha-us.org. (Yes, the Koha-US website seems down right now.) Cheers, h2 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ms. Heather Hernandez (she, her, hers) Technical Services Librarian San Francisco Maritime National Historical Park Research Center 2 Marina Blvd., Bldg. E, 3rd floor, San Francisco, CA 94123-1284 415-561-7032, heather_hernandez at nps.gov Library catalog: http://keys.bywatersolutions.com/ From stevenanickerson at gmail.com Wed Sep 22 01:45:37 2021 From: stevenanickerson at gmail.com (Steve Nickerson) Date: Tue, 21 Sep 2021 09:45:37 -0400 Subject: [Koha] Upgrading from 17.05.00.00 to "current" In-Reply-To: <99dc19f4-39e4-46fe-5a9a-65662b2c2720@kohaaloha.com> References: <146101d7a996$4ed4b3b0$ec7e1b10$@gmail.com> <99dc19f4-39e4-46fe-5a9a-65662b2c2720@kohaaloha.com> Message-ID: <00b401d7aeee$f5e983d0$e1bc8b70$@gmail.com> Upgrade is working perfectly, thank you Mason!!! -----Original Message----- From: Mason James Sent: Wednesday, September 15, 2021 11:37 PM To: Steve Nickerson ; 'koha' Subject: Re: [Koha] Upgrading from 17.05.00.00 to "current" oops, that apt line should be echo "deb http://debian.koha-community.org/koha 19.11 main jessie" > /etc/apt/sources.list.d/koha.list On 16/09/21 12:10 am, Mason James wrote: > |hi ||Steve > the 19.11 series is still supported on jessie > > the following apt line should get you the latest 19.11.x release > (||||currently koha 19.11.21) > ||echo "deb http://debian.koha-community.org/koha > || 19.11 main jessie" > > ||/etc/apt/sources.list.d/koha.list > > more info... > https://wiki.koha-community.org/wiki/Koha_on_Debian > > > ||cheers, Mason > > ||||| > On 15/09/21 6:28 am, Steve Nickerson wrote: >> Does anyone have any tips on how to successfully go from Koha 17.05 >> to anything more current on Debian 8 (Jessie) package install? I've >> tried the process I've used in the past and the other OS packages >> upgrade but Koha keeps getting "held back" no matter what I've tried (various 'koha.list' >> sources, apt-get full-upgrade, apt-get dist-upgrade, etc.). What is >> the latest version that will run on Debian 8 and what should I put in >> my koha.list source file? >> >> >> Thanks! >> >> Steve >> >> _______________________________________________ >> >> Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > From maheshpalamuttath at gmail.com Wed Sep 22 16:35:31 2021 From: maheshpalamuttath at gmail.com (Mahesh Palamuttath) Date: Wed, 22 Sep 2021 10:05:31 +0530 Subject: [Koha] Need a report for the hourly circulation Message-ID: Hello, all. We decided to circulate Reference books on hourly basis, Circulation rules, fines have been set. that's perfectly Okay and works well. What we want that, daily report for that hourly circulation. It will be nice, If that could at least include cardnumber, patronname, title, barcode, date I Hope, someone could help us thank you--- Mahesh Palamuttath From nt at ptsindia.com Wed Sep 22 19:24:18 2021 From: nt at ptsindia.com (Nalisha Tamang) Date: Wed, 22 Sep 2021 12:54:18 +0530 Subject: [Koha] serials management - numbering pattern Message-ID: Dear all, WE have the journal "BibliothecaSacra" from 1962 Vol.119 no.474 till 1986 Vol.143 no.569 now how do i set the numbering pattern for this journal as I add 'begins with' v.119 no.474 but confused regarding what number to add in the inner counter. As this is quarterly published and the volume and the number keeps increasing we can't set back to 1 or any number. IF I HAVE TO CHANGE IN THE NUMBERING PATTERN PLEASE HELP ME OUT I'M NEW In this area. Thank you Nalisha From mishravk79 at gmail.com Wed Sep 22 20:10:50 2021 From: mishravk79 at gmail.com (vinod mishra) Date: Wed, 22 Sep 2021 13:40:50 +0530 Subject: [Koha] serials management - numbering pattern In-Reply-To: References: Message-ID: Please check AACR2 /RDA for this. With Regards, Vinod Kumar Mishra, Assistant Librarian, Biju Patnaik Central Library (BPCL), NIT Rourkela, Sundergadh-769008, Odisha, India. Mob:91+9439420860 URL: http://vinod.itshelp.co.in/ ORCID ID: http://orcid.org/0000-0003-4666-7874 Scopus ID: 57223138343 *"Spiritual relationship is far more precious than physical. Physical relationship divorced from spiritual is body without soul" -- Mahatma Gandhi* On Wed, Sep 22, 2021 at 12:55 PM Nalisha Tamang wrote: > Dear all, > WE have the journal "BibliothecaSacra" from 1962 Vol.119 no.474 till 1986 > Vol.143 no.569 now how do i set the numbering pattern for this journal as I > add 'begins with' v.119 no.474 but confused regarding what number to add in > the inner counter. As this is quarterly published and the volume and the > number keeps increasing we can't set back to 1 or any number. IF I HAVE TO > CHANGE IN THE NUMBERING PATTERN PLEASE HELP ME OUT I'M NEW In this area. > > > Thank you > Nalisha > _______________________________________________ > > 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 Sep 22 20:57:44 2021 From: mik at adminkuhn.ch (Michael Kuhn) Date: Wed, 22 Sep 2021 10:57:44 +0200 Subject: [Koha] Overdrive integration in Koha 18.05 Message-ID: <04946fbf-5c97-ad9d-59dd-181c4ca37c7a@adminkuhn.ch> Hi In our library we are using Koha 18.05.03 on Debian GNU/Linux 8. According to https://bywatersolutions.com/education/overdrive-integration-in-koha Overdrive is integrated within Koha. From Overdrive we have got several bits of information but in Koha 18.05 we have only the following available system preferences: * OverDriveCirculation * OverDriveClientKey * OverDriveClientSecret * OverDriveLibraryID Filling these in indeed shows the new tab "OverDrive account" in the OPAC user account, but then an "Internal Server Error": Could not compile /usr/share/koha/opac/cgi-bin/opac/external/overdrive/auth.pl: Can't locate WebService/ILS/OverDrive/Patron.pm in @INC (you may need to install the WebService::ILS::OverDrive::Patron module) (@INC contains: /usr/share/koha/lib /usr/share/koha/installer /usr/share/koha/lib/installer /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl . /var/lib/koha/sbtreu/plugins) at /usr/share/koha/lib/Koha/ExternalContent/OverDrive.pm line 24. BEGIN failed--compilation aborted at /usr/share/koha/lib/Koha/ExternalContent/OverDrive.pm line 24. Compilation failed in require at /usr/share/koha/opac/cgi-bin/opac/external/overdrive/auth.pl line 27. BEGIN failed--compilation aborted at /usr/share/koha/opac/cgi-bin/opac/external/overdrive/auth.pl line 27. Does anyone know the solution to this? I see in later versions of Koha there are more preferences: * OverDriveAuthName * OverDriveUsername * OverDrivePasswordRequired * OverDriveWebsiteID We have the necessary bits of information from Overdrive but we can't fill them in in Koha 18.05. Does this mean the Overdrive integration in Koha 18.05 is not functional and we will have to update to a newer Koha version? 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 caroline.cyr-la-rose at inlibro.com Thu Sep 23 00:59:41 2021 From: caroline.cyr-la-rose at inlibro.com (Caroline Cyr-La-Rose) Date: Wed, 22 Sep 2021 08:59:41 -0400 Subject: [Koha] serials management - numbering pattern In-Reply-To: References: Message-ID: Hi Nalisha, If it doesn't ever go back to 1, you shouldn't need to put anything in the inner counter. The inner counter serves only to tell Koha where how many issues have already been published in the cycle. If there is no cycle, there is no need for the inner counter. Caroline On 2021-09-22 03 h 24, Nalisha Tamang wrote: > Dear all, > WE have the journal "BibliothecaSacra" from 1962 Vol.119 no.474 till 1986 > Vol.143 no.569 now how do i set the numbering pattern for this journal as I > add 'begins with' v.119 no.474 but confused regarding what number to add in > the inner counter. As this is quarterly published and the volume and the > number keeps increasing we can't set back to 1 or any number. IF I HAVE TO > CHANGE IN THE NUMBERING PATTERN PLEASE HELP ME OUT I'M NEW In this area. > > > Thank you > Nalisha > _______________________________________________ > > Koha mailing list http://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 cornejo.alvaro at gmail.com Thu Sep 23 03:51:40 2021 From: cornejo.alvaro at gmail.com (Alvaro Cornejo) Date: Wed, 22 Sep 2021 10:51:40 -0500 Subject: [Koha] Overdrive integration in Koha 18.05 In-Reply-To: <04946fbf-5c97-ad9d-59dd-181c4ca37c7a@adminkuhn.ch> References: <04946fbf-5c97-ad9d-59dd-181c4ca37c7a@adminkuhn.ch> Message-ID: Hi Michael The module referred in the message is an external perl module you have to install separately. You can find it in metacpan here: https://metacpan.org/pod/WebService::ILS::OverDrive::Patron Note I don't know if there are additional configs to do or how to integrate it with koha. 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 mer. 22 sept. 2021 à 03:58, Michael Kuhn a écrit : > Hi > > In our library we are using Koha 18.05.03 on Debian GNU/Linux 8. > > According to > https://bywatersolutions.com/education/overdrive-integration-in-koha > Overdrive is integrated within Koha. From Overdrive we have got several > bits of information but in Koha 18.05 we have only the following > available system preferences: > > * OverDriveCirculation > * OverDriveClientKey > * OverDriveClientSecret > * OverDriveLibraryID > > Filling these in indeed shows the new tab "OverDrive account" in the > OPAC user account, but then an "Internal Server Error": > > Could not compile > /usr/share/koha/opac/cgi-bin/opac/external/overdrive/auth.pl: Can't > locate WebService/ILS/OverDrive/Patron.pm in @INC (you may need to > install the WebService::ILS::OverDrive::Patron module) (@INC contains: > /usr/share/koha/lib /usr/share/koha/installer > /usr/share/koha/lib/installer /etc/perl > /usr/local/lib/x86_64-linux-gnu/perl/5.20.2 /usr/local/share/perl/5.20.2 > /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 > /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 > /usr/local/lib/site_perl . /var/lib/koha/sbtreu/plugins) at > /usr/share/koha/lib/Koha/ExternalContent/OverDrive.pm line 24. > BEGIN failed--compilation aborted at > /usr/share/koha/lib/Koha/ExternalContent/OverDrive.pm line 24. > Compilation failed in require at > /usr/share/koha/opac/cgi-bin/opac/external/overdrive/auth.pl line 27. > BEGIN failed--compilation aborted at > /usr/share/koha/opac/cgi-bin/opac/external/overdrive/auth.pl line 27. > > Does anyone know the solution to this? > > I see in later versions of Koha there are more preferences: > > * OverDriveAuthName > * OverDriveUsername > * OverDrivePasswordRequired > * OverDriveWebsiteID > > We have the necessary bits of information from Overdrive but we can't > fill them in in Koha 18.05. Does this mean the Overdrive integration in > Koha 18.05 is not functional and we will have to update to a newer Koha > version? > > 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 Patricia.Dowling at oireachtas.ie Thu Sep 23 03:59:10 2021 From: Patricia.Dowling at oireachtas.ie (Patricia Dowling) Date: Wed, 22 Sep 2021 15:59:10 +0000 Subject: [Koha] Purchase suggestions and acquisitions workflows Message-ID: <17620d69ff484f6f827cd54040b7bc36@oireachtas.ie> Good afternoon to all Koha users. We in the Irish parliamentary library (or Oireachtas) are looking at purchase suggestions in Koha and our acquisitions workflows. We are using version 20.11 As we understand it this is the way purchase suggestions and associated notices work in Koha 1) Suggestion received -- notice text sent will be NEW_SUGGESTION 2) Suggestion accepted or rejected - if you change the status to Accepted the notice text sent will be ACCEPTED. If you change the status to Rejected the notice text sent will be REJECTED. 3) Suggestion ordered - if a material is Ordered the ORDERED notice text is sent. 4) Order received - The AVAILABLE notice is sent on the point of receive and this can only be altered by holding off receiving the item until it is ready. 5) Suggestion available - We think this overlaps with the AVAILABLE notice text? We are considering deleting the Suggestion ORDERED notice so that notices are not sent out when a suggestion has been ordered as it suggest to the user that the item is ready when in reality it may not yet have been catalogued. Are other libraries are actively using purchase suggestions features in Koha and if so can you share some information on the workflows you have adopted? Do you have any tips on what works best based on your experience? Thanks in advance Patricia Dowling Leabharlannaí Sinsearach| Senior Librarian Seirbhísí Córas agus Ábhair| Systems & Content Services Leabharlann an Oireachtais | Oireachtas Library Seirbhís Thithe an Oireachtais | Houses of the Oireachtas Service +353 (0)1 6183222 library.oireachtas.ie (internal) www.oireachtas.ie/library patricia.dowling at oireachtas.ie Lárdheasc Fiosrúcháin | Central Enquiry Desk +353 (0)1 6184701 library.and.research at oireachtas.ie Cuireann Seirbhís Thithe an Oireachtais fáilte roimh chomhfhreagras i nGaeilge Beartas ríomhphoist an Oireachtais agus séanadh. oireachtas.ie/ga/email-policy/ Oireachtas email policy and disclaimer. oireachtas.ie/en/email-policy/ From cacho at genac.org Thu Sep 23 04:23:13 2021 From: cacho at genac.org (Hector Gonzalez Jaime) Date: Wed, 22 Sep 2021 11:23:13 -0500 Subject: [Koha] How to Update and Upgrade Koha In-Reply-To: References:

Message-ID: Hi, I'd like to, but I didn't have an account for the wiki, so I'm waiting for it to be enabled. On 9/20/21 4:47 AM, Jonathan Druart wrote: > Hi Hector, Well detailed instructions, it would help to have them on > the wiki page :) > Would you mind updating the existing section? > https://wiki.koha-community.org/wiki/Koha_on_Debian#Upgrade -- Hector Gonzalez cacho at genac.org From katrin.fischer.83 at web.de Thu Sep 23 06:43:03 2021 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Wed, 22 Sep 2021 20:43:03 +0200 Subject: [Koha] How to Update and Upgrade Koha In-Reply-To: References:

Message-ID: <3343d9eb-db7a-6ba6-877a-ed7d663099a6@web.de> Hi Hector, I've confirmed your wiki account request. Happy editing! :) Katrin On 22.09.21 18:23, Hector Gonzalez Jaime wrote: > Hi, I'd like to, but I didn't have an account for the wiki, so I'm > waiting for it to be enabled. > > On 9/20/21 4:47 AM, Jonathan Druart wrote: >> Hi Hector, Well detailed instructions, it would help to have them on >> the wiki page :) >> Would you mind updating the existing section? >> https://wiki.koha-community.org/wiki/Koha_on_Debian#Upgrade > From sowen at almaschools.net Thu Sep 23 07:37:21 2021 From: sowen at almaschools.net (Scott Owen) Date: Wed, 22 Sep 2021 15:37:21 -0400 Subject: [Koha] DBMS auto increment Message-ID: Hi All, https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix Is this still the best procedure when getting the following error ? ************************************************ You should not ignore this warning. The problem is that InnoDB does not keep auto_increment across SQL server restarts (it is only set in memory). So on server startup the auto_increment values are set to max(table.id)+1. To know how to avoid this problem see the related wiki page: DBMS auto increment fix Problems foundCheckouts The following ids exist in both tables issues and old_issues: 4782, 4781 ************************************************ Any sql to clean things up in the two tables ? From black23 at gmail.com Thu Sep 23 07:38:32 2021 From: black23 at gmail.com (Mike D.) Date: Wed, 22 Sep 2021 21:38:32 +0200 Subject: [Koha] Template toolkin and MARC field/subfields Message-ID: Hello, community, does anyone have experience with using MARC fields in notices? Specifically, we would need to output the contents of some fields/sufields to text in e-mail notice using the template toolkit. For example, $t and $g in field 787. Is this possible? Does anyone have experience with this? Thanks Michal From josef.moravec at gmail.com Thu Sep 23 17:03:06 2021 From: josef.moravec at gmail.com (Josef Moravec) Date: Thu, 23 Sep 2021 07:03:06 +0200 Subject: [Koha] Template toolkin and MARC field/subfields In-Reply-To: References: Message-ID: Hello Mike, I would try something like this: https://gist.github.com/xmorave2/cd926ec245e34c4f42537de221016f5c see especially this part (lines 6 to 10): [% record = checkout.item.biblio.metadata.record %] [% field787 = record.field('787') %] [% IF field787 %]. [% field787.subfield('t') %] [% field787.subfield('g') %]. [% END %] Best regards, Josef On Wed, Sep 22, 2021 at 9:39 PM Mike D. wrote: > Hello, community, > does anyone have experience with using MARC fields in notices? > Specifically, we would need to output the contents of some fields/sufields > to text in e-mail notice using the template toolkit. For example, $t and $g > in field 787. Is this possible? Does anyone have experience with this? > > Thanks > > Michal > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > -- Josef Moravec josef.moravec at gmail.com From tubia at hacari.net Fri Sep 24 02:30:33 2021 From: tubia at hacari.net (Jacopo) Date: Thu, 23 Sep 2021 14:30:33 +0000 Subject: [Koha] Koha 21.05 Internal server error on https Message-ID: Hi, I recently tried to install Koha 21.05 on a Debian 10.10 server and then to move 2 libraries from another Koha instance (20.05), which was unsuccessful but will be the subject of another email. Currently I am experiencing a different issue: recurrent internal server errors both on for the opac and the intranet when connecting though https (http is working). The error I get, from /var/log/koha/library/opac-error.log: ``` [Thu Sep 23 14:36:17.087937 2021] [cgi:error] [pid 21969] [client xxx] AH01215: Use of uninitialized value $compiled in concatenation (.) or string at /usr/lib/x86_64-linux-gnu/perl5/5.28/Template/Provider.pm line 572.: /usr/share/koha/opac/cgi-bin/opac/opac-main.pl [Thu Sep 23 14:36:17.088568 2021] [cgi:error] [pid 21969] [client xxx] AH01215: compiled template : Can't locate /tmp//usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/opac-main.tt.ttc: /tmp//usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/opac-main.tt.ttc: Permission denied at /usr/lib/x86_64-linux-gnu/perl5/5.28/Template/Provider.pm line 571.: /usr/share/koha/opac/cgi-bin/opac/opac-main.pl [Thu Sep 23 14:36:17.088598 2021] [cgi:error] [pid 21969] [client xxx] AH01215: : /usr/share/koha/opac/cgi-bin/opac/opac-main.pl [Thu Sep 23 14:36:17.118243 2021] [cgi:error] [pid 21969] [client xxx] AH01215: Template process failed: file error - cache failed to write opac-main.tt.ttc: Error in tempfile() using template /tmp/usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/XXXXXXXXXX: Could not create temp file /tmp/usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/Ti3EjV0TMw: Permission denied at /usr/lib/x86_64-linux-gnu/perl5/5.28/Template/Document.pm line 301.: /usr/share/koha/opac/cgi-bin/opac/opac-main.pl [Thu Sep 23 14:36:17.156177 2021] [cgi:error] [pid 21969] [client xxx] End of script output before headers: opac-main.pl [Thu Sep 23 14:36:18.597239 2021] [cgi:error] [pid 21969] [client xxx] AH01215: Use of uninitialized value $compiled in concatenation (.) or string at /usr/lib/x86_64-linux-gnu/perl5/5.28/Template/Provider.pm line 572.: /usr/share/koha/opac/cgi-bin/opac/errors/500.pl [Thu Sep 23 14:36:18.597997 2021] [cgi:error] [pid 21969] [client xxx] AH01215: compiled template : Can't locate /tmp//usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/errors/errorpage.tt.ttc: /tmp//usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/errors/errorpage.tt.ttc: Permission denied at /usr/lib/x86_64-linux-gnu/perl5/5.28/Template/Provider.pm line 571.: /usr/share/koha/opac/cgi-bin/opac/errors/500.pl [Thu Sep 23 14:36:18.598021 2021] [cgi:error] [pid 21969] [client xxx] AH01215: : /usr/share/koha/opac/cgi-bin/opac/errors/500.pl [Thu Sep 23 14:36:18.613489 2021] [cgi:error] [pid 21969] [client xxx] AH01215: Template process failed: file error - cache failed to write errorpage.tt.ttc: Error in tempfile() using template /tmp/usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/errors/XXXXXXXXXX: Could not create temp file /tmp/usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/errors/mVp8iM_cko: Permission denied at /usr/lib/x86_64-linux-gnu/perl5/5.28/Template/Document.pm line 301.: /usr/share/koha/opac/cgi-bin/opac/errors/500.pl [Thu Sep 23 14:36:18.646433 2021] [cgi:error] [pid 21969] [client xxx] End of script output before headers: 500.pl ``` The ownership of /usr/share/koha/{intranet,opac} is set to the user www-data. The ownership of /etc/koha/sites is set to the user koha_koha. Any help would be greatly appreciated. Thanks! Jacopo From mik at adminkuhn.ch Fri Sep 24 03:09:29 2021 From: mik at adminkuhn.ch (Michael Kuhn) Date: Thu, 23 Sep 2021 17:09:29 +0200 Subject: [Koha] Overdrive integration in Koha 18.05 In-Reply-To: References: <04946fbf-5c97-ad9d-59dd-181c4ca37c7a@adminkuhn.ch> Message-ID: <543b1f13-326c-eaa4-e4c4-5f5dc8707d73@adminkuhn.ch> Hi Alvaro > The module referred in the message is an external perl module you have > to install separately. > > You can find it in metacpan here: > > https://metacpan.org/pod/WebService::ILS::OverDrive::Patron > > Note I don't know if there are additional configs to do or how to > integrate it with koha. Thanks for your message! I have seen that this module is available in Meta CPAN. But I don't think this is the proper way to solve this problem in our Debian package installation of Koha 18.05.03. Especially since there are only four system preferences instead of eight anyway. At the moment I guess the desired Overdrive integration was never (fully) functional in Koha 18.05.03 and we will have to update to a newer version to actually use the Overdrive integration as intended. 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 > Le mer. 22 sept. 2021 à 03:58, Michael Kuhn > a écrit : > > Hi > > In our library we are using Koha 18.05.03 on Debian GNU/Linux 8. > > According to > https://bywatersolutions.com/education/overdrive-integration-in-koha > > Overdrive is integrated within Koha. From Overdrive we have got several > bits of information but in Koha 18.05 we have only the following > available system preferences: > > * OverDriveCirculation > * OverDriveClientKey > * OverDriveClientSecret > * OverDriveLibraryID > > Filling these in indeed shows the new tab "OverDrive account" in the > OPAC user account, but then an "Internal Server Error": > > Could not compile > /usr/share/koha/opac/cgi-bin/opac/external/overdrive/auth.pl > : Can't > locate WebService/ILS/OverDrive/Patron.pm in @INC (you may need to > install the WebService::ILS::OverDrive::Patron module) (@INC contains: > /usr/share/koha/lib /usr/share/koha/installer > /usr/share/koha/lib/installer /etc/perl > /usr/local/lib/x86_64-linux-gnu/perl/5.20.2 > /usr/local/share/perl/5.20.2 > /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 > /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 > /usr/local/lib/site_perl . /var/lib/koha/sbtreu/plugins) at > /usr/share/koha/lib/Koha/ExternalContent/OverDrive.pm line 24. > BEGIN failed--compilation aborted at > /usr/share/koha/lib/Koha/ExternalContent/OverDrive.pm line 24. > Compilation failed in require at > /usr/share/koha/opac/cgi-bin/opac/external/overdrive/auth.pl > line 27. > BEGIN failed--compilation aborted at > /usr/share/koha/opac/cgi-bin/opac/external/overdrive/auth.pl > line 27. > > Does anyone know the solution to this? > > I see in later versions of Koha there are more preferences: > > * OverDriveAuthName > * OverDriveUsername > * OverDrivePasswordRequired > * OverDriveWebsiteID > > We have the necessary bits of information from Overdrive but we can't > fill them in in Koha 18.05. Does this mean the Overdrive integration in > Koha 18.05 is not functional and we will have to update to a newer Koha > version? > > 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 cmkelleymls at gmail.com Fri Sep 24 16:56:39 2021 From: cmkelleymls at gmail.com (Charles Kelley) Date: Fri, 24 Sep 2021 13:56:39 +0900 Subject: [Koha] =?utf-8?q?Display_of_Damage_Status_=28952_=E2=80=A14=29?= Message-ID: Hi, all! My library has a fairly significant number of books with yellowing paper. The books are still usable -- we would withdraw it otherwise -- and we plan to keep them in circulation until the paper turns brown or brittle. We have marked such books with the appropriate damage value in 952 ‡4. Unfortunately, this has led to confusion among some staff and almost all the patrons because Koha reports the books "Availability: No items available: Damaged (1)." We would like to show a different statement, something akin to: "Availability: every item available but 1 damaged." The latter would mean that all items are available for circulation but one is damage. Of course, if all items are available but none is damaged, the notice would read "Availability: every item available." Is this possible? Might the OPACHiddenItems list be a solution to this? Many thanks, everyone! -- 気を付けて。 /ki wo tukete/ = Take care. -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk at aol.com [h] cmkelleymls at gmail.com [p] linkedin.com/in/cmkelleymls Meeting Your Information Needs. Virtually. From katrin.fischer.83 at web.de Mon Sep 27 19:18:35 2021 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Mon, 27 Sep 2021 08:18:35 +0200 Subject: [Koha] =?utf-8?q?Display_of_Damage_Status_=28952_=E2=80=A14=29?= In-Reply-To: References: Message-ID: <48686a01-6aa9-d2a1-feb0-75a81ea7ba24@web.de> Hi Charles, I think what you describe, has been reported as *Bug 18062* - Damaged Status shows unavailable in results I am not aware of a way to change this at the moment. OpacHiddenItems would hide the damaged items from view and if there are only damaged items, the record would be hidden as well. Hope this helps, Katrin On 24.09.21 06:56, Charles Kelley wrote: > Hi, all! > > My library has a fairly significant number of books with yellowing > paper. The books are still usable -- we would withdraw it otherwise -- and > we plan to keep them in circulation until the paper turns brown or brittle. > We have marked such books with the appropriate damage value in 952 ‡4. > > Unfortunately, this has led to confusion among some staff and almost > all the patrons because Koha reports the books > > "Availability: No items available: Damaged (1)." > > We would like to show a different statement, something akin to: > > "Availability: every item available but 1 damaged." > > The latter would mean that all items are available for circulation but > one is damage. Of course, if all items are available but none is damaged, > the notice would read "Availability: every item available." > > Is this possible? Might the OPACHiddenItems list be a solution to this? > > Many thanks, everyone! > From katrin.fischer.83 at web.de Mon Sep 27 19:19:07 2021 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Mon, 27 Sep 2021 08:19:07 +0200 Subject: [Koha] DBMS auto increment In-Reply-To: References: Message-ID: <3e2ba79d-5394-e02a-8dca-a0e29a13f65b@web.de> Hi Scott, yes, the wiki page has all the current information and suggestions on how to solve this issue. It also notes the DBMS versions where the problem will be fixed. The easiest way to resolve the problem is deleting the doubled up entries from the old* and deleted* tables. Then you can implement the fix and restart your DBMS server to reset the primary keys to the correct values. This will prevent the creation of more doubled up IDs between the tables. Hope this helps, Katrin On 22.09.21 21:37, Scott Owen wrote: > Hi All, > > https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix > > > Is this still the best procedure when getting the following error ? > > > ************************************************ > > You should not ignore this warning. > > The problem is that InnoDB does not keep auto_increment across SQL server > restarts (it is only set in memory). So on server startup the > auto_increment values are set to max(table.id)+1. > > To know how to avoid this problem see the related wiki page: DBMS auto > increment fix > Problems foundCheckouts > > The following ids exist in both tables issues and old_issues: > > 4782, 4781 > > > ************************************************ > > Any sql to clean things up in the two tables ? > _______________________________________________ > > Koha mailing listhttp://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 Tue Sep 28 01:52:31 2021 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Mon, 27 Sep 2021 14:52:31 +0200 Subject: [Koha] New Koha minor versions released - security fixes included, UPGRADE! Message-ID: Hello everybody, I am announcing, on behalf of the whole Koha release team, synchronised releases for the four release versions we are currently supporting. The release notes are available below: 21.05.04 - https://koha-community.org/koha-21-05-04-released-%e2%9a%a0-security-release/ 20.11.10 - https://koha-community.org/koha-20-11-10-released-%e2%9a%a0-security-release/ 20.05.16 - https://koha-community.org/koha-20-05-16-released-%e2%9a%a0-security-release/ 19.11.22 - https://koha-community.org/koha-19-11-22-released-%e2%9a%a0-security-release/ As they contain security bug fixes we suggest you upgrade all the Koha instances you are in charge of as soon as possible. Let us know if you have any questions. Regards, Jonathan From shaffendi at gmail.com Tue Sep 28 02:28:05 2021 From: shaffendi at gmail.com (Shafrizan Affendi) Date: Mon, 27 Sep 2021 21:28:05 +0800 Subject: [Koha] Renewal notice email Message-ID: Hi there. Im using Koha ver 21.05. I would like to ask how can I generate renewal notice (email) and send message que in every hour? If im not mistaken, default koha will send the email in the midnight. For example, i renew 1 book at 10 am. and will get the email notice at midnight. I want to make koha send the notice email right after i renew the book so that i can receive the email at 11.01 am. Can anyone help me? Thanks in advance From r.delahunty at arts.ac.uk Tue Sep 28 03:07:23 2021 From: r.delahunty at arts.ac.uk (Raymund Delahunty) Date: Mon, 27 Sep 2021 14:07:23 +0000 Subject: [Koha] Purchase suggestions and acquisitions workflows In-Reply-To: <17620d69ff484f6f827cd54040b7bc36@oireachtas.ie> References: <17620d69ff484f6f827cd54040b7bc36@oireachtas.ie> Message-ID: We are making a lot of use of Purchase Suggestions. In 18.11 many features had to be "managed" by jQuery in IntranetUserJS and we are delighted many are now Koha system parameters (We moved to 20.11 recently). For example, we have significantly redesigned the OPAC form. We had both the Ordered and received tabs hidden, and I forgot to hide them again, and I was reminded to do this by a colleague ASAP. There does seem to be unnecessary overlap... at least using our workflows. Just a few minutes back I noticed the link Suggestions pending approval (showing the logged in library and All libraries) vanishes where there are no "Pendings". I'd prefer it to say Library A: 0 / All libraries 103. But I fixed that by adding this to Intranetmainuserblock just now:

Backdoor to Purchase Suggestions

Unusually I was asked to hide the Delete button on OPAC and this has been done, but we do say the user can contact their librarian to have a suggestion deleted. Ray Delahunty University of the Arts London -----Original Message----- From: Koha On Behalf Of Patricia Dowling Sent: 22 September 2021 16:59 To: koha at lists.katipo.co.nz Subject: [Koha] Purchase suggestions and acquisitions workflows Good afternoon to all Koha users. We in the Irish parliamentary library (or Oireachtas) are looking at purchase suggestions in Koha and our acquisitions workflows. We are using version 20.11 As we understand it this is the way purchase suggestions and associated notices work in Koha 1) Suggestion received -- notice text sent will be NEW_SUGGESTION 2) Suggestion accepted or rejected - if you change the status to Accepted the notice text sent will be ACCEPTED. If you change the status to Rejected the notice text sent will be REJECTED. 3) Suggestion ordered - if a material is Ordered the ORDERED notice text is sent. 4) Order received - The AVAILABLE notice is sent on the point of receive and this can only be altered by holding off receiving the item until it is ready. 5) Suggestion available - We think this overlaps with the AVAILABLE notice text? We are considering deleting the Suggestion ORDERED notice so that notices are not sent out when a suggestion has been ordered as it suggest to the user that the item is ready when in reality it may not yet have been catalogued. Are other libraries are actively using purchase suggestions features in Koha and if so can you share some information on the workflows you have adopted? Do you have any tips on what works best based on your experience? Thanks in advance Patricia Dowling Leabharlannaí Sinsearach| Senior Librarian Seirbhísí Córas agus Ábhair| Systems & Content Services Leabharlann an Oireachtais | Oireachtas Library Seirbhís Thithe an Oireachtais | Houses of the Oireachtas Service +353 (0)1 6183222 library.oireachtas.ie (internal) www.oireachtas.ie/library patricia.dowling at oireachtas.ie Lárdheasc Fiosrúcháin | Central Enquiry Desk +353 (0)1 6184701 library.and.research at oireachtas.ie Cuireann Seirbhís Thithe an Oireachtais fáilte roimh chomhfhreagras i nGaeilge Beartas ríomhphoist an Oireachtais agus séanadh. oireachtas.ie/ga/email-policy/ Oireachtas email policy and disclaimer. oireachtas.ie/en/email-policy/ _______________________________________________ Koha mailing list https://eur04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fkoha-community.org%2F&data=04%7C01%7CPatricia.Dowling%40oireachtas.ie%7Cb0f409d78c084093cf1908d981c56ea8%7Cce71ecf00b9747b2966cb4ecc8db23f2%7C1%7C0%7C637683507231860049%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=rbajhKmLBjLo4h2FHZz6IHe%2FwQNxVXfqfOrgyfTvrIA%3D&reserved=0 Koha at lists.katipo.co.nz Unsubscribe: https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.katipo.co.nz%2Fmailman%2Flistinfo%2Fkoha&data=04%7C01%7CPatricia.Dowling%40oireachtas.ie%7Cb0f409d78c084093cf1908d981c56ea8%7Cce71ecf00b9747b2966cb4ecc8db23f2%7C1%7C0%7C637683507231860049%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=ClPtPZznrOsfg188kVUcU4foFotidK5TkJhQNSotD8g%3D&reserved=0 This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of UAL Short Courses Limited the following also applies: UAL Short Courses Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY Beartas ríomhphoist an Oireachtais agus séanadh. oireachtas.ie/ga/email-policy/ Oireachtas email policy and disclaimer. oireachtas.ie/en/email-policy/ This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of UAL Short Courses Limited the following also applies: UAL Short Courses Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY Beartas ríomhphoist an Oireachtais agus séanadh. oireachtas.ie/ga/email-policy/ Oireachtas email policy and disclaimer. oireachtas.ie/en/email-policy/ This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of UAL Short Courses Limited the following also applies: UAL Short Courses Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY Beartas ríomhphoist an Oireachtais agus séanadh. oireachtas.ie/ga/email-policy/ Oireachtas email policy and disclaimer. oireachtas.ie/en/email-policy/ From tom_burke at mac.com Tue Sep 28 05:01:36 2021 From: tom_burke at mac.com (Tom Burke) Date: Mon, 27 Sep 2021 17:01:36 +0100 Subject: [Koha] Fwd: New Koha minor versions released - security fixes included, UPGRADE! References: Message-ID: <2906019E-7F97-497D-A760-E72DBD5AB41D@mac.com> Can I seek a bit of reassurance, please? We have a server running several instances which is currently on 19.11.00.000. Obviously we want to upgrade this. We have tried doing a significant upgrade (to 20.11) on a test site, and have run into some issues which we are still investigating. We might therefore decide to meet the present security-driven upgrade requirement by simply going from 19.11.00 to 19.11.22 . Is it safe to assume that there is no schema change in such an upgrade? Tom Burke > Begin forwarded message: > > From: Jonathan Druart > Subject: [Koha] New Koha minor versions released - security fixes included, UPGRADE! > Date: 27 September 2021 at 13:52:31 BST > To: koha , koha-devel > > Hello everybody, > > I am announcing, on behalf of the whole Koha release team, > synchronised releases for the four release versions we are currently > supporting. > > The release notes are available below: > 21.05.04 - https://koha-community.org/koha-21-05-04-released-%e2%9a%a0-security-release/ > 20.11.10 - https://koha-community.org/koha-20-11-10-released-%e2%9a%a0-security-release/ > 20.05.16 - https://koha-community.org/koha-20-05-16-released-%e2%9a%a0-security-release/ > 19.11.22 - https://koha-community.org/koha-19-11-22-released-%e2%9a%a0-security-release/ > > As they contain security bug fixes we suggest you upgrade all the Koha > instances you are in charge of as soon as possible. > > Let us know if you have any questions. > > Regards, > Jonathan > _______________________________________________ > > 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 Sep 28 05:13:52 2021 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Mon, 27 Sep 2021 18:13:52 +0200 Subject: [Koha] Fwd: New Koha minor versions released - security fixes included, UPGRADE! In-Reply-To: <2906019E-7F97-497D-A760-E72DBD5AB41D@mac.com> References: <2906019E-7F97-497D-A760-E72DBD5AB41D@mac.com> Message-ID: <4328e1b5-d782-fb6a-858d-05c03de55581@tuxayo.net> Hello, On 21-09-27 18:01, Tom Burke wrote: > Can I seek a bit of reassurance, please? We have a server running several instances which is currently on 19.11.00.000. Obviously we want to upgrade this. We have tried doing a significant upgrade (to 20.11) on a test site, and have run into some issues which we are still investigating. We might therefore decide to meet the present security-driven upgrade requirement by simply going from 19.11.00 to 19.11.22 . Is it safe to assume that there is no schema change in such an upgrade? There are a few data migrations and schema changes https://git.koha-community.org/Koha-community/Koha/src/branch/19.11.x/installer/data/mysql/updatedatabase.pl#L20256 Which the DB upgrade script handles. Cheers, -- Victor Grousset/tuxayo From sowen at almaschools.net Tue Sep 28 06:08:56 2021 From: sowen at almaschools.net (Scott Owen) Date: Mon, 27 Sep 2021 13:08:56 -0400 Subject: [Koha] DBMS auto increment In-Reply-To: <3e2ba79d-5394-e02a-8dca-a0e29a13f65b@web.de> References: <3e2ba79d-5394-e02a-8dca-a0e29a13f65b@web.de> Message-ID: Thank you. Is there a way to verify that the "fix" is working ? Just watch for data errors ? On Mon, Sep 27, 2021 at 2:19 AM Katrin Fischer wrote: > Hi Scott, > > yes, the wiki page has all the current information and suggestions on > how to solve this issue. It also notes the DBMS versions where the > problem will be fixed. > > The easiest way to resolve the problem is deleting the doubled up > entries from the old* and deleted* tables. Then you can implement the > fix and restart your DBMS server to reset the primary keys to the > correct values. This will prevent the creation of more doubled up IDs > between the tables. > > Hope this helps, > > Katrin > > On 22.09.21 21:37, Scott Owen wrote: > > Hi All, > > > > https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix > > > > > > Is this still the best procedure when getting the following error ? > > > > > > ************************************************ > > > > You should not ignore this warning. > > > > The problem is that InnoDB does not keep auto_increment across SQL server > > restarts (it is only set in memory). So on server startup the > > auto_increment values are set to max(table.id)+1. > > > > To know how to avoid this problem see the related wiki page: DBMS auto > > increment fix< > https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix> > > Problems foundCheckouts > > > > The following ids exist in both tables issues and old_issues: > > > > 4782, 4781 > > > > > > ************************************************ > > > > Any sql to clean things up in the two tables ? > > _______________________________________________ > > > > 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 shaffendi at gmail.com Tue Sep 28 11:52:01 2021 From: shaffendi at gmail.com (Shafrizan Affendi) Date: Tue, 28 Sep 2021 06:52:01 +0800 Subject: [Koha] Renewal notice email In-Reply-To: References: Message-ID: I do have access to the server. Can you tell me which *.pl that i need to set in cron.hourly? i tried process_message_queue.pl in cron.hourly but not successful. On Tue, 28 Sep 2021, 12:25 am Coehoorn, Joel, wrote: > This is possible, but it's managed via the linux cron tables rather than > via the Koha user interface. You'll need someone who can ssh into the > server and is comfortable using a linux cli prompt to edit files. > > Joel Coehoorn > Director of Information Technology > York College of Nebraska > > > On Mon, Sep 27, 2021 at 8:28 AM Shafrizan Affendi > wrote: > >> Hi there. Im using Koha ver 21.05. >> >> I would like to ask how can I generate renewal notice (email) and send >> message que in every hour? >> >> If im not mistaken, default koha will send the email in the midnight. >> >> For example, i renew 1 book at 10 am. and will get the email notice at >> midnight. I want to make koha send the notice email right after i renew >> the >> book so that i can receive the email at 11.01 am. >> >> Can anyone help me? Thanks in advance >> _______________________________________________ >> >> 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 Tue Sep 28 14:52:35 2021 From: cmkelleymls at gmail.com (Charles Kelley) Date: Tue, 28 Sep 2021 10:52:35 +0900 Subject: [Koha] =?utf-8?q?Display_of_Damage_Status_=28952_=E2=80=A14=29?= In-Reply-To: References: Message-ID: Hello, all! In our latest exchange, on 28 Sept. 2021 at 08:01 [JST], I received the following from Katrin Fischer, to wit:: I think what you describe, has been reported as > > *Bug 18062* > - > Damaged Status shows unavailable in results > > I am not aware of a way to change this at the moment. > > OpacHiddenItems would hide the damaged items from view and if there are > only damaged items, the record would be hidden as well. > > Hope this helps, Thanks for the advisement. Drat! I guess we'll advise the staff and patrons to ignore the statement until the bug is exterminated. I'll sign onto the report. Thanks again. -- 気を付けて。 /ki wo tukete/ = Take care. -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk at aol.com [h] cmkelleymls at gmail.com [p] linkedin.com/in/cmkelleymls Meeting Your Information Needs. Virtually. From shaffendi at gmail.com Wed Sep 29 15:33:07 2021 From: shaffendi at gmail.com (Shafrizan Affendi) Date: Wed, 29 Sep 2021 10:33:07 +0800 Subject: [Koha] Renewal notice email In-Reply-To: References: Message-ID: Anyone can help me out please 😅 On Tue, 28 Sep 2021, 6:52 am Shafrizan Affendi, wrote: > I do have access to the server. Can you tell me which *.pl that i need to > set in cron.hourly? i tried > process_message_queue.pl in cron.hourly but not successful. > > > > On Tue, 28 Sep 2021, 12:25 am Coehoorn, Joel, wrote: > >> This is possible, but it's managed via the linux cron tables rather than >> via the Koha user interface. You'll need someone who can ssh into the >> server and is comfortable using a linux cli prompt to edit files. >> >> Joel Coehoorn >> Director of Information Technology >> York College of Nebraska >> >> >> On Mon, Sep 27, 2021 at 8:28 AM Shafrizan Affendi >> wrote: >> >>> Hi there. Im using Koha ver 21.05. >>> >>> I would like to ask how can I generate renewal notice (email) and send >>> message que in every hour? >>> >>> If im not mistaken, default koha will send the email in the midnight. >>> >>> For example, i renew 1 book at 10 am. and will get the email notice at >>> midnight. I want to make koha send the notice email right after i renew >>> the >>> book so that i can receive the email at 11.01 am. >>> >>> Can anyone help me? Thanks in advance >>> _______________________________________________ >>> >>> 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 Thu Sep 30 04:12:27 2021 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Wed, 29 Sep 2021 17:12:27 +0200 Subject: [Koha] Roles for 22.05 open Message-ID: Hello everybody, The roles for the 22.05 release cycle are now opened. The vote will take place during one of the dev meetings in October. https://wiki.koha-community.org/wiki/Roles_for_22.05 The description of the roles can be found at this wiki page https://wiki.koha-community.org/wiki/Project_roles Regards, Jonathan From kohanews at gmail.com Thu Sep 30 06:03:37 2021 From: kohanews at gmail.com (Koha Newsletter) Date: Wed, 29 Sep 2021 19:03:37 +0200 Subject: [Koha] Koha Community Newsletter: September 2021 Message-ID: The Koha Community Newsletter for September 2021 is here: * https://koha-community.org/koha-community-newsletter-september-2021/ 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 tom_burke at mac.com Thu Sep 30 07:43:11 2021 From: tom_burke at mac.com (Tom Burke) Date: Wed, 29 Sep 2021 19:43:11 +0100 Subject: [Koha] Upgrade order Message-ID: Hello the list We presently have a server with 5 instances, running 19.11.22 on Deb 9 (stretch). Over the new few months we aim to upgrade both - from stretch to buster, and from 19.11 to 20.11 or maybe 21.05. Which is the best order to do the upgrades in? OS first, or Koha? My natural caution leads me to prefer to do them separately. Tom Burke From cmkelleymls at gmail.com Thu Sep 30 15:27:50 2021 From: cmkelleymls at gmail.com (Charles Kelley) Date: Thu, 30 Sep 2021 11:27:50 +0900 Subject: [Koha] Deleted Visible Records Message-ID: Hi, all! Some months ago, I deleted several records. None of the deleted records shows up in a regular search of the catalog. However, all three show up when I run a report on framework codes, they suddenly show up. When I go look by the bib. record number (999 $c), I see "NoTitle", and when I click on the link to "NoTitle", Koha tells me that the record does not exist. So the records show up only in the report(s), the evidence tells me, not in a general catalog search. Is this a known bug? Is there a fix yet if it is a known bug? Many thanks, all. -- 気を付けて。 /ki wo tukete/ = Take care. -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk at aol.com [h] cmkelleymls at gmail.com [p] linkedin.com/in/cmkelleymls Meeting Your Information Needs. Virtually. From julien.sicot at univ-rennes2.fr Thu Sep 30 20:00:46 2021 From: julien.sicot at univ-rennes2.fr (Julien Sicot) Date: Thu, 30 Sep 2021 09:00:46 +0200 Subject: [Koha] linked item subfield to unlinked item subfield (items.more_subfields_xml) Message-ID: Hi everyone, Do you know if there is a method, a script or a tool to easily migrate a linked (koha db) item subfield to an unlinked item subfield (ie : items.more_subfields_xml). We will soon upgrade koha from 18.11 to 20.11and we are trying to find a solution to the removal of items.paidfor subfield. We have used paidfor to store some item values so that can be easily searched using the item search functionality… Sadly, in 20.11 we have not determined any other column in the database that are not already in use or linked to another marc subfield… Thanks for any help, Best, Julien Sicot Applications documentaires DSI - Pôle Applications Université Rennes 2 02 22 51 44 41 From jonathan.druart at bugs.koha-community.org Thu Sep 30 20:45:59 2021 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Thu, 30 Sep 2021 09:45:59 +0200 Subject: [Koha] linked item subfield to unlinked item subfield (items.more_subfields_xml) In-Reply-To: References: Message-ID: Salut Julien, 'Easily' I don't know. But quite easily with a small script. 0. Have 2 frameworks, FwA with your subfield linked to paidfor and FwB with no DB link 1. loop over the items 2. Retrieve the item and save it using FwB (C4::Items::ModItemFromMarc) Haven't tried, but it should work. If you write it, I can review it if you want. Cheers, Jonathan Le jeu. 30 sept. 2021 à 09:00, Julien Sicot a écrit : > > Hi everyone, > > Do you know if there is a method, a script or a tool to easily migrate a linked (koha db) item subfield to an unlinked item subfield (ie : items.more_subfields_xml). > We will soon upgrade koha from 18.11 to 20.11and we are trying to find a solution to the removal of items.paidfor subfield. We have used paidfor to store some item values so that can be easily searched using the item search functionality… > > Sadly, in 20.11 we have not determined any other column in the database that are not already in use or linked to another marc subfield… > > Thanks for any help, > Best, > > Julien Sicot > Applications documentaires > DSI - Pôle Applications > Université Rennes 2 > 02 22 51 44 41 > > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha