Bug 38256

Summary: Link vendors to ERM data providers
Product: Koha Reporter: Matt Blenkinsop <matt.blenkinsop>
Component: AcquisitionsAssignee: Matt Blenkinsop <matt.blenkinsop>
Status: Signed Off --- QA Contact: Testopia <testopia>
Severity: enhancement    
Priority: P5 - low CC: david, lisette, mathsabypro
Version: Main   
Hardware: All   
OS: All   
GIT URL: Change sponsored?: ---
Patch complexity: --- Documentation contact:
Documentation submission: Text to go in the release notes:
This enhancement adds a 'Vendor' field to the ERM eUsage data providers' form, with a dropdown list of vendors created in the acquisitions module. This ability to link an ERM data provider to a vendor record will allow reporting on cost data from baskets and orders, and linking to usage statistics.
Version(s) released in:
Circulation function:
Bug Depends on: 38010    
Bug Blocks:    
Attachments: Bug 38256: Add a column for a vendor
Bug 38256: Update API specs for new column
Bug 38256: DBIC files
Bug 38256: Update the UI to handle the new vendor field
Bug 38256: Add a column for a vendor
Bug 38256: Update API specs for new column
Bug 38256: DBIC files
Bug 38256: Update the UI to handle the new vendor field
Bug 38256: Add a column for a vendor
Bug 38256: Update API specs for new column
Bug 38256: DBIC files
Bug 38256: Update the UI to handle the new vendor field

Description Matt Blenkinsop 2024-10-24 10:27:56 UTC
There should be the ability to link an ERM data provider to a vendor record. This will enable us to get cost data from baskets/orders and link to usage statistics
Comment 1 Matt Blenkinsop 2024-12-04 10:19:04 UTC
Created attachment 175150 [details] [review]
Bug 38256: Add a column for a vendor

(cherry picked from commit 757664a10e2bea8632c9c44bfe3e9d7f589903fc)
Comment 2 Matt Blenkinsop 2024-12-04 10:19:06 UTC
Created attachment 175151 [details] [review]
Bug 38256: Update API specs for new column

(cherry picked from commit ca1a85aa8819f9dd24e1bacc285913919f8950d6)
Comment 3 Matt Blenkinsop 2024-12-04 10:19:09 UTC
Created attachment 175152 [details] [review]
Bug 38256: DBIC files

(cherry picked from commit c3ce31be20b5e593b4793eb500ae1183d9773e8b)
Comment 4 Matt Blenkinsop 2024-12-04 10:19:11 UTC
Created attachment 175153 [details] [review]
Bug 38256: Update the UI to handle the new vendor field

(cherry picked from commit c4f308ed64ffc0420b1ced1426925ac84cac54ce)
Comment 5 Mathieu Saby 2025-02-10 10:20:31 UTC
Matt could you add a test plan please?
Comment 6 Matt Blenkinsop 2025-05-19 11:10:09 UTC
Created attachment 182592 [details] [review]
Bug 38256: Add a column for a vendor

(cherry picked from commit 757664a10e2bea8632c9c44bfe3e9d7f589903fc)
Comment 7 Matt Blenkinsop 2025-05-19 11:10:12 UTC
Created attachment 182593 [details] [review]
Bug 38256: Update API specs for new column

(cherry picked from commit ca1a85aa8819f9dd24e1bacc285913919f8950d6)
Comment 8 Matt Blenkinsop 2025-05-19 11:10:15 UTC
Created attachment 182594 [details] [review]
Bug 38256: DBIC files

(cherry picked from commit c3ce31be20b5e593b4793eb500ae1183d9773e8b)
Comment 9 Matt Blenkinsop 2025-05-19 11:10:17 UTC
Created attachment 182595 [details] [review]
Bug 38256: Update the UI to handle the new vendor field

(cherry picked from commit c4f308ed64ffc0420b1ced1426925ac84cac54ce)
Comment 10 David Nind 2025-06-06 02:16:10 UTC
Created attachment 183022 [details] [review]
Bug 38256: Add a column for a vendor

(cherry picked from commit 757664a10e2bea8632c9c44bfe3e9d7f589903fc)
Signed-off-by: David Nind <david@davidnind.com>
Comment 11 David Nind 2025-06-06 02:16:14 UTC
Created attachment 183023 [details] [review]
Bug 38256: Update API specs for new column

(cherry picked from commit ca1a85aa8819f9dd24e1bacc285913919f8950d6)
Signed-off-by: David Nind <david@davidnind.com>
Comment 12 David Nind 2025-06-06 02:16:17 UTC
Created attachment 183024 [details] [review]
Bug 38256: DBIC files

(cherry picked from commit c3ce31be20b5e593b4793eb500ae1183d9773e8b)
Signed-off-by: David Nind <david@davidnind.com>
Comment 13 David Nind 2025-06-06 02:16:20 UTC
Created attachment 183025 [details] [review]
Bug 38256: Update the UI to handle the new vendor field

(cherry picked from commit c4f308ed64ffc0420b1ced1426925ac84cac54ce)
Signed-off-by: David Nind <david@davidnind.com>
Comment 14 David Nind 2025-06-06 02:22:17 UTC
I have signed off. 

However, I did note that for a new vendor to show up in the dropdown list on the usage data provider, that I have to do a hard refresh of the page.

Testing notes (using KTD):
1. Apply the patch
2. Update the database: updatedatabase
3. Rebuild the schema: dbic (not sure if this is required or not)
4. Rebuild the Vue application: yarn build
5. Restart everything: restart_all
6. Clear your browser cache.
7. Enable the ERM module.
8. Add a new data provider: eUsage > Data providers > New usage data provider
9. Note that there is a new 'Vendor' field under the description field, and the dropdown lists current vendors created in the acquisitions module.
10. Add and edit a usage data provider, and link them to a vendor (My Vendor).
11. Add a new vendor in the acquisitions module, repeat step 10 and link the usage provider to the new vendor. (A hard browser refresh may be required.)