Some libraries want to use the IndependantBranches feature to prevent libraries from editing each other's patron records while still allowing any library to issue items to another library's patrons. It appears that this behavior may have been standard in some previous versions of Koha, but is currently not.
Created attachment 12562 [details] [review] Bug 8839 - Independant Branches - Checkout to patron belonging to another branch Adds the new system preference IndependantBranchesPreventIssuing to control whether IndependantBranches stops one branch from viewing the patron record or issuing items to a patron from a different library.
It's not that clear from a Koha administrator perspective since IndependantBranches means no authorization to modify anything from another branch. And what will you do if a library want the contrary: preventing issuing but allowing to see other branch borrowers? Couldn't you reach your goal with a syspref named 'IndependantBranchOverwriteTo', with those values: - nothing - Issue to other branches - See other branches borrowers - Issue to other branches and see other branches borrowers
(In reply to comment #3) > It's not that clear from a Koha administrator perspective since > IndependantBranches means no authorization to modify anything from > another branch. And what will you do if a library want the contrary: > preventing issuing but allowing to see other branch borrowers? > > Couldn't you reach your goal with a syspref named > 'IndependantBranchOverwriteTo', with those values: > > - nothing > - Issue to other branches > - See other branches borrowers > - Issue to other branches and see other branches borrowers Without a large amount of development, it's not possible to issue to a borrower without being allowed to see them. The same goes for being able to view a borrower without being able to issue to them ( though this is less complicated ). I think this is a good start. Those other options can be added on an as needed basis. I do wonder if I should change the name of the system preference to something like IndependantBranchesCirculation instead though.
Ok, I understand! I was scratching nowhere. From my perspective, trying to have the end user perspective, the difficulty is to understand how both sysprefs work together: IndependantBranches and the new one. Cascading sysprefs are a pain to work with... Yes, a syspref without negative spelling, witouth 'prevent', would be better to understand.
Created attachment 12748 [details] [review] Bug 8839 - Independant Branches - Checkout to patron belonging to another branch Adds the new system preference IndependantBranchesPreventIssuing to control whether IndependantBranches stops one branch from viewing the patron record or issuing items to a patron from a different library.
Created attachment 14865 [details] [review] Bug 8839 - Independant Branches - Checkout to patron belonging to another branch Adds the new system preference IndependantBranchesCirculation to control whether IndependantBranches stops one branch from viewing the patron record or issuing items to a patron from a different library.
You may be aware about the IndependantBranches preference issue. Setting IndependantBranches to "Don't Prevent" overrides the AutoLocation "Require" ip range restrictions, allowing remote access from anywhere, with implications for security. Auth.pm around line 834: if (C4:Context->boolean_preference('IndependantBranches') && C4::Context->boolean_preference('AutoLocation')){ # we have to check they are coming from the right ip range If we do not restrict remote access, we need to implement stronger login security. So I am wondering how the new IndependantBranches settings affect security. Are we still wide open to password cracking if we say "Don't Prevent" for IndependantBranches? Or do the new settings help secure the system?
Sorry, that's probably a separate issue...
No test plan.
Still valid?
Kyle, is this resolved with the newer library group features?