[Koha-devel] [Koha] RFC: Circulation Rules Interface and Backend Revamp RFC

[Jesse]

It's a bit hard to parse out the changes in 5872, but I believe that the
main difference between this proposal and 8369/5872 are the non-tabular
interface and the new database structure.

Here's my main argument for a non-tabular interface: many of the circ
policies are common to an entire branch, category or itemtype, but the
current interface requires them to be duplicated for every combination that
needs new circ rules. It's very very difficult for a table to show the
per-policy inheritance that we need to untangle this mess; 5872 made an
effort, but I'd argue that with as complicated as the inheritance can be,
the grey-cell approach could become quite confusing rather quickly. The new
interface might need tuning, but I believe we need something different from
what we have now.

(By the way, if you have a system with very complicated issuingrules,
please post a dump on bug 15521! It'll be very useful for planning the
backend and interface.)

2016-01-08 2:17 GMT-07:00 Jonathan Druart <
jonathan.druart at bugs.koha-community.org>:

> (continuing on devel only)
>
> That's good news :)
> We absolutely need a discussion here indeed, not to reproduce previous
> attempts who failed.
> For instance, (I have only 2 examples in mind) :
> - Simplify the DB structure: Bug 8369 - default_branch_circ_rule and
> default_circ_rules tables useless
> - Modify the display : Bug 5872 - Enhancements to circulation
> You can find on comment 27 a screencast to show you the interface
> suggested: http://screencast.com/t/4duT8KV6VjQ (Thanks Liz for that!)
>
> As I completely agree the current interface has show its limits, I
> personally think that the table is a good way to have an overview of
> the rules. What you suggest seems less easy to understand, especially
> for libraries using very complex circ rules.
>
> Cheers and good luck :)
> Jonathan
>
> 2016-01-07 20:12 GMT+00:00 Jesse <pianohacker at gmail.com>:
> > The backend and frontend of the circulation/policy rules in Koha have
> been
> > extended and stretched to the point where they cause a fair amount of
> > issues and frustration. Many librarians and developers are uncertain when
> > default rules are applied, and the very large number of possible settings
> > makes the interface and backend unwieldy.
> >
> > Full details for our intended solution can be found at the link at the
> > bottom of this email, but here's the gist:
> >
> > Instead of having one database row with all settings for a given
> > library/category/itemtype, allow each setting (checkout length, fine
> > amount, holds allowed, etc.) to be specified separately.
> > Rework the interface to more clearly show the specificity of
> > default/specific rules, and allow for this new database model.
> > Accomplish the above incrementally by gradually changing APIs.
> >
> >
> http://wiki.koha-community.org/wiki/Circulation_Rules_Interface_and_Backend_Revamp_RFC
> >
> > Any and all comments are appreciated. Development on this project has
> been
> > fully sponsored, and we are looking to start work later this year.
> > --
> > Jesse Weaver
> > _______________________________________________
> > Koha mailing list  http://koha-community.org
> > Koha at lists.katipo.co.nz
> > https://lists.katipo.co.nz/mailman/listinfo/koha
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>



-- 
Jesse Weaver
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20160113/14657298/attachment.html>