January 2020 - Koha - lists.katipo.co.nz

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

18 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

Koha on Debian 10
by Clogher Historical Society 09 Jun '22

09 Jun '22

Hi, Thanks for the replies, it seems that I need to be running Debian 9 ( Stretch) not version 10 (Buster) but there is someone called: mtj on IRC who is working on Debian 10. There doesn't seem to be a downgrade option in Debian so reinstalling the whole operating system is pretty awkward. I hope (MTJ) includes Debian 10 support soon. Best Regards, Aindriú

5 7

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

Check-in Receipt
by Mubassir Ahsan 15 Feb '21

15 Feb '21

Is there any way to print check-in receipt in koha. *Best wishes.--------------------Md. Mubassir Ahsan* *Library In-Charge* Southeast University Phone: +8801916303060 Email: mahsandu(a)gmail.com Facebook: mmahsan <http://facebook.com/mmahsan> Skype: mahsandu Twitter: mahsandu

4 4

moving database from 17.5 to 19.11 error
by Alvaro Cornejo 27 Aug '20

27 Aug '20

Hi I´m tryin to do the DB move from 17.5 to 19.11. I take following steps: - backup 17.5 with koha-backup and I get two files a sql.gz and a tar.gz - scp both files to new server - run koha-remove biblioteca - run koha-restore sql tar files and I start having a lot of errors like: ERROR: File exists: /var/lib/koha/biblioteca/biblios/key/ and at the end I have: ERROR 1396 (HY000) at line 1: Operation DROP USER failed for 'koha_biblioteca'@'%' ERROR 1819 (HY000) at line 1: Your password does not satisfy the current policy requirements DBI connect('database=koha_biblioteca;host=localhost;port=3306','koha_biblioteca',...) failed: Access denied for user 'koha_biblioteca'@'localhost' (using password: YES) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1517. DBI connect('database=koha_biblioteca;host=localhost;port=3306','koha_biblioteca',...) failed: Access denied for user 'koha_biblioteca'@'localhost' (using password: YES) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1517. DBI connect('database=koha_biblioteca;host=localhost;port=3306','koha_biblioteca',...) failed: Access denied for user 'koha_biblioteca'@'localhost' (using password: YES) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1517. DBI connect('database=koha_biblioteca;host=localhost;port=3306','koha_biblioteca',...) failed: Access denied for user 'koha_biblioteca'@'localhost' (using password: YES) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1517. DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: Access denied for user 'koha_biblioteca'@'localhost' (using password: YES) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1520. at /usr/share/koha/lib/Koha/Database.pm line 107 Something went wrong rebuilding biblio indexes for biblioteca DBI connect('database=koha_biblioteca;host=localhost;port=3306','koha_biblioteca',...) failed: Access denied for user 'koha_biblioteca'@'localhost' (using password: YES) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1517. DBI connect('database=koha_biblioteca;host=localhost;port=3306','koha_biblioteca',...) failed: Access denied for user 'koha_biblioteca'@'localhost' (using password: YES) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1517. DBI connect('database=koha_biblioteca;host=localhost;port=3306','koha_biblioteca',...) failed: Access denied for user 'koha_biblioteca'@'localhost' (using password: YES) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1517. DBI connect('database=koha_biblioteca;host=localhost;port=3306','koha_biblioteca',...) failed: Access denied for user 'koha_biblioteca'@'localhost' (using password: YES) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1517. DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: Access denied for user 'koha_biblioteca'@'localhost' (using password: YES) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1520. at /usr/share/koha/lib/Koha/Database.pm line 107 Something went wrong rebuilding authority indexes for biblioteca [....] Restarting apache2 (via systemctl): apache2.serviceJob for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xe" for details. failed! I double checked that mysqroot pass is the same on both systems. How do I check "user koha_biblioteca" password to be the same on both systems? |-----------------------------------------------------------------------------------------------------------------| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.com

5 7

Remove Not For Loan / Available distinctions
by Elaine Bradtke 26 Aug '20

26 Aug '20

We've been running Koha for a while, but have a new person in charge and they (correctly) pointed out that displaying Available / Not Available status for a collection that's 99% reference only is useless and possibly confusing. Is there an easy way to switch this display off? A quick look round the preferences didn't show anything. We're trying to avoid custom configurations because we've got very minimal, volunteer support. Right now, just about everything shows up as 'not available' even though it's sitting right there on the shelf. Thanks! Elaine Bradtke 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

2 3

duplicate biblios
by Nalisha Tamang 07 Feb '20

07 Feb '20

Dear all, As we have imported 26,ooo books into koha and I already had 4700 books entered manually . as I have added 0 in front of barcode with the 4700 books e.g (02412). when i imported 26000 books it didn't replace the existing records which has no 0 in front of barcode e.g (2400). Now when I check the catalog it shows many duplicates. which would be 26000 books + 4700 books + duplicate biblios. Now I don't know what to do????????? I have attached the screenshot... please help me ASAP.... With regards, Nalisha

2 2

Elasticsearch recent works at BibLibre
by Claire Hernandez 31 Jan '20

31 Jan '20

Hi, This week, some devs work together to move forward concretely on Elasticsearch issues encountered. You will find below a focus on some points (some are at poc state today) written by Alex and Jajm from BibLibre. We would be glad to discuss these topics at hackfest in march and having user feedbacks too :) #1 Proof of concept for language analyzers bug 21357 - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21357#c32 It's an attempt at having a default ES configuration with stemming, elision, etc. that works with multi-languages catalogs You can read the comments and patch for more information. #2 Compatibilites for tomorrow Compatibility with latest version of Search::Elasticsearch - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24552 Compatibility with Elasticsearch 7.x : Problem: Search::Elasticsearch is not yet compatible with ES 7.x, so we are stuck with ES 6.x (unless we use something else...) #3 Querying Elasticsearch in a better way POC query_string => boolean query https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24555 This POC is about replacing the use of full text queries (query_string) with Boolean queries for biblio search Advantage: => No search craches with special character ( "!", ")" etc...) => Separate query context and filter context: - Search scores are not altered by facets, - Ability to use range filter (i.e for publication date facet) Regards, Claire.

2 1

Status "in transit" after checking in
by Michael Kuhn 31 Jan '20

31 Jan '20

Hi Our library is financed by two organisations. Thus we have one Koha 18.11 instance with two separate branches, but only one circulation counter where we are checking in the items. Say we are logged in at the counter with branch A and checking in an item belonging to branch B - this will result in the following status message for the item: "In transit from branch A to branch B since 26/01/2020". To set this status to "Available" we need to log in as branch B and to check in the item once more. We would better like if the status could just go to "Available" since in fact there is no transport necessary. After some fruitless reading of the manual I came up with the idea to just delete the content of table "branchtransfers" every minute via cronjob: DELETE FROM branchtransfers; The status is then "Available", as desired. Is this possible/advisable, or do you know a better way? 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

2 1

double fines
by Margo Duncan 31 Jan '20

31 Jan '20

Good afternoon, Recently we have some patrons that are being double charged fines. It looks like when the item is turned in, the accruing fine (FU) remains and a fine (F) for the same amount is added as a second line. It doesn't appear to be happening to all patrons and I cannot determine a pattern. We are on version 18.11.02. Has anyone had this problem? Or any suggestions where to start looking? Thank you! Margo Margo Duncan, MLS Head of Library Systems Robert R. Muntz Library The University of Texas at Tyler 903.566.7174 | mduncan(a)uttyler.edu<mailto:mduncan@uttyler.edu>

8 13