[Koha-devel] A configurations table

[dcook at prosentient.com.au]

I think that I’ve been the most vocal critic against it, but even I changed my mind a few months ago.

 

I don’t see any reason not to try it out. Jonathan has helped me realize that sometimes we (and especially me) talk things to death. If someone is willing to work on something, especially a new idea, I think that should be encouraged. 

 

Time to move it back to “Needs Signoff”?

 

David Cook

Software Engineer

Prosentient Systems

Suite 7.03

6a Glen St

Milsons Point NSW 2061

Australia

 

Office: 02 9212 0899

Online: 02 8005 0595

 

From: Koha-devel <koha-devel-bounces at lists.koha-community.org> On Behalf Of Tomas Cohen Arazi
Sent: Tuesday, 22 December 2020 7:30 AM
To: koha-devel <koha-devel at lists.koha-community.org>
Subject: [Koha-devel] A configurations table

 

Hi all, I'm not sure I already mentioned this, but I proposed a new table on bug 26129 [1]. The table is quite similar to 'systempreferences'. The key difference is its companion classes are designed to allow per-branch, per-itemtype and per-category options.

 

This is basically a generalization of the 'circulation_rules' table, and also the 'systempreferences' one.

 

I originally envisioned it so I could set SMTP servers to libraries without a library_to_smtp table. I abandoned the idea because it was too much for what I was doing, but now I found:

 

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22457

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10589

 

which basically require this table and methods to calculate the effective (boolean) based on library and patron category. And I wouldn't like to see that implemented by reinventing the wheel.

 

The 'configurations' table IS reinventing the wheel, but in a way that can be reused and with a reasonable programming API (i.e. you don't need to create new tables for your per-<something> rules, just reuse this internally).

 

We could think of (eventually) refactoring our system preferences to fit here, or not, and just use it as the backend for some settings that require this.

 

Cheers

 

[1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26129


 

-- 

Tomás Cohen Arazi

Theke Solutions (http://theke.io <http://theke.io/> )
✆ +54 9351 3513384
GPG: B2F3C15F

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20201222/d7e113d7/attachment.htm>