Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
eHoldings Sprint 88, eHoldings Sprint 89
-
5
-
Spitfire
Description
Holding record data that stored internally in Eholdings has to be associated with different KB credentials. Some samples of the data are:
- package details (name, content type)
- provider name
Services that work with such data should be updated to apply filtering by credentialsId.
More details can be found in the dedicated section of "Spike: MODKBEKBJ-390 - describe design for "Single tenant multiple EBSCO KBs" scenario"
Requirements
- locally stored package/provider/resource/title information should be filtered by credentialsId
Acceptance Criteria
- changes covered with unit tests
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-1994 eholdings app | Single Tenant w/ Multiple Libraries Support
-
- Closed
-
- is defined by
-
MODKBEKBJ-390 Spike: describe design for "Single tenant multiple EBSCO KBs" scenario
-
- Closed
-
- relates to
-
MODKBEKBJ-398 Spike "Single tenant + KBs": Updating existing endpoints for providers/packages/resources/titles
-
- Closed
-