Adding a note that I tried these specific call numbers on the community demo server. With the classification scheme set to LC, I saw the following in the call_number sortkey field:
The call numbers did sort as expected in the shelf browse. I suspect the issue you're seeing is that the LC class scheme wasn't applied to one or both of the call numbers.
Adding a note that I tried these specific call numbers on the community demo server. With the classification scheme set to LC, I saw the following in the call_number sortkey field:
QD305.T45T55 2013 - QD0305 T45 T55 02013
QD31.2.A75 1989 - QD00312 A75 01989
The call numbers did sort as expected in the shelf browse. I suspect the issue you're seeing is that the LC class scheme wasn't applied to one or both of the call numbers.
See - http:// mlnc4.noblenet. org/eg/ opac/record/ 253?query= kathy%27s% 20adventures; qtype=keyword; locg=1; detail_ record_ view=0; expand= cnbrowse# cnbrowse