- Koha - lists.katipo.co.nz

Koha as a CMS - software error after upgrade to 20.11
by Isabel Pineda 13 Jan '21

13 Jan '21

Hi. I have upgraded my Koha version from 20.05 to 20.11. I am using Koha as a CMS and after the upgrade I get an error when I try to access the CMS pages: Software error: "GetDailyQuote" is not exported by the C4::Koha module Can't continue after import errors at /usr/share/koha/opac/cgi-bin/opac/pages.pl line 27. BEGIN failed--compilation aborted at /usr/share/koha/opac/cgi-bin/opac/pages.pl line 27. In the release notes for Koha 20.11 I can see that something has changed for GetDailyQuote. Does anybody know what I have to change to make it work again? I am trying some things but I haven't succeeded yet. I am not using the functionality of the daily quotes. Thank you Isabel Pineda

1 1

Call for news - Newsletter January 2021
by Koha Newsletter 13 Jan '21

13 Jan '21

Hi I'm collecting news for the January 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. For events: * Please include dates for past events. If I can't find dates I may not add it. * Announcements for future events with dates to be announced are fine, e. g. Kohacon. * For past events, one month back is the cut-off. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. Thank you! Michael Kuhn Editor, Koha Community Newsletter

1 0

(no subject)
by Koha Newsletter 13 Jan '21

13 Jan '21

Hi I'm collecting news for the January 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. For events: * Please include dates for past events. If I can't find dates I may not add it. * Announcements for future events with dates to be announced are fine, e. g. Kohacon. * For past events, one month back is the cut-off. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. Thank you! Michael Kuhn Editor, Koha Community Newsletter

1 0

SQL Report Coding need.
by MAMCET Library 13 Jan '21

13 Jan '21

Dear all good morning Please send the SQL Patrons Fine payment date wise report coding. Koha version 20.5 -- Thanking you.. Librarian, MAMCET <http://mamcet.com/> Trichy-Chennai Trunk Road, Siruganur, Tiruchirappalli-621 105.

1 0

koha-US General Meeting reminder: Wedesday, January 13th
by Jason Robb 12 Jan '21

12 Jan '21

Our next koha-US general meeting is *tomorrow, *Wednesday, January 13th. Join us as we kick off 2021 with our first general meeting of the year. We'll go over the results from last month's votes, run through our major events for the year, and get updates on various initiatives from our committees. As always, we'll have time to talk bugs, issues, and everything Koha. When: 8:30a PT / 11:30a ET / 16:30 UTC (time converter <https://www.timeanddate.com/worldclock/fixedtime.html?msg=koha-US+January+g…> ) Where: https://us02web.zoom.us/j/648572897?pwd=TUpsRE1TYlFPWWxTWFl4TVovSTJ3Zz09 Agenda: https://docs.google.com/document/d/1qjKHwW91pP4zw1PB5k0Zr6wObvqMr6zZSM1PLTC… If you have additional topics for the agenda, please send them to secretary(a)koha-us.org Meetings are held via Zoom video conferencing. A microphone and webcam are recommended but not required. Zoom is available for Windows, Mac, and Linux on desktops, and Android and iOS on mobile devices. For help getting started, visit: https://support.zoom.us/hc/en-us/categories/200101697 These meetings are always free and open to any and all. Jason Robb koha-US secretary secretary(a)koha-us.org

1 0

Zebra required if using Elasticsearch?
by Bales (US), Tasha R 12 Jan '21

12 Jan '21

Good afternoon, I think the answer to the question in my subject is, "yes", but I'd like to check my understanding. After installing Koha in a VM and reviewing various documentation, my understanding was that using Zebra or Elasticsearch was an either/or choice, you use one or the other. However, the Elasticsearch entry on the wiki<https://wiki.koha-community.org/wiki/Elasticsearch> suggests that eliminating Zebra dependency in favor of going full Elasticsearch is a work in progress. Is this accurate? I'm asking because I'm anticipate trouble getting access to download RHEL packages for Zebra<https://www.indexdata.com/resources/software/zebra/>. I was hoping we could entirely avoid it and just use Elasticsearch. Thanks for your time!! Tasha R. Bales

