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

Bug in memberentry.pl
by Henri-Damien LAURENT 08 Jun '05

08 Jun '05

IMHO, some of the latest changes to member management leaded to a bug in Member adding. On HEAD : > [Wed Jun 08 18:29:21 2005] [error] [client 127.0.2.5] Global symbol > "$member" requires explicit package name at > /home/hdl/Koha/koha-dev/koha/members/memberentry.pl line 244., > referer: http://kohadev.demo/cgi-bin/koha/members/member.pl > [Wed Jun 08 18:29:21 2005] [error] [client 127.0.2.5] Execution of > /home/hdl/Koha/koha-dev/koha/members/memberentry.pl aborted due to > compilation errors., referer: > http://kohadev.demo/cgi-bin/koha/members/member.pl > [ With 2.2 Version, We get on to the Error Page, Without adress. I can't think how. Will investigate on that on Friday if not Fixed by then. -- Henri-Damien LAURENT

2 1

question on aqorders table
by Paul POULAIN 07 Jun '05

07 Jun '05

Hi, Could someone from katipo explain what is the meaning of the various columns in aqorders table that are related to an amount. I see : * listprice (the price entered when placing the order ?) * totalamount (seems always empty) * freight (empty or=0 for me ? Maybe should be attached to the aqbasket table if it's freight fees, as they should be counted only once) * unitprice (the price really paid ?) * rrp (?) * ecost (?) * gst (?) Many thanks. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

3 2

Koha 2.2.3 translation & roadmap & release notes
by Paul POULAIN 07 Jun '05

07 Jun '05

Hello all, TRANSLATION & ROADMAP =============================== Koha 2.2.3 is almost ready. Translators can/must work on their translation files (.po) You MUST update your translations file & check them. There are at least[*] : 9 new strings and 23 fuzzy in OPAC and 17 untranslated / 29 fuzzy in default librarian template. I plan to release Koha 2.2.3 next monday, so you have almost 1 week do update your translations. Reminder : export PERL5LIB=/path/to/koha ./tmpl_process3.pl update -r -i ../../koha-tmpl/intranet-tmpl/default/en -s po/default_intranet_your_language.po --exclude=.*unimarc.* ./tmpl_process3.pl update -r -i ../../koha-tmpl/intranet-tmpl/default/en -s po/default_intranet_fr_FR.po Once you have updated, commit the new po file, i'll take care of tmpl_process3.pl install before releasing. Note : for ppl that don't have cvs access, i can rebuild a .po file and send it by mail. [*] because i'm not 100% sure that my french translation file comes from 2.2.2b, it can be more recent, so there can be more strings to translate. RELEASE NOTES ============================== The release notes should be the following (maybe more, but not less, all what is written here is done & ready) BUGFIXES ***** Critical & Minor mixed === ACQUISITION === * adding supplier info to basket.pl (for order printing) * adding a date filter on acquisition history search === OPAC === * minor fix in subject link (normal view) === CATALOGUE === * it's possible to change a framework type when editing a biblio * (critical) bugfix in authorities : in biblio repeated fields, when you choosed an authority entries, it was copied in all the fields, not only in one. * bugfix : when you duplicate a MARC field (for the 2nd time or more), the last field was duplicated too. * bugfix in subject link, in normal view * bugfix when duplicate authority suspected, the link to see the other authority was wrong. * bugfix in items : the Edit biblio button was wrong. * bugfix when MARC=OFF, subject modifs were not stored in MARC database. * bugfix in z3950 client, for BNF (problem probably due to upgrading of some sofwtare in UNIMARC) === AUTHORITIES === * bugfix in "next page" in authority search (was buggy under certain circumstances only) === CIRCULATION === * bugfix : checking issuing rules under certain circumstances was buggy (reported issuing OK where it should not) * bugfix : renewal by issuing a book again did not work correctly. === BORROWERS === * better management of joining & expiry dates : - dates can be manually typed when adding a borrower. - Empty fields are automatically calculated (joining = today & expiry date calculated from borrower category) - Expiry date can be modified * checking expiry date when trying to issue a book & forbidding issuing when expiry date reached. ** IMPORTANT ** This check was not done before. Thus, you may be unable to issue books where you could before. You can update your database borrower by borrower or with the following SQL command on the server : "update borrowers set expiry='2005-31-12'". You can limit the update to a borrower category with "update borrowers set expiry='2005-31-12' where categorycode='A'" (all SQL commands must be typed without any ") * template improvements & some bugfixes in fines management. === PARAMETERS === * in marctagstructure, next & previous button no more loose frameworkcode & link to default framework IMPROVEMENTS === ACQUISITION === * in history search, a filter has been added on order date. * there are now 2 differents totals : one for rrp column & one for est column === CATALOGUE === * There is also a FindDuplicate feature for MARC Authorities * Dictionnary search : for titles, author & subject, there is now a "dictionnary search". when the user clic on ..., a popup appear, that enable search in biblios as well as in authorities. For example, if user clic on author, and enter "Hugo", he will fing all authors & authority having "Hugo". He then can choose the Hugo he want and run the search with what he has found (& other criteria as well if he want) * it's now possible to change the framework of a biblio * the overduenotice.pl script (that sends a mail to borrowers with late issues) contains the list of late items (title, author) === PARAMETERS === * a new button in marctagstructure.pl has been added : if selected, only actived fields/subfields are shown. Subfields used are in a summary just under the tag. Strongly limits the number of lines shown & more user friendly. * Adding 2 checks in marc parameter checking : only 1 MARC tag must be mapped to item tab and warning if there is NULL in a frameworkcode' === REPORTS === * in "borrowers with no issues" wizard, adding "without issues since" === OPAC === * basket / bookbag sending now has item list and an iso2709 file attached * links to reach suggestions & virtual shelves from any OPAC page * improvements in style sheet for better standard compliance. OPAC works perfectly under opera & konqueror. * added a systempref to define an alternate image as logo (for main page & top-left image on each page) * added a systempref to choose either to show or hide "lost" items. Note that "lost items" can be related to an authorised value list, so does not necessary mean "item definetly lost". Even here, some libraries want to see lost items, and some don't want. This parameter will make everybody happy ! * adding a "complete historyview" for subscription. Show year by year all issues, whatever the status (arrived, missing...) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Bugsquash Session Next Week
by Joshua Ferraro 07 Jun '05

07 Jun '05

Hi everyone, I caught paul, hdl slef and Genji on IRC today and we settled on next Tuesday, June 14 at 15:00 GMT for the next Bugsquash Session. Here's the time in your area: http://tinyurl.com/779cy I count 68 bugs in Koha 2.2 and HEAD: http://tinyurl.com/as66z We'll be working through the bugs, assigning the tough ones and fixing the easy ones. If you can attend, please do (even if you can only attend briefly). (also, I must appologize to the NZ crowd, would you like to schedule a different meeting later this week? Let me know) -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Koha ILS, Mambo Intranet, DiscrimiNet Filter jmf(a)liblime.com | Full Demos at http://liblime.com | 1(888)KohaILS

1 0

Summary 2005-06-06
by mjr＠phonecoop.coop 07 Jun '05

07 Jun '05

What have the koha developers been doing this week? tipaul added MARC new setup checks, added a new build_marc_Tword, changed iso2709 file sending to an attachment, changed pay page to redirect to patron page added systemprefs to control "lost" item display and logo image, fixed and improved dictionary searches, made some graphic improvements to default/en marctagstructure template, and fixed bugs in acqui.simple/additem, the order receive screen, overdue notices, help screens and css/en templates. hdl fixed bugs in opac-full-serial and opac-serial-issues, updated opac-full-serial-issues screens, added a default/de translation by hellen, fixed a bug requiring PDF::API2, added tabsub to css/en opac templates added email-sending to opac-sendbasket, made display changes to default/en marctagstructure, added date to overduenotices and list of books and barcodes, and added a subscription history to serials. hellen updated the default/de intranet translation for 2.2.2 gmccullagh split SearchBiblio and SearchMarc, added opac-search-biblio script, improved opac-search display genjimoto added availability features into SearchMarc and opac-search, added support and editors for mediatype, itemtypesubcategory and itemtypecategory, added search options sidebar to css/en templates, added a catalogsearch() feature to updatedatabase and SearchMarc, and fixed bugs in opac-search, issue/reserve overrides and MARC=OFF subject handling. doxulting updated a lot of unimarc plugins. oleonard fixed an sql_update() bug (870) in css/en opac-search. joshferraro fixed bug 981 in opac-userdetails (missing comma - so did tipaul?). -- MJR/slef Compiled from cvs logs and cvs2cl.pl Full changelog is at http://www.ttllp.co.uk/koha/changelog

2 1

Searching: Zebra
by Joshua Ferraro 06 Jun '05

06 Jun '05

Hi everyone, I've spent the last couple of days playing around with Indexdata's Zebra (http://www.indexdata.dk/zebra/) Zebra is another example of a textual database engine. Zebra can natively index MARC records, so I started by dumping out NPL's records (which took about 20 minutes). Indexing 150K records took just under 3 minutes and all the searches I've done using Zebra's integrated Z39.50 Server have taken less than a second. I haven't had a chance to write a wrapper yet to integrate the search into our existing code but you can try it out at the LOC's generic Z39.50 gateway: http://www.loc.gov/cgi-bin/zgate?ACTION=INIT&FORM_HOST_PORT=/prod/www/data/… This link will allow you to search NPL's 150K database (you could also use any Z39.50 client (like Yaz) to do the search. The server's IP is 66.213.78.76:9999 and the db name is VOYAGER (because that's the only way I could get the LOC's gateway to connect). Zebra is very high performance (it's in use for systems with tens of millions of records). It supports incremental database updates on live systems, exact boolean search expressions, relevance-ranked free-text queries (not sure about stemming). Of the searching ideas we've come up with so far this one is by far the most impressive. There are still some other textual database engines out there (lucene, clucene, xapian, namzu, to name a few), so if anyone would like to try these out and commit some sample indexing/searching scripts I'd be happy to try them out. Coments, questions? -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Koha ILS, Mambo Intranet, DiscrimiNet Filter jmf(a)liblime.com | Full Demos at http://liblime.com | 1(888)KohaILS

2 1

Adding new biblio problem....
by Silva, Ernesto - Webmaster 06 Jun '05

06 Jun '05

Hi everyone, It's been a while since my last post but Andres and I are still working on Koha for our University (Universidad ORT Uruguay), the system is in production state, about 90% of functionallity running. Now the bad news, our librarians reported some strange problems during the catalog process, it seems that one of them (Mr. A in branch A) adds a new biblio and after a while (minutes, hours) the record is modified by another librarian (from Mr. B in branch B). I know this may be a user mistake but they assure me they haven't modified any record, just added one. I've taken a look at the Biblio.pm code and everything seems to be ok ad the NEWnewbiblio function, the process is almost atomic, there is no big reason to begin thinking in concurrency problems (at least for now). Has anyone had this troubles before? Best regards Ernesto.

1 0

css help, please
by Paul POULAIN 06 Jun '05

06 Jun '05

Hi, Does anyone know why in this page : http://bureau.paulpoulain.com:9006/cgi-bin/koha/opac-serial-issues.pl?bibli… The table, that is very long, does not make the mainbloc (light blue) being extended. The look is really dirty & i don't see how to solve this problem. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Marc tag_strucure & subfield_structure
by Partha Mukhopadhyay 06 Jun '05

06 Jun '05

Dear friends, Can any one send me the marc_tag_structure and marc_subfield_structure tables with data (compatible with koha win ver. 2.2.2b)? In fact, the previous win version of koha (2.0.0) includes a sample200 database from where the abovementioned two tables can be copied to blank200 database. But in the 2.2.2 version of koha there is only one database blank222 (which contains nothing) and the sample200 tables of marc tags and subfields are not compatible with the new version of koha due to presence of a new primary field in subfield table (frameworkcode). Under such circumstances, if any one wnat to test the new version he or she has to input all the marc tags and subfields in the database first. I want only this two tables to save manual labour and time. Hope someone will response. P S Mukhopadhyay Vidyasagar Universiy, WB, India -- India.com free e-mail - www.india.com. Check out our value-added Premium features, such as an extra 20MB for mail storage, POP3, e-mail forwarding, and ads-free mailboxes! Powered by Outblaze

1 0

optimising the opac a little
by Gavin McCullagh 05 Jun '05

05 Jun '05

Hi, I'm a newbie here so please be patient with me. I'm going to open up straight away into a proposal, I hope people don't think this rude. If it can't be done, chances are you know why and I don't cause I'm new :-) I have a proposal which I'd like to suggest to optimise the Koha web based opac system. I'd like your opinions as to whether I'm right on track, doing redundant work or just plain off my rocker. It seems from a fairly cursory look that the opac system is basically constructing queries with LIKE '%xxx%' within them to interrogate the biblio table. This works fine of course but if those columns are unindexed this LIKE query seems (in my experience) a little slow. Suggestions to optimise: 1. Add FULLTEXT indexes to each of the searched columns (author,title,...) 2. Change the LIKE queries to use something like the following: SELECT ......, MATCH biblio.title AGAINST ('$titleSearchString' IN BOOLEAN MODE) AS TitleRelevance FROM biblio ..... WHERE ..... AND MATCH biblio.title AGAINST ('$titleSearchString' IN BOOLEAN MODE) ORDER BY TitleRelevance DESC The where clause does a word search of the title field which is very quick, as long as the indexes are in place. The TitleRelevance field in the select gives a match relevance so that you're best matches appear first (ORDER BY TitleRelevance DESC). I was mullign it over in my head and I suspect the way to combine two different column relevances is to multiply them. -- Reservations -- 1. FULLTEXT indexes and MATCH are in MySQL as of version 3.23.23. Is it likely people are using other databases which don't have FULLTEXT indexes? Is it likely people are using older versions of MySQL? http://dev.mysql.com/doc/mysql/en/fulltext-search.html http://www.databasejournal.com/features/mysql/article.php/1578331 http://jeremy.zawodny.com/blog/archives/000576.html 2. BOOLEAN MODE is a very recent addition. Indeed it's not in the MySQL package in Debian Woody. It is in sarge though (Mysql >v4.0.1). This is strictly optional for now as it just makes the searching more powerful (allowing use of wildcards, string removal, etc.). I'm not sure if an old version will ignore it or complain, but this could be left out for now. http://dev.mysql.com/doc/mysql/en/fulltext-boolean.html http://www.databasejournal.com/features/mysql/article.php/1587371 Most people don't use the boolean mode stuff, so it might be nice to have a random "tip" on the search page like: Tip: to search for partial strings use the * wildcard eg "Mac*" will match "MacCarthaigh". and a link to some advanced searching tips. 3. The addition of indexes on the biblio table will slow insertions/updates down. This is a price you pay for faster searching. In my experience it's worth the sacrifice. So, is this all useless nonsense? Should I crawl back under that rock? I'm willing to roll up my sleeves and get at it but I'd like to know this work is useful and it would help to have someone known in the community to keep an eye on the code. As I see it this is a mainly sql task and there shouldn't be too many changes to the perl code itself but I'm not so familiar with the greater part of the project code so I'd rather have someone to look over my shoulder now and then. Here is an example I've just done in PHP on MySQL with a similar database structure. There are ~20K records. http://simms.celt.dias.ie/~gavin/opac/ You can search the titles for 'gael*', the author for 'breatnach', keywords for 'royal' and 'ireland'. I have not yet implemented cross-linking. I'll take this down in a few days. Gavin

4 5