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

Meeting solr : Schedule
by LAURENT Henri-Damien 07 Dec '10

07 Dec '10

Hi, We plan to do 2 meetings around solr so that the most people can be aware of the status of our work on solr. The two meetings scheduled are : Tuesday 7th, 21PM UTC Wednesday 15th 11AM UTC Main aim is to present our work, what we did and what we are to do, and try and gather good will and try and unite. It is still early stage though we worked hard, and those meetings can also be the place where you can provide feedback and questions. Schedule is : - We will first try and state the reasons that prompted us into that rewrite. - Then we will present what is working at this stage, and the way one can setup a new install - and the bricks we chose in order to make things more flexible - What we will do (What has to be done) - What could be done - Our ideas for a better integration * use cases on search so that we could have Unit tests on search * Development of modules with ZOOM for Data::SearchEngine We hope you can be there or read the logs. Any further questions you may want to ask can be asked on list. -- Henri-Damien LAURENT

3 4

New Koha Mailing List - Koha Docs
by Nicole Engard 07 Dec '10

07 Dec '10

Hi all, Thanks to Henri-Damien at BibLibre we now have a working mailing list for sending patches to the documentation. Visit: https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-docs and sign up if you want to help out with the manual. The manual is available via the official git repo: http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary , just make sure you update the right version - there are now 3.2 and 3.4 manuals in that repo. If you would like to start a new language file, just let me know and I'll put some files in your language folder to get you started. Thanks a bunch, Nicole C. Engard Documentation Manager

1 0

Suppressing records in Koha 3.2.x
by Altaf Mahmud 06 Dec '10

06 Dec '10

Hello, Can someone please tell me how can I query to list the suppressed items in Koha database? Which database field indicates that the item is suppressed in OPAC view? Thanks. -- Altaf Mahmud System Programmer Ayesha Abed Library BRAC University Bangladesh.

4 8

Re: [Koha-devel] [Koha-patches] [PATCH] [Bug 5465] Makefile.PL asks for too high version of Business::ISBN
by Chris Nighswonger 02 Dec '10

02 Dec '10

CC'ing the dev list.... On Thu, Dec 2, 2010 at 11:16 AM, Liz Rea <lrea(a)nekls.org> wrote: On Thu, Dec 2, 2010 at 9:39 AM, Chris Nighswonger < cnighswonger(a)foundations.edu> wrote: > On Thu, Dec 2, 2010 at 9:48 AM, Liz Rea <lrea(a)nekls.org> wrote: > >> Backing down the version to 2.0301 to match the Lenny available package. >> > > Hmm... 2.05 is the newest version of this module in cpan. I think > Makefile.PL should always ask for what is truly the newest version rather > than being tied to a particular distribution. > > my $0.02 worth > > Kind Regards, > Chris > > I did actually think about this before I did it. :) > > I asked around if it would be better to update the documentation to take > the package out of the install script and add it to the CPAN list, or do > what I did, and the general consensus was that backing down the required > version was a better option (since the newer version doesn't add any > functionality that we actually use), so I did that. > > The reason is that a lot of people use Lenny (and or Ubuntu, which would > cause this same issue), and Squeeze/Sid aren't stable yet (even though they > work fine, I know that). Every indication I've gotten is that "we" prefer > packaged versions of things instead of pulling direct from CPAN. I chose to > eliminate the error message when installing on Lenny/Ubuntu from > Makefile.PL, and allow a required version that was lower than the current > version to help eliminate a bad user experience (An error!!! OMG! What do I > do!). > > I truly don't care which way it's done: we can remove it from the package > script and add it to the modules requiring installation through CPAN, no > problem. I'll do those patches too, if necessary. > > That said, I don't think the reasoning behind this particular patch is > unsound, based on past precedent. > I'm not familiar with what has been the rule in the past. However, it is my opinion we should establish one standard rather than attempting to work around two different ones. If we are going to take the Debian/Ubuntu repo version as the standard, we should set all modules available in those repos to the max current version available in those repos, and be sure that policy is clear in the docs. We should also develop only over those currently available versions. (I realize in this particular case there is no programmatically compelling reason to use the latest version, but that is not always the case.) FWIW, I favor Debian/Ubuntu personally, but am concerned about this from a policy standpoint. If we indeed see this as the best direction to go, I recommend we add something like this to our coding guidelines: When/Where available, Koha Perl dependencies should be sourced from the current stable Debian/Ubuntu repository. Perl dependencies not available in the repository should be sourced from CPAN. Code development should be limited to the most current version available from the proper source. Exceptions to this policy may be made by gaining consensus from the developer section of the community. or some such language... Kind Regards, Chris

