https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19021

--- Comment #15 from David Cook <[email protected]> ---
I'm not very familiar with this code, but I think this might actually be a data
issue rather than a code issue.

I had 2 items with near identical itemcallnumbers but very different cn_sort
values:

AL AH 616.951 SEX 2013  -  616_951000000000000_SEX_2013
AL AH 616.951 SEX 2010  -  AL_AH_616_951000000000000_SEX_2010

I've just edited the first item in the staff client and it's changed
616_951000000000000_SEX_2013 to AL_AH_616_951000000000000_SEX_2013.

I'm trying to find the code responsible for generating the cn_sort value, but
I'm guessing that the code must have changed at some point, and the database
upgrade script didn't re-run the cn_sort re-generation en masse, which is fair
enough since that would be a big task for some libraries. 

I'm going to run touch_all_items.pl and see if it solves my problem without
applying the patch on this bug report...

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to