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

General project IRC meeting - 1 July 2009
by Galen Charlton 09 Jun '09

09 Jun '09

Hi, The next general meeting of the Koha project will be held on the #koha IRC channel at 19:00 UTC+0. The following standing agenda items will be discussed: 1. Koha 3.2 update 2. Koha 3.0.x update 3. Actions from the previous IRC meeting To suggest additional agenda items, please go to the wiki page for this meeting located at <http://wiki.koha.org/doku.php?id=meetingnotes09jul01>. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

1 0

Koha-3.0.2 Stable release
by LAURENT Henri-Damien 08 Jun '09

08 Jun '09

Hi, we are very happy to announce Koha3.0.2 Stable has been released on http://download.koha.org/ Its name is koha-3.00.02.tar.gz You can download file and signatures You can check the integrity of the package; either by verifying the provided GPG signature (.sig) or by comparing the MD5 checksum: c3fee4abbb29c88f97a5f7db5fe9eebf koha-3.00.02.tar.gz I have also tagged this in Git as "version 3.00.02 final" v3.00.02-final You can download. An extract of release notes is pasted below This release is bugfix only release, and doesnot include new features which would require some database changes. It does add some databases changes though but only to FIX bugs. The next release scheduled in July will include features which are now in master but not ported yet to stable because of database change required. That is to say mainly many content enhancement were not integrated Librarything, Syndetics, Baker&Taylor, Babeltheque, and BranchTransferLimits. But we are willing to make them into the next release which will come out as soon as possible in July. Cheers -- Henri-Damien LAURENT Koha 3.0.2 Release : This release of Koha 3.0.2 includes the following general improvements over the previous release fixes : xslt support for UNIMARC added UNIMARC support for search available items only and weight field better IE7 support for intranet Show Summary in opac results opac-browser Serial subscription report translations improved 178 commits for bug fixes are listed into the release notes.

2 3

Only available language, in a Koha 3.0.2 git installation, is "English" (en)
by Ricardo Dias Marques 08 Jun '09

08 Jun '09

Hi all, For the first time, I have tried to install Koha in Debian (Debian 5.0, a.k.a Debian Lenny). I had some problems with it, but I think that I managed to solve them. The installation was done from git (so it's a "dev" installation, as opposed to a "single" or a "standard" one). As I usually do, this is an UNIMARC and NoZebra setup. The first surprise was when I ran the "Koha Web Installer", right in "Step 1": the only language that appears in the dropdown list is "en" (English). The text above the dropdown reads "Please pick your language from the following list. If your language is not listed, please inform your systems administrator". The "Koha version" (in the "Intranet" > "Home" > "About Koha" > "Server Information" tab) is "3.00.02.012" (so, I think, that's essentially Koha 3.0.2). Apache version is 2.2.9 MySQL version is 5.0.51a Perl version is 5.10 After running the Web Installer, in the "Intranet" area (running on the 8080 port) , the only language that appears for the "System Preference" opaclanguages is also "English(en)". May I have missed something? I have other installations, running Koha 3.0.1 on openSUSE, and there I get the full list of available languages. Thanks in advance for any help, comments and/or pointers. Cheers, Ricardo Dias Marques lists AT ricmarques DOT net Installation Guide for Installing Koha 3 on openSUSE 11 http://wiki.koha.org/doku.php?id=opensuse_11.0

2 2

Future of koha-maintenance.git ?
by Zeno Tajoli 04 Jun '09

04 Jun '09

Hi to all, now we have the new stable versione, Koha 3.0.2 But I don't understood exactly the future of koha-maintenance.git and the path to version 3.0.3. We will continue to use koha-maintenance.git in the near future ? Will koha-maintenance.git update to present stable version (there same fix only in stable) ? The fixes for 3.0.3 will be on koha-maintenance.git or on branch 3.0.x ? I think we can use all 3 branch in this way: -- master branch: experimental version, it will become 3.2, not stable, many problems -- koha-maintenance: branch to test fix on the stable version, quite stable with problems but also with bugfix -- 3.0.x: stable branch, only translation fix and very few bugfixes At the end of fixing time, fix of koha-maintenance go to 3.0.x Probably from october 2009 master will be quite stable and we start to bugfix it prior of 3.2 release (with Release Candidates?) What do you think about it ? Bye Zeno Tajoli Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

