| Summary: | Restrict access to pages by home library or patron category | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Christopher Brannon <cbrannon> |
| Component: | OPAC | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | caroline.cyr-la-rose, jandrews, nick, patrick.robitaille |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34892 | ||
| Change sponsored?: | --- | Patch complexity: | Trivial patch |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
| Attachments: | Bug 23650 - Add address of restricted page to syspref description | ||
|
Description
Christopher Brannon
2019-09-19 20:39:18 UTC
Created attachment 93010 [details] [review] Bug 23650 - Add address of restricted page to syspref description To test: 1 - Look at the restricted page syspref 2 - Check that the url is listed 3 - Add some content to the page 4 - Save the prefs 5 - Verify the address listed takes you to the page on the opac This would be incredibly helpful for libraries (like ours) who have users that can access some electronic resources but not all. Aside from branch ID or patron type (which would likely satisfy our needs), ZIP code could be useful for some libraries as a tool to differentiate patrons. Maybe instead of building this on top of the restrictedpage setting, the new Pages could be used here. I was discussing something similar with Owen on IRC today. We were talking about the opac-restrictedpage page, how this is one page that is only accessible to logged in users. I thought it would be interesting to move this functionality to the pages and add an "logged in users only" flag for OPAC pages. This way we could have more than one restricted page. We could add a limit by patron category, as asked in this bug. Here are some thoughts off the top of my head... - Find away to move the current content of the restricted page to an entry in the additional_contents table (move RestrictedPageContent to to additional_contents.content and RestrictedPageTitle to additional_contents.title) - How do we change the link that users would have added to an html customisation to point to the opac-restrictedpage page? - Getting patron category or home library necessitates that the user be logged in (unless there is something in apache or something like that I guess?) - We could add a check box "logged in patrons only" to OPAC pages - If checked, it could open to a multi-select of patron categories where only the selected categories would be able to access this page. - There is already a library limit per page, but it would be nice that this be multi-select to prevent having to create and maintain a page per library - I don't think we'd need to specify RestrictedPageLocalIPs per page, I think this could stay in the system preferences What else? |