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

rss
by hadi kress 07 May '07

07 May '07

dear koha developers, why don't u add rss to the database? hadi http://www.khayma.com/librarians --------------------------------- Ahhh...imagining that irresistible "new car" smell? Check outnew cars at Yahoo! Autos.

4 5

Koha 2.2.9 has been released
by Paul POULAIN 07 May '07

07 May '07

http://download.savannah.nongnu.org/releases/koha/koha-2.2.9.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.9 is more than 250,000 lines of code (see : http://bureau.paulpoulain.com/cvslog/) , contributed by about 50 different developers (46, +translators). 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 safely ignore them. KNOWN BUGS ********** Critical/blocking : * mySQL5.0 : Koha 2.2.9 is NOT guaranteed to be compatible with mySQL 5.0. However some bugs are fixed in 2.2.9, so that should work at least partially. Report any problem encountered, we will continue to improve things in 2.2.10. * 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 ======= CHANGES ======= There are only bugfixes and very minor enhancements in this release : * Major bug in addbiblio and additem (Bug 1330). Previously, if you added a field to a biblio it would save it with the same tagorder as one of the items, and then editing an item would result in it being deleted. * fixed some SQL queries (mySQL5 errors. That does not mean koha 2.2.x is mySQL5 compliant, but that's some errors identified & fixed. Expect koha 2.2.9 to work with fewer problem under mySQL5) * fixed a SQL typo in overdues fixing on return (database was not properly updated) * Solved a problem where a plugin value(fixed fields...) would be lost when editing a record * fixed a bug in expiry date calculation * ENH in z3950 search : adding a test in search to avoid a system error if the server returns an invalid error (can happend, depending on z3950 server) * ENH: Added finer ISBD parsing to allow subfield values to contain {}. * ENH: removed an extra (& useless although harmless) call to MARChtml2xml * ENH: if branch unknown from Koha, take it from userenv, instead of first-defined. This will set branch to users registration branch if not explicitly set. ============= TRANSLATIONS ============= Translations updates : A lot of translations have been updated & completed. Some are partials, but included in the release. Here is a detailled list, language by language : LIBRARIAN (INTRANET) interface - ENGLISH : Templates npl and default available (native language) - CHINESE : Templates default (60% translated) and npl (95% chinese Classic and chinese Taïwan) - FRENCH : Templates default (100% translated) - ITALIAN : Templates default (95% translated) - POLISH : Templates default (30% translated) - SPANISH : Templates default (60% argentin spanish, 95% spanish spain) - UKRANIAN: Templates default (95% translated) and npl (60% translated) OPAC (PUBLIC) interface - ENGLISH : Templates npl and css available (native language) - CHINESE : Templates css (90% translated, chinese Classic and Chinese Taïwan) and npl (90% for both too) - FRENCH : Templates css available (100% translated) - HUNGARIAN: Templates npl (90% translated) - JAPANESE: Templates npl (95% translated) - KOREAN : Templates npl (95% translated) - ITALIAN : Templates css (100% translated) - POLISH : Templates css (75% translated) - SPANISH : Templates css (75% translated) - UKRANIAN: Templates css (100% translated) and npl (90% translated) BE CAREFUL with those translations : most requires that your database is unicode, some that it is latin1 (iso8859-15). So don't hesitate to check and remove any translation that would give strange results (in OPAC mainly, as in librarian interface the librarian can't change the language easily). The templates are in $KOHA/opac/htdocs/opac-tmpl/TEMPLATE/LANGUAGE. Note that the problem will be removed by koha 3, as everybody will be in unicode... -- 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

holidays on rel_2_2
by Antoine Farnault 07 May '07

07 May '07

Hi all, I'm currently synchronizing default & npl template on rel_2_2. Holidays has been added for npl template but i see no link to holidays.pl... Is it normal ? I will add a link to hollidays on parameters for default template. bye, -- Antoine Farnault

2 1

[Fwd: Re: Koha Virtual Appliance]
by Rachel Hamilton-Williams 05 May '07

05 May '07

