August 2011 - Koha-devel - lists.koha-community.org

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

koha-3.00.00 make fails
by Rick Welykochy 28 Dec '13

28 Dec '13

Hi all, I have downloaded http://download.koha.org/koha-3.00.00.tar.gz and began installing it on Debian/etch (in a Linux vserver environment). 0. FINE: cd koha-3.00.00 1. FINE: perl Makefile.PL 2. FAIL: make : : : Manifying blib/man3/C4::UploadedFile.3pm Manifying blib/man3/C4::BackgroundJob.3pm Manifying blib/man3/opac::opac-dictionary.3pm Manifying blib/man3/serials::member-search.3pm /usr/bin/perl "-Iblib/arch" "-Iblib/lib" fix-perl-path.PL blib /usr/bin/perl "-Iblib/arch" "-Iblib/lib" rewrite-config.PL blib/KOHA_CONF_DIR/koha-conf.xml Bad arg length for Socket::inet_ntoa, length is 0, should be 4 at rewrite-config.PL line 67. make: *** [blib/KOHA_CONF_DIR/koha-conf.xml] Error 255 Any ideas what went wrong and how to fix? Aside: there were a couple of other problems with this "out of the box" debian based install of Koha 3.0 which had to be fixed along the way, e.g. seven missing perl modules and libgd not found. I'll report on the entire process from unpacking to a running Koha/3.00.00 once I get to the end. cheers rickw -- ________________________________________________________________ Rick Welykochy || Praxis Services || Internet Driving Instructor The manual said Windows XP/SP2 or better so I installed Linux.

4 5

Restructuring C4
by Ian Walls 21 Sep '11

21 Sep '11

Fellow Developers, Last night, I stayed up late running circ/circulation.pl through NYTProf, to get an idea where we may be able to optimize circulation for speed. After much frustration (darn session IDs...), I was able to get a report. The results were... not exactly what I expected. It seems that much of the time spent running circ/circulation.pl is spent BEGINing the various C4 modules, multiple times. C4::Items, for example, is BEGuN 14 times in the execution of circ/circulation.pl. More stats: C4::Accounts - 8 BEGINs C4::Acquisition - 14 BEGINs C4::Auth - 14 BEGINs C4::Biblio - 14 BEGINs C4::Branch - 5 BEGINs C4::Circulation - 22 BEGINs C4::Context - 18 BEGINs C4::Dates - 12 BEGINs ... and so on. Even modules like C4::XSLT, C4::SMS, C4::Suggestions, and C4::Search::PazPar2 are BEGuN several times, without any calls to any of their subroutines. Some modules, it seems, don't have an END at the end... I was also able to get a Graphviz file out, showing all the package calls (folks may remember my keen interest in such things from KohaCon). Running it through sccmap to detect cycles, I found a very long one between several of the modules. About 8 packages long. All this indicate to me that we REALLY need to start thinking about imposing some kind of structure on C4. I'm thinking something with two-levels: Level 1 : Calls to the database, other direct interaction with stored data Level 2: Calls to Level 1 functions to manipulate data all our scripts would then be modified to call only Level 2, which would take care of talking to Level 1. At the worst, a particular Level 1 package would be BEGuN as many times as there were Level 2 packages BEGuN in the script (and we could certainly do better). It would eliminate all the cycles, as well. I can provide access to my report for anyone who needs it, or more details about how I obtained it. Whatever any of you need to keep this conversation going. This is a big deal, in my opinion, and we need to start detangling our code before too much long, or we're going to get seriously bogged down. Cheers, -Ian -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls(a)bywatersolutions.com Twitter: @sekjal

11 25

3.4.x String Freeze
by Chris Nighswonger 16 Sep '11

16 Sep '11

Ok everybody... 3.4.x is presently in a string freeze. The only string affecting patches that will be accepted at this point are blocker and security related bugs. Other patches will be pushed up to the release date. Kind Regards, Chris

1 1

tools should they be command line executable as well ?
by Paul Poulain 15 Sep '11

15 Sep '11

Hello all, On http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5636 Ian asked a question last month no-one answered. So I ask it here: > Style question to the community: should core pages in the staff client (like > tools/cleanborrowers.pl) have both a templated page in the staff client AND a > command-line presence, or should the commandline tool be a separate script in > misc/? > > At this time, there doesn't seem to be any precedent for inclusion in the core > script. Before passing this patch for QA, I'd like to get some feedback, as > this may both open doors for us, as well as create additional work to create > consistency of implementation for existing jobs. My answer is: * right, there is no precedent * This feature to clean borrowers from command line is highly useful : most libraries want to define a rule, and have it applied every week, through a cronjob. But some want to clean manually. So it's meaningful to have a script for both cases. * I think it's fair to have this script run from both, and it's better than having 2 scripts for that, it's easier to maintain * I think a few other script could usefully have the same feature : import_borrowers, batchMod (that does both mod and deletion of items), and that's probably all. So, overally, my choice is : let the need decide. If it's useful for some, do it, but double check for security issues. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

3 2

koha 4.0 / solR / Zebra : A working group is born ?
by Paul Poulain 03 Sep '11

03 Sep '11

