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

Integrating PTFS code into 3.4
by Chris Cormack 12 May '10

12 May '10

Hi All I'm sure most of you are aware that on May 10 (us time), PTFS made a whole pile of their hitherto private changes public in the form of a public git repo. Galen (as Release Manager for 3.2) has gone through them and marked the ones that are able to be included in 3.2 and in fact in the last day we have integrated most of those. But since we are well inside feature freeze, the new features need to wait for 3.4 (along with everyone else's new features). So it becomes part of my responsibility (as RM for 3.4) to work on the integration of them, new features from everyone else, and to make sure the work on things like C4::Search, C4::Languages, DBIx::Class, etc which are slated for 3.4 doesn't get lost. To that end, we have a wiki page http://wiki.koha-community.org/wiki/PTFS_Harley_Integration where we will be tracking integration. What my plan is, is to get each of the features isolated into a branch based off master. Then QA (Colin) can look at them and make any recommendations needed. Once they pass QA, then I will apply the usual RM rules: does this feature or bugfix cause any regressions, does it change the default behaviour in unexpected ways, and so on. Then if problems are found they can be fixed and the code resubmitted for inclusion. Just to reiterate, there is no special treatment involved here, the same rules that apply for every other developer apply, what makes this different is that there are just a big pile of commits to work through at one time. Here is a feature branch that I have created by cherry-picking the relevant code from the ptfs/Bug3469 branch. http://git.koha-community.org/gitweb/?p=koha.git;a=shortlog;h=refs/heads/ne… I'm hoping that PTFS can help creating these branches, but anyone can do so at let me know where to pull from. They need to have the changes isolated if possible and be based on new_features. (Which at the moment tracks master). The faster we can get these feature branches created, the sooner we will be able to step through the next parts of integration. If there are dependencies - and I have been warned granular permissions is a prerequisite for a lot of the new features - this should be noted clearly on the wiki page. If we have the features isolated as much as possible, then they can be integrated independently, which would mean that one features' failure to meet the test for inclusion would not stop all the others being included. So this is our first step. It also allows people to merge that feature and test it only. Looking forward to having many of you helping create these branches :) Chris Cormack RM Koha 3.4

5 6

HTML::Template
by Marcel de Rooy 12 May '10

12 May '10

Hi all, Working with Koha 3.00.06.09 from git (origin/3.0.x), I think that there is a syntax error on the html template opac-detail.tmpl. For this template, matching the if´s and endif´s etc. by hand is quite laborious. Can anyone of you point me to a better way of checking such templates? Thanks! Marcel

2 2

maxItemsinSearchResults
by Chris Cormack 11 May '10

11 May '10

Hi All There is a system preference maxItemsinSearchResults, which is only used in 2 places, both in C4::Search. It's not referenced anywhere else and hence is not set. But by not setting it, it means that in the staff client the counts of items available at each branch behaves in an unexpected way. my ( $availableitemscount, $onloanitemscount, $otheritemscount ); $maxitems = ( C4::Context->preference('maxItemsinSearchResults') ) ? C4::Context->preference('maxItemsinSearchResults') - 1 : 1; for my $key ( sort keys %$onloan_items ) { (++$onloanitemscount > $maxitems) and last; push @onloan_items_loop, $onloan_items->{$key}; } for my $key ( sort keys %$other_items ) { (++$otheritemscount > $maxitems) and last; push @other_items_loop, $other_items->{$key}; } for my $key ( sort keys %$available_items ) { (++$availableitemscount > $maxitems) and last; push @available_items_loop, $available_items->{$key} } So as it's not set, $maxitems is always 1, so at most the count for 2 branches (yes the code is broken in other ways) is shown. So if you have 6 items, each at a different branch, and all available, then you will only see at most 2 listed in the branches breakdown on the search results page. The way I see it, we either kill the references to this systempreference, or add it back (I can only assume it existed at one time). Opinions? Chris

2 1

Harley integration
by Galen Charlton 11 May '10

11 May '10

Hi, I've started a wiki page to track the integration of 'Harley' into 3.2 and 3.4: http://wiki.koha-community.org/wiki/PTFSHarleyIntegration I created this page as an adjunct to the bugs database, which should be considered authoritative concerning the status of any particular issue or enhancement. The vast majority of the changes are enhancements that necessarily will be targeted for 3.4, as I do not plan on lifting the 3.2 feature freeze. I've noted a few cases where there is overlap between PTFS work and current or proposed patches. I would appreciate updates to this wiki page by PTFS and others as Harley gets sorted out. Regards, Galen -- Galen Charlton gmcharlt(a)gmail.com

