- Koha - lists.katipo.co.nz

Koha Release 19.05.14
by Lucas Gass 31 Aug '20

31 Aug '20

Hello everyone! The Koha community is proud to announce the release of Koha 19.05.14. Koha 19.05.14 is a security release, including 3 security fixes, 6 enhancements, and11 bugfixes The full release notes can be viewed here: https://koha-community.org/koha-19-05-14-released/ <https://koha-community.org/20-05-02-release/> Debian packages are available. Thanks to everyone involved! Cheers, -- Lucas Gass Web Developer

1 0

Koha 19.11.09 Released
by Lucas Gass 31 Aug '20

31 Aug '20

Hello everyone! The Koha community is proud to announce the release of Koha 19.11.09. Koha 19.11.09 is a security release, including 3 security fixes, 8 enhancements, and 45 bugfixes. The full release notes can be viewed here: https://koha-community.org/koha-19-11-09-released/ <https://koha-community.org/20-05-02-release/> Debian packages are available. Thanks to everyone involved! Cheers, -- Lucas Gass Web Developer

1 0

Koha 20.05.03 released
by Lucas Gass 31 Aug '20

31 Aug '20

Hello everyone! The Koha community is proud to announce the release of Koha 20.05.03. Koha 20.05.03 is a security release, including 3 security fixes, 44 enhancements, and 67 bugfixes The full release notes can be viewed here: https://koha-community.org/8481-2/ <https://koha-community.org/20-05-02-release/> Debian packages are available. Thanks to everyone involved! Cheers, -- Lucas Gass Web Developer

1 0

Zebra error
by Luis Moises Rojas 31 Aug '20

31 Aug '20

Hello, We have more than 13,000 biblios, but after used zebra_reindex only say: 10.000 of 12.671 when you used the advanced search. Any idea? Does zebra has a config file? -- *Luis Moisés Rojas P.*

1 0

ElasticSearch Working!!!!
by Luis Moises Rojas 27 Aug '20

27 Aug '20

Hello everybody, Finally, our elasticsearch is working on KOHA, but and this my question now: After reindex everything its says: Total 13,245 records indexed But when you go to koha, advanced search says: 10000 de 12354 resultados cargados (10000 de 12354 loaded) Any idea? -- *Luis Moisés Rojas P.*

1 0

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

Office365 and Koha selfregistration verification mails
by Marcel de Rooy 27 Aug '20

27 Aug '20

FYI The Office365 Advanced Thread Protection feature rewrites URLs and verifies them when you click on them. When you try to register in Koha with an Office365 email address, you will have a problem. This has a nasty side-effect on selfregistration mails when you enabled verification mails. What happens, is: when Office365 verifies the link, the selfregistration is completed and Office365 receives the credentials. The user actually does a second call, the token is no longer found and he receives a failure message. The Koha verification process is effectively sabotaged. Note that you could add the Koha server domain as a do-not-rewrite URL in the Office365 ATP setup somewhere.. Marcel

1 1

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

Help with SQL script please
by Carlos Lopez 26 Aug '20

26 Aug '20

Hi everyone I'm trying to produce a list of itemnumbers for a list of bibliographic records with biblionumbers where subfield $9 in the 100 tag is in a list of authids for authorities with the value "Jesuit" in 373$a (where trying to populate a particular ccode with a set of items that we know will be relevant for that ccode). I have the following SQL query which SEEMS to run but brings up no results (even though I know that we have authority records with 373$aJesuit linked from bibliographic records with items attached): ---- SELECT i.itemnumber, b.title, b.author FROM items i LEFT JOIN biblio b ON b.biblionumber = i.biblionumber WHERE i.biblionumber IN (SELECT biblionumber FROM biblio_metadata WHERE ExtractValue(metadata, '//datafield[tag=100]/subfield[@code="9"]') IN (SELECT authid FROM auth_header WHERE ExtractValue(marcxml, '//datafield[@tag="373"]/subfield[@code="a"]') LIKE "Jesuit%")) ---- Can anyone spot where I've gone wrong? Or perhaps point me to an easier way of doing this? 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

3 3

Internal redirects exceeded on staff and opac interface
by Alvaro Cornejo 26 Aug '20

26 Aug '20

Hi, Doing a check on koha error logs I saw several of this error logs in both interfaces. How/where can I enable debug to check the origin of the error? [Mon Aug 24 07:42:42.636346 2020] [core:error] [pid 18902] [client 134.209.80.26:36734] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace. [Mon Aug 24 12:45:01.343417 2020] [core:error] [pid 5070] [client 34.75.137.220:37887] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace. I´m running 19.11.08.000 under ubuntu 18.04 Regards Alvaro |----------------------------------------------------------------------------------------| Stay safe / Cuídate/ Reste sécurisé *7* Switch off as you go / Apaga lo que no usas / Débranchez au fur et à mesure. *q *Recycle always / Recicla siempre / Recyclez toujours P Print only if absolutely necessary / Imprime solo si es necesario / Imprimez seulement si nécessaire

1 0