6 7

About Hourly loans RFC
by Paul Poulain 02 Dec '10

02 Dec '10

Hello world, I can't see who really wrote http://wiki.koha-community.org/wiki/Hourly_Loans_RFC, if it's still planned, who will write this great RFC. Do I miss something ? Is it an abandonned_RFC from LL (don't think so, we had http://wiki.koha-community.org/wiki/Hourly_circulation_policies_RFC that was the LL one if i'm not mistaking) ? hint/light welcomed ;-) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

2 2

Meeting solr doodle tendencies closing tomorrow
by LAURENT Henri-Damien 02 Dec '10

02 Dec '10

Hi, here are the tendencies for the solr meeting : Tuesday, 7th december, 21h UTC and Wednesday, 15th December, 11h UTC I propose that we close the vote on Monday, at 21PM UTC in order to be able to have the time to send a mail for final votes. As a side note, non techy people are welcome at this meeting. Even though techy questions will be assigned. Feel free to invite. mibbit is a very handy tool to attend irc. I still have to make a real agenda for this meeting with all the questions people raised, why we did this, how we solved some issues, what drove our choices and what is the plan, and how we can work all together is still a good starting point. It will be posted on the wiki and here. Only 12 people voted. It is a good start though. I think there are many things that we could work on in groups. The search engine is one of them, Data persistance, and Plack another, Template organisation another, choosing one javascript framework (concensus seems to be in favour of jquery, but how, who when actions ?) .... if you like the idea of those meetings, please feel free to support the idea and come to those meetings and eventually organize one on the theme you favor or need. -- Henri-Damien LAURENT

5 4

ICU chains
by Ian Walls 01 Dec '10

01 Dec '10

Fellow Kohackers, There has been some talk before of using ICU chains with Zebra in order to resolve issues with diacritic search. I've looked at the patch from BibLibre ( http://git.biblibre.com/?p=koha;a=commit;h=c2465153cccb8965b0008186cdb0a94a…) and it seems pretty straightfoward, but it's nearly a year old, and I'm wondering if any work has been done since then. Does this commit resolve the issue (at least for French diacritics)? There has also been some recent posting on handling both Roman and Devangari script ( http://old.nabble.com/Re:-display-search-result-problem-p28106148.html) It references the BibLibre commit. If this methodology is working, what should we do to get it committed to Koha? I'd imagine that we'd need to generalize it to work with all languages... either by making a master set of rules, or having different xml files that can be called depending on your language choice... ideas? Cheers, -Ian -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls(a)bywatersolutions.com Twitter: @sekjal

3 2

meeting solr
by LAURENT Henri-Damien 29 Nov '10

29 Nov '10

Two weeks ago, I said that we would organise a meeting around solr and our developments in progress. We think we may now plan that. We think we could do that next week or the week after in order to tell the community the point what we achieved, what we are missing (And the first and most time-consuming task would be to gather some biblios and some use cases to test so that we donot induce regressions, what we plan to work on, and what the community could help us to do.) Our plan is to share our work on a regular base so that you can all see the direction we are willing to take, and the reasons why we implemented things that way. I would like to invite you to the Doodle poll "meeting solr". I donot want to interfere with the regular meeting. It is more a kind of "Come and play". We will have an up and running interface. Every body interested or even skeptical about this development may come and make his own opinion. Please follow the link in order to participate in the poll: http://doodle.com/2eh7spytgmydduca We will take at least two meetings at two different time in the day so that the wider audience can benefit and ask questions. We will try and assign the questions that you may have. We will therefore take the top two options. One in the morning, and one in the evening. I hope you will join us. -- Henri-Damien LAURENT BibLibre

