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

Information on arabic and Unicode on Koha
by Armelle Nedelec 09 Mar '06

09 Mar '06

Hello I've heard that a team is working on arabic in Koha. Do you know of it and would it be possible to contact (and help) them ? What's the current status of utf-8 and Koha ? Regards Armelle Nedelec Consultant

3 2

Koha 2.2.6 = version numbering + Roadmap
by Paul POULAIN 08 Mar '06

08 Mar '06

Hi, In rel_2_2, kados, hdl and other commited a lot of changes. There is still no changes in the DB, but I think we should call this version 2.4.0 This will reflect 2 importants things : * it has many new features (like amazon images, item creation on serial receipt...) * it may have new bugs. I talked with joshua about this, he agrees. ROADMAP : ========= I planned to release 2.2.6 at end of march. But now, I think we should decide when we freeze the rel_2_2. The question is : does someone have other new features to commit on rel_2_2 or can I declare "feature freeze" and we ONLY commit bugfixes ? -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org)

4 5

INEO, new Koha support in France
by Pierrick LE GALL 07 Mar '06

07 Mar '06

Hi Koha team, As some of you already know, INEO media system (France) wishes to support Koha development. They choose to support by adding a new developer to the team. This is why I've been hired for. I should work full time on Koha :-) I have no particular skills in Koha or librarian domain yet. What I know better is free software, Perl and MySQL (concerning Koha related stuff). I'm currently learning librarian domain and Koha. By now, I don't exactly know which features I will implement first. This will depend on first Koha based customers INEO will have and the opinion of the existing team. I'm 25 years old, I'm married, my son is 7 months old. More details about me on my website http://le-gall.net/pierrick (french only, sorry). I'm very enthusiastic working on such a project (team and software, I mean). Bye -- Pierrick LE GALL INEO media system

2 2

Meeting Minutes for March 6th, 2006
by Joshua Ferraro 06 Mar '06

06 Mar '06

Hi all, Here are the meeting minutes from today's meeting: Present: chris, hdl, pierrick, russ, thd, kados INTRODUCTION Welcomed Pierrick to the development team. Pierrick is the new full- time Koha developer who works for INEO. We're very happy to have him on board! PERL-ZOOM chris has the plugin for perl-zoom and 2.2.x working. Currently, searches and adding items and biblios works. he's going to continue working on: shell scripts for installing new search points (itemtype, series title, format, location, barcode, call #, publisher, published between dates) deletions of biblios and items edits of biblios and items bulkmarcimport.pl and rebuild_zebra.pl order by (title, author, etc.) returns (to update holdingbranch) AUTHORITIES kados previewed some improvements in authorities control display, specifically an OPAC auth search as well as a new way to display the 'summary'. This can be viewed on opac.liblime.com (do an auth search on 'Lewis' or 'Twain' for examples). KOHA NON-PROFIT We discussed the idea of creating a 'Koha Foundation'. We need to discuss on koha-devel what our goals would be for such an organization so we can clearly define its role. kados will start a thread on this topic asap. Cheers, -- Joshua Ferraro VENDOR SERVICES 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

1 0

New Feature: Zebra Plugin for rel_2_2
by Joshua Ferraro 06 Mar '06

06 Mar '06

Hi all, As discussed at our last meeting, Zebra/ZOOM-Perl will be available as a plugin for rel_2_2 as a 'drop-in replacement' for the current MARC-in-SQL design. Of course, you don't _need_ to use Zebra in rel_2_2, but it is available as an option. So ... how do you get it going? Here's a brief installation overview for those of you who'd like to start testing: PREPARE THE SERVER 1. Install Koha 2.2.5 2. Install the latest versions of Yaz, Zebra, and Net::Z3950::ZOOM 2. Create two CVS repositories on your server, one for HEAD and one for rel_2_2 3. Symlink the Koha 2.2.5 installation to the rel_2_2 CVS repo as outlined in the 'Updating Koha' document on kohadocs.org UPDATE YOUR DATABASE ALTER TABLE biblioitems ADD marcxml TEXT NOT NULL; ALTER TABLE itemtypes ADD imageurl char(200); ALTER TABLE biblio ADD frameworkcode VARCHAR( 4 ) NOT NULL AFTER biblionumber; CONFIGURE ZEBRA 1. cd /path/to/rel_2_2_cvs/koha 2. ln -s /path/to/rel_2_2_cvs/kohahris/koha-head/misc/zebra/usmarc/ zebra 3. edit koha.conf add: zebradb=localhost:2100/kohaplugin 4. Start Zebra: sudo zebraidx create kohaplugin sudo zebrasrv localhost:2100 SYNC THE PLUGIN FILES WITH HEAD The following files in your rel_2_2 Koha need to be replaced with HEAD versions: Modules: Biblio.pm Context.pm SearchMarc.pm Amazon.pm Review.pm Search.pm Intranet: addbiblio.pl additem.pl detail.pl MARCdetail.pl ISBNdetail.pl OPAC: opac-detail.pl opac-MARCdetail.pl opac-ISBDdetail.pl You need to edit the new files to change the path from 'cataloging' back to 'acqui.simple' (in 3.0 the path will change). At this point, you should be able to import fresh batches of records using the bulkmarcimport.pl script in HEAD. Searching and acquisitions should also work. Once you get it going, you can easily keep it up to date by keeping your HEAD cvs repo up to data and copying over the above files each time. Let me know if these instructions don't work for you or if you have any questions. Cheers, -- Joshua Ferraro VENDOR SERVICES 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

