Duplicate
Details
Assignee
UnassignedUnassignedReporter
Sobha DuvvuriSobha DuvvuriFix versions
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Unassigned
UnassignedReporter
Sobha Duvvuri
Sobha DuvvuriFix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created November 6, 2019 at 6:29 PM
Updated March 30, 2020 at 9:34 AM
Resolved March 30, 2020 at 9:34 AM
As part of MODKBEKBJ-292, we want to support separate holdings for each institution that's part of a consortia. Since these will be still part of a single tenant, how does the database schema need to change to support tags, notes, agreements and licenses?
It could be as simple as storing the custid in the tables for tags and notes but we need to figure it out. Similarly, not sure how this change would affect agreements and licenses - probably no change needs to be done there since ids(package, resource) might be unique based on institution.
Acceptance Criteria:
Get holdings accounts of a consortia that has multiple institutions.
Figure out how or if ids are changing?
Document/Present findings to the team
Create associated implementation stories in several apps as need be.