[Koha-bugs] [Bug 9921] Make it possible to force 001 = biblionumber

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

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

--- Comment #14 from M. de Rooy <m.de.rooy at rijksmuseum.nl> ---
Nuño:
Thanks for your patch adjustments and the effort to synchronize all language
files in this regard.

But I still have some thoughts about this:
1) I think we cannot force the plugin at upgrade time (in the updatedatabase
change). If someone already has another plugin there, you cannot overwrite
that.
I would consider this a blocker for this patch.
You could consider the update if there is no plugin attached. You could print a
upgrade warning statement if there is another plugin.

2) My personal opinion is that we should stop making changes in all the
language folders. Let an active language maintainer do that. This is currently
not the policy however; note that I sent a message to the dev list just now
about this topic. More ideally, you would insert the plugin only in the general
(English) file and just update the translations in the language (the plugin
filename does not need translation at all).
What we should do in the meantime, is however a little bit gray area now.
So, this does not block your patch.

3) I feel that incrementalControlNumber is not (really) a pref. I can imagine
more cases where we might need a sequential number. Would it be interesting to
move it perhaps to Tools in a more general context such as a sequence number
engine with its own table (id, keyname, seqnumber, date)? 
There are more fields like callnumber (with plugins) that could use such an
approach..
This does again not block your patch, but we could trigger the discussion on a
more general solution.

-- 
You are receiving this mail because:
You are watching all bug changes.