This table could, theoretically, completely replace systempreferences. I'm not sure that's the best idea... but I can't really say why. If something should truly be global, then it could just be NULL/NULL/NULL for the context. We're going to be supplying context-sensitive keys in the each time we call, anyway, so we just won't for global things, or we won't supply itemtype for things that are univeral for item type, etc.
I think that it should, however, completely replace issuingrules, and that's where I'm thinking most of the C4/Circulation changes would come in.
-Ian
Le 10/05/2012 17:04, Ian Walls a écrit :
> Paul,does the new table REPLACE the systempreference one or is it added ?
>
>
> Creating a new table allows us to develop this in parallel and commit
> progress incrementally without risking damage to the existing system
> (until we're ready to do the swapover, that is).
(If it's a replacement, then I'm OK)
Unless i'm missing something, the accessor to preferences is centralized
> It also forces us to
> review the subroutines that access this table, and make them clean in
> the Koha namespace. I think building new would be better here than
> modifying what we already have, since C4::Circulation is already pretty
> messy.
in C4::Context, and I don't see the relation to C4::Circulation.
I agree that the switch to Koha namespace is a valid reason, but we must
plan & define it clearly & with as many details as possible. Probably a
topic for the hackfest next month...
--
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08