Bug 25704 - With ICU chains on, searching by callnumbers does not produce accurate results
Summary: With ICU chains on, searching by callnumbers does not produce accurate results
Status: RESOLVED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Searching - Zebra (show other bugs)
Version: 19.11
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-10 00:13 UTC by Kelly McElligott
Modified: 2024-01-01 09:31 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kelly McElligott 2020-06-10 00:13:23 UTC
This seems to be a change in functionality around the 19.05.09 version, with ICU chains turned on, the ability to search using the "Call Number" option from the staff client or the OPAC search, is not working accurately.

It will pull results but not all good results and certainly not find all the results for that particular search.
Comment 1 David Cook 2020-06-10 03:19:02 UTC
Hmm the ICU files don't look like they've changed in 5 years, so nothing on that end.

Without more detail, this might be considered a support report rather than a bug report. (I'd suggest turning up the verbosity on the Zebra server logging, and comparing ICU vs CHR call number searching to see what differences are happening at the Zebra server level.)
Comment 2 Katrin Fischer 2020-06-11 10:05:50 UTC
Did you change the UseICU system preference?

I remember something about different 'quoting' that this influences.
Comment 3 Kelly McElligott 2020-06-11 11:08:12 UTC
Katrin,
The ICU system preference is set to be activated, as well as being turned on in the backend.  Is there a different system preference you are talking about?  
David, Thanks!  I will have that angle looked into.
Comment 4 Katrin Fischer 2020-06-11 12:18:01 UTC
Hi Kelly, that was the one I was thinking about. It might still be worthwhile looing into what that pref does change... maybe this is a case where it needs to be taken into account?
Comment 5 David Cook 2020-06-12 05:17:45 UTC
(In reply to Katrin Fischer from comment #4)
> Hi Kelly, that was the one I was thinking about. It might still be
> worthwhile looing into what that pref does change... maybe this is a case
> where it needs to be taken into account?

I was wondering about that as well, and the only thing I could see what some different quoting, so it would be interesting to compare the Zebra search results. Difficult to troubleshoot remotely though...
Comment 6 Katrin Fischer 2020-06-13 18:07:40 UTC
Hi Kelly, 

could you add a search example? I'd like to test and see if I have an idea.

Another thing that comes to mind, could the *NumbersPreferPhrase make a difference? We usually see bad search results with word list, but much better results with phrase searches.

Are you using the call number search from advanced search and simple search or are there any differences there?
Comment 7 David Cook 2021-01-05 00:33:50 UTC
Tempting to mark this as invalid unless we can get some steps for reproducing the problem.
Comment 8 Liz Rea 2021-02-10 17:58:34 UTC
https://catalog-comm.bjesf.bywatersolutions.com/cgi-bin/koha/opac-search.pl?idx=callnum&q=TX+724+S66&branch_group_limit=

Also I don't appreciate the attitude around "this is a support report" with the threat to close the ticket. That is something that other projects do but we should not, because we are not jerks.

Liz
Comment 9 Katrin Fischer 2021-02-10 19:35:48 UTC
Hi Liz, if you look at the history of this bug you can see that David and I tried our best to reproduce the issue and figure this one out. Then we got no more information for over 9 months and were not able to reproduce the issue

David recently reviewed ICU related bugs after fixing a major ICU bug that had been standing for years and could still not reproduce it. I feel he did nothing wrong here. 

Also please don't just add a link, but steps on where you searched and what the expected result are. And can you check the *NumbersPreferPhrase please as requested in comment#6?
Comment 10 David Cook 2021-02-10 23:00:31 UTC
(In reply to Liz Rea from comment #8)
> Also I don't appreciate the attitude around "this is a support report" with
> the threat to close the ticket. That is something that other projects do but
> we should not, because we are not jerks.

Apologies if it sounded like a threat. I can assure you that there was no attitude behind my comment. As Katrin noted, I was doing a review of ICU bugs. I have a fair bit of experience debugging Zebra and ICU, and I'm keen to solve all the Zebra ICU bugs for the benefit of everyone. It's just not clear at this point whether this is a genuine bug in Zebra or Koha.
Comment 11 David Cook 2021-02-10 23:05:29 UTC
(In reply to Liz Rea from comment #8)
> https://catalog-comm.bjesf.bywatersolutions.com/cgi-bin/koha/opac-search.
> pl?idx=callnum&q=TX+724+S66&branch_group_limit=
> 

Thanks for providing the link. As Katrin noted, can you provide more context? How many search results should be returned for this query?

I just tried https://catalog-comm.bjesf.bywatersolutions.com/cgi-bin/koha/opac-search.pl?idx=callnum&q=HV+5825+W56&branch_group_limit and I got back the 1 record that I expected to get. 

How certain are you that the call number "TX 724 S66" exists in the database?

I just tried another search: https://catalog-comm.bjesf.bywatersolutions.com/cgi-bin/koha/opac-search.pl?idx=&q=kw%2Cphr%2Crtrn%3D%22TX+724+S6%22&branch_group_limit=

I'm getting a lot of "TX 724 S6" call numbers but not "TX 724 S66". 

At this point, I can't reproduce the problem.

Happy to look into this more, if more detail can be provided.
Comment 12 Katrin Fischer 2024-01-01 09:31:44 UTC
I can confirm that
callnum:TX 724 S6 leads to 1 result
callnum:callnum:TX 724 S66 has 0 results
callnum,rtrn:TX 724 S6 has 5 results

All seems to work as intended.

We'll definitely need more information here, since we could not reproduce the issue and for the link provided we don't know expected results or current configuration. I am closing this as INVALID, but please re-open if you still have issues.