1 0

Fwd: [koha-commits] main Koha release repository branch, master, updated. v3.02.00-188-g4b69538
by Nicole Engard 29 Nov '10

29 Nov '10

I think this was brought up before but how do I know what has changed in these files? Commit emails that tell me bug numbers and a short title/summary are much more helpful than this. I use these emails to determine what to update in the manual and I can't keep track if I have to go hunt down these commit numbers. Is there another way to format these types of messages to look like the ones that include details about each patch? Nicole ---------- Forwarded message ---------- From: Git repo owner <gitmaster(a)git.koha-community.org> Date: Sun, Nov 14, 2010 at 9:22 PM Subject: [koha-commits] main Koha release repository branch, master, updated. v3.02.00-188-g4b69538 To: koha-commits(a)lists.koha-community.org This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "main Koha release repository". The branch, master has been updated via 4b69538f9bf6809126cc404a7bc09b02c3830328 (commit) via 38360b766c32ab89c6e5ee87d2459692b47f2b29 (commit) from c0272a6b66e053a86010c7eb8fce1bf080bf428b (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- ----------------------------------------------------------------------- Summary of changes: admin/aqbudgetperiods.pl | 4 +++- admin/aqbudgets.pl | 4 +++- admin/aqplan.pl | 5 +++-- .../prog/en/includes/budgets-active-currency.inc | 1 + .../prog/en/modules/admin/aqbudgetperiods.tmpl | 4 +++- .../prog/en/modules/admin/aqbudgets.tmpl | 6 +++--- .../prog/en/modules/admin/aqplan.tmpl | 2 +- .../prog/en/modules/virtualshelves/shelves.tmpl | 6 +++++- koha-tmpl/opac-tmpl/prog/en/css/opac.css | 5 ++++- .../opac-tmpl/prog/en/modules/opac-shelves.tmpl | 3 ++- 10 files changed, 28 insertions(+), 12 deletions(-) create mode 100644 koha-tmpl/intranet-tmpl/prog/en/includes/budgets-active-currency.inc hooks/post-receive -- main Koha release repository _______________________________________________ koha-commits mailing list koha-commits(a)lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-commits

3 6

flaw in C4/Biblio.pm when controlnumber not set
by Reed Wade 29 Nov '10

29 Nov '10

Hi, I was playing around with strange records (one with no setting for control number) and managed to tickle this-- 703156da (Katrin Fischer 2010-11-24 11:35:43 -0500 1266) sub GetMarcControlnumber { 703156da (Katrin Fischer 2010-11-24 11:35:43 -0500 1267) my ( $record, $marcflavour ) = @_; 703156da (Katrin Fischer 2010-11-24 11:35:43 -0500 1268) my $controlnumber = ""; 703156da (Katrin Fischer 2010-11-24 11:35:43 -0500 1269) # Control number or Record identifier are the same field in MARC21 and UNIMARC 703156da (Katrin Fischer 2010-11-24 11:35:43 -0500 1270) # Keep $marcflavour for possible later use 703156da (Katrin Fischer 2010-11-24 11:35:43 -0500 1271) if ($marcflavour eq "MARC21" || $marcflavour eq "UNIMARC") { 703156da (Katrin Fischer 2010-11-24 11:35:43 -0500 1272) $controlnumber = $record->field('001')->data(); 703156da (Katrin Fischer 2010-11-24 11:35:43 -0500 1273) } 703156da (Katrin Fischer 2010-11-24 11:35:43 -0500 1274) } which causes-- Can't call method "data" on an undefined value at /home/reedpetone/koha/dev/koha/C4/Biblio.pm line 1272. when I do this-- http://koha/cgi-bin/koha/opac-detail.pl?biblionumber=2 ------- Since it's a small and recent item, advice on IRC was to just send this to the list. -reed

2 2