It should be possible to limit which vendors can be seen based on library groups
That would have been very helpful for us in the past. For some libraries the contacts etc. are not the same and having "duplicate" vendors with no way to see which libraries a vendor "belongs" to makes things difficult currently. Can you share some more specifics about the implementation?
In short you will be able to set a list of library groups on a vendor record that determine which groups this vendor is visible to. When a user requests a page relevant to vendors the system will return a filtered list based on the user's logged in branchcode. Essentially if the user's branchcode exists in a library group then any vendors attached to that group (or any parent groups) will be returned but any attached to groups where that branch does not exits will be filtered out
Thanks Matt, I was hoping it would be able to have a vendor shared by multiple libraries, which this implementation would allow.
Created attachment 175155 [details] [review] Bug 38290: Add a column for library group visibility (cherry picked from commit a0a31abca79ae7c0e282211724eb995bd92e5b9b)
Created attachment 175156 [details] [review] Bug 38290: DBIC file (cherry picked from commit 3dbc11064865b842a33167925a350c31b2f62773)
Created attachment 175157 [details] [review] Bug 38290: Add library group limit classes
Created attachment 175158 [details] [review] Bug 38290: Add library group api client (cherry picked from commit 67277c0bc4da4ac3bafd436c77b49bc7884e3f5b)
Created attachment 175159 [details] [review] Bug 38290: Add fields to the UI for CRUD
Created attachment 175160 [details] [review] Bug 38290: Add cypress tests (cherry picked from commit e270a21e248c58ae7f402628252c9589dccb618e)
Created attachment 175161 [details] [review] Bug 38290: Set lib_group_visibility as null