https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31032
--- Comment #8 from Katrin Fischer <[email protected]> --- (In reply to Donna from comment #7) > I don't know what the original intention of branch limits was, but can speak > to how libraries are expecting it to work now. When something (patron > category, attribute, auth value) is limited by branch the expectation is > that I can see the data, but if I edit the field, the only options I see are > the ones that my logged in branch are supposed to see. > > For instance, if patron category FEE is limited to branch A and B, and I am > logged in at branch C, I should be able to search for patrons in that > category, display their record, see they are category FEE, but when I create > a new patron, or try to edit their record, I do not have the patron category > option of FEE. Exactly, I think we need to differentiate between new and existing. Because at te moment editing other library's data, we create a data loss situation :( : See Bug 31422 - Library limitations might cause data loss I think if you are allowed to edit other branch's data, we should add a 'keep current' option that allows you to leave values unchanged at least. Or we'd need to add hints that these limitations can only be recommended if you take other precautions like limiting who can edit patron and item data. (would be really happy to see bug 20256 bounce back into QA queue) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
