[Koha] Split Call Numbers--Variation

Chris Nighswonger cnighswonger at foundations.edu
Tue Mar 15 10:08:43 NZDT 2011


2011/3/14 Marty <ontariowolf64 at yahoo.com>
>
> That's kind of surprising, I have been playing around a bit on my test box and for me Library of Congress numbers never seem to get split. They usually come in this format: 917.1/0022/2 which always shows up on my labels as 917.100222 and that is obviously too long.
>
> But you gave me an idea, and when I replace the '/' with a space in the itemcallnumber the numbers obediently split. For me that works with text as well as numbers.
> ..
> I think it would be useful to be able to choose a separator character, something similar as you get when you import csv files in Base or Excel.
> (On Koha 3.02.04.000)
>
You may see some examples of what the LCCN splitting algorithm is
looking for by looking around line 32 here:

http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=t/Labels_split_lccn.t;h=da323173d3ffc71cb8be134c3ce2022b19ee3a16;hb=HEAD#l32

Also around line 113 here:

http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=C4/Labels/Label.pm;h=0ea2de93cb05e7fb4a6ffec687b4897026bfaf71;hb=HEAD#l113

What has been done is to split based on known examples. If you have an
example of a call number which does not split as you would expect,
please add a comment to bug 2500
(http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2500) which
includes the number as it appears in-line and then as you expect it to
split.

There appear to be a rather infinite variety of ways folks express
call numbers in-line, so until someone pays for development of a
method of allowing end-users to cook up their own splitting
algorithms, this is the way to get your method into the code. :-)

Kind Regards,
Chris


More information about the Koha mailing list