February 2015 - 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

koha 3.14.13 released
by Fridolin SOMERS 03 Nov '15

03 Nov '15

The Koha community is proud to announce the release of 3.14.13. This is a security and maintenance release and contains 2 security bugfixes. As always you can download the release from http://download.koha-community.org. Have a look at release post : http://koha-community.org/koha-3-14-13-released "Get the pie while it's hot". Regards, -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.somers(a)biblibre.com

1 4

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

Problems with Indexdata idzebra-2.0 build (Zebra 2.0.59)
by Tomas Cohen Arazi 04 May '15

04 May '15

There have been reports of problems with retrieving facets from Zebra using the latest idzebra build from IndexData's wheezy repository. I'm not able to install that version yet, to give it a try, I any one you succeeds please let me know so we track this down. For now, we should encourage people to use Debian's/Ubuntu's instead of adding IndexData's repo. Regards -- Tomás Cohen Arazi Prosecretaría de Informática Universidad Nacional de Córdoba ✆ +54 351 5353750 ext 13168 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F

4 7

Upgrade path for packages
by Tomas Cohen Arazi 16 Mar '15

16 Mar '15

We still need to fix our packaging schema in which people are forced to jump into .0 releases because of our repository naming schema. I propose we step forward and create "3.18", "3.20" and so on, instead of just "stable", "oldstable", etc. This way no one will be forced to jump into another major release. "stable" "oldstable" and "testing" might still be usable as they are now, nothing prevents a .deb package from populating more than one slot. Or even of symbolic links... Some of you expressed your concerns about "people indefinitely using obsolete/insecure releases". I propose that once a release goes "unmaintained" [1] a "last" release/package adding a red-notorious warning message on the intranet footer is pushed stating that the release is no longer maintained and provinding a link for upgrade instructions. I hope we can fix this once and for all soon. [1] unmaintained = it has no release maintainer on some "Roles for XX" vote. -- Tomás Cohen Arazi Prosecretaría de Informática Universidad Nacional de Córdoba ✆ +54 351 5353750 ext 13168 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F

5 4

Authorities and Linking
by Joy Nelson 27 Feb '15

27 Feb '15

HI all- I am not able to find any open BZ tickets for work done to improve the function of the authority linker script. Specifically, I am looking for information on how (or if) the Linker Options (broader headings) is in working order. The manual calls it experimental right now. Is there an open BZ ticket for this or a closed one (because it's fixed -yay) that I can review? Thanks Joy Nelson Director of Migrations ByWater Solutions <http://bywatersolutions.com> Support and Consulting for Open Source Software Office: Fort Worth, TX Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/>

1 0

Re: [Koha-devel] [Koha] Koha development
by Brendan Gallagher 25 Feb '15

25 Feb '15

Marshall - I think we are all curious to what you are going to say here? Thanks, Brendan On Mon, Feb 16, 2015 at 12:21 AM, Magnus Enger <magnus(a)libriotech.no> wrote: > Hi! > > On 12 February 2015 at 15:07, Marshall Breeding > <marshall.breeding(a)librarytechnology.org> wrote: > > Could each of the support firms or individuals involved in Koha > development > > please either post to this list or send to me individually the FTE that > you > > or your organization contributes for each of the major categories of > > activity? > > Libriotech is (so far!) a one man band, I am the sole employee. That > is the easy part. > > In 2014 I held a temporary part time position at Oslo Public Library, > so all my work on Koha was done on their time. > > In 2015 I plan to do some development and some QA and contribute to > the Koha wiki. Maybe, if I'm lucky, I can achieve this: > > Development: 4-50% > QA: 10% > > But I also have customers I need to keep happy, so only time will tell > how it actually turns out... > > Best regards, > Magnus Enger > Libriotech > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha > -- --------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting and Complete Support Packages Headquarters: Santa Barbara, CA - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com info(a)bywatersolutions.com

2 1

Koha 3.18.4 released
by Chris Cormack 23 Feb '15

23 Feb '15

The Koha release team are proud to announce the release of Koha 3.18.4. This release contains one security fix and users are recommended to upgrade to this release. You can either wait a day or 2 for the packages to be released, or you can download the tarball at http://download.koha-community.org Please read http://koha-community.org/koha-3-18-4-released/ for the release notes Chris

1 0

Re: [Koha-devel] OPAC !DOCTYPE
by Paul A 20 Feb '15

20 Feb '15

At 06:05 PM 2/19/2015 -0700, Jesse wrote: >The shortened doctype looks odd, but is the new official recommendation >for HTML 5. Koha has changed to this for the OPAC and (I believe the staff >side). Yup, but I tried that (explicitly declaring HTML5) and it throws up dozens of errors (50+ of them yui css) and hundreds of warnings. Putting it back to XHTML substantially decreases the list. Best -- Paul >2015-02-19 17:59 GMT-07:00 Paul A ><<mailto:paul.a@navalmarinearchive.com>paul.a(a)navalmarinearchive.com>: >doc-head-open.inc in 3.08 started by adding: > ><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" >Â Â >"<http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd>http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > >3.18 just adds <!DOCTYPE html> -- which gives rise to "errors" in most >verification processes (W3C etc).Â Was there a reason to change >this?Â (Can't find anything in bugs.) > >I'm playing with the Google mod_pagespeed in Apache 2.4, and adding the >full DOCTYPE seems necessary. I haven't (yet) seen a downside to adding it >back in. > >Best -- Paul > >_______________________________________________ >Koha-devel mailing list ><mailto:Koha-devel@lists.koha-community.org>Koha-devel(a)lists.koha-community.org >http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >website : <http://www.koha-community.org/>http://www.koha-community.org/ >git : <http://git.koha-community.org/>http://git.koha-community.org/ >bugs : <http://bugs.koha-community.org/>http://bugs.koha-community.org/ > > > > >-- >Jesse Weaver --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>

2 1

Ldap Authentication error
by Bobby 20 Feb '15

20 Feb '15

Hi guys .. am running koha 3.16 (using debian 7 packages) however I am unable to get ldap authentication working I have setup the ldap paremeters in /etc/koha/site/opac/koha-conf.xml <useldapserver>1</useldapserver> <ldapserver id="ldapserver" listenref="ldapserver"> <hostname>localhost</hostname> <base>ou=People,dc=example,dc=edu,dc=ng</base> <replicate>0</replicate> <update>1</update> <auth_by_bind>1</auth_by_bind> <mapping> <userid is="uid"></userid> <firstname is="givenname"></firstname> <surname is="sn"></surname> <email is="mail"></email> <phone is="telephoneNumber"></phone> <password is="userPassword"></password> </mapping> </ldapserver> however when I do a perl opac-user.pl userid=foo password=passwd > /tmp/junk.txt I get this error perl opac-user.pl userid=foo password=passwd > /tmp/junk.txt LDAP bind failed as kohauser foo: LDAP error #34: LDAP_INVALID_DN_SYNTAX # The request contained an invalid DN

4 8