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

git stats
by Paul POULAIN 20 May '08

20 May '08

Hello, I sometimes look at git.koha.org/gitstat/, it's a really usefull & great tool. The only thing I find strange is : http://git.koha.org/gitstat/chart.php, options "xxx (Koha release)". In the list, appears 22 very old CVS tags, and not the koha 3.0 alpha or beta (or master) branches. Is there a way to setup something to have them? I'm interested by some of the stats Koha can do (like total number of commit, top commiters, # of koha developpers, commits per hour...) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

1 0

How do I disable PazPar2 in Koha 3 Beta 2?
by Ricardo Dias Marques 19 May '08

19 May '08

Hi, Like I mentioned here before (in other posts), I have Koha 3 Beta 2 installed in a (Xen) Virtual Machine, running Linux (openSUSE 10.3), with Apache 2.2.4 and MySQL 5.0.45. I have tried to set up Koha to use UNIMARC, Zebra and PazPar2. I added a few document records to the catalog, but my searches in the "OPAC" (and in the "Intranet") always come back empty, although the records are being inserted in the MySQL Database (at least, they appear in the "biblio" table). I'm thinking that this may be due to having answered "yes" to the "Install the PazPar2 configuration files? [no]" question during Koha installation (at a time when I did NOT have installed PazPar2 from the IndexData web site) . So, I would like to know this: is there a (preferrably clean and easy) way of *disabling* PazPar2 *after* having done the Koha installation? I have searched for "pazpar2" in the "System Preferences" administration page at http://hostname:8080/cgi-bin/koha/admin/systempreferences.pl but it comes back empty. Browsing the koha-conf.xml file I find these two sections that look relevant: __________  <listen id="mergeserver">tcp:@:11001</listen> <server id="mergeserver" listenref="mergeserver"> <directory>/var/lib/koha/zebradb/biblios</directory> <config>/etc/koha/zebradb/zebra-biblios.cfg</config> <cql2rpn>/etc/koha/zebradb/pqf.properties</cql2rpn> </server> [snip] <pazpar2url>http://localhost:11002/search.pz2</pazpar2url> __________ Any feedback / information would be much appreciated. Thanks in advance! Best wishes, Ricardo Dias Marques lists AT ricmarques DOT net

4 8

RFC: add optional HTTP status argument to output_html_with_http_headers
by Galen Charlton 19 May '08

19 May '08

Hi, The bibliographic details scripts can redirect to errors/404.pl if the requested bib is not found. However, when called like this (as opposed to via ErrorDocument), 404.pl actually returns HTTP status 200. Since users may want to permalink to bibs via /cgi-bin/koha/opac-detail.pl?biblionumber=FOO, having 404.pl actually return a 404 status code would help link checkers. Consequently, I propose to modify C4::Output::output_html_with_http_headers to accept an optional fourth parameter, the HTTP status code and text. For example: output_html_with_http_headers $query, $cookie, $template->output, "404"; or output_html_with_http_headers $query, $cookie, $template->output, "404 Bibliographic record not found"; Any thoughts or objections to this? Regards, Galen -- Galen Charlton Koha Application Developer LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709

3 2

"freezing" koha 3.0
by Paul POULAIN 19 May '08

19 May '08

Hello, I begin to be really troubled by all those new features added in the main trunk... I think we really should stop hacking koha that much & work only on stabilizing things. And by stabilizing I mean "stop adding anything new, strictly, really strictly, just fix things that have to be fixed" just some examples of the side effects/problems with this activity : 1- the french translation was 100% done. I just updated the .po file : 192 fuzzy (chain changes) and 45 untranslated strings. And I keep the translation update really often. I'm afraid other translators will have a very bad surprise, seeing 20 or 25% of the stuff they already did has to be redone, because each change in the template will result in 2- I see some new features like patron images, tagging, serialsadditem at subscription level[1], move to yui 2.5.1 (from 2.31.), new sysprefs by dozens, important changes in the DB structure (the great new permission/sub permission, the old_issues table). Important code refactoring/cleaning. All those great. Undoubtfully. But the risk to introduce some unexpected bugs where things were working previously is really BIG. Just 2 examples : one patch of me troubled kados, because he broke something in another page : the problem was directly introduced by a change in API (C4::Dates.pm). I was not wrong with my patch, I just discovered a larger problem (that atz has fixed iirc). the patch to add a new way to introduce issuing rules resulted in the unexpected bug #2000. [1] yes, I know, this patch is mine. but with the release being so delayed, I was tired to delay this patch & have decided to send it. 3- I see some gui changes, done by owen, that are great. but such changes can be done forever, things will never be perfect (and one will find something awful when someone else will say it's great :-\ ). 4- Joshua, you've announced the alpha for jan, 4. beta for feb, 1st and stable for march, 1st. We are almost may 1st, and still no stable version released. I would be interested to know how many commits were related to true "bugfixes" and how many were related to "improvement/cleaning/new features". I would say it's 30% / 70% (numbers not calculated scientifically ;-) ) In french we says "better is sometimes enemy of good". I think we are facing this situation : "better" is now our biggest enemy. So, I request/propose the following decision to be taken : - we didn't have had an irc meeting for a long time, it's time to plan one. - no changes in the code, except true bugfixes. "imperfection" fixes will be for later. - no more changes in templates except true spelling problems (or true bugfixes, of course), to let time to i18n teams to do their job. - create a branch, as soon as possible, to have ppl doing improvements on the dev branch, and bugfixes on the 3.0 branch. That's how we did for 2.0 and 2.2. I released a version once every 3 month or something like that. I agree we didn't had a company like LibLime doing 125/130 commits every month. (http://git.koha.org/gitstat/chart.php?chart_parameter1=3&chart_parameter_ve…) but 3.0 will never be ready if we continue like that. And with git, it should be "easy" for ppl wanting to have an hacked version of 3.0, with a backported improvement from the dev branch to be done. I'm sure, because I have some patches for some of our customers, that we haven't commited to the main repo (some of them will never be, some of them will be for 3.2, probably) Joshua, you probably have a different opinion than mine, as RM. But as previous RM, I had to write my thoughts. I hope you'll understand my opinion and agree on most of it. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

10 26

RFC: 'Edit-Items' staff permission
by Mason James 15 May '08

15 May '08

Hi All, What does anyone think about changing the current 'edit-catalogue' permission into 2 separate permissions? An 'edit-catalogue' permission, and a 'edit-items' permssion. The idea behind this is to give the Koha Administrator the ability to: 1) allow some staff accounts to make changes to a catalog record at both the bib-level and item-level 2) restrict some staff accounts to make changes to a catalog record at the item-level *only* I have already made a mod for a koha3-beta2 install to do this, and its a pretty small and safe mod. I'll work on this tomorrow to get it working with Galen's newer permissions stuff in HEAD and send over the patch. Does this sound like a feature we can get included in koha3-beta3? Cheers, Mason. _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