Hi, As you all know, BibLibre has worked hard on integrating solR as search engine into Koha. The resulting work is live in 2 french libraries, and we plan to integrate it into Koha 4.0 Our preference went to do a in-depth work. It mean we changed the API a lot, as well as most of the logic behind the search in Koha. It means we can't keep zebra working as it is today. Fortunately, the proposed structure is modularized, so it's possible to re-implement zebra for those who want to stay with it. It's also possible to reintegrate NoZebra or any other search engine. Zeno Tajoli sent us a mail with some starting work about this re-implementation of zebra. I catched tcohen on IRC today, his boss gave him some time to investigate too. Claire Hernandez (our development manager) is also helping. Unless i'm mistaking, it's a draft of a "search engine working group". If anyone else is interested, drop me (or claire) a mail, we could organize an IRC session. PS: i've submitted a presentation for KohaCon11 about what we did around solR. But it will be librarian-oriented. We will/could/should probably have a topic about that during HackFest as well ;-) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

9 10

jquery plugin
by Paul Poulain 02 Sep '11

02 Sep '11

Hello koha-devel, On the bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6086 Alex proposes to add a new jquery filter for tables, picnet.table.filter.min.js (An example of the filter is here: http://www.picnet.com.au/resources/tablefilter/demo.htm ) We already have some jquery plugins for table: * tablesorter = let you sort table columns. Widely used in Koha. * tablesorterPager = automatically paginate long tables. Used in admin section of Koha, and in readingrec * uiTableFilter = add a generic filter to tables. Used only in serials claims if i'm not mistaking. uiTableFilter and tablefilter achieve almost the same goal: * uiTableFilter propose just one filter, generic, outside of the table. You enter something, and any cell with the entered value is kept, others are hidden * tablefilter add a line to the table, just below column names (see the screenshot on bug 6086) the filter can be very detailled. It handles filters from a list, not only from an entered value. We have options: * those 2 plugins are not exactly the same, let's go with both (at the price of sometimes graphic inconsistencies or difficulties to choose one or the other plugin) * uiTableFilter is great, the other gives us too much detail, let's stick with uiTableFilter, don't add another table plugin ! * tablefilter is great, it's better to have a lot of details, it's easier to understand how it works (the uiTableFilter is outside the table, it's strange...) switch to tablefilter and remote uiTableFilter ! What do you think we should do ? Is there an other thing we should take care of ? Anyone knowing the killing-plugin-for-table we should use for sorting/filtering/doing everything on table ? Personally, I think I prefer a little bit tablefilter, I already had some usability questions from Owen about uiTableFilter used in a smart-rules patch we've submitted (and has not been applied yet) Depending on the conclusion, i'll QA the 6086 differently ;-) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

6 7

Kohacon11 : paper abstracts to arrange into a program.
by Koustubha Kale 31 Aug '11

31 Aug '11

Hi All, Please find attached a CSV file with paper abstracts submitted for Kohacon11. Any apologies or last minute submissions before we finalize the program for the three days using these? Also please let me have your suggestions as to how to order these into a program. 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

1 1

2011-09-02 Global bug squashing day #4
by Magnus Enger 30 Aug '11

30 Aug '11

Dear Community! Just a gentle reminder that GBSD#4 is approaching fast: http://wiki.koha-community.org/wiki/2011-09-02_Global_bug_squashing_day Please bear in mind that the Release Manager has declared the following dates: * Feature freeze – 22 September 23:59 UTC – From this point on, no new features will be considered for inclusion into 3.6.0 * String freeze – 8 October 23:59 UTC – no bugs that change templates accepted after this point. This allows the translators to translate without things changing on them http://koha-community.org/key-dates-3-6-0/ That means we have about 3 weeks for getting any new features in! And there are (at the moment) 83 (!) bugs/patches waiting to be signed off: http://bugs.koha-community.org/bugzilla3/buglist.cgi?bug_status=NEW&bug_sta… See one in there that you would like to make sure makes it into Koha 3.6? YOU can help it along by signing off on it! http://wiki.koha-community.org/wiki/Sign_off_on_patches Of course, we should take every opportunity to sign off patches in the coming weeks, but why not make a concerted effort on Friday September 2nd 2011 (in your timezone) and see how far we can get, as a team? Could we cut the queue in half? Happy hunting! Magnus Enger PS And you don't have to be a developer to help either!

1 0

System design
by Paul 29 Aug '11

29 Aug '11

Our budget has finally allowed me a new "all singing, all dancing" server and it has physically arrived. Two questions if I may -- and if I'm off topic, plz say so: 1) The system (Ubuntu 11.04) is being installed on a SSD (solid state drive) which recommends keeping "writes" to a minimum for longevity. This obviously includes logs, etc, but not necessarily the sql database. A quick "find / -iname" on the sandbox (Koha 3.02.05.000) for '*koha*' is enormous. Does anyone have to hand a list of "system" versus "run-time" directories and files? I'm particularly curious about Zebra (which I do not fully understand) as it appears to be proliferous and ubiquitous. 2) I have stabilized a partially customized Koha 3.2.5 which is close to meeting our needs. Koha 3.4 would be my choice on the new server (and I'm not worried about cosmetics -- CSS, etc) but how bullet-proof is the data conversion (as of now about 80,000 records)? I truly want Koha to be our long term data solution for our holdings, but am still wet behind the ears with Koha, so all help would be appreciated. Many thanks in advance for all suggestions. Paul Tired old sys-admin

2 1