https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23671 Bug ID: 23671 Summary: Elasticsearch shouldn't throw exception on an uppercase subfield identifier Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: trivial Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs@lists.koha-community.org Reporter: nicolas.legrand@bulac.fr Depends on: 23670 MARC 21 specifies a subfield identifier “may be any any lowercase alphabetic or numeric character” (https://www.loc.gov/marc/96principl.html section 8.4.2). It is not that clear for Unimarc or even for ISO 2709 itself. Our catalogue in Unimarc use uppercase alphabetic subfield identifier for items. When we try to index it with Elasticsearch, it throws an exception (well, it tries to, this is fixed by Bug 23670). We think Elasticsearch shouldn't be picky about uppercase alphabetic subfield identifier, especially when Koha permits their creation in the MARC Framework or in the Elasticsearch mapping. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23670 [Bug 23670] Load Koha::Exceptions::ElasticSearch module in Koha::SearchEngine::Elasticsearch -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.