Bug 36352 - Allow agreements to have multiple vendors
Summary: Allow agreements to have multiple vendors
Status: ASSIGNED
Alias: None
Product: Koha
Classification: Unclassified
Component: ERM (show other bugs)
Version: 23.05
Hardware: All All
: P5 - low enhancement
Assignee: Jake Deery
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-18 18:28 UTC by Billie Anne Gebb
Modified: 2025-11-26 12:35 UTC (History)
9 users (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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?
Comment 6 Mathieu Saby 2025-11-26 12:23:45 UTC
Could we revert the status to NEW ?
Comment 7 Pedro Amorim 2025-11-26 12:35:36 UTC
Adding my thoughts here, now that bug 38201 is in main. This should now depend on bug 41275.
With bug 41275, the VueJS part of this development is:
1) Add the following code to the vendor attribute in AgreementResource:
allowMultipleChoices: true
2) Handle the - potentially multiple - vendors within onFormSave in preparation to submit to the API.

The database + REST API spec changes are still required.