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
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
We have the default classification source set to Library of Congress. The problem appears to be two different encoding methods. -----Original Message----- From: koha-bounces@lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Fridolin SOMERS Sent: Monday, March 24, 2014 6:19 AM To: koha@lists.katipo.co.nz Subject: Re: [Koha] call number sort problem 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 _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Fridolin SOMERS <fridolin.somers@biblibre.com> wrote:
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. ... So can I adjust the sorting method, or is there something wrong with my data?
items.cn_sort calculation depends on items.cn_source value, if no value, the default classification source is used (defined in syspref "DefaultClassificationSource").
I think I understand this, but I don't understand how to make a call number like "H B34" sort before one like "HM B34". It seems the default is to sort spaces after letters and numbers (which takes me all the way back to Hollerith sorts!). Can this be changed, and if so, how? Regards, / Bruce / Bruce A. Metcalf Library Director The Augustan Society, Inc.
Look into database the values of items.cn_sort for thoses callnumbers. Le 11/06/2014 05:29, Bruce A Metcalf a écrit :
Fridolin SOMERS <fridolin.somers@biblibre.com> wrote:
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. ... So can I adjust the sorting method, or is there something wrong with my data?
items.cn_sort calculation depends on items.cn_source value, if no value, the default classification source is used (defined in syspref "DefaultClassificationSource").
I think I understand this, but I don't understand how to make a call number like "H B34" sort before one like "HM B34".
It seems the default is to sort spaces after letters and numbers (which takes me all the way back to Hollerith sorts!).
Can this be changed, and if so, how?
Regards, / Bruce / Bruce A. Metcalf Library Director The Augustan Society, Inc. _______________________________________________ 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
Fridolin SOMERS <fridolin.somers@biblibre.com> wrote:
Look into database the values of items.cn_sort for thoses callnumbers.
The call numbers are fine. It's the sorting sequence I wanted to change. As in my previous post, I effected this by changing to a different set of "Classification Filing Rules". "LCC" did what I wanted, "Generic" did not. Regards, / Bruce / Bruce A. Metcalf Librarian The Augustan Society, Inc.
Le 11/06/2014 05:29, Bruce A Metcalf a écrit :
Fridolin SOMERS <fridolin.somers@biblibre.com> wrote:
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. ... So can I adjust the sorting method, or is there something wrong with my data?
items.cn_sort calculation depends on items.cn_source value, if no value, the default classification source is used (defined in syspref "DefaultClassificationSource").
I think I understand this, but I don't understand how to make a call number like "H B34" sort before one like "HM B34".
It seems the default is to sort spaces after letters and numbers (which takes me all the way back to Hollerith sorts!).
Can this be changed, and if so, how?
Regards, / Bruce / Bruce A. Metcalf Library Director The Augustan Society, Inc. _______________________________________________ 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 _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Hie, If you changed the default classification source, it will not affect the actual classification source in items, nor the items.cn_sort. You may use the script touch_items.pl to edit all items and so recompute the items.cn_sort. Best regards, Le 04/07/2014 18:25, Bruce A Metcalf a écrit :
Fridolin SOMERS <fridolin.somers@biblibre.com> wrote:
Look into database the values of items.cn_sort for thoses callnumbers.
The call numbers are fine. It's the sorting sequence I wanted to change.
As in my previous post, I effected this by changing to a different set of "Classification Filing Rules". "LCC" did what I wanted, "Generic" did not.
Regards, / Bruce / Bruce A. Metcalf Librarian The Augustan Society, Inc.
Le 11/06/2014 05:29, Bruce A Metcalf a écrit :
Fridolin SOMERS <fridolin.somers@biblibre.com> wrote:
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. ... So can I adjust the sorting method, or is there something wrong with my data?
items.cn_sort calculation depends on items.cn_source value, if no value, the default classification source is used (defined in syspref "DefaultClassificationSource").
I think I understand this, but I don't understand how to make a call number like "H B34" sort before one like "HM B34".
It seems the default is to sort spaces after letters and numbers (which takes me all the way back to Hollerith sorts!).
Can this be changed, and if so, how?
Regards, / Bruce / Bruce A. Metcalf Library Director The Augustan Society, Inc. _______________________________________________ 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 _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ 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
At 09:36 AM 7/7/2014 +0200, Fridolin SOMERS wrote:
Hie,
If you changed the default classification source, it will not affect the actual classification source in items, nor the items.cn_sort.
You may use the script touch_items.pl to edit all items and so recompute the items.cn_sort.
I can't find any documentation on 'touch_items.pl' except a few mentions on IRC chat <https://www.google.com/search?q=site%3Akoha-community.org&q=touch_items.pl&sa=Search&gws_rd=ssl> -- could you please point me in the right direction? Thanks -- Paul
Mmmm, I only found misc/maintenance/touch_all_items.pl (or bin/maintenance) Bernardo -- Bernardo Gonzalez Kriegel bgkriegel@gmail.com On Mon, Jul 7, 2014 at 11:24 AM, Paul A <paul.a@navalmarinearchive.com> wrote:
At 09:36 AM 7/7/2014 +0200, Fridolin SOMERS wrote:
Hie,
If you changed the default classification source, it will not affect the actual classification source in items, nor the items.cn_sort.
You may use the script touch_items.pl to edit all items and so recompute the items.cn_sort.
I can't find any documentation on 'touch_items.pl' except a few mentions on IRC chat <https://www.google.com/search?q=site%3Akoha- community.org&q=touch_items.pl&sa=Search&gws_rd=ssl> -- could you please point me in the right direction?
Thanks -- Paul _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Yes, it's this one. Run it with "--help" for manual. Le 07/07/2014 17:34, Bernardo Gonzalez Kriegel a écrit :
Mmmm, I only found misc/maintenance/touch_all_items.pl (or bin/maintenance)
Bernardo
-- Fridolin SOMERS Biblibre - Pôles support et système fridolin.somers@biblibre.com
At 09:24 AM 7/8/2014 +0200, Fridolin SOMERS wrote:
Yes, it's this one. Run it with "--help" for manual.
paul@-----:/usr/share/koha/bin/maintenance$ ./touch_all_items.pl --help You need to install the perl-doc package to use this program. My sandbox is busy with non-Koha development at the moment, and policy is not to touch the production boxes. Is there any write up in the koha-community documentation that I can refer to? I also note that there are two other utilities (remove_items_from_biblioitems.pl and touch_all_biblios.pl) that sound interesting -- could potentially avoid working direct in MySQL. I apologise for not noticing any of these over the last two years! Best -- Paul
Le 07/07/2014 17:34, Bernardo Gonzalez Kriegel a écrit :
Mmmm, I only found misc/maintenance/touch_all_items.pl (or bin/maintenance)
Bernardo
-- Fridolin SOMERS Biblibre - Pôles support et système fridolin.somers@biblibre.com _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
--- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>
Hi there Paul, I've just run it for you. NAME touch_all_items.pl SYNOPSIS touch_all_items.pl touch_all_items.pl -v touch_all_items.pl --where=STRING DESCRIPTION When changes are made to ModItem (or the routines that are called by it), it is sometimes necessary to run ModItem on all or some records in the catalog when upgrading. This script does that. --help Prints this help -v Provide verbose log information. --where Limits the search with a user-specified WHERE clause. Hope this helps, Fabio 2014-07-08 15:14 GMT+02:00 Paul A <paul.a@navalmarinearchive.com>:
At 09:24 AM 7/8/2014 +0200, Fridolin SOMERS wrote:
Yes, it's this one. Run it with "--help" for manual.
paul@-----:/usr/share/koha/bin/maintenance$ ./touch_all_items.pl --help You need to install the perl-doc package to use this program.
My sandbox is busy with non-Koha development at the moment, and policy is not to touch the production boxes. Is there any write up in the koha-community documentation that I can refer to?
I also note that there are two other utilities (remove_items_from_ biblioitems.pl and touch_all_biblios.pl) that sound interesting -- could potentially avoid working direct in MySQL. I apologise for not noticing any of these over the last two years!
Best -- Paul
Le 07/07/2014 17:34, Bernardo Gonzalez Kriegel a écrit :
Mmmm, I only found misc/maintenance/touch_all_items.pl (or bin/maintenance)
Bernardo
-- Fridolin SOMERS Biblibre - Pôles support et système fridolin.somers@biblibre.com _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
--- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
I forgot to say you can read the perl code, you will find the text shown by the --help option. Le 08/07/2014 15:14, Paul A a écrit :
At 09:24 AM 7/8/2014 +0200, Fridolin SOMERS wrote:
Yes, it's this one. Run it with "--help" for manual.
paul@-----:/usr/share/koha/bin/maintenance$ ./touch_all_items.pl --help You need to install the perl-doc package to use this program.
My sandbox is busy with non-Koha development at the moment, and policy is not to touch the production boxes. Is there any write up in the koha-community documentation that I can refer to?
I also note that there are two other utilities (remove_items_from_biblioitems.pl and touch_all_biblios.pl) that sound interesting -- could potentially avoid working direct in MySQL. I apologise for not noticing any of these over the last two years!
Best -- Paul
Le 07/07/2014 17:34, Bernardo Gonzalez Kriegel a écrit :
Mmmm, I only found misc/maintenance/touch_all_items.pl (or bin/maintenance)
Bernardo
-- Fridolin SOMERS Biblibre - Pôles support et système fridolin.somers@biblibre.com _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
--- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>
_______________________________________________ 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
participants (6)
-
Bernardo Gonzalez Kriegel -
Bruce A Metcalf -
Fabio Tiana -
Fridolin SOMERS -
Margo Duncan -
Paul A