I think Koha should be taking care of normalizing the call number into something like “AL_333_910000000000000_WHY_1986” (admittedly a Dewey-ish example) for sorting purposes. If Koha isn’t sorting the call number correctly, I think it’s worth raising an issue. It seems to me that the on-screen inventory list and the CSV/spreadsheet export inventory list should be identical in how they’re sorted. That way you can print off a shelf list, do your inventory, and then scroll through your screen marking items as seen in the order that they were seen for real. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Sebastian Hierl [mailto:s.hierl@aarome.org] Sent: Friday, 28 September 2018 7:11 PM To: dcook@prosentient.com.au Cc: Koha Devel <koha-devel@lists.koha-community.org>; koha <koha@lists.katipo.co.nz> Subject: Re: [Koha] Inventory lists incorrectly sorted Thank you for raising this issue, David. We sort the reports we generate from Koha in Excel with the following formula by Lee Ann Nolan and Jameson Conley: https://scholarsphere.psu.edu/concern/generic_works/qv33rw719 The formula is a big help, but it doesn't work for call numbers starting three letters, such as in the K class <https://www.loc.gov/aba/publications/FreeLCC/freelcc.html> , where there are numerous call numbers starting with KJA, KKH, KZA, etc. I would love to hear whether anyone has devised a better script or formula to sort LC call numbers in either LibreOffice / OpenOffice or Excel. Thank you, Sebastian -- Sebastian Hierl, Ph.D. Drue Heinz Librarian, Arthur & Janet C. Ross Library American Academy in Rome Via Angelo Masina 5 00153 Rome Italy T: +39 06 5846 417 F: +39 06 5810 788 On Fri, Sep 28, 2018 at 8:33 AM David Cook <dcook@prosentient.com.au <mailto:dcook@prosentient.com.au> > wrote: Hi all, Has anyone had a problem where the lists generated by the inventory tool don't seem to be sorted correctly? I received reports of this and during my investigation I found https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19021 but that didn't seem to solve the root problem, which actually appears to be with the item data stored in the database - rather than Koha code per se. I've opened https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21447 to look into this. I've solved it in my case using touch_all_items.pl <http://touch_all_items.pl> , but it might not be feasible for everyone to run this. Keen to hear ideas about how people think we should resolve this issue for all people. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> https://lists.katipo.co.nz/mailman/listinfo/koha