https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41936 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook@prosentient.com.au --- Comment #1 from David Cook <dcook@prosentient.com.au> --- I know I bumped into this recently, so I'll look at what's happening... In the item search, the default sort is by title ascending. If you sort it explicitly, it'll say it's using itemcallnumber but under the hood it should use cn_sort (see C4::Items::SearchItems). In the inventory, the sort is by items.cn_sort then itemcallnumber, then title. If an item doesn't have a cn_source or a cn_source that doesn't work with its itemcallnumber, then it will be empty, and that can lead to confusing results. Note that the SQL sorting is lexicographic so L100, L1, and L2 would be sorted like this: L1, L100, L2. -- So often a confusing sorting will be because of having an itemcallnumber which can't be computed into cn_sort in a semantic way. But that's a data problem. Koha is doing the best it can with the information that it has at hand. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.