2 1

mail to patches@koha.org not coming through
by Joe Atzberger 04 Jun '09

04 Jun '09

The patches I send from our development server to patches(a)koha.org stopped going through yesterday. I still get the CC from git, but the originals seem to be stuck in moderation. Would the administrator for the patches list please advise what I can do to remedy the problem? -- Joe Atzberger LibLime - Open Source Library Solutions

4 6

Could Koha's git official repository be also set up for HTTP access?
by Ricardo Dias Marques 04 Jun '09

04 Jun '09

Hi all, At work, I'm behind a proxy and firewall, that blocks most outgoing traffic, other than http (port 80) and https / SSL (port 443). Because of this, I can NOT clone with git's official repository, given that operations like: git clone git://git.koha.org/pub/scm/koha.git kohaclone ... use the "git" protocol (and not the "http" protocol) that uses a different port than http /https, and thus those operations are blocked. I have worked around this limitation, by using git with the copy of the "koha.git" file available at http://repo.or.cz that, although usually lagging some hours behind the official repository at koha.org, does provide the http interface to git command line operations. So, I can do this: git clone http://repo.or.cz/r/koha.git kohaclone Unfortunately, today I'm trying to do a git fetch from that repository, and the operation seems to be hanging halfway: myhost:~/mykohaclone # git fetch Getting alternates list for http://repo.or.cz/r/koha.git Getting pack list for http://repo.or.cz/r/koha.git Getting index for pack f9c9014fe52c94a9e55c41d8b0c652a8d8b27d4d Getting index for pack 749f1fcddab3af809cc3cdfba4642dc2deebda67 Getting pack 749f1fcddab3af809cc3cdfba4642dc2deebda67 which contains d010503b803cf1888caf25f6ac150a58b663dc21 walk d010503b803cf1888caf25f6ac150a58b663dc21 walk 1c1c585073c0fc2bcbe3957f1b57e7ef4c4410fa got 4b812f1b40e635216c278c61389628f12bdcf847 walk 4b812f1b40e635216c278c61389628f12bdcf847 walk b10cd79ba32cff7130edd75bcb3f6025a0240619 Getting pack f9c9014fe52c94a9e55c41d8b0c652a8d8b27d4d which contains b6c086302bcfbeca92184465ea28f6efd3ad0738 [ ...stops (hangs) here, without any further output] So, it would be nice, at this point, if I could "switch" git to use an http interface to the official git repository at koha.org. There are some instructions regarding this setup at: Setting up a git repository which can be pushed into and pulled from over HTTP(S) http://www.kernel.org/pub/software/scm/git/docs/howto/setup-git-server-over… Do you think that this could be done? Or is it already done? I would like to avoid doing things like setting up SSH tunnels over HTTPS and the like, if possible. Thanks in advance! :) Cheers, Ricardo Dias Marques lists AT ricmarques DOT net Installation Guide for Installing Koha 3 on openSUSE 11 http://wiki.koha.org/doku.php?id=opensuse_11.0

2 2

RFC: Upgrading to jQuery 1.3.2
by John Beppu 03 Jun '09

03 Jun '09

Currently, Koha uses jQuery 1.2.3. I would like to get it upgraded to the current release which is *1.3.2<http://docs.jquery.com/Release:jQuery_1.3.2> *. The significant changes that the 1.3 series brings can be found here: *http://docs.jquery.com/Release:jQuery_1.3* The 1.3 series brings many performance improvements and few new features, but a few things had to be deprecated along the way. The one that seems to cause the most problems for upgraders is the deprecation of the *XPath attribute selector syntax*<http://www.learningjquery.com/2009/03/3-quick-steps-for-a-painless-upgrade-…>, but luckily, it's also easy to fix. If you have any concerns about this upgrade, please speak up. Thanks, --beppu

