April 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

Moose vs Moo
by Paul Poulain 04 Jun '15

04 Jun '15

Hi the list, Just reading Frédéric thoughts about Moose & Moo written on bug 11190. For those who missed the IRC dev meeting yesterday, this bug was discussed yesterday : http://meetings.koha-community.org/2015/development_irc_meeting_15_april_20… I don't know which decision we must take, but I strongly think that we must all read Frédéric arguments. Maybe Moo/Moose was a good decision, maybe not. Anyway, there are not so many scripts using Moo/Moose, so we can stil change our minds. Next steps ? I'd like to have more informations. For example: * arguments in favor of Moo ? * is the argument "the overhead is cancelled by Plack persistency" valid & is it removing this argument in favor of Moo ? * I'd like to have more details about "too many important features are lost" with Moo ? *Comment # 36 <http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11190#c36> on bug 11190 <http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11190> from Frédéric Demians <mailto:frederic@tamil.fr> * Few personal notes about Moose vs Moo (just seen IRC dev meeting logs): There is an overhead using Moose for small short lived programs. But for long- running cronjob/maintenance scripts, there isn't any problem using Moose. For Koha WUI scripts, Moose start time is a problem as long as Koha operates in CGI mode. As soon as there is persistence (Plack), it isn't a problem anymore. This issue of runtime penaly due to using a large and complex library, doing a lot of stuff behind the scene, is not different with Moose and DBIx::Class I don't say DBIx::Class is bad. Moose it bad too => So let's go with Moose! I'd say both libraries share a lot of good things. I think that Moose has various advantages over other OO frameworks. It's complete, very well documented, widely used, a standard, carefully packaged for all major Linux distro. All books about the so-called "modern-Perl movement" deals with using Moose as OO. There is the Perl's famous moto: There's more than one way to do it. Applied to OO, this could conduct to chaos. There are so many ways to do OO in Perl. Code become unreadable and unreliable. Moose forces to adopt a proper and consistent OO approach. Moo try to solve a non-issue (library weight, startup time) in modern execution environments at high price: too many important features are lost. -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

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

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

"News" area is gone
by Luciana Coca 01 May '15

01 May '15

Hello everyone! The "News" area have dissappeared. The configuration and preferences are correct. I have deleted and created new News, but nothing happend. Please, help me. Thank you all. Luciana.

2 1

Language overlays or: On the way to finally resolve important translation issues in Koha
by Marc Véron 30 Apr '15

30 Apr '15

Dear Koha community, Koha is translated in almost 50 languages - but it has no possibility to switch between languages for authorised values and item types (or more generally: database content). This is a long outstanding issue, see the discussion on Bug 7789 (2012-03-22). And it is a really painful one for multilingual countries, organisations, schools, museums, libraries... Especially the OPAC looks not very professional when untranslated text pops up. There are several more or less ugly workarounds: 1) Have all language versions in the same description, e.g. for OPAC_SUG something like "Damaged | Beschädigt | Abîmé" "Upcoming title by popular author | Neuer Titel eines populären Autors |Oeuvre... ... ... " 2) Have some sophisticated JavaScript tricks 3) Have custom Plug-ins 5) Locally tweak the code 6) Provide custom packages A couple of days ago I filed Bug 14063 - Implement language overlay for authorised values It is a small, minimal invasive patch (19 lines) that uses additional entries in the table authorised_values. To use it, one can simply create an additional entry with a trailing language code, e.g. BSELL-de-DE or BSELL-fr-FR It can be used "As is" without any changes to the database or to the user interface. A similar patch for Item types (Bug 14064) is in preparation. In comment #5 on Bug 14063, Joubu proposes to have a more generic solution with a table with columns "type" column (will contain "authorised_values", "item_types", "sysprefs", etc.) and "lang" ('fr-FR', 'de-DE', etc.). The complexity will be to implement an ergonomic view to edit the different translation. I totally agree with this. Typo3 CMS, for example, works with such language overlays e.g. for page content, and it works great. I'm best willing to help to implement such a generic solution. However, my concern is that it could take a very long time to get there. Now I have following questions: - In what (realistic) timeframe / for what Koha Version could such a generic solution be implemented? - Based on your experience, what development time would be necessary? - Who could contribute to this (time, maybe funding)? - What do you think about kind of "Taskforce language overlay" - What do you think to have Bug 14063 (Signed-off) and later Bug 14064 as a transitory solution to fix the issue for the most exposed places (e.g. Search interface in OPAC)? - I know and share concerns about temporary solutions, but we simply would need a small SQL script to move the language overlays from tables "authorised_values" and "itemtypes" to the new overlay table (once the generic solution is ready). Looking forward to your comments! Have a great day! Marc Véron (mveron)

5 4

License question
by Mark Tompsett 30 Apr '15

30 Apr '15

Greetings, While looking at bug 5685, I noticed the newer version is only licensed under MIT. Is that license compatible with the GPL3 that Koha is? GPML, Mark Tompsett

2 1

Re: [Koha-devel] [Koha] 3.18.06 Package Warning
by Robin Sheat 28 Apr '15

28 Apr '15

Barry Cannon schreef op ma 27-04-2015 om 13:54 [+0000]: > This installs 3.16.09 fine. Reverting to the "stable" source and > running an upgrade successfully gets Koha up to the latest version > (3.18.06.01). Damnit. The fix introduced in 3.18.06.1 was because fresh installs were possible but upgrades weren't. My fix ended up making it so that upgrades were possible, but fresh installs aren't. Now I've hopefully tested all the combinations and didn't encounter any issues, so have uploaded 3.18.06.2. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF

2 1

Hidden items associated item types turning up in facets - anyone done work on this?
by Liz Rea 28 Apr '15

28 Apr '15

Hi all, I'm just curious whether anyone has done work specifically on the hidden items and facets. I can see that there are bugs for hiding the associated item types from the Advanced Search, and quite a bit of work has been done to make the hiding more complete - but I wasn't able to find if anything had been done with the facets. Also quite curious if anyone has a thought on whether or not hiding associated item types will be easier or harder with 3.18+ (zebra facets). Please, share your thoughts! Cheers, Liz -- -- Liz Rea Catalyst.Net Limited Level 6, Catalyst House, 150 Willis Street, Wellington. P.O Box 11053, Manners Street, Wellington 6142 GPG: B149 A443 6B01 7386 C2C7 F481 B6c2 A49D 3726 38B7

4 5