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

New features commited in rel_3_0
by Paul POULAIN 27 Nov '06

27 Nov '06

Hello, a mail about new features added in CVS by us recently : In serials management : hdl did a lot of things : - he has updated serials management to have official scripts using the alt_ written by katipo : the previous "official" have been removed. - he added new screens to update serials status all at once : the list of waited/late serials is shown, the librarian can choose the one he want, and can update all of them in just 1 screen) - he improved a lot the SerialsAddItem : this feature let the library create an item on the fly when recieving a serial. now, the item form is exactly the same as in additems.pl, there is a lot of javascript (very web 2.0 ;-) ) - he added the branchname to the subscription description : this way, the librarian & the user can see the branch where the subscription is stored. This feature can still be a little bit improved I think In permissions, Antoine : - cleaned all permissions, by removing some (few) of them & cleaning all scripts to be sure they use the correct permission. - added "EditAuthorities", "Serials" and "Reports".They do what they are supposed to do ;-) In virtual shelves, I added a timestamp, to know the date/time where a book whas added in the shelf. It will then be easy to create a RSS feed for virtual shelves. In Suggestions : Antoine added a feature to select a reason why the suggestion has been accepted or rejected. The reason list is defined in Authorised values "suggest". In Tools, Antoine has added a script (tools/clean_borrowers.pl) that let the library : - remove all borrowers that did not issue anything since X days - anonymize all issues that have been returned more than Y days ago. X and Y being defined by the librarian before executing the script. In OPAC, i'll commit soon (it's written), a new script for the patron, that will show the X most issued items of a given itemtype (or all) for a given branch (or all), for materials acquired in the last 3/6/12/9999 months. Test & enjoy ;-) -- 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 0

koha 2.2.7 is available for download
by Paul POULAIN 23 Nov '06

23 Nov '06

Koha 2.2.7 has been released & is available at : http://download.savannah.nongnu.org/releases/koha/koha-2.2.7.tar.gz 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.7 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.7 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. * 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.7 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.6 => 2.2.7 ********************** - NEW z3950 client (for quick cataloguing) : it's based on ZOOM, and DOES NOT REQUIRE a daemon on the server. It has 2 majors consequences : it should work well on MS-windows servers platforms and it's much easier to install : just install Koha, and you have it. Another improvement is that you can select the servers you want to query. And, last but not least, it should be a little bit faster for single server searches. - some packages dependancy during install where missing - biblios without any title will show "no title" as title, in the result list, making them clickables - for libraries with IndependantBranche=YES, the biblio can be deleted only if it has no items attached or the librarian is a superlibrarian. This prevent a librarian from deleting a biblio with existing items in another branch. -- 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 0

what does everyone use to indent/beautify their TMPL files?
by Mason James 21 Nov '06

21 Nov '06

hiya Everyone, ive been thinking (for a while) about a way to standardize the way we format/indent *.tmpl files in koha because... some of the *.tmpl files i create look awful, and they are just too complex for me to work out a consistant way of formatting them. ive been playing a little with 'tidy' recently (http://tidy.sourceforge.net/) and ive got 'tidy' to parse and indent a tmpl file without too much moaning, using a config .rc file like this... $ cat .tidyrc new-blocklevel-tags: tmpl_loop tmpl_if tmpl_else tmpl_unless new-inline-tags: tmpl_var tmpl_include indent: auto indent-spaces: 1 vertical-space: n wrap: 0 then, run tidy like so... $ tidy -c .tidyrc test.tmpl -- so, the question is...... - what tools does everyone use for their own *.tmpl indenting/formatting/beautifying? - are there better ones than 'tidy'? - is it a good idea for us to find a tool that formats our tmpl files in a standard way? any ideas folks? cheers, Mason. -- Mason James Katipo Communications www.katipo.co.nz +64 4 934 1285

5 4

The future of the prog templates
by Owen Leonard 21 Nov '06

21 Nov '06

Joshua and I have been discussing the future of the prog templates, and we'd like to get some input from the group. The prog templates were originally intended as minimal templates with only structural markup with no style information. They would be used only by programmers when develeloping new features. Because the templates would be minimal, it would be easier for designers of alternate templates to diff changes and incorporate them into their own templates. Now that 3.0 is starting to be used in production environments it's time to ask, are the prog templates still serving that purpose, or are they becoming the defacto default template? The issue is important to me because I believe that in order to provide the right amount of flexibility and detail for good design and usability the templates would have to be expanded: additional markup would have to be added to create the possiblity of one, two, and three-column designs, for instance. Divs would be added for the purpose of controlling layout--divs which have no semantic meaning. This kind of change is at odds with the original intention of the prog templates. If it is agreed that the prog templates should be expanded to allow more flexibility for more complex styling, some discussion would have to follow about the kind of layout scheme we should use. The system I chose for NPL's dev_week opac, for instance, is based on this one: http://www.positioniseverything.net/articles/onetruelayout/appendix/holygra… It has worked well for us, but includes some extra markup, as I said. If others have a tried-and-true layout that uses less extraneous markup please chime in. What does everyone think? Thanks, Owen -- Web Developer Nelsonville Public Library http://www.athenscounty.lib.oh.us

5 5

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