Bug 38290 - Add library group limits to vendors
Summary: Add library group limits to vendors
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Acquisitions (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Matt Blenkinsop
QA Contact: Testopia
URL:
Keywords:
Depends on: 38010 38207 38291 38209
Blocks:
  Show dependency tree / graph
 
Reported: 2024-10-29 16:40 UTC by Matt Blenkinsop
Modified: 2024-11-07 15:06 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Blenkinsop 2024-10-29 16:40:18 UTC 
It should be possible to limit which vendors can be seen based on library groups
Comment 1 Katrin Fischer 2024-10-29 16:47:16 UTC 
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?
Comment 2 Matt Blenkinsop 2024-10-29 16:59:12 UTC 
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
Comment 3 Katrin Fischer 2024-10-30 06:58:48 UTC 
Thanks Matt, I was hoping it would be able to have a vendor shared by multiple libraries, which this implementation would allow.