2 1

Zebra issue?
by Nicholas van Rheede van Oudtshoorn 10 May '10

10 May '10

Hello all, Hope this is the right mailing list for this question. I'm busy trying to migrate a Koha installation from one machine to another (and in the process update to a new version of Koha!). Everything seems to be working, except for the zebra functionality. When I try to run rebuild_zebra.pl (with -b -r -w -v ) I get the following: Zebra configuration information ================================ Zebra biblio directory = /var/lib/koha/zebradb/biblios Zebra authorities directory = /var/lib/koha/zebradb/authorities Koha directory = /usr/share/koha/intranet/cgi-bin BIBLIONUMBER in : 999$c BIBLIOITEMNUMBER in : 999$d ================================ skipping authorities ==================== exporting biblio ==================== 18401.................................................................................................... Records exported: 18417 ==================== REINDEXING zebra ==================== 16:40:27-10/05 zebraidx(29888) [log] zebra_start 2.0.43 abd433d1a315576cf1f4a53f2c70365f9a76477f 16:40:27-10/05 zebraidx(29888) [log] config /etc/koha/zebradb/zebra-biblios.cfg 16:40:27-10/05 zebraidx(29888) [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-safari.so 16:40:27-10/05 zebraidx(29888) [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-grs-regx.so 16:40:27-10/05 zebraidx(29888) [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-grs-marc.so 16:40:27-10/05 zebraidx(29888) [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-dom.so 16:40:27-10/05 zebraidx(29888) [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-alvis.so 16:40:27-10/05 zebraidx(29888) [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-grs-xml.so 16:40:27-10/05 zebraidx(29888) [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-text.so 16:40:27-10/05 zebraidx(29888) [warn] previous transaction did not finish (shadow disabled) 16:40:27-10/05 zebraidx(29888) [warn] previous transaction didn't reach commit 16:40:27-10/05 zebraidx(29888) [log] enabling shadow spec=/var/lib/koha/zebradb/biblios/shadow:4G 16:40:27-10/05 zebraidx(29888) [log] cache_fname = /var/lib/koha/zebradb/biblios/shadow/cache 16:40:27-10/05 zebraidx(29888) [fatal] Node node_zebra missing 16:40:27-10/05 zebraidx(29888) [warn] Cannot obtain EXPLAIN information 16:40:27-10/05 zebraidx(29888) [fatal] zebra_begin_trans: cannot open register ==================== CLEANING ==================== Additionally, when I up the verbosity of the actual zebrasrv logging, searching for a record in Koha (intranet) gives the following. 16:18:31-10/05 zebrasrv(3) [session] Session - OK 3 unix:/var/run/koha/zebradb/bibliosocket 29756 16:18:31-10/05 zebrasrv(3) [request] Auth idPass kohauser - 16:18:31-10/05 zebrasrv(3) [request] Init OK - ID:81 Name:ZOOM-C/YAZ Version:4.0.3 7b5205fa8cc74d5d17334216a5cd616296edb1a9 16:18:31-10/05 zebrasrv(3) [fatal] Node node_zebra missing 16:18:31-10/05 zebrasrv(3) [warn] Cannot obtain EXPLAIN information 16:18:31-10/05 zebrasrv(3) [request] Search biblios ERROR 109 1 1+0 RPN @attrset Bib-1 @or @or @or @or @attr 1=36 @attr 4=1 @attr 6=3 @attr 9=32 @attr 2=102 theology @attr 1=4 @attr 4=1 @attr 6=3 @attr 9=28 @attr 2=102 theology @attr 1=4 @attr 4=1 @attr 9=26 @attr 2=102 theology @attr 4=6 @attr 5=1 @attr 9=14 @attr 2=102 "theologi? " @attr 4=6 @attr 9=14 @attr 2=102 theology 16:18:31-10/05 zebrasrv(3) [session] Connection closed by client Has anybody else seen anything like this? In particular, what is the "node_zebra" node that it keeps coimplaining is missing? I think I told koha to use dom instead of gsr.... could this be the problem? (And if so, can I revert back to gsr?) The machine I'm throwing this on is a fresh installation of the latest Fedora, with all the latest indexdata sources installed. Hope there's some hope here - I've been bashing my head against this for the better part of an afternoon already! Thanks in anticipation, Nicholas van Oudtshoorn Perth Bible College (IT Manager)

1 0

Changing 'Fines' to 'Charges'
by Chris Cormack 07 May '10

