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

perldoc.koha-community.org
by Galen Charlton 20 May '10

20 May '10

Hi, I've set up a new website for Koha's POD: http://perldoc.koha-community.org/. This is refreshed nightly from a current Git fetch and formatted using Pod::Simple::HTMLBatch. I've (arbitrarily) chosen to HTMLify the POD for the master branch, 3.0.x, and all tags starting with 'v'. If you have suggestions or comments, please respond to me or the list. Regards, Galen -- Galen Charlton gmcharlt(a)gmail.com

1 0

Availability in Koha Was: Re: [Koha-patches] [PATCH 2/2] Fixes bug 4481: Limit to Available filters out many available items.
by Liz Rea 20 May '10

20 May '10

While we're talking about availability, thought I'd put this out there. Our statewide ILL system would really appreciate a single field for availability on items: a "yes, you can have that for ILL" or "No, I'm sorry, that item is lost, checked out, out for repair, local use only, In transit, or any one of the plethora of other reasons why this item isn't available." The statewide system currently uses AutoGraphics, which can only check one field. We are currently having them check the 952$q. Here's a brief rundown from the coordinator of the statewide ILL: "Since Koha puts status information into different subfields (rather than putting different statuses in the same subfield), we had to pick on subfield to look at. The KEGGr group decided that the best subfield to use was the 952$q. When an item is checked out, the date due appears in that subfield and AGent marks it as Not Available; if the $q is missing, the item is presumed available. My understanding is that other statuses such as Lost or In Transit appear in different subfields. Other Z target catalogs use a single subfield for status information, so when we look in the 852$s (for example), we might see On Shelf, or Checked Out, or Lost, or Mending, etc. Since there's just a single place to look, we can determine all of the different statuses and route requests accordingly." I wanted to make sure that an authoritative availability field is added if availability is revamped. It would make our life a whole lot easier. Liz Rea NEKLS On May 19, 2010, at 7:53 AM, Ian Walls wrote: > Thanks! I was sure there was an explanation for why the code was originally commented out, and a more comprehensive system for determining 'availability' is definitely called for. I had some complaints from folks on our end that the link wasn't working at all, and the functionality I get by adding those lines back in is better for them that otherwise. > > I'll temporarily make use of my patch for these folks until a better one is ready. Thanks for the update! > > > -Ian > > On Tue, May 18, 2010 at 7:08 PM, LAURENT Henri-Damien <henridamien.laurent(a)biblibre.com> wrote: > Le 19/05/2010 00:04, Ian Walls a écrit : > > From: Ian Walls <Ian.Walls(a)med.nyu.edu> > > > > --- > > C4/Search.pm | 25 ++++++++++++------------- > > 1 files changed, 12 insertions(+), 13 deletions(-) > > > > diff --git a/C4/Search.pm b/C4/Search.pm > > index 229ee40..e7c9c76 100644 > > --- a/C4/Search.pm > > +++ b/C4/Search.pm > > @@ -1256,21 +1256,20 @@ sub buildQuery { > > my $group_OR_limits; > > my $availability_limit; > > foreach my $this_limit (@limits) { > > -# if ( $this_limit =~ /available/ ) { > > -# > > -## 'available' is defined as (items.onloan is NULL) and (items.itemlost = 0) > > -## In English: > > -## all records not indexed in the onloan register (zebra) and all records with a value of lost equal to 0 > > -# $availability_limit .= > > -#"( ( allrecords,AlwaysMatches='' not onloan,AlwaysMatches='') and (lost,st-numeric=0) )"; #or ( allrecords,AlwaysMatches='' not lost,AlwaysMatches='')) )"; > > -# $limit_cgi .= "&limit=available"; > > -# $limit_desc .= ""; > > -# } > > -# > > + if ( $this_limit =~ /available/ ) { > > + > > +# 'available' is defined as (items.onloan is NULL) and (items.itemlost = 0) > > +# In English: > > +# all records not indexed in the onloan register (zebra) and all records with a value of lost equal to 0 > > + $availability_limit .= > > +"( ( allrecords,AlwaysMatches='' not onloan,AlwaysMatches='') and (lost,st-numeric=0) )"; #or ( allrecords,AlwaysMatches='' not lost,AlwaysMatches='')) )"; > > + $limit_cgi .= "&limit=available"; > > + $limit_desc .= ""; > > + } > > + > > # group_OR_limits, prefixed by mc- > > # OR every member of the group > > -# elsif ( $this_limit =~ /mc/ ) { > > - if ( $this_limit =~ /mc/ ) { > > + elsif ( $this_limit =~ /mc/ ) { > > $group_OR_limits .= " or " if $group_OR_limits; > > $limit_desc .= " or " if $group_OR_limits; > > $group_OR_limits .= "$this_limit"; > Hi Ian. > Nahuel will work on a real fix for availability. > Since at the moment customers are complaining (quite fairly) that > availability cannot be at biblio level but should rather be at item level. > And they are correct. > But When indexing elements only at biblio level, we cannot provide them > with the best accurate information. > So Nahuel already did some work on that. > But it need some improvement, which he will do soon. > _______________________________________________ > Koha-patches mailing list > Koha-patches(a)lists.koha.org > http://lists.koha.org/mailman/listinfo/koha-patches > > > > -- > Ian Walls > Lead Development Specialist > ByWater Solutions > ALA Booth # 817 > Phone # (888) 900-8944 > http://bywatersolutions.com > ian.walls(a)bywatersolutions.com > Twitter: @sekjal > _______________________________________________ > Koha-patches mailing list > Koha-patches(a)lists.koha.org > http://lists.koha.org/mailman/listinfo/koha-patches

