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

whois JohnN ?
by Stephen Hedges 31 May '05

31 May '05

Does anybody know the "JohnN" who joined us for the IRC meeting on May 20? If you do, could you send me the info off-list? Thanks! -- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges(a)skemotah.com

1 0

Re: [Koha-devel] inverted list Proof of Concept [quest for search]
by Paul POULAIN 30 May '05

30 May '05

Tümer Garip a écrit : > Dear Paul, (cc to koha-devel to this mail sent personnaly to me) > > Excellent idea. I wanted to write to you for a long time. Now I take > this opprtunity > I have already tried it and it looks it is definitely the way to go. > 1- I had a few problems which I thought I should share it with you. The > problem with the foreign characters lies in the fact that the perl code > changes everything to uppercase but offcourse not the accented > characters. So say a Turkish word 'çim' becomes 'çIM'. We also have say > 'ÇIM'. These two words produce identical index keys for MySql as it is > case insensitive. I know this, but it's just a proof of concept. > That is why you are getting SQL errors as Mysql is finding duplicating > keys and dropping some our your data. I have changed the PRIMARY index > on your table to INDEX and this solves the problem. nope. The correct way to go is to remove all accented characters. Seems we could do this with : use utf8; use Unicode::Normalize; $w = NFKD $w; $w =~ s/\pM//g; > 2- Is there a reason we are using 'title' as one of the keys of the > inverted file?. Are we going to use this 'title' anywhere else later on. > If not it is taking unnecessary space. I used bibid-biblionumber > combination and your code still works. yes, but you can't order the result by title without another sql query. That's why I think we need one table for each ordering we want to have with biblio-ORDERING_FIELD like : biblionumber-title, biblionumber-author, biblionumber-dewey... > If there is nothing that I am > missing I suggest we use bibid-biblionumber. This way we can reach the > MARC files or old Koha files directly if we need to at a later stage. > > 3- Another subject: > I have translated the NLP opac pages for 2.2.2b to Turkish. I do not > intend to translate intranet pages. I could not use the .po files as the > making of Turkish sentences is almost upside down. If there is any need > for these files I can e-mail them to you. Could be interesting, but the problem is that templates are changing, so you must use .po files. softwares like KDE or Gnucash uses .po files & are translated to turkish isn't it ? > > Good work, > > Tumer Garip > > NEU Library > Cyprus -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

inverted list Proof of Concept [quest for search]
by Paul POULAIN 27 May '05

27 May '05

Hi, After some chat with Kados, I've spent some time to write a proof of concept for my inverted list idea. It's not perfect, but it works quite good. I've commited it in CVS a few minuts ago (misc/build_marc_Tword.pl and C4::SearchMarcTest.pm files) NPL should run it on their DB, that is really huge, and report how performances are. How it works : =============== * create the table marc_Tword with the following structure : CREATE TABLE `marc_Tword` ( `word` varchar(80) NOT NULL default '', `usedin` text NOT NULL, `tagsubfield` varchar(4) NOT NULL default '', PRIMARY KEY (`word`,`tagsubfield`) ) TYPE=MyISAM; * open a console & type export PERL5LIB & export KOHA_CONF as usual. * fill this table with misc/build_marc_Tword.pl. Warning, this script uses a very very consumming but very fast method to fill the table : it does everything in memory, then write everything. Another method is provided (& commented), but it's 100x times slower (really !) * open opac-search.pl and replace use C4::SearchMarc; by use C4::SearchMarcTest; as the API hasn't changed, it will work immediatly. * go to opac-search (advanced search) & search whatever you want. It Should work fine (except in "Any word" that is not implemented for instance) LIMITS : ========== * build_marc_Tword has problem with extended chars (accented ones mainly). So don't be afraid if you get sql errors. They are not a problem for a POC * search works always order by title, whatever you choose. * search works only search WORDA and WOARDB, not yet WORDA or WORDB or WORDA except WORDB. Due to structure, those search should cost exactly the same thing as others. you can test WORDA or WORDB very easily. in SearchMarcTest, at line 240, replace @result = keys %intersect; by @result = keys %union; Some infos on perfs/size : ============================ On my largest DB (1 900 000 lines in marc_subfield_table), the build_marc_Tword.pl script requires 60s for the 1st SQL read, then 120s for reading the whole table, then another 100s to write the table. It takes up to 350-400 MB of RAM, and at the end, the marc_Tword table is 245 000 lines, for 100MB of disk space. Note we could probably lower this number by checking better %ignore_list. Tests : ======== A search on a title word (socia*, with a *) that get 4500 results arrives in less than 2 seconds (mysql cache being empty). A search on another word (chan*) that get 590 results is the same time. A search on both words (socia* chan*) is 446 results and get the same duration. Doing the same test on a 2.2 install is VERY different : my SCSI hard disk does a lot of noise & the result for socia* chan* requires almost 20 seconds to appear. Testing with a OR (chan* OR socia*) get 4930 results, in probably less than 2 seconds. (Those results could probably be improved a little, as there are a lot of SQL queries to get item number & status & biblio subtitle.) Note that in the logs, you'll get something for every sql->execute (with the sql executed). You can see that most queries are not about the search itself, but about the item number & status. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

