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

Koha Blog Aggregator
by Joshua M. Ferraro 15 Dec '06

15 Dec '06

So what's up with the Koha Blog Aggregator? It seems to be unmaintained. I think we should either link it to the places developers are blogging (or other feeds, etc.) or remove it from the home page. Here are a few active feeds (not all blogs) that might be worth adding: MJ Ray: http://mjr.towers.org.uk/blog/all.rss Katipo developers blog: feed://http//blog.katipo.co.nz/?feed=comments-rss2 My personal blog://http//kados.org/feed/ LibLime's news: http://liblime.com/news/RSS The developer wiki: http://wiki.koha.org/feed.php Anyone know of any other koha-related blogs/feeds? Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

4 4

About serials claim/late issues
by Henri-Damien LAURENT 13 Dec '06

13 Dec '06

Hi I have some questions about serials Module. It seems that some functions are broken in rel_3_0. For instance, when getting on claims page, looking at the logs, i see : Undefined subroutine &main::bookseller This function I guess is supposed to get a bookseller and (hopefully) retrieve the list of late or waiting issues. But this function exists nowhere in rel_3_0 Code. Would you have a Copy of the *.pm files you use ? I also saw claim form 1 2 3 4 in claims.pl code. And I wonder what those forms are linked to ? Where they are ? What they are likely to be ? How they get processed ? -- Henri-Damien LAURENT

2 1

koha 2.2.7 & koha rel2_2
by long_sam.tw 11 Dec '06

11 Dec '06

Hello,all After install koha 2.2.7,koha don't work well. you must modify koha-http.conf Add SetEnvIf Request_URI "\.pls" PERL5LIB"/usr/local/koha/intranet/modules" SetEnvIf Request_URI "\.pls" KOHA_CONF "/etc/koha.conf" to koha.conf,koha still have some functions don't work. my soultion,you can add use lib 'your path/modules';（place in front of use C4::modules.） to every koha perl script,use script help you do it. So, you don't modify koha-http.conf script：http://kohaa.blogspot.com/2006/12/test-note.html Longshan ___________________________________________________ 您的生活即時通－溝通、娛樂、生活、工作一次搞定！ http://messenger.yahoo.com.tw/

1 0

Problems with exchange rates
by José Parrella 11 Dec '06

11 Dec '06

Greetings, I'm trying to setup the exchange rates in a test Koha setup. The currency of my country, VEB, is at 2150 VEB per USD. So I'm setting up VEB with a rate of 1, and USD with a rate of 2150, but I always end up with 99.99999 VEB per USD. This is happening with Koha 2.2.7 in a Debian Sarge system. After peeking in currency.pl and C4::Acquisition, I changed the data type for the "currency" table with the following SQL statement: ALTER TABLE currency CHANGE rate rate float(9,5); I'm now able to use this value in the Acquisitions module. Is this the right way to achieve this? If so, are you planning on changing the default data type for the "rate" column in the next releases? Jose -- José M. Parrella -> Debian Sid, k2.6.17.13 Escuela de Ingenieria Electrica Universidad Central de Venezuela -> ucvlug.info

1 0

Subject heading translation in Z.3950 records
by José Parrella 10 Dec '06

10 Dec '06

