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

Koha from CVS
by Daniel Holth 25 Jan '04

25 Jan '04

Is there a tutorial somewhere on installing Koha from CVS? Thanks, Daniel Holth

3 2

Library of Congress
by Daniel Holth 24 Jan '04

24 Jan '04

Now that Koha 2 rc something is using more MARC and has a nice MARC editor it should be easier to use LC Call numbers. In the past I had wondered, 'how would I order search results by LC Call?' Well, format a sorting field like this in the database, with optional dots: BV.004529.200000.L3600 and it should sort lexicographically more or less like LC Call numbers are intended to sort. Does anyone know if there is a maximum length to each part of the number? Thanks, Daniel Holth

1 0

EAN to ISBN
by Daniel Holth 24 Jan '04

24 Jan '04

I've been frustrated that Koha woudn't accept EAN numbers like this, that I scan with a certain cat-shaped barcode wand: 9780061020674 This is the EAN for a paperback edition of Sourcerer (a novel of Discworld) by Terry Pratchett. It's encoded in a barcode. The ISBN is 0-06-102067-2 - embedded in the EAN, except the EAN has its own checksum. Enter a module I dub ISBNParse.pm - in my tree (newest 2.x .tar.gz downloaded from sourceforge) I put this in koha/intranet/modules/C4/ISBNParse.pm; then files like isbnsearch.pl can be modified: ---- use C4::ISBNParse; if ( !$isbn && !$title ) { print $input->redirect('addbooks.pl'); } else { $isbn = C4::ISBNParse::isbnfu($isbn); $input->param('isbn', $isbn); ---- If Business::ISBN is installed you get EAN-to-ISBN conversion, and this agrees nicely with my barcode scanner. If I had a CueCat that output scrambled data, I would further enhance ISBNParse.pl to unscramble the CueCat data (if /that/ module was available). I hope this can work for somebody! The main trick is figuring out where to insert it; perhaps the isbnfu() calls could find a home in Search.pm. It might make sense to enforce dashes (or their absence) in ISBN numbers? - Daniel Holth -------- ISBNParse.pm: # Convert EAN to ISBN when given EAN; when given ISBN, pass through. # When given unrecognizable text, pass through. package C4::ISBNParse; # This is free software; you can redistribute it and/or modify it under the # terms of the GNU General Public License as published by the Free Software # Foundation; either version 2 of the License, or (at your option) any later # version. # # This is distributed in the hope that it will be useful, but WITHOUT ANY # WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR # A PARTICULAR PURPOSE. See the GNU General Public License for more details. # # Copyright 2004 Daniel Holth <dholth(a)fastmail.fm> use strict; require Exporter; use vars qw($VERSION @ISA @EXPORT $HaveISBN); $VERSION = 0.01; @ISA = qw(Exporter); @EXPORT = qw(&isbnfu); BEGIN { eval 'use Business::ISBN qw ( is_valid_checksum isbn_to_ean ean_to_isbn )'; $HaveISBN=1 unless $@; } sub isbnfu { my $input = shift; print STDERR "\n$HaveISBN isbnfu $input\n"; my $isbn; if($HaveISBN) { print $input; $isbn = ean_to_isbn($input); if($isbn) { $isbn = new Business::ISBN($isbn)->as_string; } unless($isbn) { $isbn = new Business::ISBN($_); if($isbn) { $isbn = $isbn->as_string; } } unless($isbn) { $isbn = $input; } } else { $isbn = $input; } return $isbn; }

2 1

(no subject)
by None 22 Jan '04

22 Jan '04