07 May '10

Hi all Currently on the checkout page, and the borrowers pages, we have tab down the left hand side that is named 'Fines'. Often it is not fines at all but rental charges or some other thing. I would like to rename it to Charges ... (I can of course just do this in the translation for NZ english, but I thought Charges might be a better default value for everyone) What do people think? Bad Idea? Chris

8 7

2. Changing 'Fines' to 'Charges' (Chris Cormack)
by Patrick Andrew Jansen 07 May '10

07 May '10

I support the idea of changing the tab name to Charges as that encompasses fines. Patrick Andrew Jansen -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

2 1

Possible IRC tutorial nginx and FastCGI
by Brendan Gallagher 07 May '10

07 May '10

Hi All - Friday evening here (west coast USA), Saturday evening in New Zealand. Chris Cormack was showing quite a few of the developers that hang out in the IRC #koha channel - his testing database of koha - fed through nginx and FastCGI. I was absolutely amazed at the speed that pages from the opac were being delivered and watching some of the tests with speed comparisons between apache and nginx. I want to learn more. So, I would like to propose or maybe ask chris - if he would schedule a time that he could demo or even give a tutorial on nginx and FastCGI on the IRC channel (which is a good medium because those who can't make it will be able to read the logs). I am hoping that others get encouraged and want to investigate the possibilities. So, If you're interested in this please let me/the list know and I'll bug chris to set up a time to give a tutorial. Cheers, Brendan Of course I'd like to encourage as many people to attend (it's surprising how much I've learned through osmosis) --------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO, Director of Innovation Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting and Complete Support Packages Headquarters: Santa Barbara, CA - Office: West Haven, CT Phone # (888) 900-8944 http://bywatersolutions.com info(a)bywatersolutions.com See us at ALA : BOOTH # 817 ---------------------------------------------------------------------------------------------------------------

7 11

Patron Identification and Authorisation
by Patrick Andrew Jansen 06 May '10

06 May '10

Good day. This is my first post to the mailing list, so please bear with me if I tend to be a bit off on the culture of the mailing list. I am a database administrator at the National food technology Research centre in Botswana, www.naftec.org. I have installed and did a bit of customisations to the LMS , library.naftec.org for the centre. I have a few libraries that have since requested the installation of Koha, but there is always a question of identification and non-repudiation. To solve problems of repudiation and authentication I have thought of introducing Biometric identification during check out and enrolment. Being new to both Koha and Perl, I have difficulties of where to start and where to introduce these customisations. I am a Java programmer, and in Java there are a few facilities such as AJAX and webservices that I could use to solve this problem. Please assist on this regard. Maybe I should share my thoughts: If possible, I am thinking of form submission to throw a picture picked somehow from the Finger print scanner and authenticate the Patron through Koha on the staff client. I am also thinking of a standalone GUI application to authenticate and authorise checkout but that clatters the workflow. Please assist. Patrick Andrew Jansen -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

force install DBD::mysql problem
by bariki.kamara＠out.ac.tz 06 May '10

06 May '10

Hi, I want to install perl module DBD::mysql on the Ubuntu v9.04(Server Edition) but I face the following problem below, cpan>force install DBD::mysql CPAN: Storable loaded ok (v2.18) Going to read /home/kohaadmin/.cpan/Metadata Database was generated on Wed, 05 May 2010 14:28:31 GMT CPAN: YAML loaded ok (v0.66) Going to read /home/kohaadmin/.cpan/build/ ............................................................................DONE Found 11 old builds, restored the state of 11 Running install for module 'DBD::mysql' Running make for C/CA/CAPTTOFU/DBD-mysql-4.014.tar.gz Has already been unwrapped into directory /home/kohaadmin/.cpan/build/DBD-mysql-4.014-SzWBCO '/usr/bin/perl Makefile.PL INSTALLDIRS=site' returned status 512, won't make Running make test Make had some problems, won't test Running make install Make had some problems, won't install Can any one help to solve the problem. Regards, Bariki G. Kamara ---------------------- CONFIDENTIALITY NOTICE -------------------------------- PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS E-MAIL This email is intended only for the person to whom it is addressed and may contain confidential information and may be legally privileged. If you are not the intended recipient, you are notified that you may not use, distribute or copy this document in any manner whatsoever. Kindly also notify the sender by email and/or delete this e-mail. Any views or opinions expressed in this e-mail are those of the sender and do not necessarily coincide with those of the Open University of Tanzania. --------------------THE OPEN UNIVERSITY OF TANZANIA--------------------------

1 0