https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34147
--- Comment #18 from Katrin Fischer <[email protected]> --- (In reply to Jonathan Druart from comment #17) > > As patron visibility is a feature of permissions and groups, I don't think > > we should enforce if based on category limitations. > > > NOTE: the categories for searching are still limited in the left hand > > filters - but not in the dropdown if you click the options button in the > > top search form. This is beyond the scope of this bug. > > Then what? We need to follow-up here. > > Is there a consensus on the desired behaviour? IIRC the original goal of > this "library limitation" at category level was to completely restrict the > access. Since we now have the library groups, does it mean we should get rid > of it? I am not sure if the assumption is correct about the original goal. I think it's more: you cannot "use" the category as a restricted library. This means you cannot add patrons with this category for your library. The whole purpose of the feature is not always clear in all areas. But we already had the issue where libraries can see and edit patrons of other libraries and had to work around that to avoid unintentional data loss on editing these patrons. So for the "Add" buttons we should definitely enforce library limitations. For the pull down in search I think it's also helpful, but more for usability - the library restrictions can be used to "shorten" the pull downs to what you actually use. But if a datatable has patrons I can see with library categories I can't use, I think having them in the filter would not hurt? -- You are receiving this mail because: 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/
