- Koha - lists.katipo.co.nz

Advice for how to update huge numbers of bib records, for former Millennium user
by Bales (US), Tasha R 22 Jan '21

22 Jan '21

What would be the Koha equivalent to Millennium Create Lists* (or Alma Normalization Rules and Record Sets)? So far, I see that lists and carts can be used to update records in Koha, but this seems to demand working with a pre-determined list of record numbers, or else by manually adding items to a cart. What if I need to update a huge number of "unknown" records meeting specific criteria? Can anyone suggest what the approach would be to accomplish an objective like this: A non-administrator with limited technical skills needs to gather and update 40,000 bib records in Koha that can't be identified by any single unifying attributes. My Millennium query might have looked like this: * Bib record not attached to order AND * (Location is Y or Location is X or Location is Z) and * Author is not TODD and * Note doesn't have FREE *Millennium Create Lists allows you to create a Boolean Search, with up to about 20 statements, to query the entire database (various methods to search subsets or existing result sets also exist) and saves it to a file that can then be exported, or operated on (to apply global updates to fixed or variable fields, for instance). No knowledge of SQL is needed. Thanks in advance for any tips. As an administrator, I could conceivably do this with SQL, but that's not feasible for cataloging staff. We update large quantities of records all the time. Tasha R. Bales

3 4

Logical schema about holds
by BOUIS Sonia 21 Jan '21

21 Jan '21

Hello, Is there somewhere, someone (a really wonderful person) who had the idea to do a logical schema of how the holds work in Koha, with all the options possible and especially with a multi branches Koha where not all the branches chose to allow reserves. Yes, sometimes, I still believe in Santa Claus :) Cheers Sonia BOUIS Responsable du Service des applications documentaires BIBLIOTHÈQUES UNIVERSITAIRES Bibliothèque de la Manufacture UNIVERSITÉ JEAN MOULIN LYON 3 1C AVENUE DES FRÈRES LUMIÈRE CS 78242 69372 LYON CEDEX 08 ligne directe : +33 (0)4 78 78 79 03 http://bu.univ-lyon3.fr<http://bu.univ-lyon3.fr/> L'Université Jean Moulin est membre fondateur de l'Université de Lyon

1 0

Auto renewal not working
by Michael Kuhn 20 Jan '21

20 Jan '21

Hi Our library works with Koha 20.05.02 on Debian GNU/Linux 10. The automatic renewal doesn't work as expected. These are the relevant circulation rules: * Loan period: 28 * Unit: Days * Renewals allowed (count): 5 * Renewal period: 28 * No renewal before: (empty) - according to https://bywatersolutions.com/education/setting-up-auto-renewals-with-new-fe… it is said that a blank value will indicate that the auto-renewal will occur on the day it is due. * Automatic renewal: Yes * No automatic renewal after: (empty) * No automatic renewal after (hard limit): (empty) In the staff client we can see the checkouts of the users - but for every checkout it says "0 Can no longer be auto-renewed - number of checkout days exceeded (5 of 5 renewals remaining)". In fact NONE of these checkouts were EVER auto-renewed. As we see in table "issues" the value in column "auto_renew" is "1". But the value in column "auto_renew_error" changes from NULL to "auto_too_soon" after the checkout day, then after some days to "auto_too_late". No auto renewal is ever performed. We have set system preference "RenewalLog" to "Log" but no renewal actions are ever logged. How can we get auto renewal get to work properly? 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(a)adminkuhn.ch · W www.adminkuhn.ch

3 6

Fwd: SQL Report Coding need.
by Elaine Bradtke 19 Jan '21

19 Jan '21

I'm a cut and paste report writer, I think you need someone who really understands SQL. Forwarding to the list. Elaine VWML <https://vwml.org> ---------- Forwarded message --------- From: MAMCET Library <mamcet.library10(a)gmail.com> Date: Sat, Jan 16, 2021 at 7:30 PM Subject: Re: [Koha] SQL Report Coding need. To: Elaine Bradtke <eb(a)efdss.org> This report genereted but not out put ples help. Koha version 20.4 This report run Error in "T1.accounttype " 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) On Wed, 13 Jan 2021, 11:49 pm Elaine Bradtke, <eb(a)efdss.org> wrote: > Do any of the reports here come close to what you need? > https://wiki.koha-community.org/wiki/SQL_Reports_Patrons > Elaine > VWML <https://vwml.org> > > > > On Tue, Jan 12, 2021 at 10:28 PM MAMCET Library < > mamcet.library10(a)gmail.com> wrote: > >> 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. >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha(a)lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> >

