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

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

re searching databases
by COURYHOUSE＠aol.com 14 Jan '04

14 Jan '04

Pate - Steve et al. here is the link i mentioned http://69.94.4.132/perlarchive.com/guide/Searching/Databases/index.shtml

1 0

Perl / regexp question
by paul POULAIN 13 Jan '04

13 Jan '04

Hi, In the translator tool, we have a little problem. 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)/$1$subst$2/g; gives : <a href="/koha/chercher.pl">chercher</a> dans la bibliothèque. that is WRONG !!! (search.pl must not be replaced !) & I couldn't find the regexp that could work better. I tried to use HTML::Tree, HTML::TreeBuilder, but without success : it doesn't enjoy HTML::Template syntaxt & create bad HTML :-( I also tried to play with HTML::Parser, but without success neither. For instance, the workaround is NOT to replace strings translated by IGNORE, but that's really a poor way to do it, as some things are no more translated. 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... -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

biblioitems.place & item location (Call Number ?)
by paul POULAIN 12 Jan '04

12 Jan '04

Hi, I try to figure what biblioitems.place field is done for & I can't find. I also try to find where is the "location" (Call Number ?) of a given item is hidden in items table & i can't find neither. It may be stored in biblioitems (biblioitems.classification) table, but it's a poor choice imho, as 2 differents items can be located in 2 differents places. So I think we lack a field in items table. If you confirm we do, i'll rename "bulk" field to CN & modify OPAC accordingly. Other way to say this : I think Koha works fine if location is found with dewey or another classification number, but NOT when you have a library with a "strange" location method (like the one i'm working on at the moment...) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Re: Koha translation
by paul POULAIN 12 Jan '04

12 Jan '04

Desarrollo Koha a écrit : > >>> DO NOT translate manually the spanish templates, that are outdated >>> you're right. >>> But look in misc/translator directory, file translator_doc.txt >>> >>> ¿where ?. I have downloaded the koha-2.0.0RC1.tgz file from >>> sourceforge and i can not find the file you are talking about. >> >> It is NOT in 2.0.0RC1, only in CVS. >> if you don't want to play with CVS, i can send you the 4 interesting >> files. Ask me. > > > Ok, I have found that in CVS, but it seems to have problems in order > to translate to spanish. > > Some of the strings (with more than one word) are ignored (the > "Advanced Search (More Options)" for instance). > > I don't know how to solve that. And I don't think the english > expressions can be easily translated (with the embeded variables). > I will be working in the translations :-):-) (with the automated > translator while possible) I think the problem is only on strings where there is a regexp special char, like ()$^... I've fixed this in CVS/rel2_2_0. Tell me if it's better now. PS : pls post in koha-devel/koha-translate. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Re: [Koha] Kohas Z39.50 Server - re UNIMARC
by baljkas＠mb.sympatico.ca 12 Jan '04

12 Jan '04

Friday, January 9, 2004 18:20 CST Hi, Joshua. et al. Just a quick reply re your parenthetic point for Paul, to wit, >(BTW, Paul, you said to remind you to commit this change to CVS; I'm > not sure but I wouldn't be surprised if UNIMARC's leaders were a bit > different, so maybe we should hold off on that [snip]) my reading of the UNIMARC standards (cf. URL <http://www.ifla.org/VI/3/p1996-1/concise.htm>) indicates that the Leader and Directory have the same structure as MARC21 (and for that matter, USMARC and CANMARC). Just FYI. Cheers, Steven F. Baljkas library tech at large Koha neophyte Winnipeg, MB, Canada

3 2

Koha's Z39.50 Server
by Joshua Ferraro 09 Jan '04

09 Jan '04

Hiya, I've just committed a _basic_ Z3950 Server to CVS (in the HEAD Branch; in the z3950/server/ directory) and I wanted to make a few comments about it. (BTW: is everyone ok with moving the files in z3950 to z3950/client/ ?) First of all, the it's built using Indexdata's SimpleServer perl module Version 0.07, so if you want to use it you will have to install SimpleServer which you can get from: http://ftp.indexdata.dk/pub/simpleserver/ (BTW: whoever is doing the Koha installation script and documentation on dependencies may want to add SimpleServer). Secondly, you will need to change the leader information in Koha's MARCgetbiblio subroutine in Biblio.pm to reflect the following (or if you know how to manipulate the leader you can change it to reflect your data; this example leader should be functional for all MARC21 data). Look for the following near line 700: #---- TODO : the leader is missing $record->leader(' '); and change it to: #---- TODO : the leader is partly fixed for MARC21 $record->leader(' nac 22 1u 4500'); (BTW, Paul, you said to remind you to commit this change to CVS; I'm not sure but I wouldn't be surprised if UNIMARC's leaders were a bit different, so maybe we should hold off on that; also, I've also got some other leader qualms but they will have to wait for another email) So the actual server is implemented in a single Perl script for now (I plan to break it up for the next version) and you can get it from CVS or from my website at: http://kados.org/LibraryScience/zed-koha-server.pl (it's there for the folks who don't use CVS) You may need to change the permissions on the script--as root run: [jmf@koha]koha#chmod 755 zed-koha-server.pl Run the zed-koha-server.pl script as root: [jmf(a)koha]#./zed-koha-server.pl The server will take care of managing the network connections for you (it runs on port 9999), and it will spawn a new process whenever a new connection is received. The script implements a search handler and a fetch handler which allows Z3950 clients to query and retrieve records in MARC21 (the only record format it supports so far). It's set up to log to the terminal so you will need to keep the terminal running or the script will stop (I think it's the same with Koha's Z3950-Client; some day it would be nice to log to a file and run it as a service...). Let me say a word about holdings data. Right now, for historical reasons, most MARC21 installations of Koha probably use the 852 tag to store holdings data (actually I'm not sure there are any other MARC21 installations of Koha besides Nelsonville :-) ). For example, Nelsonville Public Library uses the following: 852a Organization code 852b Home branch 852h Classification 852p Barcode However, many Z3590 clients aren't set up to pull holdings data from the 852x fields but from the 952x/942x fields. So for now I've hard-coded the server to automatically duplicate the data like this: ## Convert from 852/4 to 952: ## 942a --> 852a Organization code ## 952b --> 852b Home branch ## 942k --> 852h Classification ## 952p --> 852p Barcode So the MARC record has the data in both places. If you're fluent in Perl and you look through the documentation for SimpleServer you will see that I have implemented query-parsing using a series of very clumsy substitutions. Right now I'm working on rewriting the search_handler to use the RPN member which will allow for much cleaner parsing of the query and will make it much easier to implement new features like Boolean. But the clumsy version should work fine in most cases--Nelsonville Public Library System has been using it for about two months to interface with the statewide resource sharing program MORE with no problems. I think that's it. Let me know how it works out or if you have any questions. -- Joshua Ferraro

1 0