2 1

Patrons with no Checkouts report
by Toni 19 May '10

19 May '10

Hello, After looking into the code of the predefined report "Patrons with No Checkouts" (borrowers_out.pl), I wonder whether the way it is generated (at least in Koha version 3.0.5) is a Bug: It only takes into consideration "old_issues" table, which means that Patrons having items for the first time will appear in the list of "Patrons with no Checkouts". Taking this case (first time users) into account should be as easy as filtering out by the "issues" table in addition to the old_issues table. Is it a BUG? Should I therefore report it? If I report it, I could attach the necessary modification to make it work taking in consideratin first time borrowers, Do you accept "casual" patches from external people? Thanks, Toni

1 0

patches for 3.0.x
by Marcel de Rooy 19 May '10

19 May '10

Hi all, Just a ´dumb´question from someone who just started submitting a few minor patches: Galen wrote: This patch is similar to commit 731b82f7641565c, which is present in HEAD and, if this is a significant enough issue in 3.0.x, should be cherry-picked to that branch. I've marked bug 4159 as a duplicated of bug 3519. What is the procedure for a patch to reach 3.0.x too (in general; this patch is not that relevant) ? I did not find such a topic on the wiki or overlooked it ;) Regards, Marcel

2 1

Koha-3.0.6 Stable release
by LAURENT Henri-Damien 19 May '10

19 May '10

