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

Daemon to look after the zebraqueue commit (from chris)
by Paul POULAIN 19 Nov '07

19 Nov '07

Hello world, I see a patch/commit from chris, about a script called zebraqueue_daemon, that seems to replace zebraqueue_start. Is it the case ? if yes, does it mean zebraqueue_start is now deprecated ? why does that have been done silently ? what about the new deps introduced ? -- Paul POULAIN BibLibre SARL Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

2 1

Possibility of defaulting biblio.datecreated to now()
by Chris Nighswonger 15 Nov '07

15 Nov '07

Hi all, Does anyone see any reason not to default biblio.datecreated to now()? -- Chris Nighswonger Faculty Member Network & Systems Director Foundations Bible College & Seminary www.foundations.edu www.fbcradio.org

2 2

items.ccode or items.itype ?
by Paul POULAIN 15 Nov '07

15 Nov '07

Hello world (and mainly liblimers) kados told me on the chat last week that the item-level circulation stuff relied on items.ccode field. I see this morning commits from Ryan, that speak of "further mods to change from ccode to itype at item-level itypes" Does it mean ccode won't be used anymore and the field name is in fact items.itype ? Is there something i've missed here ? -- Paul POULAIN BibLibre SARL Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

2 1

Re: [Koha-devel] do we really want postgres support NOW ?
by Joe Atzberger 14 Nov '07

14 Nov '07

> Is there truly such a big interest in PostgreSQL over MySQL compared to > Zebra over MySQL? > Zebra is run "along side" your database to generate and maintain indexing. Broadly speaking, I agree with Paul and Chris that "full support" for postgress (backed by robust testing) is unlikely to be available in 3.0, out of the box. --Joe Atzberger Systems Administrator, LibLime

1 0

commit "various authorities fixes" (from galen)
by Paul POULAIN 14 Nov '07

14 Nov '07

Hello world, I have some comment & thoughts about this commit : http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=commit;h=fa480ea4f3e9a8f9db… * 152 field for authority type is unused in marc21, so using it is harmless. But it's the correct field for unimarc, so I think we could accept it (as 1xx is the correct place imho) * why would be need to use summary only in UNIMARC ? The limits of the summary feature are the same in MARC21 & UNIMARC. And for full headings, it does not work 100% correctly in unimarc as well. So let it empty. That's what we say to our customers * The complete building of authority include some non translatable strings. It's not due to galen commit, but I think we will (in france) see this question thrown back to us quite soon... I don't know how we will solve it atm. knowing 2 and 3 users can choose to have something translated or something correct from a MARC pov. I know some customers that will prefer one, some prefering the other. -- Paul POULAIN, consultant senior BibLibre SARL Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

2 1

do we really want postgres support NOW ?
by Paul POULAIN 14 Nov '07

14 Nov '07

Hello again, We are a few days before a beta release of Koha 3.0 chris N. adds a lot of feature to support postgresSQL. which is undoubtfully a good feature. But do we want it now ? after rebasing this morning, all my koha setups were messed up : encoding was wrong again. Looking at last night commits, i've found a small error : $dbname instead of $db_driver in Context.pm This may have been unseen by the RM if test were not using non ascii char. The fix was trivial to do (patch sent to kados & chris) But I think we should NOT do so deep changes now. Maybe it's time for a 3.0-stable branch in git that will get only bugfixes ? -- Paul POULAIN, consultant senior BibLibre SARL Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

4 3

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