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

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

Translator tool improved
by paul POULAIN 16 Jan '04

16 Jan '04

Hi, I've just commited many translator tool improvements. Now, the translator tools works perfectly fine. * managing strings with LIMITED pragma when the string is a koha intenral code too (like search) * improving speed by 50 : just by reading the whole file before s///g, instead of doing a s///g on each line ! (on 1000 lines translation file, that makes a HUGE difference !) * NOT overwritting unchanged file => now, we can commit only what has changed ! * removing useless chars (., ?, spaces...) at end of strings. WORKS on french OPAC AND INTRANET without problems. Enjoy, and publish new localised versions of Koha in a few hours :-) PS : thanks to Jean Blaise that translated the intranet (1130 lines) to french. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Re: [Koha] Can't add member to Koha
by paul POULAIN 15 Jan '04

15 Jan '04

Greg Prapat a écrit : > Dear Paul, pls, answer on koha-dev > 1. I'm using Koha version 1.2.3. So, i can't help you : i'm 2.0 release manager & never installed a 1.2.3 (really) > 2. This is the error message from the log file > > DBD::mysql::st execute failed: Can't connect to local MySQL server > through socket '/var/lib/mysql/mysql.sock' > (2) at /usr/local/koha/intranet/scripts/z3950daemon/processz3950queue > line 259, <KC> line 22. this one means the mySQL server is down. > DBD::mysql::st fetchrow failed: fetch() without execute() at > /usr/local/koha/intranet/scripts/z3950daemon/proc > essz3950queue line 264, <KC> line 22. > Thanks, > Greg > -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

3 4

Re: [oss4lib-discuss] Upcoming Koha development (fwd)
by Pat Eyler 15 Jan '04

15 Jan '04

here's some feedback on a request I made on teh oss4lib mailing list -pate ---------- Forwarded message ---------- Date: Thu, 15 Jan 2004 06:58:14 -0800 From: Denise Sharp <denise(a)sharp.ath.cx> To: Pat Eyler <pate(a)eylerfamily.org> Cc: oss4lib-discuss(a)lists.sourceforge.net Subject: Re: [oss4lib-discuss] Upcoming Koha development Pat et al, I work in a special library that has more types of call numbers than any other library I've worked in. We use Library of Congress, SuDocs, and a call number section that was invented specifically for things written by our company. The more flexibility you can build into the call number system, the better. Thanks for asking! --Denise Sharp Pat Eyler wrote: > Hello everyone, > We're in the closing phases of beta releases for Koha 2.0, and have > just opened up development for the 2.2 release (2.1 will be the > development series which leads to 2.2). We've identified some targets for > 2.2, but would like to have the larger OSS4Lib, Library, and Library > consulting communities help us flesh out our development goals for 2.2 and > beyond. > > The big new features we hope will be part of 2.2 are: > a Z39.50 server (working version completed) > an RSS report engine (working version completed) > an expanded serials module (under design in France) > switchable call number systems (at least Dewey and Library of Congress) > This one should include the ability to run more than one > call number system at once. > catalog search enhancements (e.g., adding a google-like syntax) > many more bundled reports (we're still trying to identify good > candidates) > > Some other features might include: > NCIP > RFID integration (already done at one library) > context sensitive searching of appropriate record types > Advanced Reader handling for K12 school libraries > better consortia features (already done for a largish consortium) > integrated ILL system > > I'd like to hear your feedback on the ideas that have come up so far (and > the ones we've missed). Even better, I'd love to see you get involved in > the dialogue. > > thanks, > -pate > > Pat Eyler > Kaitiaki/manager migrant Linux sys admin > the Koha project ruby, shell, and perl geek > http://www.koha.org http://pate.eylerfamily.org > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Perforce Software. > Perforce is the Fast Software Configuration Management System offering > advanced branching capabilities and atomic changes on 50+ platforms. > Free Eval! http://www.perforce.com/perforce/loadprog.html > _______________________________________________ > > > oss4lib-discuss(a)lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/oss4lib-discuss > see also http://oss4lib.org/ > -- "We cannot direct the wind but we can adjust the sails."

1 0

z39.50 & Bugzilla
by Mike Mylonas 15 Jan '04

15 Jan '04

Hi Team Was looking through http://bugs.koha.org today, and saw that the issue for the z39.50 Server has been resolved (thanks Joshua) I am thinking that we should create a seperate Bugzilla component for the z39.50 server to allow us to track issues etc. I was about to create the component, and stuck a mild problem which I would like your comments on ... do we (a) Create a component for the z39.50 server, and leave the z39.50 client as part of the Catalogue component (b) Create a seperate component for the server and the client (c) Create a z39.50 component to handle both client and server. or (d) Don't create any components as both client and server belong the in current Catalogue compnent Your thoughts would really be appreciated Cheers Mike (Dragon28)

4 4