December 2017 - Koha - lists.katipo.co.nz

Sorry, your Google login failed
by tony.h 19 Jan '23

19 Jan '23

Greetings, I'm having trouble getting the Google login to work since upgrading/rebuilding Koha (we rebuilt the VPS and followed the install guide: https://wiki.koha-community.org/wiki/Debian) *The problem:* 1) I can log in through my local account, no problem. 2) I then try to login through my Google account 3) After pressing allow from the accounts.google.com site, a message is displayed: /Sorry, your Google login failed. .../ The full message is below. "Log in to your account Google login Sorry, your Google login failed. The email address you are trying to use is not associated with a borrower at this library. Please note that the Google login will only work if you are using the e-mail address registered with this library. If you want to, you can try to log in using a different account Log in with Google If you do not have a Google account, but do have a local account, you can still log in:" There are no errors in the Apache log files. *Configuration* Since we had troubles, I'm following the testing guide to configure the OAuth login: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10988#c68 I removed the Google OAuth entries: DELETE FROM systempreferences WHERE variable LIKE 'GoogleO%'; I then ran the upgrade schema tool, as I did when I imported the db: sudo koha-upgrade-schema keiin_lib I added values back in admin panel (Home › Administration › System preferences > Google OpenID Connect I confirmed the 4 values are displayed in the MySQL DB: SELECT * FROM systempreferences WHERE variable LIKE 'GoogleO%'; Any thoughts? Tony -- View this message in context: http://koha.1045719.n5.nabble.com/Sorry-your-Google-login-failed-tp5895227.… Sent from the Koha-general mailing list archive at Nabble.com.

5 5

Location of tag 245$c in koha database
by vinod mishra 30 Jul '21

30 Jul '21

Dear All, May i know the location of marc tag 245$c im koha database/table, i wish to get the report of the same. With Regards, Vinod Kumar Mishra, Assistant Librarian, Biju Patnaik Central Library (BPCL), NIT Rourkela, Sundergadh-769008, Odisha, India. Mob:91+9439420860 Website: http://mishravk.com/ ORCID ID: http://orcid.org/0000-0003-4666-7874 *"Spiritual relationship is far more precious than physical. Physical relationship divorced from spiritual is body without soul" -- Mahatma Gandhi*

3 4

change of domain name
by glernil evangelista 13 Jan '20

13 Jan '20

Good day! How can I change the domain name of a koha instance? I have a Koha 12.0 installed using debian repository.

4 3

Koha upgrade 3.18.11 --> 3.20.07
by Bortel, Gary 16 Oct '19

16 Oct '19

I am seeing two MySQL errors thrown when trying to update from 3.18.11 --> 3.20.07. Are these benign or something about which concern should be raised? The installation here is Ubuntu 14.04.3 with a multi-tenant package install of Koha. Mysql Ver 14.14 Distrib 5.5.46, for debian-linux-gnu (x86_64) using readline 6.3 . . . . Upgrade to 3.20.00.002 done (Bug 5010: Fix OPACBaseURL to include protocol) Upgrade to 3.20.01.000 done (Koha 3.20.1) Upgrade to 3.20.01.001 done (Bug 9942: Privacy is correctly set) Upgrade to 3.20.01.002 done (Bug 13993: Correct orderstatus for transferred orders) Upgrade to 3.20.02.000 done (Koha 3.20.2) Upgrade to 3.20.03.000 done (Koha 3.20.3) DBD::mysql::db do failed: Can't create table 'koha_library.#sql-4b9_42' (errno: 121) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 10584. Upgrade to 3.20.03.001 done (Bug 14205: Deleting an Item/Record does not remove link to course reserve) Upgrade to 3.20.03.002 done (Bug 14717: Prevent 0000-00-00 dates in patron data) DBD::mysql::db do failed: Duplicate entry '1-self_checkout' for key 'PRIMARY' at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 10614. Upgrade to 3.20.03.003 done (Bug 14298: AutoSelfCheckID user should only be able to access SCO ) Upgrade to 3.20.04.000 done (Koha 3.20.4) Upgrade to 3.20.04.001 done (Bug 14820: SMSSendUsername and SMSSendPassword are not listed in the system preferences) Upgrade to 3.20.05.000 done (Koha 3.20.4) Upgrade to 3.20.06.000 done (Koha 3.20.5) Upgrade to 3.20.06.001 done (Bug 14978: Make sure issues.itemnumber is a unique key) Upgrade to 3.20.07.000 done (3.20.7 release) gcb ______________________ Gary C. Bortel IT Services Manager, Library Development Program Office of the Secretary of State, Washington State Library 6880 Capitol Boulevard Southeast P.O. Box 42460 Olympia, WA 98501-2460 gary.bortel(a)sos.wa.gov<mailto:gbortel@secstate.wa.gov> voice: 360.570.5588 fax: 360.586.7575 Washington State Library: Empowering 21st Century Washington

