Summary: | Library::CallNumber::LC does not follow LC standards for Area Subarrangments of cataloged maps | ||
---|---|---|---|
Product: | Koha | Reporter: | Barton Chittenden <barton> |
Component: | Architecture, internals, and plumbing | Assignee: | Galen Charlton <gmcharlt> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | bugzilla, flyingendpaper |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Barton Chittenden
2016-09-07 15:46:11 UTC
We just got Elasticsearch, and these call numbers with colons in them appear to be sorting correctly: https://keys.bywatersolutions.com/cgi-bin/koha/opac-search.pl?q=callnum%2Cphr%3Ag4364&offset=40&sort_by=call_number_asc Our Koha version is 19.05.07.000 --h2 We're now on 21.05 with Elasticsearch and the call numbers are no longer sorting correctly--call numbers with the cutter S5:2 are sorting before S5. --h2 (In reply to Heather from comment #2) > We're now on 21.05 with Elasticsearch and the call numbers are no longer > sorting correctly--call numbers with the cutter S5:2 are sorting before S5. > > --h2 Hi Heather! I think you might be seeing Bug 29632 - Callnumber sorting is incorrect in Elasticsearch (In reply to Katrin Fischer from comment #3) It sure could be, Katrin! Nick Clemens filed bug 29632 just a few days ago--maybe that's a duplicate of this one? Or that's a better written/better one than this one, which has been languishing for years? I think Barton's bug was about a possible issue with the library we use to generate the cn_sort - the sortable form of the callnumber - for LC callnumbers. As this should be fixed by the maintainers of this library, he has filed it here: https://github.com/libraryhackers/library-callnumber-lc/issues/10 If things have worked ok for you before, they will probably work ok once Elasticsearch uses cn_sort for sorting as well. |