Bug 37449

Summary: Authority matching using Elasticsearch on 'Number' fields fails
Product: Koha Reporter: Martin Renvoize (ashimema) <martin.renvoize>
Component: CatalogingAssignee: Nick Clemens (kidclamp) <nick>
Status: ASSIGNED --- QA Contact: Testopia <testopia>
Severity: major    
Priority: P5 - low CC: anke.bruns, bernard.scaife, dcook, fridolin.somers, m.de.rooy, nick, phil
Version: Main   
Hardware: All   
OS: All   
GIT URL: Initiative type: ---
Sponsorship status: --- Comma delimited list of Sponsors:
Crowdfunding goal: 0 Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Description Martin Renvoize (ashimema) 2024-07-24 12:35:20 UTC
The query created for authority search always uses `.ci_raw`.. but that doesn't exist for all search field types, including 'Number'.

Fridolin added ci_raw for type 'Std Number' in bug 31695 because of this, but I'm not sure that's the right approach globally.

We found this when attempting to add a 001 match rule.. local-number defaults to type 'Number' and this never matches anything because 'Number' doesn't include a ci_raw to search against.
Comment 1 Anke Bruns 2025-11-18 10:23:55 UTC
We just solved this for a self-defined index in our own instances by setting the index type in mappings.yaml to "string" instead of "number".

Don't know if this might be a good idea for the "local-number" index as well.