How we can input a very large field
by Andrés Tarallo 26 May '05

26 May '05

We are making some fixes into our production instalation. We noticed that the input field in cataloging only allows 255 characters and is an input field. We have currently resume fields that are much larger than that (about 3000 characters). We re trying to develop a way to make our templates aware of the fact that a field is large enough to be better input in a text field insted of an input field. We want to develop something more generic. An idea we have: having in the system preferences a list of fields that may contain large values. When we're about displaying an input field we should take into account the systems preferences. We will accept your fedback, we hope we can contribute this back to the CVS. Andres

4 6

Minutes of Website/Interface Design Meeting 2005-05-26
by Joshua Ferraro 26 May '05

26 May '05

Present at various times: NZ: rach, russ, irma GB: shaun and ben US: owen and kados ID: indradg 1/. koha.org Website a. Review of Russ's site map and ideas about _what_ koha.org is: 1. it's a place that appeals to those in libraries making decisions about library systems 2. it's a resource for developers b. we're going to put case studies up (DIY case studies like NPL as well as 'supported' case studies from software support providers: we'll have a framework for easily adding more case studies c. addressed tension between the koha.org site and the sites of companies who offer services around koha; we need to keep koha.org as vendor neutral as possible to attract more vendors d. "Showcase" section of koha.org will include links to 'official koha demos' as well as vendor demos (to showcase what vendor support can produce) e. We're going to have an official blog but for now we'll just aggrogate existing developer blogs from the homepage f. add links to presentations folks have done on Koha; as well as upcoming events where Koha will be showcased and links to arguments _for_ open source in libraries g. design process: rach and russ will rework the site map based on our meeting and will make some wireframes they will also. russ and shaun will get a 'content delivery schedule to divvy up the jobs. shaun will continue to work on his design. (Added later) Irma will proofread and do QA on the website. 2/. Koha Interfaces a. we will break up templates into 'programmer templates and 'official koha templates' b. programmer templates are just stripped-down templates for testing/demonstrating functionality c. 'official koha templates' are crafted using design principles: beauty, usability, standards compliance, accessibility (PDA, screen readers, etc.), color coordination, graphical appeal, etc. d. NPL templates will be used as design models, but default templates will be redesigned. e. there was some brief discussion of using kea for template design 3/. Roles a. rach and owen will be Interface Designers, rach will focus on design (graphically) and owen will do the coding; shaun and ben will work on an alternate set of templates and will contribute some improvements in wording, etc. b. LibLime can provide hosting for a staging server where the process can be observed c. Irma will do proofing and QA Complete log at: http://koha.org/cgi-bin/logs.pl?recall=recall&saved_query=Website%20Interfa… -- 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

3 2

mysql version
by Paul POULAIN 26 May '05

26 May '05

Hi Koha team, Henri Damien just commited a few minuts ago a code that executes perfectly for him. But not for me. The reason : it's an imbricated SQL query. mySQL 4.0 don't handle imbricated SQL queries, where 4.1 does without problem. So the question is : do we want to define a minimum for running Koha ? (knowing that, for example, mandriva default mySQL is 4.0 If we use a too recent version of Koha, then it will be harder to install) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

4 7

Bugsquashing Session
by Joshua Ferraro 26 May '05

26 May '05

Hi everyone, Let's squash some bugs! Here's the list of outstanding bugs in 2.2 and HEAD: http://tinyurl.com/7wslw I count 159 total: that's a lot of bugs! Since this is our first bug squashing event in quite a while I need some help scheduling it -- and future events. So first off, who wants to join us in squashing bugs? And when would be the best times for you? I'd like to make this a weekly event so lets find a time (or rotate the time) so as many of us can participate as possible. In case you're new to the bug reporting system in Koha it's here: http://bugs.koha.org If you'd like to get involved but aren't sure how let me know and I'll answer any questions you might have. -- 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 1

Website/Interface Design Focus Group
by Joshua Ferraro 26 May '05

26 May '05

Hi everyone, OK ... Let's get this ball rolling. As I mentioned in my last e-mail, the website/interface design focus group will focus on the overall user experience of Koha on the website, documentation, and interfaces. So: colors, logos, layout, standards compliance, usability, beauty, accessability, etc. Let's plan a meeting on #koha to discuss all the issues involved and to map out a plan of attack. How is 7PM GTM Thursday 27th on IRC? Here's the time in your area: http://tinyurl.com/dk29s Let's try to get a clear picture of what we're going to dicuss before the meeting so we can keep it brief -- what should be on the agenda? Let me know if the time isn't good for you and what time would be better. -- 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

4 10

Re: [Koha-bugs] Z39-50 client
by Paul POULAIN 26 May '05

26 May '05

Twily a écrit : > Hello, > > Koha was installed in a research laboratory - the LabSAD - at the > University of Grenoble, in order to create its library catalog. > > At first, the Z39-50 client was not working at all (tests with > versions 2.0.2 & 2.2.2), although the installing process was followed > step by step - PERL5LIB export, etc... > > After a long digging, a problem was discovered in this file : > /usr/local/koha/intranet/cgi-bin/z3950/search.pl > > Indeed, here is what is written line 60 : $random = rand(1000000000); > A float with 8 digits is included in the database, to identify the > Z39-50 request. > Later, only 4 digits remain. Since both numbers are not identical, the > request is stopped. > > After replacing all $random = rand(1000000000); > by $random = int(1000000000); , everything works perfectly. > > Thank you to change this in future versions of Koha, > > Caroline Naget and the LabSAD team Thanks for your report. I'll take care of it. What is your platform (Perl version & other important things). Because it works perfectly for me for all my customers, that are on various linux, aix or solaris systems. Note koha-bugs is usually only for automatic mailing from bugs.koha.org. So it would be better for another bugreport, either : * reporting it on bugs.koha.org * send a mail to koha-devel mailing list where developpers are speaking of dev problems. Last note : n'hésitez pas à vous déclarer sur www.koha.org/wiki, KohaUsers (login & mot de passe sont indiqués dans la fenêtre qui vous les demande. C'est une mesure anti pourissement). Et n'hésitez pas à vous abonner et vous présenter sur la liste infos (www.koha-fr.org >> Aller plus loin >> Support >> Support communautaire). Vous y trouverez d'autres grenoblois (Wesford) et d'autres labos du CNRS (math, histoire,...) utilisant Koha. A très bientôt dons ;-) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

frenchies & irc [POLL]
by Paul POULAIN 25 May '05

25 May '05

At day time here in france, we often are some frenchies. and only frenchies, so we speak french. According to you : 1- please open a #koha-fr channel to speak french only here. 2- continue speaking on #koha, in french. It's logged & someone from France will translate important things, so i've no problems with french language. 3- pls, speak only english, even when you are only frenchies. (pls don't answer 3 ;-) ) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

3 2