hie, items.cn_sort calculation depends on items.cn_source value, if no value, the default classification source is used (defined in syspref "DefaultClassificationSource"). Le 21/03/2014 22:05, Margo Duncan a écrit :
We're having some issues with call number sort in our reports and I'm wondering if anyone has any insights.
It appears that cn_sort has two different methods of sorting call numbers. One way is that 0 is added so that a call number of HD30.19 is HD003019. The other way is with _ so HD30.19 is HD_0030_19. This has the result of sorting the call numbers into two separate batches within a single report. It doesn't matter what the method of sorting call numbers is (as long as it works) but we need it to be consistent. So can I adjust the sorting method, or is there something wrong with my data? And if there's something wrong with my data, what do I need to adjust to have the the call numbers sort correctly?
We're running 3.14.03 on Debian.
TIA, Margo
Margo Duncan, MLS Systems Librarian Robert R. Muntz Library The University of Texas at Tyler 903.566.7174 | mduncan@uttyler.edu<mailto:mduncan@uttyler.edu>
Help the library with our strategic planning! Take this survey: http://goo.gl/albmQj
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Fridolin SOMERS Biblibre - Pôles support et système fridolin.somers@biblibre.com