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.
We're starting to add data to eRM and identified this requirement too.
+1
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
Yes, we need different vendors, with different roles (customisable), like in CORAL ERM and FOLIO ERM
Jake, I see the ticket is ASSIGNED. Does it mean you are planning a development?
Could we revert the status to NEW ?
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.