[Koha-bugs] [Bug 18203] Add per borrower category restrictions on placing ILL requests

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Sat Mar 25 20:00:33 CET 2023


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

Pedro Amorim <pedro.amorim at ptfs-europe.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Failed QA                   |In Discussion

--- Comment #15 from Pedro Amorim <pedro.amorim at ptfs-europe.com> ---
> 2) Behavior in staff interface
> 
> I think, we should not use the staff person's patron category for the check
> on the 'new request' button in the staff interface.
> 
> If a staff user has permissions for the interlibrary loans module, they
> should be able to place ILL requests for the users of the library. They are
> usually not placing ILL requests for themselves, but for others. Similar to
> hold requests.
> 
> The check on the category should be implemented in the patron search/the
> user they try to place the request for. But I am not sure if this would have
> to be done in the backends then?

Yes, I agree with this idea. But it's the backend who is responsible for
attaching the borrowernumber to the illrequest. However, this does seem a bit
redundant for the staff UI, i.e. if a staff member already has the ill
permission, this check should not even be required (since ill permission needs
to be assigned on a per user in the first place anyway).

I suggest we restructure this bug's functionality to just apply to OPAC, since
I also believe the original problem it's trying to solve is only on the OPAC
anyway (prevent certain patron categories from being able to place requests to
avoid costs/noise)

> 3) Changed behaviour for existing installations
> 
> As all categories are allowed to place ILL requests now, we should set "Can
> place ILL requests?" to yes for all categories if the ILLModule is
> activated. This way we won't break things for libraries and they can
> implement the new feature if they chose to do so.

Should we:
1) keep canplaceill default 0, and in atomicupdate set to 1 for every existing
installation if ILLModule sys pref is enabled, or
2) change canplaceill default to 1, which means upon enabling ILLModule it just
works for everyone and then let staff members untick the canplaceill checkbox
for any given category.

Please Katrin let me know what you think of the above, or if some of what I
said doesn't make sense or is wrong.
Thanks!

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


More information about the Koha-bugs mailing list