December 2014 - Koha-devel - lists.koha-community.org

Z39.50 marc21 to unimarc
by Andrea Furin 16 Feb '16

16 Feb '16

Hi. I need to import Z39.50 marc21 results in a unimarc database: is it possible? Tia andrea f.

3 2

How to get CAS based Single Sign On working?
by Koustubha Kale 25 May '15

25 May '15

Hi All, I have a situation where we have a main website based on Joomla. This Joomla site uses CAS to authenticate users. We would like users ( who have already logged in to the Joomla site via CAS) to be able to follow a link to Koha site and be logged in automatically ( e.g. Single Sign On ). I have got simple CAS ( not proxy CAS ) working with Koha ( version 3.2.6 ) using the same CAS server as used by Joomla site. Still when I login to Joomla site with CAS, and then go to Koha and click on login and follow the CAS login link, I am asked to fill up CAS login information again. How can this be avoided by using CAS SSO? I have read through http://wiki.koha-community.org/wiki/SSO_CAS_improvements and am confused by the statement "Note: simple sso cas support (no proxy) has been done already by biblibre, is in testing and should be released in Koha 3.2" in there. Does this statement mean that SSO is possible with simple CAS? If yes how to set it up? If not, I have also read through bugs 6012, 5630 and the CAS Proxy examples. Frankly I haven't been able to figure out how I can achieve the above required functionality based on all the reading. Any help is much appreciated.. Another related query is, Is it possible to automatically create users in Koha once they have authenticated with CAS? Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2

3 3

Clarification of Plack wiki insructions
by Mark Tompsett 16 Jan '15

16 Jan '15

Greetings, I am trying to set up plack. I found some instructions here: http://wiki.koha-community.org/wiki/Plack "This instructions assume that your Koha checkout is /srv/koha. If it's in some other location, you have to change /srv/koha to correct folder throughout all scripts below. Create following file and call it opac.psgi" Great, except I'm not sure where opac.psgi goes. Let's say I have a git install: /home/mtompset/kohaclone. Where does opac.psgi go? Let's say I have a package install: /usr/share/koha. Where does opac.psgi go? And am I correct to assume that /srv/koha is to be substituted with those either of those paths that I have given? Help and clarification would be appreciated. I'm trying to test my revisions to bug 5010 completely. GPML, Mark Tompsett

4 3

Any bugs you want worked on?
by Chris Cormack 07 Jan '15

07 Jan '15

Hi all In a few weeks the next batch of bright young things will be participating in the catalyst open source academy. http://www.catalyst.net.nz/show-and-tell/open-source-academy Every year a team of 14-17 year olds does some work on Koha, fixing bugs, testing, etc. So in the preparation to the academy I encourage you all to tag any bugs you would like them to look at as 'academy' in bugzilla. Thanks for your help Chris -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

8 8

Documentation review
by Robin Sheat 06 Jan '15

06 Jan '15

I've redone the documentation about the packages. Currently it's untested, that may be a job for tomorrow. However, it'd be good to get a couple more opinions before I publish them. The audience for these is "people who have a reasonable idea of how to get around in Linux", so it's not supposed to be a total newbie guide. I'm aiming for it to have enough information for someone to know what's going on, but not so much that it becomes hard to follow, especially in the "Installation Process" section. The informational bit at the bottom can be wordier. As such, I'm mostly interested to know: * Do the instructions work (though, as I haven't tested them myself yet, I wouldn't be surprised to find an error or three in them), * are there common scenarios that it doesn't account for, and * is there useful/important information that's missing. You can find my new draft here: http://wiki.koha-community.org/wiki/Talk:Koha_on_Debian -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF

3 2

Inquiry regarding replication
by Mark Tompsett 02 Jan '15

02 Jan '15

Greetings, I was playing around with MySQL replication recently, and was wondering if anyone actually used it as part of their Koha setup. And if so, what purpose? Why was I playing with it? I was pondering how to handle loss of internet access to a remote host (e.g. Asia undersea cable gets cut and the Philippines is cut off from their hosted data in Amsterdam). Any ideas? GPML, Mark Tompsett

2 1

Re: [Koha-devel] 3.18 install [was: koha-common install]
by Paul A 31 Dec '14

31 Dec '14

At 09:07 AM 12/30/2014 +1300, Chris Cormack wrote: [snip] >It is because you decided not to install using the packages, and instead >used the tarball, so none of the package supplied scripts >will be there Yup... I tried four times (twice on a 32-bit sandbox, and twice on a new 64-bit machine due to go into production soon), reinstalling the whole server from scratch each time, and coha-common failed every time. So I went back to my notes from Koha 3.8 and used the tarball for 3.18.2. Do you have a list of the "package supplied scripts" not in the tarball? That would be most useful for me to chase down any final "missing advantages" of 3.18 -- our staff are excited at getting their hands on the "new version." Anyways I'm getting closer. The Zebra failure was that the daemon wasn't running, cured with a: paul@hood:/etc/init.d$ sudo ln -s /usr/share/koha/bin/koha-zebra-ctl.sh koha-zebra-daemon paul@hood:/etc/init.d$ sudo /etc/init.d/koha-zebra-daemon start Starting Zebra Server Bingo! OPAC and Staff now functional.

