https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41932
--- Comment #62 from David Nind <[email protected]> --- (In reply to Marcel de Rooy from comment #61) > (In reply to David Nind from comment #57) > > 2. After the patch, I used Intermediate Perl (biblionumber = 126) and added > > call numbers. > > > > +----------------+-------------------------+ > > | itemcallnumber | cn_sort | > > +----------------+-------------------------+ > > | A 2 | A_2_000000000000000 | > > | B2 | B_2_000000000000000 | > > | A 1 12-1 | A_1_000000000000000_121 | > > | B22c | B_22C | > > | B123 45 | B_123_450000000000000 | > > | C4 | C_4_000000000000000 | > > +----------------+-------------------------+ > > Yeah, this doesnt look good. It tells me that Dewey is used. Could you > please check the following statements from comment53: > > You need to really change a call number to update cn_sort. If you just save > an item, the call number is not marked "dirty" and cn_sort will not be > affected. > You should have the correct rule in effect. When you default to Dewey and > you add an item, they will look like 1_000000000000000_A_1 as you mentioned. > Should we explicitly say: set $2 to Other and change call number? Or change > the pref DefaultClassificationSource ? > > Did you change the $2 value to Other for those items? The tests now pass (KTD uses Debian 13 (Trixie) by default). I didn't originally understand what was meant above, but I think I've now worked it out: 1. In the authorized value option for 952$2 (BKS framework) there is cn_source 2. There is no cn_source authorized values category under Administration > Basic parameters > Authorized values. 3. When adding or editing items there are two values in the dropdown list: - Dewey Decimal Classification - Library of Congress Classification 4. When I add a new item it defaults to Dewey Decimal Classification for 952$2 5. If I change DefaultClassificationSource to "Other/Generic Classification Scheme", there are now three items listed in the 952$2 dropdown list 6. Before changing the classification scheme in 952$2, the database query results were: select itemcallnumber, cn_sort from items where biblionumber=126; +----------------+-------------------------+ | itemcallnumber | cn_sort | +----------------+-------------------------+ | A 1 12-1 | A_1_000000000000000_121 | | B2 | B_2_000000000000000 | | A 2 | A_2_000000000000000 | | B22c | B_22C | | B123 45 | B_123_450000000000000 | | C4 | C_4_000000000000000 | +----------------+-------------------------+ 7. After changing each item so that 952$2 is now "Other/...." I get the results shown in the test plan: select itemcallnumber, cn_sort from items where biblionumber=126; +----------------+-----------+ | itemcallnumber | cn_sort | +----------------+-----------+ | A 1 12-1 | A_001_121 | | B2 | B0002 | | A 2 | A_2 | | B22c | B0022C | | B123 45 | B0123_45 | | C4 | C4 | +----------------+-----------+ 8. Which I think is what is required. 9. For the record that I added call numbers to before the patch, I changed the 952$2 to "Other/...": - Before and after the patch, the SQL results were: select itemcallnumber, cn_sort from items where biblionumber=146; +----------------+----------------------+ | itemcallnumber | cn_sort | +----------------+----------------------+ | A 11 | A_11_000000000000000 | | A 9 | A_9_000000000000000 | | A 25 | A_25_000000000000000 | | NULL | _ | +----------------+----------------------+ - After the patch, and changing the 952$2 for the items so that it is "Other/...", the SQL results are now: select itemcallnumber, cn_sort from items where biblionumber=146; +----------------+---------+ | itemcallnumber | cn_sort | +----------------+---------+ | A 11 | A_11 | | A 9 | A_9 | | A 25 | A_25 | | NULL | | +----------------+---------+ So the missing step (for me) to make this work is to set DefaultClassificationSource system preference to "Other/...." and use that option for 952$2 (or maybe modify Classification configuration > Classification sources > z (Other/Generic Classification Scheme) so that "In use" = "Yes"?). Then it shows up in the dropdown list for 952$2. However, even if I update the items for the record I added call numbers to before the patch, it no longer sorts as expected (sorts as A 11, A 25, A 9; instead of A 9, A 11, A 25). Is this because it would need something in the new ClassSortGenericFormats system preference to make it sort correctly? -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected] website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