2 1

Using a Native XML Database with Koha
by Walls, Ian 03 Jun '09

03 Jun '09

Developers, A recent post in the Koha discussion list about MODS support reminded me of something I'd be thinking of for a while. I've heard of talk of developing Koha to support other standards that MARC, such as DC, MODS or METS. It certainly would be nice to be able to use whichever schema best fit ones collection, and to be able to mix different types of standards together into a common interface and management system. I suppose one of the major difficulties would be finding a way to map all those different standards to a relational database, without exploding the number of tables and complexity. So, the thought occurred to me: since most of these formats are already in XML (or could be mapped to it easily enough), why not use a Native XML Database? This would save on mappings, since XQuery would be used to extract information directly from the XML. It would also be flexible enough to allow for home-grown Schemas to be mixed in with standards. There would also be one less translation in getting the information out of storage and into an AJAX interface. The one major concern I see (aside from all the re-coding) is speed. Could a Native XML Database, with the proper indexes, perform as quickly as Koha does now with MySQL and Zebra? And is there any way to answer that without doing the re-coding? I just thought I'd throw this out as food for thought, and hopefully some discussion. I don't know if this has been mentioned before (couldn't find it in the email archives), but it could prove to be worth looking at. Cheers, Ian Walls Systems Integration Librarian NYU Health Sciences Libraries (212) 263-8687 </PRE> <html> <body> ------------------------------------------------------------<br /> This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is proprietary, confidential, and exempt from disclosure under applicable law. Any unauthorized review, use, disclosure, or distribution is prohibited. If you have received this email in error please notify the sender by return email and delete the original message. Please note, the recipient should check this email and any attachments for the presence of viruses. The organization accepts no liability for any damage caused by any virus transmitted by this email.<br /> ================================= </body> </html> <PRE>

5 4

Patches Documentation
by Nicole Engard 03 Jun '09

03 Jun '09

Hi all, Just a friendly reminder to include a comment in your patch submissions so that I can document your changes without having to ask additional questions. Assume I don't understand anything and write the descriptions with that in mind :) more detail for me never hurts. --- Nicole C. Engard Open Source Evangelist, LibLime (888) Koha ILS (564-2457) ext. 714 nce(a)liblime.com AIM/Y!/Skype: nengard http://liblime.com http://blogs.liblime.com/open-sesame/

1 0

Questions about waitingreserves.pl report in Circulation
by Liz Rea 02 Jun '09

02 Jun '09

Developers: We had a few questions about the waitingreserves.pl report. Of course the scenario is specific to our consortium but wanted to get your take on it. 1. The location displayed in the ACTION column when canceling a 'hold over' item is the item's home library; but often, there is a hold on the item for another library (not the home library). It is the next library in the holds queue that should display in this column, rather than the item home location. 2. Canceling the 'hold over' from waitingreserves.pl should trigger a transit prompt, instructing the staff person to send the item on to the hold library, if a hold exists on the item. This doesn't happen. Nothing happens when the 'hold over' is canceled. A staff person, seeing the information displayed in the ACTION column, would naturally assume that the item is to return to its home library. So, regardless of whether a hold exists, the 'hold over' canceled item is being returned home. We have found that a hold transit prompt will trigger if the canceled hold item is checked in after it is canceled. But this is a two-step process that we have not yet trained any of our libraries to perform, as we just discovered this issue. We are seeing lots of problems associated with this, since many hold items are being sent back to their home locations, instead of their next hold location. Attached is a screen shot illustrating the issue. The cancel hold item, TWILIGHT, has a long hold list, but the instructions say to return the item to its home location, MCLOUTH. It should actually go to NORTONVILLE to fill the next hold on the list, as illustrated in the second screen shot, which is the transit prompt that only displays if the item is Checked In. Is this an area where development will need to be sponsored, or is it a known issue/bug? I looked and was unable to find anything on it in bugzilla, so apologies if I missed it. Thanks for your time and efforts and for putting out a great product Liz Rea NEKLS

1 0