[Koha-bugs] [Bug 5670] Housebound Readers Module
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Thu Sep 29 11:34:05 CEST 2016
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5670
--- Comment #64 from Jonathan Druart <jonathan.druart at bugs.koha-community.org> ---
(In reply to Alex Sassmannshausen from comment #63)
> (In reply to Jonathan Druart from comment #62)
> > (In reply to Alex Sassmannshausen from comment #61)
> > > > Same for HSBND_ROLE, it seems that another value is not taken into account
> > > > completely. It appears when editing a patron, but not on the housebound
> > > > details. What is the use case exactly?
> > >
> > > You should find that HSBND_ROLE appears when creating an individual
> > > housebound_visit. Any patrons tagged as chooser or deliverer will then
> > > appear as values which can be selected in the chooser and deliverer
> > > dropdowns in the edit/create visit screen.
> >
> > Ok but what could be a third value? What could be a third value and how it
> > is supposed to behave?
>
> Thinking about this some more last night, it feels like the current design
> is not appropriate. You're quite right asking whether there could be third
> values, and the answer is there cannot. The UI expects there to be only two
> values.
>
> My alternative proposal now would be:
> - create a new custom table "housebound_role"
> - with three columns (borrower_id, deliverer, chooser)
> - remove the current dependency on extended patron attributes
> - remove HSBND_ROLE authorised values
>
> So within this approach, I reduce complexity (no extended attributes, fewer
> authorised values), and confirm that housebound roles are not supposed to be
> extensible.
>
> WDYT?
Yes, I think that it makes more sense and will be less confusing for developers
and users.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are watching all bug changes.
More information about the Koha-bugs
mailing list