--=====================_23239326==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed What is the function of the "itemnumber" field in the "items" table in Koha? Where does it come from? How is it used? In the MARC/Koha cross reference document on http://www.koha.org/wiki (which I realize is woefully out of date) the "itemnumber" field references MARC tag 890, subfield "c", which, as far as I can tell is not used elsewhere in Koha. In fact, neither MARC21 nor UNIMARC define tag 890 at all (see http://www.loc.gov/marc/bibliographic/ and http://www.ifla.org/VI/3/p1996-1/sec-uni.htm for tag definitions under MARC21 and UNIMARC, respectively). I have tried to put together a cross reference spreadsheet based not only on the cross reference document noted above, but also by reference to fields defined in Koha. Any information I can get on this or related questions will be appreciated. Thanks, Tom Madron Tom Madron Enterprise-Wide Computing, Inc. 1023 15th Avenue, South Nashville, TN 37212 Telephone: 1-615-259-2771 URL: http://www.ewcnet.com mailto:tmadron@ewc-inc.com --=====================_23239326==_.ALT Content-Type: text/html; charset="us-ascii" <html> What is the function of the "itemnumber" field in the "items" table in Koha?  Where does it come from?  How is it used? In the MARC/Koha cross reference document on <a href="http://www.koha.org/wiki" eudora="autourl">http://www.koha.org/wiki</a> (which I realize is woefully out of date) the "itemnumber" field references MARC tag 890, subfield "c", which, as far as I can tell is not used elsewhere in Koha.  In fact, neither MARC21 nor UNIMARC define tag 890 at all (see http://www.loc.gov/marc/bibliographic/ and http://www.ifla.org/VI/3/p1996-1/sec-uni.htm for tag definitions under MARC21 and UNIMARC, respectively). I have tried to put together a cross reference spreadsheet based not only on the cross reference document noted above, but also by reference to fields defined in Koha. Any information I can get on this or related questions will be appreciated. Thanks, Tom Madron <x-sigsep></x-sigsep> <div align="center">Tom Madron Enterprise-Wide Computing, Inc. 1023 15th Avenue, South Nashville, TN 37212 Telephone: 1-615-259-2771 URL: <a href="http://www.ewcnet.com/" eudora="autourl">http://www.ewcnet.com</a> <a href="mailto:tmadron@ewc-inc.com" eudora="autourl">mailto:tmadron@ewc-inc.com</a> </div> </html> --=====================_23239326==_.ALT--

1 0

Re: [Koha-devel] Koha 2.0.0RC1 is dead. Long live to koha 2.0.0RC2!!!
by Owen Leonard 21 Jan '04

21 Jan '04

> This one is not yet completely fixed: > > * 662 : poor SQL calls, that could be used for > > SQL injection (security problem) By the way, thanks to MJR for putting in a lot of time on this bug. It's never as fun to this kind of important polishing as it is to add new stuff. > > Are these three the only blockers? > > I see the following as blockers/critical in bugzilla: > 196 cri P1 user input not checked for HTML tags > 436 cri P2 circulation.pl only partially templated > 662 cri P2 Probable insecure use of prepare() > 293 cri P2 Error Issuing Book - 1 436 is a pernicious one, but enough progress has been made that I wouldn't consider it a blocker, even though it still irritates me :) 293 is definitely a problem for circ staff. I don't know about the proper use of blocker/critical/major etc., but I'll toss in these bugs that make day-to-day life hard for our staff: 612 maj P2 Renewal failure gives no feedback 670 maj P2 "Waiting" status often inaccurate 605 maj P2 circulation.pl only shows one waiting item 613 maj P2 Deleting one of a patron's multiple reserves on a single item deletes all 661 maj P2 circulation.pl no longer shows flags 617 maj P2 OPAC renew function available even if item is on reserve 668 maj P2 Cancelling reserve upon check-out does not work -- Owen ---- Nelsonville Public Library http://www.athenscounty.lib.oh.us

1 0

Koha 2.0.0RC1 is dead. Long live to koha 2.0.0RC2 !!!
by paul POULAIN 21 Jan '04

21 Jan '04

