Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Duplicate
-
None
-
-
5
-
Spitfire
Description
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.
TestRail: Results
Attachments
Issue Links
- duplicates
-
MODKBEKBJ-390
Spike: describe design for "Single tenant multiple EBSCO KBs" scenario
-
- Closed
-
- has to be done before
-
MODKBEKBJ-298
Tags | Single Tenant + Multiple Libraries| Assigned tags must be tied to library/institution
-
- Blocked
-
-
MODNOTES-120
Notes | Single Tenant + Multiple Libraries | Assigned notes must be tied to a library/institution
-
- Blocked
-
- relates to
-
UXPROD-1994 eholdings app | Single Tenant w/ Multiple Libraries Support
-
- Closed
-
-
MODKBEKBJ-292
[Spike] Multiple libraries + one tenant: Ability to store multiple RM API keys per tenant
-
- Closed
-