Hi, I am happy to announce Koha3.0.6 Stable, which fixes bugs from 3.0.5 has been released on http://download.koha-community.org/ Its name is koha-3.00.06.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: e17b336ecee3e4423463d27567701056 koha-3.00.06-all-translations.tar.gz 1b7533fc92d1473ad98799e8dec8da63 koha-3.00.06.tar.gz I have also tagged this in Git as "Version 3.00.06" v3.00.06 v3.00.06 In order to save bandwidth, and provide you with faster install, I am releasing two versions, one without translations bundled, and one which contains all the potential translations available. With the first install, if you install install Locale::PO via cpan and you go into the koha-3.0.6/misc/translator directory, you can install a language using ./install-code.pl your language codes. For instance ./install-code.pl fr-FR es-ES find a list here of all the patches included Alex Arnaud (1): (MT 3267) Add Homebranch and Holdingbranch search criterion on circulation stat. Garry Collum (1): Bug 4276: Proposed fix for "Related Subjects" links in Opac. Henri-Damien LAURENT (28): (bug #4021) recent acquisitions Error500 on undefined biblio (bug #3042) Changing XSLT sysprefs to take filename [Followup] (bug #3894) reserve/request.pl (Bug 4049) Searching itemtypes returning noise (bug #4020) XSLT unimarc display MT 1587 : CSV export for cart and shelves, with the ability to define different export profiles Adding RIS and bibtex export C4/XSLT Removing unconditionnal comment fixing updatedatabase Updatedatabase : Updating edititems permissions Bug fix: Authentication with cardnumber allows superlibrarian access updatedatabase : fixing XSLT syspref type Adding release notes 3.0.6 Revert "(bug #3778) GetBranchesLoop and searchMyLibraryFirst" Fixing hierarchy processing Followup admin/categorie.pl Reintroducing finedays in updatedatabase Bug 4320 : Text::CSV::Encoded Problem with error message Better conformance for UNIMARC Authorities Encoding BuildUnimarcHierarchies : Fixing infinite loop Minor Fix : IndependentBranchPatron misspelling Bug 4326 ; returndate were fixed on the day before Adding XSLTreultsFilename and XSLTDetailFilename Release notes 3.0.6 Followup Adding system preference XSLT*FileName Changing version to 3.0.6 Jane Wagner (1): Bug 3663 screen changes to OPAC advanced search Marc Chantreux (6): correctly add authid readable format selection remove a warning remove warning remove useless lines _koha_add_biblioitem rewrite Matthias Meusburger (22): MT2631 : adds sysprefs for MARC or ISBD display in OPAC MT2663 : Adds an itemcallnumber plugin MT2636 : Send a different notification whether an hold has been made from OPAC or from the Intranet MT2582: Fix user deletion without permission MT2938 : Adds a permission for editing items MT 2116: Addons to the CSV export MT 3044 : Adds missing links for opac cart and shelf download MT2889 : Fix statistics' itemtype when item-level_itypes is ON MT3160 : Fix plugin callback when subfields are cloned batchRebuildBiblioTables.pl doesn't crash anymore when GetMarcBiblio fails. MT3421: Moves subscription history in a separate page Nahuel ANGELINETTI (46): (bug 3536) fix homeorholdingbranch on return (bug #3950) rebuild pendingreserves and fix reserves and transfert case (bug #3950) continue to rebuild pending reserves (bug #4004) disallow access for non-logged in users in opac Revert "(bug #3801) fix itemtype administration" (bug #4002) fix database for single itemnumber and foreign key (bug #4044) don't trap fatal error if there is no start date (bug #4038) fix birth date filter in borrowers stats (bug #4043) fix checkoverdues sqlquery (bug #4050) update datelastseen even if document isn't on loan (bug #4051) add columns in csv export of overdues (bug #4052) fix mandatory field/subfield deletion [followup](bug #4051) add borrower "title", and complete address in csv [3.0.x] (bug #4055) backport canbook/itembereserved [followup](bug #3348) fix spent values and spent resume (bug #4062) add item index in zebra conf [followup](bug #4062) marc21 item support (bug #4075) add use of getrecordvalue in opac-detail [3.0.x](bug #4084) fix offline circ (bug #4287) add enrolment period update in 22 to 30 script [3.0.x] (bug #4263) fix the edition of items with repeatable subfields (bug #4290) searching for author in repository (bug #4195) fix OAI repository (bug #4051) fix mistake in overdues (bug #4295) fix overduerules edition (bug #4207) receive shipment problem (MT #3076) make cancel button working on return (bug #4319) allow reserves on waiting items [followup](bug #4055) fix backport error (bug #4334) create needed sample datas [followup](bug #4334) fix duplicate entries in sql Fix kohastructure for deletedborrowers (bug #4358) fix sql query in C4::Members::GetAllIssues (bug #3737) fix title search in order history (bug #4487) permit - and . in callnumber plugin (bug #4490) do not warn each notice if xslt is on (bug #4491) fix weird code in search scripts Nicole Engard (1): Bug 3857: Add tools menu to left of CSV Profiles page Paul Poulain (6): bug fixing : Patron Search : IndependentBranches warning on C4/Biblio.pm (bug #3950) only show on shelf items Fixing Hierarchies : taking any heading subfield (MT3318) RSS OPAC: Adding CDATA term in title and description tags. Sébastien Hinderer (1): Bugfix in errors/*.pl and opac/errors/*.pl Pleas be aware that some improvements affect the way Hold are used. Please be aware that you have to check for each library, each itemtype, the hold policy in order to enable holds for an itemtype. By default, Hold is disabled. Some new systempreferences comes in : - IndependentBranchPatron if you have to search your patron only of your library (default is 0) - XSLTResultsFilename and XSLTDetailFilename (File PATH Major updates are related to : - subscription history page has been made independent from subscription-add - Adding some exports to Koha as csv. - Major security issue. - Fixing and enhancing Holds message - Fixing enhanced messaging system. You can download. Cheers -- Henri-Damien LAURENT