9 22

Library Summary / Stats - Report Page - Help
by SATISH 01 Oct '19

01 Oct '19

Dear All, I have a suggestion or expectation in koha regarding library summary. a default page dedicated to "library summary" which is in-built in koha (may be inside reports) and gives: 1. No.of Non Repetitive Titles (which means records) : 0000 2. No. of books (items): 0000 3. No. of books issued / checked out (as on date): 0000 4. No. of Active Patrons Cards: 0000 5. No. of De-activated/ Expired Patrons Cards: 0000 6. Total Expenditure on Books: 0000 (in respective currencies) "Example: http://eprints.iisc.ernet.in/ | Number of publications in the repository: 44108" Instead of running separate sql queries which are commonly needed, repetitive in requirements as a "*ready reference*", could be displayed in a single summary page or "about library", and this should not be created manually, and could be generated from the script itself. This also helps during library inspection committee visits, auditing takes place, whenever reporting is required for the stake holders, etc.. If this facility is already available, kindly let me know, how to achieve this. Otherwise, kindly consider this as a suggestion. With thanks Satish MV Librarain Govt. Engineering College, Hassan. Karnataka. www.gechassan.ac.in --

3 7

Problem uploading patrons
by Elaine Bradtke 26 Aug '19

26 Aug '19

We're running 3.18.04. One (and only one) of my colleagues is unable to upload patron files. It's very curious, she has all the permissions, and I and another colleague have uploaded the same file without a problem. I have even logged into her account and uploaded the file successfully. But whenever she tries she gets a long string of error messages that boil down to Koha not parsing the header row. I've asked her to clear her browser (Firefox) history and cookies (there's an 8 hour time difference so I won't know if this works til tomorrow) Other than that I don't know why she can't do it and we can. Any ideas what might be causing the problem? -- Elaine Bradtke Data Wrangler VWML English Folk Dance and Song Society | http://www.efdss.org 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 --------------------------------------------------------------------------- "Writing about music is like dancing about architecture" --Elvis Costello (Musician magazine No. 60 (October 1983), p. 52)

9 14

Unable to Check-In Error
by SATISH 19 Sep '18

19 Sep '18

Hi, Running Koha 16.11.11 / Package Installation/ Ubuntu 14.04 Desktop with MySQL. (updating from previous versions as and when the new releases are made) "Unable to Check-In" message is displayed for few patrons when trying perform checkin. Can you please help me how to fix the issue. Please find screenshots of the same here. https://ibb.co/nHf0FG https://ibb.co/mNHahw Already did dbms auto increment fix as per URL https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix#The_solution With Thanks Satish MV Librarian Govt. Engineering College, Hassan Karnataka. --

6 10

Add pictures in notices
by BOUIS Sonia 03 Jul '18

03 Jul '18

Hello, Do you have any tip to add pictures in notices template. I've seen that we could add a picture in branches.opac_info but it isn't sufficient for us. We want to use discharge notices but we need to insert a signature in it to make it "official" for other universities. I would like to insert a signature picture in the discharge notice template but I don't see how to do.. Thanks in advance, Cheers Sonia BOUIS Responsable du Service des application 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

4 4

Re: [Koha] Koha 17.05 and memcached
by Adrian 15 May '18

15 May '18

Thank you very much Guille! Finally I made it work, but is a weird configuration... the only way to make it work at least on 17.05, was to have part of the config in the xml file, and the rest on the apache-configured file: ... SetEnv MEMCACHED_SERVERS "127.0.0.1:11211" SetEnv MEMCACHED_NAMESPACE "koha-intra" ... I receive a warning on the about koha page (Config read from ENV and koha-conf.xml), but the Status is green and running. Thank you for your help! -- View this message in context: http://koha.1045719.n5.nabble.com/Koha-17-05-and-memcached-tp5939903p594095… Sent from the Koha-general mailing list archive at Nabble.com.

7 15

doubt regarding serial numbering pattern
by pariyaram central library 02 Feb '18

02 Feb '18

Hello.... I am a fresher in koha and now carrying out the serial section and I have a doubt regarding the serial planning. Now I am doing a journal LANCET which is a weekly having 51 issues and the vol changes with 25th issue but the issue no is continuous up to 51. my problem is the issue no has got 5 digits and in the prediction pattern while giving 10064 in BEGINS WITH column OF ISSUE NO and while going to the test prediction pattern, it will begin with 10064 but the next issue will be numbered 1 next issue will be numbered 2 and so on. The actual pattern in which the journal arrives is mentioned below.ie 1.vol no 389 iss no 10064 2.vol no 389 iss no 10065 3.vol no 389 iss no 10066 4.vol no 389 iss no 10067 5.vol no 389 iss no 10068 . . . . . 25.vol no 390 iss no 10089 . . . . 51.vol no 390 iss no 10115 KINDLY HELP * sd/Central library*

2 1