| Summary: | Allow agreements to have multiple vendors | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Billie Anne Gebb <billieanne.gebb> |
| Component: | ERM | Assignee: | 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: | 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: | |||
|
Description
Billie Anne Gebb
2024-03-18 18:28:13 UTC
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? |