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

Discussion concerning the possible use of M::B rather than EU::MM for Koha installation
by Chris Nighswonger 14 Nov '07

14 Nov '07

In looking at how to approach the installation of marc/lang options for zebra with makefile, I ran across Module::Build which is a pure perl variety of ExtUtils::MakeMaker. Since we also have to address the issue of cross platform installation of Koha and M::B supports cross platform installtion, I am wondering if there are any issues holding us back from switching to M::B? The port should not be too difficult and would only require that the installer have M::B installed on their system. Any thoughts? Chris -- Chris Nighswonger Faculty Member Network & Systems Director Foundations Bible College & Seminary www.foundations.edu www.fbcradio.org

2 1

rebuild_zebra_idx.pl
by Paul POULAIN 13 Nov '07

13 Nov '07

Hi world, i've seen a fix on rebuil_zebra_idx.pl In fact, last week I was about to remove it, as it's replaced by rebuild_zebra.pl that does much more things : 1- create zebra files *if needed* (ie : they don't exist already) 2- export datas biblio & authority (or only one) 3- run zebraidx 4- keep the export for a future use. where rebuild_zebra_idx does only the export for biblios. Could you (1st for mason, who patched rebuild_zebra_idx) give me your opinion on this ? -- Paul POULAIN, consultant senior BibLibre SARL Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

4 3

Preposed sql script filename change
by Chris Nighswonger 09 Nov '07

09 Nov '07

Hi all, I have been working on porting Koha to run over PostgreSQL. (We run Postgres on our backside with several apps currently and will be adding others, so you know something of my motive here.) In the process of the port, I have needed to distinguish between sql files for MySQL and PostgreSQL. I have been doing this by renaming sql files after this method: foo_mysql.sql foo_pg.sql This allows me to do things like '~ /_mysql\.sql/' etc. and import the correct flavor of sql. Since such a change would require cooperation, I thought I would submit it here to see what others think. I have no corner on the market, and I'm certainly open to anything that works with relative ease. -- Chris Nighswonger Faculty Member Network & Systems Director Foundations Bible College & Seminary www.foundations.edu www.fbcradio.org

2 4

zebra config files [IMPORTANT]
by paul POULAIN 09 Nov '07

09 Nov '07

Hello folks, working on unimarc for zebra, I've seen some strange things in etc zebra files : - ccl.properties don't have popularity anymore - bib1.att : att 9002 is biblioitemnumber, shouldn't it be biblionumber as in ccl.properties (biblionumber 1=9002) ? - bib1.att : att 9910 Koha-Auth-Number and ccl.properties says Authority_number 1=8910 - the zebra files in etc don't reflect at all the ones in misc/zebra. The etc directory has been added by MJ installer. Which should we consider as the correct zebra config file ? If we use etc (which I've nothing against, but we would have been pleased to have been warned), then how to handle UNIMARC settings during install ? * during perl Makefile.PL, we can't request the sysadm to know if the library want MARC21 or UNIMARC ! * during web install, we won't probably have a write access to those files. So, how to do the job ? I imagined the script rebuild_zebra.pl, that does the stuff from the systempref, and can be run after the web install. but it seems MJ choose another way. But now, I don't know how to solve the "unimarc setup" problem ! Any idea/comment welcomed. -- Paul POULAIN, consultant senior BibLibre SARL Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

3 2

Stocktake Report
by ZANG 30 Oct '07

30 Oct '07

Hi All I have to develop some custom reports and functions for a client. The stocktake report has to have a barcode printed with the item information. I am considering using the barcode.pl and barcodeGenerator.pl as a basis. The problem is, I do not get any output in the PDF file. I am new to Perl and get stuck with some elementary issues. Can someone please tell me where do I see a "warn" message. I want to use "warn" to give information about the generated sql, etc. I checked in all log files, but I cannot find it. Please help! Regards Zang

2 1

ANNOUNCE: New Installer in master git tree
by MJ Ray 21 Oct '07

21 Oct '07

Well, one koha user already tried it, so I guess I should announce it here: THE NEW INSTALLER IS IN THE MASTER TREE The new installer is based on MakeMaker, the tool that is usually used to install CPAN modules. This means that if you know how to customise CPAN-installed modules, the same things should work for you with Koha. If not, don't worry. If you want to customise the installation more than described in the README.txt, run "man ExtUtils::MakeMaker" By default, the installer doesn't ask you any questions and tries to assume sane defaults, which I think is A Good Thing, but you can override most of the settings with environment variables. For instructions on how, run perldoc rewrite-config.PL As well as the CPAN-package-style installation, there is also a very quick-and-dirty script called install-CPAN.pl which should install all dependencies from CPAN automatically. For instructions on how to package releases, run perldoc Makefile.PL TREE STRUCTURE C4/*.pm is copied to perl’s lib namespace. CGIs are copied to $(PREFIX)/lib/cgi−bin/koha/ and other scripts to koha/ in perl's lib. Config files are copied to $(PREFIX)/share/koha/etc Templates are copied to koha/templates, excluding non−files, CVS files and whitespace in filenames. KNOWN BUGS There is no zebra init script and some of the zebra-related directories are not constructed and not complete. This is partly because I don't really know what I'm doing with the zebra server yet. Can anyone explain it to me, or remind me where to find the explanation, please? Thanks, -- MJ Ray - see/vidu http://mjr.towers.org.uk/email.html Experienced webmaster-developers for hire http://www.ttllp.co.uk/ Also: statistician, sysadmin, online shop builder, workers co-op. Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/

3 7

opac login error for customer with item already check out
by Simon Mitchell 20 Oct '07

20 Oct '07

Hi every one, My koha problem - opac login error for customer with item already check out. I did find that solution to my koha 2.2.9 opac problem that was posted on the katipo list, but is was very hard to find. So am posting it here so the next time it will be easy to find it. My setup - Koha 2.2.9 NPL template Ubuntu 7.10 mysql v5 Linux library 2.6.22-14-server #1 SMP Wed Oct 10 06:35:59 GMT 2007 i686 GNU/Linux library:~$ mysql --version mysql Ver 14.12 Distrib 5.0.45, for pc-linux-gnu (i486) using readline 5.2 opac error log [Fri Oct 19 13:20:18 2007] [error] [client 59.167.xxx.xxx] HTML::Template->output() : fatal error in loop output : HTML::Template::param() : attempt to set parameter 'reserves' with an array ref - parameter is not a TMPL_LOOP! at /usr/local/share/perl/5.8.8/HTML/Template.pm line 3069, referer: http://123.243.5.81:8003/cgi-bin/koha/opac-user.pl [Fri Oct 19 13:20:18 2007] [error] [client 59.167.xxx.xxx] at /usr/local/koha/opac/cgi-bin/opac-user.pl line 166, referer: http://123.243.5.81:8003/cgi-bin/koha/opac-user.pl [Fri Oct 19 13:20:18 2007] [error] [client 59.167.xxx.xxx] Premature end of script headers: opac-user.pl, referer: http://123.243.5.81:8003/cgi-bin/koha/opac-user.pl Chris had kindly put a solution in this email, is it ok in the next release? Thanks all. Regards, Simon http://lists.katipo.co.nz/public/koha/2007-June/011850.html >From Chris's email ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Ok, So this is bizarre, If I change $template->param(RESERVES => $reserves); to $template->param(RESERVE => $reserves); In opac-user.pl And then change  to  in opac-user.tmpl Suddenly the error goes away. If either of you could confirm this works for you, that would be great, and ill commit it to cvs, so that it comes out in the next version ... weird Chris -- Chris Cormack chris.cormack at liblime.com <http://lists.katipo.co.nz/mailman/listinfo/koha> VP Research and Development www.liblime.com LibLime +64 21 542 131 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++

1 0

Chris Cormack wins award at NZ Open Source Awards
by Russel Garlick 17 Oct '07

17 Oct '07

Hi Everyone, Firstly, please excuse the cross posting. I am very pleased to announce that Chris Cormack, the current Koha QA Manager and former release manager for V1.2, won the Open Source Contributor Award at the first ever New Zealand Open Source Awards last night. The award recognizes Chris' tireless, ongoing effort working on the Koha project. Koha was also a finalist in the projects category. Chris accepted the award in his normal humble style, making a point of thanking everyone else involved. It was a great evening, with Koha getting mentioned several times, including a mention by the New Zealand Minister for ICT. Congratulations to Chris! For more about the awards see : http://www.nzosa.org.nz/ It was a great event, superbly organized by CatalystIT (an open source company here in Wellington,NZ). I'll do a post for the website with some photos soon. Cheers, Russel -- Russel Garlick russel.garlick(a)liblime.com General Manager - Australasia +64 21 542 188 LibLime Limited www.liblime.com

2 1

Issuing rules
by Paul POULAIN 12 Oct '07

12 Oct '07

Hello world, We are reviewing Koha for 3.0 Release & Joshua pointed something important: the way issuingrules worked in koha 2.2. In Koha 2.2, the way it works is : - you define the rules depending on itemtype / patron category / branch - you have "wildcard" that means "all of them". For example, * / adult / * = 5 means "an adult patron can't issue more than 5 items whatever the branch". - The circ module check ALL the rules & warn if one is not correct. So, if you don't fill a cell, it's considered as 0 (= no issue possible) - you must fill book / * / * by understanding it means : "no patron can't issue more than X book(s)" This behaviour troubled a lot users, as we often have questions about warnings that were not expected. Joshua think, and i' fully agree with him, that the user understand the wildcard as 'default if nothing specified'. So, for example, book / * / * would mean : if a specific rule is not defined for patron category, then use this default value. We should not have a "check ALL the rules", but a "check the 1st available, from most to less specific + check the total rule if available.". The "wildcard" on itemtype being renamed to "total", and being applied if defined, as total document the patron can issue. so we could have something like that adult children default book empty 3,21 5,21 serial 4,14 3,21 5,21 comic 5,21 3,21 empty total 7 empty 5 which would mean : - an adult can issue 5 books for 21 days (default rule) - an adult can issue 4 serials for 14 days (specific rule) - an adult can issue 7 documents total - a child can issu 3 books, 3 serials, 3 comics, but 5 document maximum The "branch level" has the same behaviour : it a rule for a branch is defined, then it's applicable, otherwise, it's the default rule of the default branch. Let us know your opinion on this. It would require some tweaking on issuingrules definition & a small rewrite the CanBookBeIssued sub, to check only 2 rules (1st found + total), not 8 (every cell that fit the issue). -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

6 8

Norwegian translation of Koha
by Axel Bojer 12 Oct '07

12 Oct '07

On 2007-08-20 20:50 Joshua M. Ferraro wrote: > We're pretty close to a release of 3.0, though in the next month or so > there will be at least some changes to the HTML markup which will > affect translation. The 3.0 markup represents a fairly drastic change > from the 2.2 series so I'm afraid that translations of 2.2.x won't be > that useful. (...) > There's another, separate issue not mentioned yet, which is > translation of the MARC frameworks, including authorities control and > bibliographic entries (essentially, these are labels of the MARC tags > and subtags that a cataloger uses). That adds about 1,500 additional > lines. We have good news from Norway: NUUG ( Norwegian Unix User group, http://nuug.no/ ) have agreed to pay two translators to translate koha into norwegian (bokmål, by the way, we also have nynorsk :-). So now the next question is: How far has the translation files for Koha 3.0 come by now? As quoted above, they ought to be in good shape now, but, well, delays seems to happen, so: How is the status by now? Is it advisable and possible to start translating koha 3.0 already now or will there be major changes that will render our work (partly) useless? I also wonder how difficult it will be to make a local build with our translations? My experiences with other translation project (Scribus, OOo, KDE) shows me that it is essential to be able to look at what you have actually committed. Often it is impossible to know exactly how to translate a spesific phrase without knowing how this function works and/or what the GUI looks like. It will therefore be important for us to be able to make our own localised builds continuously to see the changes and the results. And third: If all the other questions are answered with «GO FOR IT (NOW)», then: Is it possible to put the needed files out on the net like this: http://translate.koha.org/use.php?lg=en or do you have pot- and po-files ready for us? And, finally, what about the mentioned «MARC frameworks», are there any ready made translation files for them? Best regards Axel Bojer Norwegian translator

1 0