Bug 39256 - Unable to specify ILL branches like holds branches
Summary: Unable to specify ILL branches like holds branches
Status: REOPENED
Alias: None
Product: Koha
Classification: Unclassified
Component: ILL (show other bugs)
Version: 24.11
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-05 20:10 UTC by Eric Phetteplace
Modified: 2025-10-16 15:03 UTC (History)
3 users (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Phetteplace 2025-03-05 20:10:40 UTC
The library branch settings /cgi-bin/koha/admin/branches.pl have a "Pickup location" setting which allows libraries to specify which branches serve as pickup locations for holds. It would be useful to specify whether a branch can be selected in the interlibrary loan location dropdown as well, for analogous reasons (e.g., storage branches which do not fulfill holds nor ILL requests). For our purposes, we could use the same setting to populate the ILL requests branch menu, but it is likely that other libraries may want a branch to serve only holds or holds ILLs for one of any number of reasons.
Comment 1 Holly 2025-10-16 09:15:47 UTC
This sounds a lot like the functionality described in bug 40075 - ILL Standard form should only show libraries that are pickup_locations. Is this bug looking to create a different functionality?

*** This bug has been marked as a duplicate of bug 40075 ***
Comment 2 Eric Phetteplace 2025-10-16 15:01:26 UTC
Like I said, for us pickup locations and ILL ones are the same, but I can imagine other library systems where certain branches are pickup locations but do not fulfill ILLs. But the other bug is fine for now and maybe it makes sense to wait until someone has an actual use case for this one.
Comment 3 Holly 2025-10-16 15:03:03 UTC
Sorry, I see the difference now. This would be a useful feature to have.