- Koha - lists.katipo.co.nz

Call for news - Newsletter February 2023
by Koha Newsletter 13 Feb '23

13 Feb '23

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

1 0

adding elements to opac-user.pl?
by Carlos Lopez 12 Feb '23

12 Feb '23

Hi everyone I don't know whether I'm being dense or whether there isn't much information out there: Is there a way we can add a column (specifically items.copy or items.barcode) to the "Checked out" display on opac-user.pl? For a while there we thought we were suppressing a bunch of columns from there but it turned out we were hiding columns from the "Article requests" view instead. With kind regards from the Dalton McCaughey Library Team Carlos Lopez Dalton McCaughey Library | 29 College Crescent, Parkville, VICTORIA 3052 Ph: 03 9340 8888 ext.1 | library(a)dml.vic.edu.au<mailto:library@dml.vic.edu.au> | library.dmlibrary.org.au

2 2

Update database from Koha 22.06.00.078 to 22.11.02.000 failed
by Δημήτρης Δαλαγιώργος 12 Feb '23

12 Feb '23

I upgraded my Debian system from 9 to 11. When I tried to log in to koha admin I was welcomed by the web installer. Trying to run the web installer I got the following error: Web installer › Update database We are upgrading from Koha 22.06.00.078 to 22.11.02.000 Updating database structure Update errors : Upgrade to 22.06.00.079 [14:46:54]: Bug 32030 - Add an ERM module ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs at /usr/share/koha/lib/C4/Installer.pm line 739 Added new system preference 'ERMModule' ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs at /usr/share/koha/lib/C4/Installer.pm line 739 Added new permission 'erm' ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs at /usr/share/koha/lib/C4/Installer.pm line 739 I have no idea what they mean and how to fix them. Dimitrios Dalagiorgos 3rd High School of Kozani Greece

2 2

Feedback on Koha research by koha commercial support providers
by vinod mishra 11 Feb '23

11 Feb '23

Hello Please just check and give your feedback on koha related research https://forms.gle/rwMjcBPbXpdL8XvQ9 I ensure that data will not be share with anyone. Thanks and Regards With Regards,

1 1

Re: [Koha] Beginners problems - Z39.50 and the reservoir
by Katrin Fischer 10 Feb '23

10 Feb '23

Hi René, great! You are right, there is a daemon, I am not sure why it is/was not running. Try the koha-indexer package command to start it. That will give you almost immediate indexing of new records, instead of only every 5 minutes. Hope this helps, Katrin On 10.02.23 23:04, René Seindal wrote: > Hi Katrin, > > Thanks a million. This helped me forward. > > Search engine is Zebra. I do have Elasticsearch installed on the > production server, but for now this on a test computer. > > I ended up reinstalling everything to make sure I hadn't missed > something. > > First issue, the instanced used UNIMARC but Zebra was set up to use > MARC21. That might have been part of the problem. > > Then I could get the records to appear if I used koha-rebuild-zebra -f > but only if I did a full rebuild which would be excessive in a > production environment. > > Second issue, I had to uncomment a line in /etc/cron.d/koha-common to > run koha-rebuild-zebra every five minutes. With that line active, my > records now appear in the OPAC. > > In /etc/default/koha-common I do have USE_INDEXER_DAEMON=yes but the > link in there led me to the second issue above. I would have thought > that the indexer daemon meant it wouldn't be necessary to run the > indexer from cron, but that is not what this page says: > https://wiki.koha-community.org/wiki/PackagesIndexDaemon > > In any case I can now import records into my OPAC, so for now I'm > happy :-) > > Thanks again. > > René > > On 2023-02-10 20:16, Katrin Fischer wrote: >> Hi René, >> >> the reservoir is filled automatically everytime you do a Z39.50 search >> and is separate from the catalog. As you found out already, you can >> regularly clean it using the cronjob. >> >> It sounds like you can import and save records, but later they are not >> found in the catalog? >> >> I think if you create a SQL report or query the database with something >> like "SELECT * from biblio" you'd see that the records have been stored. >> I suspect, that the search engine (either Zebra or Elasticsearch) is not >> working and therefore the records are not indexed and searchable. >> >> What is the setting of your SearchEngine system preference in >> Administration? If you set it to Zebra, try (re)starting it using the >> package commands. >> >> Hope that helps >> >> Katrin >> >> On 10.02.23 14:46, Giacomo Visini wrote: >>> Hi René, >>> >>> I'm not sure if I completely understand your post, but you want to >>> import 1 specific record using the Z39.50 application in the >>> cataloging section, right? Normally, when you get a hit (through >>> ISBN or whatever) you can import the data by clicking 'Import'. This >>> will bring you to the 'Add MARC record'-editor, with most fields >>> filled in. There you can add, delete, change your data the way you >>> like it. On the upper left side you'll have the option to 'Save' the >>> bibliographic record. That way the record will be saved and will be >>> visible in your OPAC. >>> >>> AFAIK, no "reservoir" is needed, nor the 'Manage staged records' tool. >>> >>> Note: this is the way to work to import 1 record at a time. For >>> batch imports, that's another question 😊 >>> >>> Best regards, >>> >>> Giacomo Visini I Library assistant >>> DIVA, Antwerp Home of Diamonds >>> Visiting adress library (temporary): Kaasstraat 13, B-2000 Antwerpen >>> Postal adress: Kaasstraat 13, 2000 Antwerpen >>> T + 32 3 360 52 40 M + 32 485 66 49 98 >>> giacomo.visini(a)divaantwerp.be www.divaantwerp.be >>> >>> >>> -----Oorspronkelijk bericht----- >>> Van: Koha <koha-bounces(a)lists.katipo.co.nz> Namens René Seindal >>> Verzonden: vrijdag 10 februari 2023 8:40 >>> Aan: koha(a)lists.katipo.co.nz >>> Onderwerp: [Koha] Beginners problems - Z39.50 and the reservoir >>> >>> Hi, >>> >>> I'm René Seindal, and I've been setting up an evaluation instance of >>> Koha for my wife. I'm not a librarian, but she is. We're in Italy. >>> >>> I've installe Koha on an existing Debian testing system. Everything >>> apparently went smooth and after configuration the public and the >>> intra sites are functioning. As far as I can see the 'koha-common' >>> services are running as they should. >>> >>> I then searched for an ISBN in the Italian National Library Service >>> through Z39.50. Found the book, imported it (got it twice for some >>> reason) and the records are now in the "reservoir". >>> >>> I can see them in the Cataloging section but not anywhere else. It >>> is not in the public catalog. I cannot do anything with them. I >>> cannot move them to the real catalogue. I cannot remove them. I can >>> select "Add biblio" on a menu, but that doesn't lead me anywhere >>> either. >>> >>> The "Manage staged records" section is empty. >>> >>> I've managed to remove all the records in the reservoir by fiddling >>> with a database cleanup cron job, but that removed them. The public >>> catalog remained empty. >>> >>> I'm stymied. >>> >>> This is very basic, and I can't get it to work, so I presume I'm >>> doing it wrong. >>> >>> I hope some of you can help me out. >>> >>> Thanks, >>> René Seindal