3 2

Newbie question concerning system maintenance
by Andreas Tomiak 19 Jan '21

19 Jan '21

Hello, I´ve tried to find some information in koha´s documentation, but I failed to find anything usable. Sorry for my question: Does Koha have a common way (script?) to update it to newer versions or do I have to make a new installation of it, configure it and reinstall the previous dumped database? BTW: I´ve just tried to install the version 2020.11 on a new raspberry pi 4. It works with the normal procedure without any hassle. I want to use this as a test system only. The SD cards may be restored very easy, if I´ve made some silly things with Koha on it. Nice, good work! Thanks, Andreas Tomiak Library head at HZB -- Dr. Andreas Tomiak Bibliotheksleiter ORCID https://orcid.org/0000-0002-3952-5416 SCOPUS Author ID 16450079500 ResearcherID M-5165-2015 SSR DEA900130625 GND 1132720850 VIAF ID 166149616483803750669 http://viaf.org/viaf/166149616483803750669 Tel.: +49 30 8062 42593, +49 160 9360 2804, Fax: +49 30 8062 42953 ________________________________________________________________________________________________ Helmholtz-Zentrum Berlin für Materialien und Energie GmbH Mitglied der Hermann von Helmholtz-Gemeinschaft Deutscher Forschungszentren e.V. Aufsichtsrat: Vorsitzender Dr. Volkmar Dietz, stv. Vorsitzende Dr. Jutta Koch-Unterseher Geschäftsführung: Prof. Dr. Bernd Rech (Sprecher), Prof. Dr. Jan Lüning, Thomas Frederking Sitz Berlin, AG Charlottenburg, 89 HRB 5583 Postadresse: Hahn-Meitner-Platz 1 D-14109 Berlin https://www.helmholtz-berlin.de Ringgold ID (RIN) 28340 ISNI http:/isni.org/isni/0000000110903682 ROR https://ror.org/02aj13c28 GRID https://grid.ac/institutes/grid.424048.e

2 1

Re: [Koha] Migrating Koha Servers
by Charles Kelley 19 Jan '21

19 Jan '21

Hello, all! In our latest exchange, on 18 Jan. 2021 at 20:33 [JST] I asked several questions about migrating a Koha database from one server to another, to wit: > (1) How do you find out the password to MySQL? > > (2) Does it matter whether you are running MySQL or MariaDB? > > (3) Is "koha_library" a fixed phrase? Or is it the name of the Koha > instance you are migrating, e.g., if your library is named ASDLIB, do you > use "koha_library" or "ASDLIB"? > > (4) If you are running ElasticSearch, are there complications and if so, > what are they and their solutions? > > (5) How does Zebra factor into all this? > In a recent exchange, on 18 Jan. 2021 at 23:01 [JST], Aswin Unnikrishnan <aswinunni01(a)gmail.com> replied: > Im also fairly new to koha so ill try to answer to the extent of my > knowledge. > 1. You can find all the details about your database if you check towards > the end of the koha-conf.xml file that will be present at > /etc/koha/sites/KOHA_INSTANCE/koha-conf.xml , where KOHA_INSTANCE is your > koha instance name. details will be under <config> tag. > 2. It doesn't matter if the database is mysql or mariadB. both are the > same and you can use the same commands for both. > 3. No . "koha_library" is used as an example. In most cases, you have to > change "library" with your instance name. so if your instance name is > "ASDLIB" it should be koha_ASDLIB > 4,5. I'm not exactly sure about Elastic search, but ElasticSearch and > Zebra are 2 search engines that can be used with koha. ElasticSearch is > fairly newer if I'm right, and still not incorporated into all parts of > koha, and zebra is the default search engine that koha uses. So you need > either ElasticSearch or Zebra, if you want to search for a book in your > OPAC and get the results. > In a recent exchange, on 18 Jan. 2021 at 23:01 [JST], Benjade Palmero < benpal4ever(a)yahoo.com> replied and through the Koha User discussion group on Facebook: Just dump the Koha database from your old server through mysqldump then > restore that sql file in your new server. > I keep getting the error message 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock'. I have sought remedy online but alas, none has worked for me. The migration process has taken me all weekend plus yesterday, and it has yielded no appreciable results. I have little choice but to abandon this type of migration effort and import the bibliographic .MRC file anew and reenter the rest anew unless something new comes to light in the next few hours. By the way, this is not a reflection on Aswin Unnikrishnan or Benjade Palmero. Koha ILS, v. 20.05 Debian Stretch (v. 9.13) Thanks for your help anyhow -- 気を付けて。 /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(a)aol.com [h] cmkelleymls(a)gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.

