https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23875
--- Comment #10 from Katrin Fischer <[email protected]> --- And by the reasoning that we can't prevent other fields being added... doesn't that apply to all other indexes as well? Would Elastic give you an error when searching on a string in a numerical index or just not sort them 'right'?(In reply to Ere Maijala from comment #9) > (In reply to Katrin Fischer from comment #8) > > Maybe we should have an unchangeable index for biblionumber then? The > > sorting could quickly become an issue. People tend to search very 'broadly' > > and then the tie breaker would come in quickly. At least that's what we see > > with Zebra quite often with searches for single words and similar. > > Using non-numeric sort doesn't really matter for tie-breaker unless you care > for the order. I'd actually like us to have a hard-coded biblionumber index > field. One could also argue that biblionumber should only be the last > resort, and publication date should be the primary. We'll probably end up > making it configurable. ;) publication date can get quickly problematic for serials... the first date in 008 is usually quite old. Every approach has its own problems ;) Maybe we can move the discussion of adding a hardcoded biblionumber index into another bug, but it really bugs me that the sorting of a clearly numerical value would be alphabetic... it just seems very wrong. I've ended up explaining the 'last resort' ordering a lot of times to libraries. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
