Available items limiter: No Result found ! - Common Problem
Hi, I have noticed that several Koha website gives the same error message: *No Result found ! N*o results match your search for “ ..." when a Koha OPAC user tries to limit search results by the Available items (currently available items<http://badir.maktabat-online.net/cgi-bin/koha/opac-search.pl?q=software&limit=branch:Shaf&limit=available> ). We are running Koha 3.00.5 on Debian. Does anyone have a fix for this (apparently) common problem, or understand its cause ? Thanks Massoud M. AlShareef, KnowledgeWare Tech
I have noticed instances of current installations of Koha producing a similar error: that is, after performing a search that returns many, many results, limiting to available will reduce the results to less than a page's worth (far fewer than are actually available). I suppose that on different data sets, the limiter could produce 0 results. Has anyone else experienced something like this? Could it be a problem with the way the limit is defining "availability"? -Ian 2010/5/7 massoud alshareef <massoud@kwareict.com>
Hi, I have noticed that several Koha website gives the same error message: *No Result found ! N*o results match your search for “ ..." when a Koha OPAC user tries to limit search results by the Available items (currently available items<http://badir.maktabat-online.net/cgi-bin/koha/opac-search.pl?q=software&limit=branch:Shaf&limit=available> ). We are running Koha 3.00.5 on Debian. Does anyone have a fix for this (apparently) common problem, or understand its cause ?
Thanks Massoud M. AlShareef, KnowledgeWare Tech
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Ian Walls Lead Development Specialist ByWater Solutions ALA Booth # 817 Phone # (888) 900-8944 http://bywatersolutions.com ian.walls@bywatersolutions.com Twitter: @sekjal
* Ian Walls (ian.walls@bywatersolutions.com) wrote:
I have noticed instances of current installations of Koha producing a similar error:A that is, after performing a search that returns many, many results, limiting to available will reduce the results to less than a page's worth (far fewer than are actually available).A I suppose that on different data sets, the limiter could produce 0 results.
Has anyone else experienced something like this?A Could it be a problem with the way the limit is defining "availability"?
Hi Ian If you get a chance could you try running the misc/migration/fix_onloan.pl script. And also update items set onloan = NULL WHERE onloan = '0000-00-00' Then see if it gives better results Chris
-Ian
2010/5/7 massoud alshareef <massoud@kwareict.com>
Hi, I have noticed that several Koha website gives the same error message: No Result found ! No results match your search forA a** ..."A when a Koha OPAC user tries to limit search results by theA AvailableA items (currently available items). We are running Koha 3.00.5 on Debian. Does anyone have a fix for this (apparently)A common problem, or understand its cause ? Thanks Massoud M. AlShareef, KnowledgeWare Tech _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Ian Walls Lead Development Specialist ByWater Solutions ALA Booth # 817 Phone # (888) 900-8944 http://bywatersolutions.com ian.walls@bywatersolutions.com Twitter: @sekjal
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
* Ian Walls (ian.walls@bywatersolutions.com) wrote:
after performing a search that returns many, many results, limiting to available will reduce the results to less than a page's worth (far fewer than are actually available)
On Fri, May 7, 2010 at 3:23 PM, Chris Cormack <chrisc@catalyst.net.nz> wrote:
If you get a chance could you try running the misc/migration/fix_onloan.pl script. And also update items set onloan = NULL WHERE onloan = '0000-00-00'
I see this problem in my test system running HEAD. I followed both these suggestions and there was no effect. The script produced a few lines of output (like "Onloan : 2010-03-04 for 768 / 1432"). The sql statement affected 0 rows. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org
I have the same results as Owen. I don't think items.onloan is being consulted anymore to determine an item's availability. There is a section of code in the buildQuery() function that's been commented out, and it seems to be what dealt with availability limiting. See commit 3daa3143. Also, the definition of 'available' seems a bit vague. Until the previous mentioned commit, it seems to be defined as "not checked out and not lost". But now that that section is commented out, I'm not sure how availability is being determined. Also also, perhaps it would be good to distinguish between available for checkout vs. available for use. For libraries with large non-circulating collections, this distinction becomes increasingly important. Looking forward, perhaps some way to indicate whether something is online, and if it accessible remotely or only on-site. -Ian On Mon, May 10, 2010 at 11:56 AM, Owen Leonard <oleonard@myacpl.org> wrote:
after performing a search that returns many, many results, limiting to available will reduce the results to less
* Ian Walls (ian.walls@bywatersolutions.com) wrote: than a
page's worth (far fewer than are actually available)
On Fri, May 7, 2010 at 3:23 PM, Chris Cormack <chrisc@catalyst.net.nz> wrote:
If you get a chance could you try running the misc/migration/fix_onloan.pl script. And also update items set onloan = NULL WHERE onloan = '0000-00-00'
I see this problem in my test system running HEAD.
I followed both these suggestions and there was no effect. The script produced a few lines of output (like "Onloan : 2010-03-04 for 768 / 1432"). The sql statement affected 0 rows.
-- Owen
-- Web Developer Athens County Public Libraries http://www.myacpl.org _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Ian Walls Lead Development Specialist ByWater Solutions ALA Booth # 817 Phone # (888) 900-8944 http://bywatersolutions.com ian.walls@bywatersolutions.com Twitter: @sekjal
Also also, perhaps it would be good to distinguish between available for checkout vs. available for use.
The page currently says "Limit to currently available items." I interpret this to be very broad, describing any item which is physically available for use in the library, regardless of any circulation rules the item may fall under: - On the shelf available for checkout - On the shelf for in-library use only And I agree that this should extend to records in the catalog which have no potential for being physically unavailable, e.g. electronic resources. I would interpret "currently available" to *exclude* items which are not checked out but which are "waiting" on the hold shelf. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org
+1 Records with more than one item are available when one item is available for use in the library (on shelf).
-----Original Message----- From: koha-bounces@lists.katipo.co.nz [mailto:koha- bounces@lists.katipo.co.nz] On Behalf Of Owen Leonard Sent: Monday, May 10, 2010 6:33 PM To: Ian Walls Cc: koha@lists.katipo.co.nz Subject: Re: [Koha] Available items limiter: No Result found ! - CommonProblem
Also also, perhaps it would be good to distinguish between available for checkout vs. available for use.
The page currently says "Limit to currently available items." I interpret this to be very broad, describing any item which is physically available for use in the library, regardless of any circulation rules the item may fall under:
- On the shelf available for checkout - On the shelf for in-library use only
And I agree that this should extend to records in the catalog which have no potential for being physically unavailable, e.g. electronic resources.
I would interpret "currently available" to *exclude* items which are not checked out but which are "waiting" on the hold shelf.
-- Owen
-- Web Developer Athens County Public Libraries http://www.myacpl.org _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Also also, perhaps it would be good to distinguish between available for checkout vs. available for use. For libraries with large non-circulating collections, this distinction becomes increasingly important.
This was a concern at our place, too. Since I’m not (yet) a coder, I came up with a kind of workaround that works because the 952 $y displays in the OPAC field labeled “Item type” and the 942 $c controls what appears in the OPAC field labeled “Status” (which I had to discover by trial-and-error since I didn’t see it in any documentation). Here’s how we handled it: We have an Item Type called “Books”. And another Item Type called “Book (Non-Circulating)”. Only the second one was created to be “Not for Loan.” When I create a Bib Record for a book I make sure that the Item Type in the 942 $c is “Book”. If the copy is meant to be ‘available for checkout’ then the Item Type in the Item Record 952 $y is also “Book”. The OPAC then shows the user: ‘Item Type’ “Book” and ‘Status’ “Available”. BUT if the copy is meant only to be ‘available for use’ [e.g., a reference room copy], then the Item Record 952 $y is “Book (Non-Circulating)”. In that case, the OPAC displays for the user: ‘Item Type’ “Book (Non-Circulating)” and ‘Status’ “Available”. This gets the words “non-circulating” before our users, but tells them it IS available [for use]; and because the “Book (Non-Circulating)” type is created to be Not for Loan, our circulation system won’t let these reference copies be checked out as it otherwise would. This has been helpful when we have one copy of an item in open stacks and another copy in reference. Kurt Bodling George Washington’s Mount Vernon Estate and Gardens
Thanks, Kurt, for sharing your experience with this! I've submitted a bug report for this issue: http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=4481, for those interested in tracking it. -Ian On Mon, May 10, 2010 at 1:29 PM, Kurt Bodling <kbodling@mountvernon.org>wrote:
Also also, perhaps it would be good to distinguish between available for checkout vs. available for use. For libraries with large non-circulating
collections, this distinction becomes increasingly important.
This was a concern at our place, too. Since I’m not (yet) a coder, I came up with a kind of workaround that works because the 952 $y displays in the OPAC field labeled “Item type” and the 942 $c controls what appears in the OPAC field labeled “Status” (which I had to discover by trial-and-error since I didn’t see it in any documentation). Here’s how we handled it:
We have an Item Type called “Books”. And another Item Type called “Book (Non-Circulating)”. Only the second one was created to be “Not for Loan.”
When I create a Bib Record for a book I make sure that the Item Type in the 942 $c is “Book”.
If the copy is meant to be ‘available for checkout’ then the Item Type in the Item Record 952 $y is also “Book”.
The OPAC then shows the user: ‘Item Type’ “Book” and ‘Status’ “Available”.
BUT if the copy is meant only to be ‘available for use’ [e.g., a reference room copy], then the Item Record 952 $y is “Book (Non-Circulating)”.
In that case, the OPAC displays for the user: ‘Item Type’ “Book (Non-Circulating)” and ‘Status’ “Available”.
This gets the words “non-circulating” before our users, but tells them it IS available [for use]; and because the “Book (Non-Circulating)” type is created to be Not for Loan, our circulation system won’t let these reference copies be checked out as it otherwise would. This has been helpful when we have one copy of an item in open stacks and another copy in reference.
Kurt Bodling
George Washington’s Mount Vernon Estate and Gardens
-- Ian Walls Lead Development Specialist ByWater Solutions ALA Booth # 817 Phone # (888) 900-8944 http://bywatersolutions.com ian.walls@bywatersolutions.com Twitter: @sekjal
participants (6)
-
Chris Cormack -
Fischer, Katrin -
Ian Walls -
Kurt Bodling -
massoud alshareef -
Owen Leonard