[Koha-bugs] [Bug 9921] Make it possible to force 001 = biblionumber
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Thu Jun 20 14:40:41 CEST 2013
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9921
--- Comment #41 from Nuño López Ansótegui <nunyo at masmedios.com> ---
(In reply to comment #39)
> (In reply to comment #36)
> > > I am wondering if it is dangerous to set the plugin for one framework and
> > > not for another (could be the case)?
>
> Since your pref is OFF by default, this is initially harmless.
> Suppose however that people have some frameworks, and some frameworks have a
> 001 plugin and other frameworks have not. (Not recommended of course..)
>
> They upgrade and now some frameworks have your plugin and others have the
> old (custom) one. They are perhaps not aware of this incosistency. At some
> time they activate your pref and they see your plugin in some framework,
> making the wrong conclusion that all frameworks already have it. From that
> time on, we do have a problem.
>
> Now is the question: Should we actually update a Koha db that has this
> inconsistency with potential for future problems, or should we only update
> if all frameworks do NOT have a 001 plugin?
If they have their own 001 plugin, i think that they should be able to control
their frameworks and differ if they have the default plugin 001 in Koha or not.
What do you think?
--
You are receiving this mail because:
You are watching all bug changes.
More information about the Koha-bugs
mailing list