2 1

Re: [Koha] Importing Authority Records without Renumbering
by Charles Kelley 19 Jan '21

19 Jan '21

Hello, Katrin et al! In our latest exchange, on 18 Jan. 2021 at 23:22, Katrin Fischer < katrin.fischer.83(a)web.de> wrote: to my knowledge there is currently no way to avoid this renumbering. Koha > will assign the authority record the PK from the auth_header table on > importing, you can't keep your own numbers. I think this would be a useful > switch - please consider filing an enhancement request on bugzilla if there > isn't one yet. > An excellent suggestion. I just found the Bugzilla reporting form. I'm going to try. Thanks. > I wonder: why don't you move the whole database to the new server instead > of exporting and importing data? > I've been trying that, too, but that engenders a different problem: '"Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock'". Most frustrating, to say the least. -- 気を付けて。 /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(a)aol.com [h] cmkelleymls(a)gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.

1 0

Importing Authority Records without Renumbering
by Charles Kelley 19 Jan '21

19 Jan '21

Hello, everyone! My library is migrating our Koha ILS to a new machine. We are now ready to upload the authority and bibliographic records. I tried a test upload of the authority records, but I was surprised and disappointed when in the upload of the authority records, the authority record number was changed. The change reflects the deletion of duplicate and merged authority records we have found in recent months. Needless to say, this cannot stand because the bibliographic fields that are connected to a specific authority record through $9 subfield will end up connected with a different authority record. Case in point: In the current database, I made a dummy author named Sam Loesser, and Koha automatically assigned him authority record #197. In the test database, Sam is assigned authority record #190 instead when the record is imported. I have to admit I'm using the Import (Stage ... and Staged ...) Tools, not the Perl script. Maybe the Perl script has a switch to force such record assignment. I don't know; I'm just asking. Is there a way to fix this, i.e., is there a way to force the authority record uploader to assign the authority record number that is in the 001 field of the incoming authority record? 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(a)aol.com [h] cmkelleymls(a)gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.

2 1

Help with shelf browser and classification source
by Inês M. Ferreira 19 Jan '21

19 Jan '21

Good morning, (I tried to send this email before, but I think something went wrong. If it did send, apologies for the duplicate.) I am responsible for a small private library and we have recently installed Koha (20.05.04.000, using UNIMARC and UDC). I am having some issues with the shelf browser and the classification source. The shelf browser does not appear. When clicking on the link, only a link to "close the shelf browser" does. I have just finished assigning shelving locations (995$e) to all items (due to previously having periodicals show alongside books), and for this purpose I have created 3 locations: geral (general), referência (reference), periódicos (periodicals). Before assigning the locations, the shelf browser would sometimes appear; now it never does (only the link to close it, as mentioned above). What could be the problem? I’m not sure if this is relevant and could be impacting the shelf browser, but our search doesn’t work -- it always shows no results (our IT team is working on it). A second issue (that might be related) is that although I am trying to work with UDC, I think Koha is still defaulting to Dewey. I have only found out about the setting DefaultClassificationSource a few days ago, and it is set as Dewey (I didn’t change it because I would rather change everything, including all 1000+ items, at once). On the administration menu > classification sources, I only have UDC as ‘in use’. What do I need to do to make sure all of Koha is using UDC? I am very new to Koha, so any help is appreciated! Thank you. Kindest regards, Inês F.

2 5

Migrating Koha Servers
by Charles Kelley 19 Jan '21

19 Jan '21

My library is migrating its Koha database to a new server. I have found instructions on both YouTube and static sources. But the instructions are not perfectly clear to me and I have a few questions. (1) How do you find out the password to MySQL? (2) Does it matter whether you are running MySQL or MariaDB? (3) Is "koha_library" a fixed phrase? Or is it the name of the Koha instance you are migrating, e.g., if your library is named ASDLIB, do you use "koha_library" or "ASDLIB"? (4) If you are running ElasticSearch, are there complications and if so, what are they and their solutions? (5) How does Zebra factor into all this? I'm trying to avoid * reentering frameworks; * downloading MRC files of the authority records and bibliographic records and uploading them into the new server because of suspected linkage problems between the authority records and $9 subfields in the bibliographic records; * reentering system preferences; * reentering patron information; and so forth. Thank you very much. -- 気を付けて。 /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(a)aol.com [h] cmkelleymls(a)gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.

3 2