6 5

Links authorities records with biblio records
by Salvador Zaragoza Rubio 15 May '08

15 May '08

Dear all, After installing the 3.00.00 beta version of the Koha, i've been trying to link the authorities records with the biblio records launching the link_bibs_to_authorities.pl script without success so far. I did some debugging at the koha-zebradaemon-output.log file and found out that the query looking for authorities matches didn't display any hits, because it was searching with the Match-heading Bib-1 attribute. Our authorities titles are stored in the Marc21 150$a field, that correspond with the Subject-topical-heading Bib-1 attribute, so i had to change in the Heading.pm file in the authorities method the Bib-1 attribute, suppress in the method _query_limiters the thesaurus and added terms, and add in the /etc/koha/zebradb/ccl.properties file the new Local-Use Authority Index of the Subject-topical-heading attribute. After all these changes, launching the link_bibs_to_authorities.pl script started to display results of heading changes and the zebraqueue was filled with biblio specialupdates operations. So i think this is the way how it has to be configured, at least for our authorities records. It worked for me. If anyone has a suggestion or believes that is a wrong procedure comments will be welcome. Thanks in advance and receive my best regards, Salva - ---- Salvador Zaragoza Rubio Departamento proyectos software C/ Garcilaso, 15 46003 Valencia Telf: 96 369 41 23 / 677 405 909 Fax: 96 369 34 39 www.masmedios.com

1 0

RFC on ISBN sanitisations, was: [Koha-patches] [PATCH] Bugfix ShelfBrowser using unsanitized ISBNs. Owen reported the
by Jesse 15 May '08

