Hi, Katrin: Thank you! Yes, this helps a lot and we have been using the items.cn_sort column in some of our reports and should include them in all or where we can, as for some reports we are running into problems and the ' items.cn_sort' is not recognized. I will have to review the select reports where this is the case to see whether we can fix or rewrite the query so that the function works. Thanks again and all best, -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 Sat, Sep 29, 2018 at 11:38 AM Katrin Fischer <katrin.fischer.83@web.de> wrote:
Hi Sebastian,
if you are using LOC callnumbers you could try to include the items.cn_sort column in your reports and try sorting on that. Koha generates cn_sort as a sortable form of the callnumber for LOC and DDC if the $2 in the item is set to the correct classification.
Hope this helps,
Katrin
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
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> 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
On 28.09.2018 11:10, Sebastian Hierl wrote: formula 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, 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 https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha