Summary: | Allow limiting the number of ILL requests one patron can have at a time | ||
---|---|---|---|
Product: | Koha | Reporter: | Lisette Scheer <lisette> |
Component: | ILL | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | pedro.amorim, tomascohen |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Lisette Scheer
2025-05-23 19:27:20 UTC
If you enter the following under <interlibrary_loans> in koha-conf.xml: <borrower_category> <code>S</code> <request_limit> <method>active</method> <count>2</count> </request_limit> </borrower_category> I believe you can effectively limit the number of requests that a given patron category can place. Any requests placed over that become "QUEUED". This works for any backend. Look at 'backend_create' in Koha::ILL::Request. I don't believe this information is well documented and this particular functionality was added 8 years with the very first push of the ILL module. I'm not sure if this answers this use case specifically, but thought this would be useful information to add here regardless. (In reply to Pedro Amorim from comment #1) > If you enter the following under <interlibrary_loans> in koha-conf.xml: > > <borrower_category> > <code>S</code> > <request_limit> > <method>active</method> > <count>2</count> > </request_limit> > </borrower_category> > > I believe you can effectively limit the number of requests that a given > patron category can place. Any requests placed over that become "QUEUED". > This works for any backend. Look at 'backend_create' in Koha::ILL::Request. > > I don't believe this information is well documented and this particular > functionality was added 8 years with the very first push of the ILL module. > I'm not sure if this answers this use case specifically, but thought this > would be useful information to add here regardless. I don't think I've ever heard about this or seen it in action. Huh. I think we should consider moving that into the GUI. |