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

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

problem on Importing the MARC
by Mengistu Motbaynor 03 Jun '05

03 Jun '05

Hello I am deploying koha ver 2.2 for our school library system. But I have alot of problems in Importing the MARC record in the existing library ststem. My first problem is When I import records from MARC it did not import the Items copies(barcode, Price,...) that I export it including the catalogue. But I can import the Catalogue only. Thank You Mengistu _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

1 0

What Test::Harness & Test::More package do you have installed?
by Michael Lake 01 Jun '05

01 Jun '05

Hi all The Koha requirements are unclear on what versions or what authors Perl packages are required. For instance MARC-Record & HTML-Template need Test::More There is a package Test::Simple that contains Test::More by Michael G Schwern. This needs Test::Harness however. CPAN lists three Test::Harness packages: Test::Harness run perl standard test scripts with statistics POE-0.3101 - 19 May 2005 - Rocco Caputo Test::Harness Run Perl standard test scripts with statistics Test-Harness-2.48 - 22 Apr 2005 - Andy Lester Test::Harness run perl standard test scripts with statistics Net-ext-1.011 - 10 Apr 2002 - Spider Boardman My Question is: what is the author of the Test::Harness and Test::More packages that you are using? Mike -- Mike Lake Caver, Linux enthusiast and interested in anything technical. -- UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views the University of Technology Sydney. Before opening any attachments, please check them for viruses and defects.

2 1