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

Koha as a federated library
by Anselm Olweny 17 May '10

17 May '10

Dear Colleagues and thanks for the great work, Below is content of a mail I posted to the koha list ( Koha(a)lists.katipo.co.nz) but I have not been advised about the right and best way to go about this. I am sorry for posting this to this forum. Could someone kindly advise me on this. I need this advise in order to be certainly sure that I am doing things right. I am setting up a federated library system using koha where each of the libraries needs to have its own look and feel and also should be able to search its own collection and also be able to search the collection of the other libraries in the federation by the users choice. I have also integrated koha into a CMS "joomla" in order to handle non koha pages. In my koha set up I have created the different libraries as branches and activitated the IndependantBranches preference in koha. You can see this at http://koha.apkn.org (koha in Joomla) or http://koha.apkn.org:81 (Koha pure) or http://koha.apkn.org:81/cgi-bin/koha/opac-mainug.pl and http://koha.apkn.org:81/cgi-bin/koha/opac-mainke.pl (Independent libraries). However, I am not sure whether this is the right way to set up federated libraries using koha. Could someone kindly advise me about the right way to set up federated libraries using koha? Thanks

2 2

Minimum version of Perl
by Galen Charlton 17 May '10

17 May '10

Hi, At present, the minimum version of Perl required by Koha is 5.6.1. Since MARC::Record requires 5.8.2, at the very least Koha's requirement should be 5.8.2, and 5.8.8 (the current stable release in the 5.8.x series) would be better. Are there any common platforms where this would be an issue? What about going further and bumping up to 5.10.0? Regards, Galen -- Galen Charlton gmcharlt(a)gmail.com

4 4

June General IRC Meeting
by Chris Nighswonger 14 May '10

14 May '10

Just a heads up that the wiki page has been created for the June General IRC meeting. You can find it here: http://wiki.koha-community.org/wiki/General_Meeting,_June_2_2010 Please feel free to add any items to the agenda you would like to have discussed at this meeting. Kind Regards, Chris

1 0

bugs.koha-community.org
by Chris Cormack 14 May '10

14 May '10

Hi All About a week ago, I asked people to start registering at bugs.koha-community.org in preparation for shifting there. I'm pleased to say that a lot of you have. I'd like to make a deadline for the switch now, Friday 21 May, 9am NZST (wolfram alpha is a good tool for converting that to your timezone). That is when I plan to shift all the bugs over, so if any of you aren't registered now, can you please do it before then. And from that time onwards please use bugs.koha-community.org. Before then, feel free to have a play there, get used to some of the new features, but any bugs you make or change there, will be overwritten when I do the import of bugs. Thanks very much Happy Bug Hunting Chris RM 3.4

1 0

git.koha-community.org
by Galen Charlton 14 May '10

14 May '10

Hi, As many of you know, git.koha-community.org has been in the works for a while. I am pleased to announce that it is now ready for prime time. The following main repositories are ready for use: Main Koha code ------------------ Clone URL: git://git.koha-community.org/koha.git Gitweb: http://git.koha-community.org/gitweb/?p=koha.git;a=summary Git stats: http://git.koha-community.org/stats/koha-master/ (for master branch) Koha documentation ------------------ Clone URL: git://git.koha-community.org/kohadocs.git Gitweb: http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary Git stats: http://git.koha-community.org/stats/kohadocs/ To point your current Git clone to the new repository, you can do the following: # for the Koha repository git remote set-url origin git://git.koha-community.org/koha.git # for the Koha documentation repository git remote set-url origin git://git.koha-community.org/kohadocs.git After doing so, you can fetch changes as normal. There are also a couple historical trees, kumara.git and oldkoha_1_0_7.git. git.koha-community.org is also available to host work-in-progress trees of Koha or any project directly related to Koha. If you would like to publish your Koha Git tree on this server, please send an email to koha-devel. Please note that while git.koha-community.org is backed up daily, it is not a substitute for maintaining your own backups of your WIP trees. The following individuals currently have administrative access to the server: Galen Charlton Chris Cormack Brendan Gallagher Henri-Damien Laurent Chris Nighswonger If there are any useful tools that should be added to this service, please let one of us know or email koha-devel. If you have the time and interest to help maintain and administer the Git server and would like to help, please email the current maintainers. Please note that in the unlikely event of abuse, it is within the right of ByWater's and the other maintainers to summarily yank an administrator's access. Hosting for this git server is provided by ByWater Solutions. Regards, Galen -- Galen Charlton gmcharlt(a)gmail.com

3 3

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