Greetings, Is anyone working with heading translation in the Z3950 modules? I had an idea about translating MARC 650 fields from a Z3950 records, so the subject headings are "translated" when they are imported into Koha. As of now, I'm using Lingua::Translate to translate 650a records taken from LOC's Z3950 server from english to spanish. I would like to work on this feature if nobody's working on that, or if the new Z3950 features are not going to change that much in next releases. I've currently accomplished this through a last-minute access to the proper MARC::Field in the desired MARC::Record before it gets into the marc_breeding table. I'm yet to do several stuff, like trying to integrate this into the parameters system and providing other options, like Tie::'ing to a dictionary (definitely Babelfish translations aren't that accurate) Two brief questions: is z3950_results going to be used from now on? and, only 650a records are taken into account by Koha? Also, please let me know if there's something blatantly wrong in what I'm doing. Thank you very much for your time, Jose -- José M. Parrella -> Debian Sid, k2.6.17.13 Escuela de Ingenieria Electrica Universidad Central de Venezuela -> ucvlug.info

1 0

Subject heading translation in Z.3950 records
by José Parrella 10 Dec '06

10 Dec '06

Greetings, Is anyone working with heading translation in the Z3950 modules? I had an idea about translating MARC 650 fields from a Z3950 records, so the subject headings are "translated" when they are imported into Koha. As of now, I'm using Lingua::Translate to translate 650a records taken from LOC's Z3950 server from english to spanish. I would like to work on this feature if nobody's working on that, or if the new Z3950 features are not going to change that much in next releases. I've currently accomplished this through a last-minute access to the proper MARC::Field in the desired MARC::Record before it gets into the marc_breeding table. I'm yet to do several stuff, like trying to integrate this into the parameters system and providing other options, like Tie::'ing to a dictionary (definitely Babelfish translations aren't that accurate) Two brief questions: is z3950_results going to be used from now on? and, only 650a records are taken into account by Koha? Also, please let me know if there's something blatantly wrong in what I'm doing. Thank you very much for your time, Jose -- José M. Parrella -> Debian Sid, k2.6.17.13 Escuela de Ingenieria Electrica Universidad Central de Venezuela -> ucvlug.info

1 0

koha 2.2.7 & koha rel2_2
by long_sam.tw 10 Dec '06

10 Dec '06

Hello,all 目前 koha 2.2.7 程式碼需要修改才能正常 work. 如果要 work，可以順便用 merge cvs rel_2_2。你不需要修改 koha-http.conf SetEnvIf Request_URI "\.pls" PERL5LIB"/usr/local/koha/intranet/modules" SetEnvIf Request_URI "\.pls" KOHA_CONF "/etc/koha.conf" 直接用 sed 加入 use lib '/usr/local/koha/intranet/modules'; 可以參考 http://kohaa.blogspot.com/2006/12/test-note.html http://koha.wikispaces.com/kohadebug demo site http://lit184.lacc.fju.edu.tw 龍山 ___________________________________________________ 您的生活即時通－溝通、娛樂、生活、工作一次搞定！ http://messenger.yahoo.com.tw/

2 1

Re: [Koha] Koha ZOOM install
by Jama Poulsen 08 Dec '06

08 Dec '06

On Wed, Dec 06, 2006 at 09:30:43AM +0000, MJ Ray wrote: > Jama Poulsen <jama(a)debianlinux.net> wrote: > > Oke, I'm going to study the the rel_3_0 sources a bit to see if I could > > create something resembling a /koha package, after which I'd like to try > > and automate things if useful and possibble (eventough it may not be stable > > yet). > > Take a look at the Makefile.PL and perldoc ExtUtils::MakeMaker - I'm > not sure whether anyone has taken that forwards since my initial work. I'm now looking at working with the Makefile.PL setup within the rel_3.0 tree. Some first remarks: - I believe "DBD::MySQL" should be named "DBD::mysql" (see: http://cpan.uwinnipeg.ca/module/DBD::mysql) - Any idea how to turn off the (write) tests for DBD::mysql? Or do I have to enter my root password somehwhere in a file? This test requires a running server and write permissions. Please make sure your server is running and you have permissions, then retry. ... t/insertid...........DBI connect('test','',...) failed: Access denied for user: 'root@localhost' (Using password: NO) at t/insertid.t line 13 - Module requirements - Current modules: 'DBI' => 1, 'Date::Manip' => 1, 'DBD::mysql' => 1, 'HTML::Template::Pro' => 1, 'Digest::MD5' => 1, 'MARC::Record' => 2.0, 'MARC::Charset' => 0.95, 'MARC::File::XML' => 0.83, 'Mail::Sendmail' => 1, 'PDF::API2' => 1, 'Net::LDAP' => 1, 'XML::Simple' =>1, 'XML::LibXML' => 1.58 - Extra modules: - Event - Net::Z3950 - Net::YAZ - Class::Accessor - PDF::Reuse::Barcode - Data::Random - Net::Z3950::ZOOM - C4 (and C4::Context) - MARC::Crosswalk::DublinCore - Lingua::Stem - Any other modules I missed? - Should we not specify some modules as optional, but print a warning that some functionality will not be available in the frontend/backend? Eg for: Net::LDAP PDF::API2 PDF::Reuse::Barcode - Should we register the activated (but optional) functions for later use, like a kind of plugin system? - The "PL_FILES" option usage should not conflict with package distribution things I think, but still allow for a manual install. So maybe there needs to be some trimming there. I need to look more into this. - Would it be a good idea to research into using the "PPM_INSTALL_SCRIPT" option in the Makefile.PL to do other (non-perl module) detection and configuration work before the "make install" step? (Perhaps this has already been discussed on IRC or this list?) External package (detection / configuration) to deal with: - configure Apache / Apache2 - provide a standard includable example that fits with the standard koha setup. - How about a "/etc/koha" directory where we can put the "apache-koha.conf" and the "koha.xml"? - Let the user/distribution activate the config in apache itself. - yaz (versioning important) - zebra server (versioning important) - start/stop/etc. system - configuration - should we put the z3950-daemon-options (or simple call it zebra.conf) in /etc/koha for now? (Until there is some general server package availble.) - Setup the CGI environment (this - see next item. - Setup the non-executable web server documents - Any ideas what would be best to do here? - Perhaps let the user/distribution copy a pre-made set of documents to the web server location, and change the permission. - Anything else that should be done for good packaging? Jama Poulsen

2 3

zebraop commented [for joshua 1st]
by Paul POULAIN 06 Dec '06

06 Dec '06

Hi again, Joshua, you told me yesterday that the commenting of zebraop (*) in dev_week was not a bug, but due to a problem with _zconn in Koha (that looses the connection we don't know why) + it seems that updates are long on large databases. Thus, for adding/updating biblios/items, NPL uses update_items script, running once a day (and thus having a zebra DB uptodate only once a day, which can be considered as a shame, even if not blocking) SAN-OP will go live in january, 3rd, and will do large test (library closed to public, everybody working/testing koha) on dec, 14th, to I thought it could be a good idea to investigate the problem during those tests. Joshua told me that NPL uses zebra 1.x, and SAN-OP will use zebra 2.0, so maybe it could solve the problem. Here is my question : how do we know that the update/insert went wrong ? an internal server error ? an error in the log ? nothing, just being unable to find the added/modified biblio/item ? Did the problem occur once a week or once every hour ? did they notice it occurs more on heavy load or any particular situation ? I'll report here the result of SAN-OP tests. Hoping zebra 2.x will solve it. (*) zebraop is the sub that is called when a biblio/item is added/updated/modified. -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

4 3

popularity (in 3.0) [for joshua]
by Paul POULAIN 06 Dec '06

06 Dec '06

Hello all, (and mainly joshua) The popularity, in dev_week, is stored in items (952). That is wrong according to me, because, if a book we have 4 items is issued 20+19+31+38=98 times, it's much more popular than a book issued 45+0+0+0 times That's why I propose to move the popularity field to a biblio area. The popularity field is indexed in zebra through update_items.pl script. I suggest using a non standard MARC field for this. For UNIMARC, I think 2xx area (descriptive informations) could be a good candidate. I choose (randomly) 349$a to store it. It will contain summ(items.issues) where biblionumber=xx I modify update_items & zebra config files accordingly, let me know if you are OK with this suggestion + let me know what to use in MARC21. -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

2 1