-------- Original Message -------- Subject: Re: Koha Virtual Appliance Date: Fri, 4 May 2007 08:03:58 -0500 From: Jim Kronebusch <jim(a)winonacotter.org> To: rachel(a)katipo.co.nz References: <20070503163730.M30916(a)winonacotter.org> <463A8553.9010108(a)katipo.co.nz> On Fri, 04 May 2007 12:58:59 +1200, Rachel Hamilton-Williams wrote > Hi Jim, > > i'll forward your suggestion to the Koha lists (regular and developer). > It sounds like a good idea, and we've had Koha easier to install in the > past as part of Debian, but of course every time Koha changes you have > to do a new one. > > I suspect all the project needs to do this, is someone keen to do it. > > Cheers > Rachel Thanks for your response. There always seems to be some problems with compatibility when either Debian or Koha has an update. If a virtual machine was created and distributed by the developers every time Koha was updated it sure could make life easier on the end users. And building a virtual machine under VMware isn't much different than building a standard server, so it shouldn't take much extra expertise, just a desire to do so. If this was done the end user would have a pre-built Koha server ready to go. All they would need is some instruction of which .conf files to modify for their personal domain and how to change passwords. This could make things much less technical for the end user, and who better to gather and install all dependencies than the developers. Another suggestion would be to have them talk to Debian or Ubuntu and see if one of them could add Koha into their software repository. I will be emailing Ubuntu to try and do such a thing. This would make it so that any Debian or Ubuntu user could just "apt-get install koha" and then just wait for setup prompts. Apt would handle all dependencies. At this point I am trying to build my own VMware image, if I get that done I will try and make a torrent and get it out on the internet with some instructions. Thanks again. Jim Kronebusch -- This message has been scanned for viruses and dangerous content by the Cotter Technology Department, and is believed to be clean. -- ----------------------------- Rachel Hamilton-Williams General Manager Katipo Communications Ltd Phone: +64-4-934 1285 Mobile: 021 389 128 E-mail: rachel(a)katipo.co.nz Web: www.katipo.co.nz

1 0

SQL Standards
by Joshua M. Ferraro 05 May '07

05 May '07

Hey gang, I recently got some feedback for how to make Koha's database definitions more portable to other RDMSs. Thanks to Dan Scott for the following recommendations: 1. don't use SQL92 keywords as field names, table names, etc. 2. tables shouldn't be defined with TYPE=MyISAM 3. get rid of quotes around integer values 4. remove nonsensical date defaults like 0000-00-00 (why not use NULL) 5. add SET SQL_MODE='ANSI_QUOTES' to allow using double-quotes for SQL name delimiters To this list I'll also add that we should pick a more noticeable location for the SQL definitions file to avoid confusion in the future. I'd suggest we keep it in installer/kohastructure.sql These seem like some fairly trivial changes to make. Any takers? Other comments? 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

2 1

New feature in HEAD (Koha NoZebra)
by Paul POULAIN 04 May '07

04 May '07

Hello world, I'm really proud to announce that Koha 3.0 No Zebra is on CVS. It's an optionnal feature to have Koha 3.0 without having indexdata zebra. Zebra is hard to setup & configure, so it will be a good thing for smaller libraries. I'll explain briefly how it works, on this mail and more deeply on the wiki. Brifely : - install Koha 3.0 (CVS head) and fill your database. Or update from an existing 2.2 - run misc/migration_tools/rebuild_nozebra.pl That script will : - set a specific systempreference (NoZebra) - define NoZebraIndexes systempref, that contains index definition. UNIMARC default definition is done, a MARC21 guy will do it easily. - create the needed table (nozebra) - populate it Once the script has run : - you can do CCL searches as usuall, but Koha will issue a specific SQL build. Seems i've succeeded to have AND / OR / NOT support, as well as "". So title="two towers' NOT author='tolkien' should work well - when you edit biblios, the SQL indexes are updated as well. Full compatibility with "Koha Zebra" is achieved by having only 3 specific entries in 2 packages : the API of Zebra & NoZebra Koha are strictly the same. Really. My tests show it's much musch faster than Koha 2.2 way of storing & indexing. I'll write on the wiki the limits of the NoZebra stuff & how you can/will choose between Zebra and NoZebra. 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

translating Koha
by Karen Myers 04 May '07

