| Summary: | Hide collections/locations if not for that library | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Nicole C. Engard <nengard> |
| Component: | OPAC | Assignee: | Owen Leonard <oleonard> |
| Status: | CLOSED FIXED | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | ||
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| 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: | |||
|
Description
Nicole C. Engard
2014-06-09 13:57:37 UTC
I don't think that would work in every setting and should likely be configurable. At the moment the settings for branch limitations only reflect on the staff side, but we still assume libraries can search the complete catalog, so nothing is hidden there. What about floating items etc.? I believe this is the way it works now already, although behaviour might be debatable. I cannot limit the collections/locations in order to help with catalging without limiting it to the users to that might be using multiple libraries. |