koha 2.0.0RC2 has been released : http://sourceforge.net/project/shownotes.php?release_id=211242 This version of Koha is the second in the 2.0 "stable" series. It does not mean that it has no bugs, but many libraries are using it and don't encounter unsolvable problems. If you want to adopt Koha, please do, but you're warned that this release candidate version may still have some bugs and missing features. If you test it and let us know about any we haven't seen yet, it will help us to fix them. The 2.0.x series version is "feature freezed". Only bugs or minor changes will be made in this branch. The koha team is already working on the 2.2.x version. In CVS (HEAD branch), developpers can already get 1st draft of a working z3950 server. BUGS FIXED: * 318 : allow or not a book to be loan * 537 : in borrower screen, the "fine & debts" now shows only amount due if >0, "nothing due" if borrower has no debts. * 557 : spelling error in message for no search criteria entered * 564 : Member card number not checked unique * 586 : additem.tmpl displays incorrect biblio number * 605 : circulation.pl only shows one waiting item (1 small problem remaining, see bugs.koha.org) * 614 : opac-user.pl doesn't show which items are waiting * 625 : dateformat under system prefs is confusing * 646 : Member flag must be either 'parameters' or 'superlibrarian' to log in (now, any flag enable login) * 662 : poor SQL calls, that could be used for SQL injection (security problem) * 671 : Add institutional member confirmation screen has no details * 672 : readingrec can not be reordered * 675 : "logged in" info missing * 683 : Search for barcode or illustrator says ' You did not specify any seach criteria' * minor HTML modifs & tweaks * minor improvements/bugfixes in installer * biblio & item deletion bugs fixed. * bug fixed in MARC editor, that appeared on specific MARC configuration & makes biblio adding impossible. IMPROVEMENTS: * z3950 client daemon improved a lot : many deadlock situations solved, improved problem reporting, ignoring invalid z3950 servers (or server not responding) * new french translation. Note that only english and french are up to date. Other won't work, probably. Note also that a tool for translator is now ready, and should ease a lot translating and maintaining translations. * new OPAC theme. it's called "css". It's a XHTML1.0 strict OPAC. In librarian interface, just change systempref opactheme to css to get it. Will be the default opac in 2.2 * publisher added in acquisition process (the one with basket & supplier) Basket now ordered by publisher. * notforloan field management added in itemtype administration screen * new migration script : misc/rebuildthesaurus.pl => this script can rebuild thesaurus/authority file after importing records with misc/bulkmarcimport.pl DB change : *index added into z3950results table UNIQUE KEY query_server (queryid,server) (added by installer & updater) KNOWN BUGS : * MARC upload fails silently (in breeding farm) if the file provided is not iso2709 (works fine with a valid file) * autobarcode not calculated even if autobarcode system parameter is set and MARC=on. * the MARC21 english default parameter setup is working, but some librarians reports that some choices are poor. If you use MARC21, tweak some setups to fit your needs. (note : the subject refers to what french people said when we had a king, 2 centuries ago : "the king is dead. Long live to the king" (the 1st being the old king, the 2nd being the new one. Not sure everybody around the world uses such a sentence, so I explain :-) ) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

3 2

Perl regex
by Bernardo Rechea 20 Jan '04

20 Jan '04

Hi, Paul, I just subscribed to this mailing list, but saw your message in the archives: > We have the following strings in templates : <a > href="/koha/search.pl">search</a> the library. > > In the translation file for french, we have : > search chercher > So, the regexp : > $line =~ s/(\W)$text(\W)/$subst/g; > > that is WRONG !!! (search.pl must not be replaced !) > > & I couldn't find the regexp that could work better. > [...] > but i'm still looking for a better solution to do this. > > Note : remembre we can also have <img src="XX" alt="search"> and this > search is to be replaced... Try this: $line =~ s/(<=\W)$text(?!\.pl)/$subst/g; By the way, should the original regex you posted have been > $line =~ s/(\W)$text(\W)/$1$subst$2/g; ? Otherwise you would be deleting one character before and one character after every "search". Anyway, the above regex should substitute any $text that is preceded by a non-word char and not followed by '.pl'. Since the message is almost a week old, you probably have figured it out by now, but I thought I'd give it a try, because I can't resist a regex quiz ;-D I guess I should introduce myself: my girlfriend and I volunteer for the German Library School of Boston. Recently it was decided to automate library circulation and have as well an electronic catalog. I use Linux at work and at home, and after some searches we found a nice open source project that did what we needed, Koha, so here we are. We have installed it on two laptops and it's working mostly fine save for some glitches. But I guess I should talk about that in the Koha mailing list, not here. Bernardo Rechea

1 0

