[Koha-bugs] [Bug 2500] Standing enhancement request for adding/updating call number splitting algorithms in C4/Labels.pm

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2500

David Cook <dcook at prosentient.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dcook at prosentient.com.au

--- Comment #18 from David Cook <dcook at prosentient.com.au> ---
So I've recently encountered a call number like this: 361.250994 REP NO. 11/10

The section "361.250994" is DDC, I believe.

However, "REP NO. 11/10" is entirely local. 

When printing labels and splitting call numbers, the slash between 11 and 10
gets removed using _split_ddcn. This isn't desirable, so I opted to use a
different splitting sub.

However, if I use _split_ccn, "REP NO. 11/10" gets turns into "REP NO. 11 /10",
which is also undesirable, as that means "11" gets printed on one line and
"/10" gets printed on the next. This is due to some regexp found in _split_ccn,
which pulls apart the last element in the @parts array.

Is there are a reason why the last element in the array is being pulled apart
like this? I used git blame but the original 2009 commit message from Chris
Nighswonger didn't really tell me much. 

I'm sure there is a reason, but it might make more sense for this - or another
- sub to just split on spaces. 

--

Another thought...currently there is no way to associate splitting subs with
call number classification schemes. The only way I see is to hardcode it into
Label.pm. 

Perhaps it would be an idea to specify the call number splitting rule in the
"Classification sources" part of the Administration module. 

This could be useful in several contexts. For instance, we're currently using
the _split_lccn sub for LCC and NLM, but it could also be useful for the KF
Modified classification scheme (which is a legal scheme based on LCC) and other
schemes. KDC (Korean Decimal Classification) would also probably use DDC.


Admittedly, since the behaviours are likely the same, people using KF Modified
or KDC should probably just use "LCC" or "DDC" as classification sources rather
than making new ones, so perhaps I don't actually have a good point there :p.

However...there might be times when a library wants to use the DDC filing rules
but have call number splitting just on spaces. Like in the above case where
they want to preserve those local slashes. 

I don't know. Just a thought. I've already set up "z" to use _split_ccn in the
past. I might adjust it so that it uses a different sub which just split on
spaces...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are watching all bug changes.