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

koha and ruby
by Simon Mitchell 18 Nov '06

18 Nov '06

Hi, is there a Ruby or Ruby on rails version of Koha or is one planed? I did notice that on katipo blog that there something about ruby and zebra installation. http://blog.katipo.co.nz/?cat=8 Thanks. Simon

2 1

BIG code cleaning commits
by Paul POULAIN 17 Nov '06

17 Nov '06

Hello, As you know, i have decided to fund code cleaning by hiring antoine to work on this, and i've put my hands in the code cleaning myself : * i've removed some useless subs in biblio.pm. There are probably some more to clean. It should be harmless in Koha, even if some script in misc/ won't work anymore : however, those subs must be removed, because they use marc_subfield_table table, that disappeared with zebra. So, if you meet compilation errors, don't reintroduce those subs, do it differently ! There are probably some subs still to remove, i'm not sure it's 100% done. * i've modified all scripts & templates to use biblionumber / $biblionumber only, not sometimes bib, sometimes bibid, sometimes biblio. I tried to do this carefully, but there are probably some mistakes, so fix them when you encounter them. the goal being to have a unified API to avoid trivial bugs like calling request.pl?bib=X and detail.pl?biblionumber=X and opac-detail?bibid=X. Just use biblionumber=X everywhere, and it should be OK !!! Now, i'll start moving bornum to borrowernumber to unify API for borrowers as well !!! cheers. -- 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

1 1

About HTML::Template::Pro
by Antoine Farnault 17 Nov '06

17 Nov '06