04 May '07

Good morning I am working with libraries in East Timor and am very interested in translating Koha into the local language of Tetun. I think it could have great applications in Timor which has seen an explosion of new libraries that are running on the smell of an oily rag. Am I correct in understanding that I need to translate the opac-tmpl and intranet-tpml pot files only or is there more involved? I am using Koha on Windows at this stage but I assume the translation process is similar for Windows or Linux? I have read through the translating docs from the koha website but any other insights or help would be appreciated. Karen Myers _________________________________________________________________ Advertisement: Communication evolved. Hilarious clips on messsaging here. http://ninemsn.com.au/share/redir/adTrack.asp?mode=click&clientID=763&refer…

2 1

bugzilla daily mail (for chris)
by Paul POULAIN 30 Apr '07

30 Apr '07

Hello chris, I recieve every day a mail with all my pending bugs on bugzilla. atm, the list is quite long, because it contains everything that is affected to me. So, I don't read the mail, & drop it to trash immediatly. Which is a shame, I agree. It would be much more usefull to have : - daily all BLO/CRI/MAJ/NOR bugs - weekly all bugs (including MIN/ENH) hope it's easy to do ;-) -- 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

Roadmap [important]
by Paul POULAIN 28 Apr '07

28 Apr '07

Hello world, OK, i'll release 2.2.9 soon, based on rel_2_2_7 branch+some bugs ported from rel_2_2 (and only bugfixes) I've reviewed more than 100 commits on rel_2_2 branch, and am sure the stability of this branch is not that good enough to have a 2.2.9 release based on rel_2_2. On the other hand, 3-4 major bugfixes have been done, a release is needed. So i'll do it. But I want to speak of the next step. In the last weeks, we had : - HEAD : a lot of activity from hdl & me : code cleaning mainly. it should now be done. - dev_week : a lot of activity from ccfls (kyle & cindy) and some from libLime as well : some features backported from head (holidays) and a new feature ClubsAndServices, for some testing - rel_2_2 : a lot of activity from libLime : backported some features from head (holidays), and some new features (item level reserves, serials routing lists I think it is important that all commiters says what they are doing & when they think they will get enough stability to have a roadmap and a timeline. I also think it's important that all features added on 2.2 / dev_week were also added on head (or we could loose the features. That can be acceptable, but at least we will be aware of the fact, to avoid any bad surprise) Last but not least : I think we should speak of our organisation : it seems that rel_2_2 branch will become a new version with new features. I strongly think we should not call this version 2.2.10, but 2.4 or something like that, to point that it has new features & probably less stability. So we will need a 2.4RM. In the last 3 weeks, I could not get in touch with Joshua, or almost. I'm happy that business is going well for libLime, but, pls, try to find time to the community, we need everybody to work in the same direction, and know the direction we are going ;-) Our (hdl & me) position is clear : - I support 2.2.x branch as Release Maintainer - We work hard on head to achieve a 3.0 stable asap. code cleaning is done (although it's never done in fact. But all what had to be done is done), we plan to work on YUI asap, to have koha 3.0 stable for early Q3 Waiting for everybody thoughts, wishes & args ;-) -- 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

3 2

items table
by Henri-Damien LAURENT 27 Apr '07

27 Apr '07

Hi, I am investigating in items table to see which data are used, useful and useless. I found that. Those information are meaningfull and useful : itemnumber biblionumber biblioitemnumber homebranch holdingbranch itemnotes location itemcallnumber itemlost notforloan timestamp reserves for reserve management dateaccessioned (boils down to creation date) If I understand correctly. The problem is that if MARC data is favoured, then we loose this value if not linked. wthdrawn is used in Circulation.pm to cancel an issue if set. renewals is used and updated in Circulation.pm. Maybe it could get into issues table. paidfor is used in FixAccountForLostAndReturned but usage is rather cryptic restricted (I cannot tell the difference with notforloan ?) itype ??? Those fields I propose to drop : binding (unknown use) onloan,issue_date are Already in issues + unknown use. issues (can be calculated from issues table) price,replacementprice (used in Overdues only for selection),replacementpricedate,booksellerid are account values which seem never to be used.

2 1