Bug 28892 - Item search treats lower and upper case subfields as the same
Summary: Item search treats lower and upper case subfields as the same
Status: RESOLVED WONTFIX
Alias: None
Product: Koha
Classification: Unclassified
Component: Searching (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-08-23 23:31 UTC by Katrin Fischer
Modified: 2023-07-01 13:15 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 Katrin Fischer 2021-08-23 23:31:15 UTC
At the moment when you are using upper case subfields in items and your bibliographic records, this will work in the frameworks, in cataloguing and in searching with Zebra. 

But as the item search uses SQL and ExtractValue, it will always return the contents of the lower and upper case subfield, no matter what you configured for your additional item search fields.

Example: 520$a, 520$A
Comment 1 Katrin Fischer 2021-08-23 23:55:09 UTC
Sadly I am not sure we will be able to fix this.

The biblio_metadata has a case insensitive collation right now. Which I think is what we want when searching for example for a title or author in the record. 

I am not sure we can treat the attributes (MARC fields and subfields) in the MARCXML record as case sensitive, while treating the contents of the elements as case insensitive at the same time.