3 2

Payment Report help needed.
by MAMCET Library 12 Jan '21

12 Jan '21

Dear all please help. Patrons fine pay report not generated Error in '*accounttype*' Koha version 20.5 Any Account type report not generated for example " Write amount, Pay amount and New card Collection . I enclosed the Error Screen and report coding. SELECT CONCAT("<a href=\"/cgi-bin/koha/members/boraccount.pl?borrowernumber= <http://boraccount.pl/?borrowernumber=>", T1.borrowernumber, "\" target=\"_blank\">View Transaction</a>") AS 'Click to view' , DATE_FORMAT(DATE(T1.timestamp), "%d/%m/%Y") AS 'Txn Date' , T2.cardnumber AS 'Lib Card No.' , CONCAT(T2.surname) AS 'Students Name' , T3.description AS 'Category' , T2.borrowernotes AS 'Dapartment' , CONCAT(LPAD(REPLACE(ROUND(T1.amount, 2),"-", ""), 8, " ")) AS 'Paid Amount' FROM `accountlines` T1 LEFT JOIN borrowers T2 USING (borrowernumber) LEFT JOIN categories T3 USING (categorycode) WHERE T1.accounttype="PAY" AND DATE(T1.timestamp) BETWEEN <<From date|date>> AND <<To date|date>> ORDER BY DATE(T1.timestamp) -- Thank you.. Librarian, MAMCET <http://mamcet.com/> Trichy-Chennai Trunk Road, Siruganur, Tiruchirappalli-621 105.

1 0

Point to Elasticsearch on a different server?
by Bales (US), Tasha R 11 Jan '21

11 Jan '21

We are working to install Koha on Ubuntu. We already have an Elasticsearch server. I'd like to ask, has anyone pointed their Koha instance to a different server running Elasticsearch, or is this a silly idea (i.e., should we just install Elasticsearch onto our Koha server?)? Thanks for your time, Tasha R. Bales

2 1

Biblio export does not export records when they have no items/holdings
by André Hartmann 10 Jan '21

10 Jan '21

Hello, I am having some trouble with the KOHA export of bibliographic records. In short it seems to export records only when they actually have. I am using KOHA version 18.05.14.000. Here is what I am doing exactly: KOHA --> Tools --> Export Data --> Export bibliographic records To export, I use a file specifying the biblio numbers. Let’s say it has numbers 95 and 96, where 95 does not have items/holdings but 96 has. I do not click „Don’t export items“ but even if I do it does not change anything. I do not click „Remove items…“ but even if I do it does not change anything. The „Dont export fields“ field remains empty. For output format I choose Xml but that does not matter. It is the same what ever I choose * I click the export button. Now I get my resulting Xml file which only has item #96. If I add an item/holding for #95, that one will be exported as well. How do I get it to work such that biblio records without items/holdings get exported? My aim is to use the resulting file and import it into another KOHA instance oft he same version. Thanks in advance 😊

3 2

Setting up a Local Use Only item type
by Michael Adamyk 09 Jan '21

09 Jan '21

Hi everyone, I am the manager for a Koha consortium, and I'm trying to figure out the best way to make an item that is available for checkout only at the local branch, and nowhere else. (Generally we share items freely between libraries ("branches").) In this case, though, there shouldn't be any holds placed on it from anywhere other than the home library. Think a special collection that is only available to local patrons. In the past, we've gotten around this two ways: 1. Set up a "Local Availability Only" lost status. This works well, except that it is temporary and is cleared every time an item is checked in. Not very good for a long-term solution. 2. Set up our circ rules to prevent holds on specific item types. This works only as long as other librarians don't decide to override the holds restrictions. If they do, it doesn't work as planned. What are your suggestions? Is there a Koha setting for precisely this type of situation that I am overlooking? Thanks in advance for your help! -- *Michael Adamyk* Technology Manager* | *Central Kansas Library System 620-792-4865

2 1