2 1

Debian repo pocket names changed
by Robin Sheat 30 Dec '14

30 Dec '14

TL;DR you don't need to do anything, this is just a heads up in case you notice that instructions differ from what you remember. I've just changed the names of the repository pockets from 'squeeze' to 'stable', and 'squeeze-dev' to 'unstable'. When I say 'changed', I really mean 'aliased'. So if you fetch from squeeze or stable you get exactly the same thing. In the background they are really still called their original names, but end-users shouldn't have to see that any more. This is because 'squeeze' is a bit confusing when people are installing on Debian wheezy, ubuntu, mint, and so on. oldstable is still oldstable. Now I'm going to start rewriting the package installation instructions, they've accreted over the years and it's time for a bit of summer cleaning. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF

1 0

koha-common install
by Paul A 29 Dec '14

29 Dec '14

Happy Christmas, Happy Holidays all around, Having a look at latest releases of Ubuntu and Koha on a 32-bit 'sandbox' server, newly built with latest 14.04.1 LTS Ubuntu. Koha failed despite major attempts at fulfilling dependencies, including CPAN which cannot find yaz, idzebra nor libnet-z3950-zoom-perl. I started with 130-odd missing files, individually installed all but these, despite adding deb's for koha, and Debian wheezy and squeeze to /etc/apt/sources.list I'm *guessing* that i386 is no longer supported, but couldn't find any mention at koha-community. I should be able to get a 64-bit sandbox after staff leave for the holidays later today and will try again. Here's the gory details: paul@hallowell:/$ lsb_release -a Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty paul@hallowell:/$ sudo apt-get install koha-common Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help resolve the situation: The following packages have unmet dependencies: koha-common : Depends: libnet-z3950-zoom-perl but it is not going to be installed Depends: idzebra-2.0 but it is not going to be installed Depends: yaz but it is not going to be installed E: Unable to correct problems, you have held broken packages. br -- paul

6 8

QueryParser does not manage more than 1 operator?
by Jonathan Druart 29 Dec '14

29 Dec '14

Hello dev, I tried to hack C4::Search to permit to search for a record from its ISBN whatever the form used (10 vs 13, with vs without dash). I have easily done it for the non QP form (~3 lines in C4::Search::buildQuery). It looked easy to do for using the QP too (almost the same ~3 lines in C4::Search::parseQuery). But I think there is a bug somewhere because the PQF query generated by QP is wrong, or I did not use the correct syntax. If I search for nb:foo && nb:bar => OK nb:foo || nb:bar => OK But with a 3rd term: nb:foo && nb:bar && nb:foobar => OK nb:foo && nb:bar || nb:foobar => KO (same as nb:foo && nb:bar && nb:foobar) nb:foo || nb:bar || nb:foobar => KO (same as nb:foo || nb:bar && nb:foobar) Actually the second operator is always replaced with && (AND) I don't know the the bug is come from Koha::QueryParser or OpenILS::QueryParser. Could someone familiar with this code help me giving some tricks? Regards, Jonathan PS: The tests are: is($QParser->target_syntax(' biblioserver', 'au:smith || ti:johnson || au:doe'), '@or @attr 1=1003 @attr 4=6 "smith" @or @attr 1=4 @attr 4=6 "johnson" @attr 1=1003 @attr 4=6 "doe"', 'query with 2 boolean ||'); is($QParser->target_syntax('biblioserver', 'au:smith && ( ti:johnson || au:doe )'), '@and @attr 1=1003 @attr 4=6 "smith" @or @attr 1=4 @attr 4=6 "johnson" @attr 1=1003 @attr 4=6 "doe"', 'query with 2 boolean && + ||'); And the result is: # Failed test 'query with 2 boolean ||' # at /home/koha/src/t/QueryParser.t line 56. # got: '@or @attr 1=1003 @attr 4=6 "smith" @and @attr 1=4 @attr 4=6 "johnson" @attr 1=1003 @attr 4=6 "doe"' # expected: '@or @attr 1=1003 @attr 4=6 "smith" @or @attr 1=4 @attr 4=6 "johnson" @attr 1=1003 @attr 4=6 "doe"' # Failed test 'query with 2 boolean && + ||' # at /home/koha/src/t/QueryParser.t line 59. # got: '@and @attr 1=1003 @attr 4=6 "smith" @and @attr 1=4 @attr 4=6 "johnson" @attr 1=1003 @attr 4=6 "doe"' # expected: '@and @attr 1=1003 @attr 4=6 "smith" @or @attr 1=4 @attr 4=6 "johnson" @attr 1=1003 @attr 4=6 "doe"'

2 1