Re: [Fwd: Re: library for Friend's Meeting]
by Pat Eyler 20 Jan '04

20 Jan '04

On Tue, 20 Jan 2004, William Holt wrote: > > > DBI connect('scQuakers:localhost','kohaadmin',...) failed: Access denied > for user: 'kohaadmin@localhost' (Using password: YES) at > /usr/local/koha/intranet/modules/C4/Context.pm line 368 > connected to your DB. Checking & modifying it > Can't call method "prepare" on an undefined value at > scripts/updater/updatedatabase line 619. > Problem updating database... > bash-2.05b# > > Can you explain what I should have here? Is there something I can do on > the command line to test that mysql is setup with the correct > username / root password? Try using mysql from the commandline like this $ mysql -u root -p and giving what you think the root password is at the prompt you might also try $ mysql -u kohaadmin -p and giving it the kohaadmin password -pate > > Thanks, > > -Will >

1 0

planning for search rewrite, need feedback
by Pat Eyler 19 Jan '04

19 Jan '04

Yesterday and again this morning, discussions on the #koha irc channel turned to searching and a decision was made to develop a "google-like query syntax" (GQS) for searches. In general, we want to develop a much better search back-end that: - can optimize queries - is accessible to multiple front-ends (Z39.50 server, Catalog Searches, Circ/Patron searches, reports, etc.) - handles security better than the current model - 'lowers the bar' for developers who want to work on localized improvements for searches - easily spans the range from very simple to very complex queries We're looking at two passes. The first pass would parse incoming search requests and compile GQS queries. This pass would be performed by the SearchParser::Foo family of modules (e.g., SearchParser::Basic, SearcParser::Z3950, etc.). The second pass would convert the GQS into SQL, optimize the SQL query for the Koha DB structure, and handle the returning of data to the application. We intend to create these new modules following the Perl OO style to provide the easiest possible access to developers. I volunteered to look up the google search syntax and make a first cut at how we might use it for our query syntax. Would someone be willing to look at Z39.50 searches to see what additions they' d need? (Joshua?) Are there other kinds of searches that will need special terms or operators? If so, what are they? We still need to deal with constraining searches/queries to acceptable kinds of queries against specific tables and fields. We can work on hammering that out after we agree on the syntax we need. Here's my take on the syntax: The basic unit of a search is a term. By default I think we want to match terms within a field rather than exactly matching. Terms are any of the following: aString term term = term & term = term AND term term | term = term OR term term ^ term = term XOR term (term) -term # not including term #term # begins with term term% # ends with term -#term -term% = term > term < term >= term <= term We also want to deal with the special case of: "foo * bar" There are some special operators we want to deal with. Some of these operators could be combined, any of the operators could be negated (with the syntax '-[operator]'). They should apply to the entire search: locally => this item exists in the local branch available => the item is not lost, checked out, or on hold onhold => the item is marked as reserved lost => the item is marked as lost circulating => the item can be checked out There are also operators which only act on a term (which of these should be the default, 'keyword: term'?): title: term exacttitle: term subject: term author: term exactauthor: term keyword: term branch: term marc-[recordnumber][-sub]: term # these should allow some wildcarding, like: # marc-6X0-a # marc-58X-a # # nobody in the discussion was/is a MARC expert, does # this syntax work? Some examples: title: ("looking glass") -(author: carrol%) # any title containing "looking glass" where the author doesn't # end with carrol "animal husbandry" OR (raising AND (rabbits OR chickens)) "animal husbandry" | (raising (rabbits | chickens)) # these are equivalent subject: knights AND marc-526-c >= 3 AND marc-526-c <= 4 # subject includes knights and AR reading level is between # third and fourth grade available locally subject: knights AND marc-526-c >= 3 AND marc-526-c <= 4 # as above, but local copies are available for checkout Pat Eyler Kaitiaki/manager migrant Linux sys admin the Koha project ruby, shell, and perl geek http://www.koha.org http://pate.eylerfamily.org

2 1

koha 2.0.0RC2 release date
by paul POULAIN 19 Jan '04

19 Jan '04

Hi, I'll try to release 2.0.0RC2 on Tuesday. Does anyone have an objection ? (note i'll be away - koha demo in Lyon & update in Dombes Abbey - from wed to fri this week) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0