I'm in support of using cn_sort wherever sorting occurs as that's its purpose. If I'm not mistaken, it's already being used in some places without an existing system preference, and I don't see how the Inventory tool is categorically different. Is it possible, perhaps in a plugin, to configure new normalization methods for different classification sources? That seems to be the purpose of the Classification Sources admin settings but I'm not sure. To answer Heather—I think your second question is correct, the two problems are not intertwined. One deals with LC numbers being improperly normalized and another deals with the normalized strings not being used as the sorting value in places. Best, ERIC PHETTEPLACE Systems Librarian libraries.cca.edu | vault.cca.edu | 510.594.3660 5212 Broadway, Oakland, CA 94618 1111 8th St., San Francisco, CA 94107 Preferred Pronoun(s): he/him :(){ :|: & };: On Thu, Nov 15, 2018 at 8:01 AM Hernandez, Heather < heather_hernandez@nps.gov> wrote:

Hi, Nick--

I read through Bug 21629 and if I'm reading it correctly, it says that call numbers are sorted correctly using cn_sort, but Bug 17269 describes how call numbers are not sorted correctly using cn_sort, specifically the ones with colons in them in the G Library of Congress classification schedule.

Has Bug 21629 been tested using LC call numbers with colons in them? Or is the problem of incorrect sorts of LC call numbers with colons in them unrelated?

Thank you! Cheers, h2 ~~~~~~~~~~~~~~ Heather Hernandez Technical Services Librarian San Francisco Maritime National Historical Park Research Center 2 Marina Blvd., Bldg. E, 3rd floor, San Francisco, CA 94123-1284 415-561-7032, heather_hernandez@nps.gov Library catalog: http://keys.bywatersolutions.com/ _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha