[Koha-bugs] [Bug 23681] Patron restrictions should be user definable

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

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

--- Comment #23 from Martin Renvoize <martin.renvoize at ptfs-europe.com> ---
Now that my brain has caught up with Andrews explanation I'm happy here.

Yes, the Object <-> DB naming is inconsistent.. BUT by doing so the DB <-> DB
and the Object <-> Object levels are both consistent at their level.  That
makes reasonable sense to me, though in reality I'd love to have seen
'debartment' changed to 'restriction' at the DB level consistently at the time
we decided to switch terms.. we're now dealing with legacy baggage.

As for RestrictionTypes I'm less sure.. but had a chat with Katrin and she
agreed it did make sense as a top level object..   Patron::Restrictions makes
sense as they're directly related but Patrons::RestrictionTypes doesn't as it's
the restriction itself that has a type and is a level distinct.. 
Koha::Patron::Restriction::RestrictionTypes seems a little too nested.. so
happy to stick to top level object here.

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