1 0

Beginners problems - Z39.50 and the reservoir
by René Seindal 10 Feb '23

10 Feb '23

Hi, I'm René Seindal, and I've been setting up an evaluation instance of Koha for my wife. I'm not a librarian, but she is. We're in Italy. I've installe Koha on an existing Debian testing system. Everything apparently went smooth and after configuration the public and the intra sites are functioning. As far as I can see the 'koha-common' services are running as they should. I then searched for an ISBN in the Italian National Library Service through Z39.50. Found the book, imported it (got it twice for some reason) and the records are now in the "reservoir". I can see them in the Cataloging section but not anywhere else. It is not in the public catalog. I cannot do anything with them. I cannot move them to the real catalogue. I cannot remove them. I can select "Add biblio" on a menu, but that doesn't lead me anywhere either. The "Manage staged records" section is empty. I've managed to remove all the records in the reservoir by fiddling with a database cleanup cron job, but that removed them. The public catalog remained empty. I'm stymied. This is very basic, and I can't get it to work, so I presume I'm doing it wrong. I hope some of you can help me out. Thanks, René Seindal -- René Seindal

3 3

Documented process for server and instance duplication?
by David Liddle 10 Feb '23

10 Feb '23

Hello all! I'm involved in supporting a consortium of many small libraries that utilizes a single instance of Koha on a cloud host. When a new version is released, their limited staff have to verify that all of the customizations and quirks will survive the upgrade. To facilitate this, I would like to have a process by which I create a near-duplicate of the server on my local virtualization system, modify it to suit the new environment, and then make it available for testing the upgrade. The system can easily handle the extra load, and I have an external IP address that I can assign for access. In this way, the production system can remain untouched until we're 100% certain that it can be upgraded without affecting its important functions. I managed to do this once back in 2021, but a) I did not document all of the steps I had to take to get it working, and b) there were still details I had missed that we discovered only recently. The key changes are the library name (?) and the domain/links used. Before I plow down this path again—this time doing my best to cover all the actions and changes that need to be implemented—I thought I'd poll the community. Who out there has a documented process that you'd be willing to share? What have you done? With gratitude for your consideration and contributions, David Liddle

1 0

Koha Spool folder issue
by Russel G. P. Shihepo 10 Feb '23

10 Feb '23

Dear Community Does anyone know the significance of the spool directory of koha? /var/spool/koha Regards, Russel Shihepo Notitia Systems cc

2 1

koha-US Board & General Meeting Minutes for February 2023
by Jennifer Marlatt 10 Feb '23

10 Feb '23

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

1 0

exportar registros marc bibliográficos en formato isbd
by Biblioteca FIUNER 09 Feb '23

09 Feb '23

Buenos días Existe alguna herramienta o programación que pueda aplicarse para exportar, en lote, registros bibliográficos en formato isbd? Is there any tool or programming that can be applied to export, in batch, bibliographic records in isbd format? Gracias de antemano Lic. Brenda Ramirez Jefa ------ Biblioteca "Dr. Eduardo A. Barbagelata" http://biblioteca-fing.uner.edu.ar/ (24/7 disponible) correo: biblioteca.ingenieria(a)uner.edu.ar Atención al público de lunes a viernes de 8 a 18 hs.

2 1