3 2

RFID compatibility in KOHA..
by jksamyal 19 May '10

19 May '10

Dear Sir, Kindly explain me the procedure to install and run RFID feature in KOHA 3.0. Thanks -- Jatinder K. Samyal, Dy.Librarian, Chitkara University, Baddi,Barotiwala, Himachal Pradesh-174103. URL: http://library.chitkarauniversity.edu.in/ Blog: http://culibrary.blogspot.com/ http://worldlibrarynews.blogspot.com/ http://freeaccess.ning.com Ph: 01795-5661011 Extn: 1028 Mob: +91-9805965420

1 0

Perl module dependency management
by Galen Charlton 17 May '10

17 May '10

Hi, Just pointing out the recent patches submitted by Chris Nighswonger related to bug 4444 [1]: http://lists.koha.org/pipermail/koha-patches/2010-May/006229.html http://lists.koha.org/pipermail/koha-patches/2010-May/006230.html http://lists.koha.org/pipermail/koha-patches/2010-May/006232.html http://lists.koha.org/pipermail/koha-patches/2010-May/006231.html Since this is a significant improvement over the past way of doing things and will give me a framework for more easily closing the release blocker bug 4151 [2], I intend to push this patchset in the next day or so. Before I do that, however, I am issuing a call for people to test and sign off on the patches. [1] http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=4444 [2] http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=4151 Regards, Galen -- Galen Charlton gmcharlt(a)gmail.com

3 3

Quick poll on Fines/Charges/Fees/Accounts
by Chris Cormack 17 May '10

17 May '10

Hi All So just a quick show of hands would be great The options are Leave it how it is (Fines) Fines/Fees Fees Charges Accounts My vote is for Accounts But i'd be happy with anything except Fines Chris

11 11

Koha as a federated library
by Anselm Olweny 17 May '10

17 May '10

Dear Colleagues and thanks for the great work, Below is content of a mail I posted to the koha list ( Koha(a)lists.katipo.co.nz) but I have not been advised about the right and best way to go about this. I am sorry for posting this to this forum. Could someone kindly advise me on this. I need this advise in order to be certainly sure that I am doing things right. I am setting up a federated library system using koha where each of the libraries needs to have its own look and feel and also should be able to search its own collection and also be able to search the collection of the other libraries in the federation by the users choice. I have also integrated koha into a CMS "joomla" in order to handle non koha pages. In my koha set up I have created the different libraries as branches and activitated the IndependantBranches preference in koha. You can see this at http://koha.apkn.org (koha in Joomla) or http://koha.apkn.org:81 (Koha pure) or http://koha.apkn.org:81/cgi-bin/koha/opac-mainug.pl and http://koha.apkn.org:81/cgi-bin/koha/opac-mainke.pl (Independent libraries). However, I am not sure whether this is the right way to set up federated libraries using koha. Could someone kindly advise me about the right way to set up federated libraries using koha? Thanks

2 2

Minimum version of Perl
by Galen Charlton 17 May '10

17 May '10

Hi, At present, the minimum version of Perl required by Koha is 5.6.1. Since MARC::Record requires 5.8.2, at the very least Koha's requirement should be 5.8.2, and 5.8.8 (the current stable release in the 5.8.x series) would be better. Are there any common platforms where this would be an issue? What about going further and bumping up to 5.10.0? Regards, Galen -- Galen Charlton gmcharlt(a)gmail.com

4 4