1 0

Barcodes Generator status
by Eric Bégin 04 Mar '06

04 Mar '06

1 0

New Feature: Improved MARC editor
by Joshua Ferraro 04 Mar '06

04 Mar '06

Hi all, Chris and I have been working on the MARC editor and have made considerable progress. I thought I'd just summarize some of the original bugs and the fixes we found as well as some gotchas to watch out for along the way. Bug #1 was that blank subfields were being saved. Bug #2 was that subfield order was hardcoded to always start with 'a' for repeatable tags (because it was hardcoded in the addfield routine). Bug #3 was that it was only possible to specify one set of indicators for each set of tags (ie, one for all the 650s). (because they were stored in a hash with the tag as the key). Bug #4 was that the underlying routines didn't support subfield reordering or subfield repeatability. So here's what we did: we replaced the use of the MARChtml2marc routine with a MARChtml2xml that reads in the form data and converts it to a MARC::File::XML object. It then passes that to MARC::Record via the new_from_xml() method. This works perfectly and fixes all of the above bugs. However, there is one gotcha. The MARC::File::XML new_from_xml() method converts UTF-8 data into MARC-8 by default for historical reasons. This means that entry of characters outside the normal ascii range in UTF-8 will come out as gibberish in MARC-8. Never fear, there is a solution. As soon as I noticed the problem, I requested that Mike Rylander (who has contributed greatly to this module) add the ability to specify 'no conversion' for that method and he promptly did so and committed it to the SourceForge CVS for MARC::File::XML. The caveat is that it will take a few days for me to update the CPAN version (which I _finally_ have write access to). I'll ping the list as soon as that's done. The bottom line is that to properly encode records YOU WILL HAVE TO UPDATE MARC::File::XML to the new version when you upgrade to 2.2.6. Now ... I'm off to add subfield repeatability and reordering to the interface. Cheers, -- Joshua Ferraro VENDOR SERVICES 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

1 1

new contrib in HEAD : holidays and news
by Paul POULAIN 03 Mar '06

03 Mar '06

Hello all, I've just commited a contrib from Tümer Garip (from Turkey) : (tümer : question for you at the end of the mail) * holiday : ============ in /tools/ the holiday.pl script let you define holidays (days where the library is closed), branch by branch. You can define 3 types of holidays : - single day : only this day is closed - repet weekly (like "sunday") : the day is holiday every week - repet yearly (like "July, 4") : this day is closed every year. You can also put exception : - sunday is holiday, but "2006 March, 5th" the library will be open The holidays are used for return date calculation : the return date is set to the next date where the library is open. A systempreference (useDaysMode) set ON (Calendar) or OFF (Normal) the calendar calculation. * news system : ============ in /tools/ the opac-news.pl let you create small news : - for OPAC. You must select in which language the news are shown. - for librarian interface : it does not depend on the language, as all librarians are supposed to speak the same language. Note that : - news appear in librarian interface in mainpage.pl - news don't appear anywhere in OPAC, as there are no PROG templates yet. It has to be done (copy/past from mainpage.pl should be simple) - news don't have an expiry date, the library must delete them manually. - there is no possibility to have news on a branch/borrower category basis either, that could be a nice (and easy) improvement Questions to Tümer : * i sometimes have problem to reach you directly with your mail. which mail is the correct one ? * NewsChannel.pm deals with a news_channels and news_channels_categories tables that I don't have. Do you confirm it's useless ? did I miss some feature ? * NewsChannels.pm also deals with a opac_electronic table. Same question and note. -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org)

1 0

Re: MARC Label in English
by Paul POULAIN 03 Mar '06

03 Mar '06

毛慶禎 a écrit : > Hi Mr. Poulain, Hello, > This is Anthony Mao writing from Department of Library and Information > Science, Fu Jen Catholic University, Taipei, Taiwan. 1st, please note it is better to ask mailing lists, to avoid 2 things : * having to wait 3 days because i'm off from my desktop computer and can't answer mails * letting me answering dozens (hundreds ?) of mails that many other people could answer. (I've seen you just asked on koha-devel for another question related to this one, it's a good idea !) > Before going further I was confused with Koha on > "MARC tag structure admin for default MARC framework". > > The label is in French only. Could I change it to English? During install, you have choosen "UNIMARC". UNIMARC tables are in french only, where MARC21 tables are in english only. To switch to MARC21 english, search marc_datas/marc21_en/structure_def.sql in you installation directory. in mysql, empty marc_tag_structure and marc_subfield_structure and loast the previous file to refill them. If you need authorities, you also can load : sql-datas/english/authorities_normal_marc21.sql HTH -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org)

2 1

question about MARC 995 Text
by 毛慶禎 03 Mar '06

03 Mar '06

Dear Poulain, This is Anthony Mao, associate professor of Department of Library and Informaiton Science, Fu-Jen Catholic University, Taipei, Taiwan. I have a question about Koha. MARC subfield structure admin for 995 (framework ) Second column Text is in French which is beyond my knowledge. Could I have English version from you? We installed Koha 2.2.5 http://koha.smoc.com.tw few weeks ago. -- Best regards 毛慶禎, Anthony Mao, mao at lins dot fju dot edu dot tw ICQ 30941847 Department of Library and Information Science http://www.lins.fju.edu.tw/mao/index.htm TEL +886 2 29052334, FAX +886 2 29017405 Fu-jen Catholic University, Taipei, Taiwan, R.O.C.

1 0