Bug 20716 - UDC Classification Colon search
Summary: UDC Classification Colon search
Status: RESOLVED WORKSFORME
Alias: None
Product: Koha
Classification: Unclassified
Component: Searching (show other bugs)
Version: 17.05
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-07 09:39 UTC by Paul Longbottom
Modified: 2023-09-16 14:13 UTC (History)
0 users

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 Paul Longbottom 2018-05-07 09:39:42 UTC
We have changed system preference (IntranetNumbersPreferPhrase) from "don't" to "do", system preference for the OPAC the (OPACNumbersPreferPhrase) from "don't" to "do". To allow more precise searching of our Universal Decimal Classification (UDC) classification which has led to greater precision for our retrieved results from searching. 

However in the UDC classification notation there is used a colon which means that both concepts in a title have equal weight. A search for the UDC call number 34:339.5(411) gets no hits whereas if you substitute a point for a colon the results can be obtained 34.339.5(411). Can the colon symbol be validated as a recognised character in the search string for the call number phrase search.
Comment 1 Katrin Fischer 2023-09-16 14:13:29 UTC
I have tested with the mentioned itemcallnumber "34:339.5(411)" and could find it in Koha without problems using Zebra and keyword or callnumber index.

I believe the issue has been fixed (maybe by automatically repeating the search in quotes?).