All, I've taken advice from the Koha group and enlisted the assistance of the staff in helping me find problems in Koha. One of the things we discovered in our version 3.4.1, is that the search for call number searches by word ( callnum,wrdl ) when what we think we need is callnum,phr . The callnum,wrdl works as is as long as there are no spaces.PI/1985.0031 works. 920/M69b pulls up that call number but also 920/M69ba and 920/M69bi (which to me is okay, because the 920/M69b is first) But a search for Series 21 pulls up "Series 410/Roll 2164" as well as "Series 21" and "Series 21/Yazoo County" I know how to change it in the template, but is that what I should be doing? Thanks for your help and patience. -- Linda Culberson lculber@mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives & History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Fax: 601/576-6824
On 3 June 2011 09:15, Linda Culberson <lculber@mdah.state.ms.us> wrote:
All, I've taken advice from the Koha group and enlisted the assistance of the staff in helping me find problems in Koha. One of the things we discovered in our version 3.4.1, is that the search for call number searches by word ( callnum,wrdl ) when what we think we need is callnum,phr .
The callnum,wrdl works as is as long as there are no spaces.PI/1985.0031 works. 920/M69b pulls up that call number but also 920/M69ba and 920/M69bi (which to me is okay, because the 920/M69b is first) But a search for Series 21 pulls up "Series 410/Roll 2164" as well as "Series 21" and "Series 21/Yazoo County"
I know how to change it in the template, but is that what I should be doing?
IANAC (I am not a Cataloguer) but phrase makes more sense to me. As long as it supports right truncation. Which looking at your example it appears to do. I think this could be your first patch to Koha, Linda :) Chris
Chris, We've talked it over, and we would like to try writing a patch for this, if there is no objection from the community. Thanks. Linda On 1:59 PM, Chris Cormack wrote:
On 3 June 2011 09:15, Linda Culberson<lculber@mdah.state.ms.us> wrote:
All, I've taken advice from the Koha group and enlisted the assistance of the staff  in helping me find problems in Koha.  One of the things we discovered in our version 3.4.1, is that the search for call number searches by word  ( callnum,wrdl ) when what we think we need is callnum,phr .
The callnum,wrdl  works as is as long as there are no spaces.PI/1985.0031 works.  920/M69b  pulls up that call number but also 920/M69ba and 920/M69bi  (which to me is okay, because the 920/M69b is first)  But a search for Series 21 pulls up "Series 410/Roll 2164" as well as "Series 21" and "Series 21/Yazoo County"
I know how to change it in the template, but is that what I should be doing?
IANAC (I am not a Cataloguer) but phrase makes more sense to me. As long as it supports right truncation. Which looking at your example it appears to do.
I think this could be your first patch to Koha, Linda :)
Chris
-- Linda Culberson lculber@mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives & History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Fax: 601/576-6824
On 4 Jun 2011 07:53, "Linda Culberson" <lculber@mdah.state.ms.us> wrote:
Chris, We've talked it over, and we would like to try writing a patch for this,
if there is no objection from the community.
Thanks. Linda
Hi Linda That's fantastic, and worst come to worst if ppl do want the wordlist behaviour we can make it a systempreference so ppl can choose that, but I think phrase for callnumber always makes sense. Feel free to ask on koha-devel or on irc for help if you need and again a big yay! Chris
On 1:59 PM, Chris Cormack wrote:
On 3 June 2011 09:15, Linda Culberson<lculber@mdah.state.ms.us> wrote:
All, I've taken advice from the Koha group and enlisted the assistance of the staff  in helping me find problems in Koha.  One of the things we
discovered in our version 3.4.1, is that the search for call number searches by word  ( callnum,wrdl ) when what we think we need is callnum,phr .
The callnum,wrdl  works as is as long as there are no spaces.PI/1985.0031 works.  920/M69b  pulls up that call number but
also
920/M69ba and 920/M69bi  (which to me is okay, because the 920/M69b is first)  But a search for Series 21 pulls up "Series 410/Roll 2164" as
well as "Series 21" and "Series 21/Yazoo County"
I know how to change it in the template, but is that what I should be doing?
IANAC (I am not a Cataloguer) but phrase makes more sense to me. As long as it supports right truncation. Which looking at your example it appears to do.
I think this could be your first patch to Koha, Linda :)
Chris
-- Linda Culberson lculber@mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives & History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Fax: 601/576-6824
All, We have found that the same type of problem seems to occur in 3.4 if searching for barcodes and sn (serial number/biblionumber?) A search for B3525 also pulls up B35250, B35251, B35252 ..... . And the search by biblionumber/serial number is similar. A search for "3" pulls up 10001 result(s) found for 'sn,wrdl: 3'. S\ince ours were automatically assigned" pulls up 3, 30, 301, 302, ,,. 31, 310... and so one Has anyone else noticed this and is happening with other searches that one would expect to pull up just one result? On 6/2/2011 4:15 PM, Linda Culberson wrote:
All, I've taken advice from the Koha group and enlisted the assistance of the staff in helping me find problems in Koha. One of the things we discovered in our version 3.4.1, is that the search for call number searches by word ( callnum,wrdl ) when what we think we need is callnum,phr .
The callnum,wrdl works as is as long as there are no spaces.PI/1985.0031 works. 920/M69b pulls up that call number but also 920/M69ba and 920/M69bi (which to me is okay, because the 920/M69b is first) But a search for Series 21 pulls up "Series 410/Roll 2164" as well as "Series 21" and "Series 21/Yazoo County"
I know how to change it in the template, but is that what I should be doing?
Thanks for your help and patience.
-- Linda Culberson lculber@mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives & History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Fax: 601/576-6824
The problem, at least in 3.4, does exist, but changing the query from sn,wrdl to sn,phr and bc,wrdl to bc,phr seems to fix it. But I'm still wondering if there are others - besides call numbers - for which this applies. I apologize for the multiple emails. I should do more research before I email. I'll try to keep quiet now. Thanks, Linda On 6/6/2011 1:44 PM, Linda Culberson wrote:
All, We have found that the same type of problem seems to occur in 3.4 if searching for barcodes and sn (serial number/biblionumber?) A search for B3525 also pulls up B35250, B35251, B35252 ..... . And the search by biblionumber/serial number is similar. A search for "3" pulls up 10001 result(s) found for 'sn,wrdl: 3'. S\ince ours were automatically assigned" pulls up 3, 30, 301, 302, ,,. 31, 310... and so one Has anyone else noticed this and is happening with other searches that one would expect to pull up just one result?
On 6/2/2011 4:15 PM, Linda Culberson wrote:
All, I've taken advice from the Koha group and enlisted the assistance of the staff in helping me find problems in Koha. One of the things we discovered in our version 3.4.1, is that the search for call number searches by word ( callnum,wrdl ) when what we think we need is callnum,phr .
The callnum,wrdl works as is as long as there are no spaces.PI/1985.0031 works. 920/M69b pulls up that call number but also 920/M69ba and 920/M69bi (which to me is okay, because the 920/M69b is first) But a search for Series 21 pulls up "Series 410/Roll 2164" as well as "Series 21" and "Series 21/Yazoo County"
I know how to change it in the template, but is that what I should be doing?
Thanks for your help and patience.
-- Linda Culberson lculber@mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives & History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Fax: 601/576-6824
On 7 June 2011 06:53, Linda Culberson <lculber@mdah.state.ms.us> wrote:
The problem, at least in 3.4, does exist, but changing the query from sn,wrdl to sn,phr and bc,wrdl to bc,phr seems to fix it.
But I'm still wondering if there are others - besides call numbers - for which this applies.
I apologize for the multiple emails. I should do more research before I email. I'll try to keep quiet now.
Hi Linda Multiple emails are fine, but perhaps this discussion is better on the koha-devel list. I think its not a new problem (i think 3.0.x up did this) but that doesn't mean its right. I think phr for barcode, sn, etc makes more sense and I would encourage you to widen the scope of your bug to include them. The fix is simply changes in the template so should be relatively straightforward to implement and would be a welcome fix for many libraries I think. Chris
Le 06/06/2011 20:57, Chris Cormack a écrit :
On 7 June 2011 06:53, Linda Culberson <lculber@mdah.state.ms.us> wrote:
The problem, at least in 3.4, does exist, but changing the query from sn,wrdl to sn,phr and bc,wrdl to bc,phr seems to fix it.
But I'm still wondering if there are others - besides call numbers - for which this applies.
I apologize for the multiple emails. I should do more research before I email. I'll try to keep quiet now.
Hi Linda Multiple emails are fine, but perhaps this discussion is better on the koha-devel list. I think its not a new problem (i think 3.0.x up did this) but that doesn't mean its right.
I think phr for barcode, sn, etc makes more sense and I would encourage you to widen the scope of your bug to include them. The fix is simply changes in the template so should be relatively straightforward to implement and would be a welcome fix for many libraries I think.
Chris Well, it all depends on what you search, but ext could be really what you are looking for. With phr you could look for : AAAA/BB And find AAAA/BB C AAAA/BB D or even C AAAA/BB where ext would match the exact subfield... But one default for that is that you cannot search both ext and * afaik (could be quite easy to test if anyone interested. In a yaz-client : f @attr 4=1 @attr 6=3 @attr 5=2 "your callnumber" )
and that ext search requires the completeness set to 1 on the index type you use in default.idx ... Which is commonly the case when you use p... Moreoved, consider that using p should not replace w indexing, but be added. Since there are places in the code or in database settings where lcn can be searched directly without using phr modifier. And if you donot have indexed with word... Then the search will always fail which would be worse than the problem it fixed. Hope that helps. -- Henri-Damien LAURENT
participants (3)
-
Chris Cormack -
LAURENT Henri-Damien -
Linda Culberson