15 May '08

Woops, forgot to CC the list. Yes, I think this should be moved to C4. I've been noodling around > with the notion of creating a C4::Normalize or the like to centralize > these kinds of normalizations (as ISSNs, LC card numbers, OCLC > numbers, etc. could benefit from this as well), but haven't done > anything yet. > > Regards, > > Galen Do you think we could also put standard formatting of these types of numbers in there, and make a naming scheme? Example: ISBNInternalForm('0-7434-3602-4') eq '0743436024' ISBNDisplayForm('0743436024') eq '0-7434-3602-4' Also LCCNInternalForm and LCCNDisplayForm, etc. The naming scheme is a slightly awkward one, so feel free to modify. It would be nice to have this functionality for other things too, such as C4::Amazon.

6 9

Vote NOW for the Koha Community Website Theme
by Darci Hanning 14 May '08

14 May '08

Dear Koha Community, You may now vote for the Koha Community Website Theme here: http://www.surveymonkey.com/s.aspx?sm=cXmKffvDeO7c48PVcFB4BA_3d_3d Please submit your votes by May 1, 2008, 11:59pm PDT (-0800). The winner will be announced on May 2, 2008 As stated in the poll/survey, you are reviewing the visual impact and graphical elements of the theme. Overall site structure and actual content was created in order for the themes to have something to design against. You can view each of the themes at: http://contest.hanning.name/skin1 http://contest.hanning.name/skin2 http://contest.hanning.name/skin3 If you have any problems viewing the themes, please contact Darci Hanning at darci.hanning(a)gmail.com with "Koha Theme Contest" in the Subject: line. If you have problems with the voting or survey, please contact Joshua Ferraro at jmf(a)liblime.com Cheers! Darci Hanning

10 31

Re: [Koha] Koha 3.0 beta on Kubuntu gutsy - "production mode -trapped fatal
by Mason James 14 May '08

14 May '08

> > On 2008/05/8, at 8:48 PM, Mason James wrote: > >> >> On 2008/05/8, at 6:34 PM, Ken Lomax wrote: >> >>> Hi >>> >>> I see no reason why you should need to uninstall these unless you >>> have >>> different versions of the relevant files. You may need to restart >>> the >>> mysql server "service mysqld restart" on my fedora systems. >>> >>> Check that all relevant files have the same version numbers. The >>> files I >>> have installed are >>> mysql-5.0.45 >>> mysql-devel-5.0.45 >>> mysql-server-5.0.45 >>> mysql-libs-5.0.45 >>> >>> >>> On Tue, 2008-05-06 at 15:33 -0700, rmaynord wrote: >>>> Ken: >>>> >>>> I installed the development files, but no change. Should I >>>> uninstall/install mysql or perl or koha after installing the >>>> development >>>> files? >>>> >>>>>> >>>>>> I then tried to force install DBD::mysql but received the >>>>>> message ---> >>>>>> Can't exec "mysql_config": No such file or directory at >>>>>> Makefile.PL line >>>>>> 76. >>>>>> >> >> >> Hi Robert, >> >> On a debian box, try installing the package 'libmysqlclient15-dev' >> to resolve your missing 'mysql_config' file issue. >> >> $ which mysql_config >> /usr/bin/mysql_config >> >> $ dpkg -S /usr/bin/mysql_config >> libmysqlclient15-dev: /usr/bin/mysql_config >> >> Cheers, Mason. > > > > Just a little update (on a debian box) > > The previous 'dpkg -S' example only works on packages that you > *already* have installed > Try apt-file to find out which package a file belongs to - that you > *dont* have installed. > > $ sudo apt-get install apt-file > $ apt-get update > $ apt-file search 'mysql_config' > libmysqlclient15-dev: usr/bin/mysql_config > > Mason. > _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

1 0

git, mails to patches ML & commit note
by Paul POULAIN 13 May '08

13 May '08

Hello, i've just commited a small patch with long comments, and see that the comment has been wrapped by something. Did someone realize that before, and did someone find a solution not to have commit comment eaten by some hidden beast on the server ? cheers. Note : it seems the commit note is not transformed on git itself, just on the mail to the patches list -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

2 1