Bug 23650 - Restrict access to pages by home library or patron category
Summary: Restrict access to pages by home library or patron category
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-19 20:39 UTC by Christopher Brannon
Modified: 2023-09-22 18:53 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: Trivial patch
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
Bug 23650 - Add address of restricted page to syspref description (1.31 KB, patch)
2019-09-20 16:47 UTC, Nick Clemens (kidclamp)
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Brannon 2019-09-19 20:39:18 UTC
Would like there to be the option to create multiple opac-restrictedpage.pl pages so that depending on patron or library, this information could be custom.

Would need:
* A way to identify and code for each page
* A way to specify which patron types or branches could access each page.
Comment 1 Nick Clemens (kidclamp) 2019-09-20 16:47:28 UTC Comment hidden (obsolete)
Comment 2 John Andrews 2019-09-20 19:26:20 UTC
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.
Comment 3 Katrin Fischer 2023-04-16 01:31:25 UTC
Maybe instead of building this on top of the restrictedpage setting, the new Pages could be used here.
Comment 4 Caroline Cyr La Rose 2023-09-21 18:59:33 UTC
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?