Hi koha-devel, I don't know if you 've noticed this great feature embedded in HTML::Template::Pro. HTML::Template::Pro is written from HTML::Template AND HTML::Template::Expr ( http://search.cpan.org/~samtregar/HTML-Template-Expr-0.07/Expr.pm ). So all the features from HTML::TEMPLATE::Expr are enabled for us. Briefly, this module allows expressions in the template syntax. Expressions includes comparisons, math operations, string operations and others... Enjoy ! -- Antoine Farnault

2 1

[KOHA] Searching catalog record for Arabic, Chinese character
by fclick＠streamyx.com 14 Nov '06

14 Nov '06

Greetings, I am currently playing around with KOHA v2.2.6. I tried to insert a record in catalog using arabic title as well as inserting a new member which name is using arabic. when i try to search for patron using the arabic name it successfully found the patron. However when i try to search a catalog record using arabic title (where i type arabic in the searc field) it cannot find the record. so i need to search using isbn number or other non arabic data in the record to get the record. Displaying of arabic is fine. Just i cant search. Is there any trick for this? Cause for patron searching is working but not for catalog record. Thanks Regards, Kow Ming Foong

1 0

New Feature: Improved Z39.50 Client
by Joshua Ferraro 06 Nov '06

06 Nov '06

Hi all, Tumer Garip has back-ported his improvements to the Z39.50 client to dev_week and I have backported them to rel_2_2. Please update your systems, test it out, and if everyone agrees and everything seems to be working as you expect, I propose to release 2.2.7 with the bugfixes applied since 2.2.6 as well as the MAJOR improvement to the Z39.50 client. 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

7 10

record.abs and melm declaration order.
by Henri-Damien LAURENT 31 Oct '06

31 Oct '06

Hi it seems that data indexed in record.abs depends on the order of declaration. Take for instance : melm 600 Subject-heading melm 600$a main-subject and melm 600$a main-subject melm 600 Subject-heading On the one hand, you will NOT be able to query for main-subject But on the other hand, declaring 600$a BEFORE tag 600, you will get data from 600$a when querying on main-subject. I have not read this on documentation. And this seems quite useful to know. Moreover, if you declare melm 600$a main-subject melm 600$a other-identifier the second declaration will be ignored. Hopes that helps. -- Henri-Damien LAURENT

2 1

CGI.pm
by Wojciech Zatorski 29 Oct '06

29 Oct '06

Hello Koha-devel, I have found bugs/feature in module CGI.pm. script: /cgi-bin/koha/acqui.simple/additem.pl Alert about exists of itemcallnumber and options have doubled/tripled selected options! <select name="field_value" tabindex="1" size="1" style="font-family: Courier;"> <option selected="selected" value=""></option> <option value="G">Biblioteka Filologii Germańskiej</option> <option value="P">Biblioteka Filologii Polskiej i Słowiańskiej</option> <option value="CIDE">Biblioteka Główna - CIDE</option> <option value="ODSK">Biblioteka Główna Oddz. ds Komputeryzacji</option> <option value="ZS">Biblioteka Główna Zbiory Specjalne</option> <option value="H">Biblioteka Humanistyczna</option> <option selected="selected" value="WF">Biblioteka Instytutu Wychowania Fizycznego</option> <option value="A">Biblioteka Języków Obcych</option> <option value="PD">Biblioteka Pedagogiki i Psychologii</option> <option value="N">Biblioteka Wydz. Matematyczno-Fizycznego</option> <option value="BL">Biblioteka Wydz. Nauk Przyrodniczych</option> <option value="SA">Biblioteka Wydz. Prawa i Administracji</option> <option value="THEO">Biblioteka Wydz. Teologicznego</option> <option value="E">Czytelnia Biblioteki Ekonomicznej</option> <option value="Z">Czytelnia Biblioteki Głównej</option> <option value="T">Czytelnia Biblioteki Wydz.Zarządzania i Ekonomiki Usług</option> <option value="GRO">Gromadzenie i Uzupełnianie Zbiorów</option> <option value="INF">Oddział Informacji Naukowej BG </option> <option selected="selected" value="OPR">Opracowanie Zbiorów</option> <option value="TM">Wypożyczalnia Bibl.Wydz.Zarządzania i Ekonomiki Usług</option> <option value="S">Wypożyczalnia Biblioteki Ekonomicznej</option> <option value="W">Wypożyczalnia Biblioteki Głównej </option> <option value="WM">Wypożyczalnia Biblioteki Głównej Podręczniki</option> </select> sub previous_or_default { my($self,$name,$defaults,$override) = @_; my(%selected); ############################bug? if (!$override && ($self->{'.fieldnames'}->{$name} || defined($self->param($name)) ) ) { grep($selected{$_}++,$self->param($name)); #############################bug? } elsif (defined($defaults) && ref($defaults) && (ref($defaults) eq 'ARRAY')) { grep($selected{$_}++,@{$defaults}); } else { $selected{$defaults}++ if defined($defaults); } return %selected; } END_OF_FUNC -- <wojciech(a)zatorski.net> tel. +48 509-855-239; GG: 1500861; Skype: zatorski http://www.Zatorski.Net -- Omnia mea mecum porto.

1 0

Koha translation Problem
by Pedro Faria 27 Oct '06

27 Oct '06

Dear all, I am using koha 2.2.6 and I am trying to translate it to portuguese. The OPAC interface is already translated, but now when executing tmpl_process3.pl like it is said in http://www.kohadocs.org/usersguide/apb.html (and worked for opac) I get: ... ... Making directory ../../../../templates_devel/intranet/pt/catalogue...Creating ../../../../templates_devel/intranet/pt/catalogue/detail.tmpl... Creating ../../../../templates_devel/intranet/pt/catalogue/subject.tmpl... Creating ../../../../templates_devel/intranet/pt/catalogue/searchresults.tmpl... Creating ../../../../templates_devel/intranet/pt/catalogue/detail- opac.tmpl... <b>Copyright:</b> : Completely confused parametrizing Any Help? -- Pedro Faria

1 0

New Search (rel_3_0) in question
by Henri-Damien LAURENT 18 Oct '06

18 Oct '06

Hi, I am trying to get things together for rel_3_0 with synching dev on devweek. It appears that the page search.pl (the advanced search) makes heavy use of hardcoded elements which perfectly fit USMARC but are useless for UNIMARC. Moreover, it relies on coded fields which are supposed to be mandatory, but most of the time, our custommers will overlook them and not fill them in. So this raises some problems to us. First, Up 'till now, itemtypes for instance were user defined. But with using such search, there would be some kind of "itemtypes" (see Material-type or Litterature-Code or target-Audience) that would be prompted by the system and users should change a little their way to use the software, if I don't mind. Second, lists should be marcflavour dependant or at least should be processed in the Template and not in the code. What could be proposed is to get all these things into Templates through a loop that would parse some authorised_values. For instance, Material-Type would be in category MTTY and would contain : d = large print e = newspaper format f = Braille or Moon script g = microprint h = hand-written i = multimedia (e.g. an item in regular print with a microfiche supplement) j = mini-print r = regular print z = other form of textual material for unimarc... and for usmarc # - None of the following a - Microfilm b - Microfiche c - Microopaque d - Large print f - Braille r - Regular print reproduction Eye-readable print. s - Electronic | - No attempt to code (But I found ta, tb, fk in our code stored in 07/0-1) A diffculty would be that where USMARC uses only one field (007), UNIMARC uses multiple ones 110, for serials, 126 for sound recordings, 115 for motion pictures, 130 for Microforms, each one having its own list of material type. What I am trying to say here is that it seems to me that - I have on the long-term to study both norms to try and make things together BUT - that our customers surely donot need such a tough norm abidance but they require that looking for a user-defined itemtype they can find it. This I will try and code. NEVERTHELESS, along with it and preparing the long-term developement, we think it may be useful to propose strict abidance to norms. But this should be done carefully and not with too much hardcoded lists but should be either in templates or in database so that users could invoke this or that part of base and it fills templates with right values. And we should settle which categories would be searchable and which should be in database. THEREFORE, I try and share some thoughts about that.

1 0

Koha 2.2.6 is available...
by Paul POULAIN 17 Oct '06

17 Oct '06

We worked hard, but, finally, it's here !!! Koha 2.2.6 has been released & is available at : http://download.savannah.nongnu.org/releases/koha/koha-2.2.6.tar.gz IMPORTANT : a package (not announced) was at this address, named "koha-2.2.6" was here since some days (2 weeks ?) this packages contained some bugs that were discovered just before announcing the release. So, if you had downloaded & installed this "2.2.6", you MUST reinstall, as it's not the same version. Here are the release notes : RELEASE NOTES ============= Koha is the first Open-Source Integrated Library System. Koha is a full-featured open-source ILS. Developed initially in New Zealand by Katipo Communications Ltd and first deployed in January of 2000 for Horowhenua Library Trust, it is currently maintained by a team of software providers and library technology staff from around the globe. Koha 2.2.6 is more than 250,000 lines of code (see : http://bureau.paulpoulain.com/cvslog/) , contributed by about 50 different developers (46, +translators). The 2.2.6 version of Koha is a mature product, with a lot of nice features. More than 100 libraries are registered as users on wiki.koha.org, and we are sure that at least 300 libraries use the software. There are 2 projects derived from Koha. ======== WARNINGS ======== * The librarian interface is tested only with Mozilla/Firefox. Should work (partially) with IE. OPAC should work fine with any browser. * In this release, french, english &ukrainian are up to date. Other language po files are provided in the package. If you update/complete one of them, please send it to paul @ koha-fr.org, it will be included in a 2.2.6b release ! * NEW PACKAGES REQUIRED : - Class::Accessor (0.25) - XML::SAX (0.14) - MARC::File::XML (0.83), - MARC::Charset (0.95), - LWP::Simple - XML::Simple - GD::Barcode - Data::Random - ZOOM They will be checked during upgrade process. * during install, you may get some warnings during package dependency checkings. Something like : "Too late to run INIT block at /usr/local/lib/perl/5.8.4/ZOOM.pm line 37." or "Subroutine PDF::API2::Resource::Font::Postscript::O_RDONLY redefined at /usr/share/perl/5.8/Exporter.pm line 65." You can ignore them. KNOWN BUGS ********** Critical/blocking : * mySQL5.0 : Koha is NOT compatible with mySQL 5.0 We plan to add 5.0 compatibility in Koha 3. If you want to give a try to 2.2.6 with mySQL5, you can have a look at http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1089, but it's untested & unofficial. * child card craziness, see http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1117 for details * Update child looses guarantor and address., see http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1065 for details * don't use spaces in currencies codes. Use USD, not US DOLLAR, for example. spaces breaks acquisition module. see bugs.koha.org for more information. Please report any problem in bugs.koha.org Apple users : it seems there is an annoying bug in Firefox, that you can have in librarian biblio search: only the first MARC field list is available and the others can't be opened. The problem is described and fixed at http://www.macfixit.com/article.php?story=20051226091140372 ======= CHANGES ======= Changes 2.2.5 => 2.2.6 ********************** DB CHANGES ********** DB structure : dewey field has been moved to a char(30) DB content : many many new systempreferences Koha opac stylesheets : none, but the opac css stylesheet has been redesigned even if it contains no new classes. ******** BUGFIXES ******** === ACQUISITION === * Acquisition has been deeply investigated & tested. should work fine. (there was complex problems depending on prices rebates, VAT charging,...) === CATALOGUE === * Major bugfixes in encoding handling for MARC21 : there was bugs using the MARC21 indicators for character encoding. They should have been fixed for now, and koha 2.2.6 handles MARC21 with unicode correctly. === CATALOGUING === * result page display was incorrect when searching a biblio before adding a new one. * no more saving of an empty field in the DB * Fix for splitting up fixed fields containing | in them causing incorrect storage of fixed fields in Koha DB. * An item that is on loan can't be deleted anymore. === CIRCULATION === * minor bugfix : Adding 0 before days and months in order to make date comparison work. === MEMBERS === * fixed a but to be able to modify an Institution. === PARAMETERS === * adding page facility in book funds. ************ IMPROVEMENTS ************ Almost nothing has changed in the DB & this version has been heavily tested, so the stability should be good. But you are warned that some/few bugs may occur. Please READ the release notes. Everything is compatible with previous versions, so, if you just install Koha, you should have the same behaviour as previously, but you will miss many interesting features! === ACQUISITION === * added a (crontab) script : check_suggestion.pl, that send a mail to the librarian when a suggestion is pending. * *MAJOR IMPROVEMENT* : - online help has been added - the order.pl page doesn't show baskets closed for more than 6 months anymore. - when recieving an order, you now see the list of existing parcels. The parcel code used to be the "Supplier invoice information". Now when you go to the reciept page, you see all previous recieves, and can create a new parcel, exactly as before. This does not require any change in Koha internals, but we hope it's clearer than before. - when recieving an order in a parcel, you now see all orders still waiting for a receipt. Thus, you can enter isbn/title as previously, or directly click on a title in the list. We worked hard on those new acquisition screens, and hope that you'll find it easier to use than before. === AUTHORITIES === * if the library doesn't define a summary for an authority, a standard/default one will be built automatically. * if the librarian set * as subfield, all subfields will be shown, without any separator, but respecting the order. Previously, you had to define every subfield, causing problems in case of reordered subfields. === CIRCULATION === * added a (crontab) script : overduenoticesSelect.pl, that can be used as replacement for the overduenotice script. This one has many more parameters, including a filter on branches and an external letter (to avoid the need to modify the script on each release) * merged today & previous issues list during issuing. Added a button to renew issues & return issues in 1 click === CATALOGUE === * highly improved MARC21 default framework * new systempref "sortbynonfiling". If you catalogue with complete MARC (including indicators), you can set this pref to Yes. It will remove non filing chars and order "The King Henry IV" to letter "K". This systempref is USELESS for UNIMARC (as UNIMARC doesn't manage non-filing chars in an indicator, unlike MARC21) === CATALOGUING === * added a (crontab) script : delete_authority.pl, that deletes all entries of an authority in a biblio. * *MAJOR IMPROVEMENT* in MARC editing : - duplicating a field (+ on the tag) will show a number of creation to do. Thus, you can quickly create 6 subjects lines (for example) - duplicating a subfield is no longer done with a pipe (|), but by clicking on the + facing the subfield - the "hidden" property of the framework now has 19 possible values. Look in the online help to see them. The immediate interesting value is -1, which means the subfield is minimized on the MARC editor and you must click on it to expand it. Rarely used fields/subfields are easier to manage. - a advancedMARCeditor systempref has been added. If set, tag/subfield values are not shown, except when putting the mouse on the tag/subfield. This systempref is only for "MARC addicts"! * MARC21 : many plugins have been added (by LibLime). It seems you now have as many plugins for fixed length fields in MARC21 as in UNIMARC! Note that plugins help you filling a tag/subfield in the MARC editor. === MEMBERS === * patron images management. A new systempreference has been added (patronimages, in borrowers section). If set (to an image extension, like jpg or gif), the image will be shown on patron detail or circulation page. The images must be stored in KOHADIR/htdocs/intranet-tmpl/patronimages/ . The image must be named <borrowernumber>.<patronimagessystempref> (1.jpg for example, for borrower #1) === OPAC === Many preferences have been added to OPAC. Read them carefully, as you will be able to modify highly the look and behaviour of your OPAC! * new default stylesheet for css (purple on white). A new stylesheet (contributed by liblime.com) has been added to show everybody the changes in OPAC. If you want to stay with the old one (dark/light green), just reach Koha >> Parameters >> Systempreferences >> OPAC >> opacstylesheet > modify > /opac-tmpl/default/opac_old.css * Amazon content : if the new AmazonContent systempref is set AND an AmazonDevKey/AmazoneDevTag (available on www.amazon.com) is entered in systempreferences AND XML::Simple package is installed, OPAC will show amazon cover pages when available. Note that this feature may not be legal everywhere. For example, it seems it may not be legal in France (you must ask each editor for permission) * new systempref : opaccredit. If something (including html) is stored there, the footer of OPAC pages will contain what is there (instead of the "Library powered by Koha..." that is on css default templates) * new systempref : opacnav. In this preference, you can put any html that will be added to your menu. For example, to add a button to reach the koha website : <a class="menu" href="http://www.koha.org" title="Koha world website">Koha</a> * new systempref : opacbookbag : if set to 0, the basket/book bag features will be hidden in OPAC (even for logged in users). * authorities heading search : a new menu has been added so the user can search in authorities (same behaviour as in intranet) * new systempref : opaclanguagesdisplay. If set to "yes" (default value), the list of available language is shown. Otherwise, there is no list, koha will stay in default language only. * new systempref : opacreadinghistory. If set to "yes" (default value), the reading history will be available on OPAC (for logged in users). If set to "no", the reading history never appears. * Recent Acquisition : added a new page to filter recent acquisitions on a given branch. * if you use npl templates, you can have an alternate stylesheet (to set it, go to librarian interface >> Parameters > Systempreferences > OPAC > opacstylesheet > modify > /opac-tmpl/npl/en/includes/opac.liblime.css) * when there is more than 1 item at a given location (branch/callnumber/location), the list shows the number of items, not 1 line for each (same) value. === REPORTS === * Inventory : you can now scan in a text file, on an unconnected laptop, with every book in your library. Then, just upload the file in Koha. It will "mark as seen" all books. Once you've scanned everything in your library, just query for all books not seen since the beginning of the inventory, and you'll get "lost" books. === SERIALS === * MAJOR IMPROVEMENT : Adding item creation on the fly when receiving serial : if you activate systempref > Catalogue > serialsadditems, you'll have a form to create an item on the fly at the end of the serial receipt form. The item contains the callnumber, the branch, the barcode and the location (where applicable). Go to the catalogue after setting a serial to "arrived", and you should see the item created. If you let serialsadditems to OFF, behaviour is unchanged from previous releases. * the last 5 arrived serials are shown when receiving serials. === SYSTEM PREFERENCES === === ALL == * Unimarc datas in english are provided * Unimarc datas in ukrainian are provided -- 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