Summary: | Include a user-editable area/page for terms and conditions of use in the opac | ||
---|---|---|---|
Product: | Koha | Reporter: | Liz Rea <liz> |
Component: | OPAC | Assignee: | Liz Rea <liz> |
Status: | RESOLVED MOVED | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | lisette, niamh.walker-headon, olli-antti.kivilahti, veron |
Version: | Main | Keywords: | Academy |
Hardware: | All | ||
OS: | All | ||
See Also: | http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14980 | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Liz Rea
2014-12-03 01:14:02 UTC
Maybe something for an enhanced (CMS-ised) News system? - I add "Bug 14980 - Add a page showing one news" as related. I am looking into developing this kind of a system. We have self-service libraries and we need to know in Koha if the users have agreed to the "Terms and Conditions" of self-service library use. We use this information to communicate with the self-service devices whether or not users are allowed to access the self-service resources. I already added a custom borrower attribute SST&C (Self-Service Terms & Conditions) where you use the authorised_values-list YES_NO to agree or not. You can easily add another types of T&C to borrower attributes. Now I am looking into where to show the T&C in OPAC. Probably I will have a new tab in the left navigation menu, where using the translation tools there will be placeholders that can be filled from the .po-files, matching the given custom borrower attribute. Or maybe use messaging templates instead. Exacts are fuzzy, but the user must be able to accept T&C from the OPAC. Maybe I need to write a real T&C module, maybe that would be for the best. Whatever the implementation: -one must be able to dynamically CRUD translateable T&Cs and view them in the OPAC -OPAC user must be able to agree or disagree with the T&C at any time. -All user agreement-status changes must be logged, so we know if the users is trying to trick us by switching agreement statuses. We have cut this feature from the scope of our current self-service automation project. The reason being. We need to have a stronger level of authentication than simple username + password. For example a strong authentication from the national identification service would suffice. This is out of scope as well :) Regional and Country differences apply. This bug got derailed, I still think the original feature proposal is a good one. While a general solution for adding pages to the OPAC would be nice, I agree this would be a good addition. This can be solved now by using HTML customizations and OPAC pages. :) |