Bug 36352

Summary: Allow agreements to have multiple vendors
Product: Koha Reporter: Billie Anne Gebb <billieanne.gebb>
Component: ERMAssignee: Jake Deery <jake.deery>
Status: ASSIGNED --- QA Contact:
Severity: enhancement    
Priority: P5 - low CC: edith.speller, jake.deery, jonathan.druart, jonathan.field, martin.renvoize, mathsabypro, matt.blenkinsop, michaela.sieber, pedro.amorim
Version: 23.05   
Hardware: All   
OS: All   
GIT URL: Change sponsored?: ---
Patch complexity: --- Documentation contact:
Documentation submission: Text to go in the release notes:
Version(s) released in:
Circulation function:

Description Billie Anne Gebb 2024-03-18 18:28:13 UTC
Some agreements may have multiple vendor relationships, for example, a title could be published by one entity but billed through another. It would be helpful to have both listed with the agreement.
Comment 1 Edith Speller 2024-06-24 15:42:16 UTC
We're starting to add data to eRM and identified this requirement too.
Comment 2 Michaela Sieber 2024-06-25 14:01:58 UTC
+1
Comment 3 Jake Deery 2024-07-17 14:39:31 UTC
We would presumably need to drop the foreign key on erm_agreements, and create a new table to track the relations (e.g. erm_vendor_relationships).

Because there's quite a lot of engineering involved in this, could we discuss via Mattermost the details? How might this impact the UI, etc?

https://chat.koha-community.org/koha-community/pl/dhj59s1odbgr784zfyiaswkcgr
Comment 4 Mathieu Saby 2025-01-14 04:47:53 UTC
Yes, we need different vendors, with different roles (customisable), like in CORAL ERM and FOLIO ERM
Comment 5 Mathieu Saby 2025-01-14 04:48:53 UTC
Jake, I see the ticket is ASSIGNED. Does it mean you are planning a development?