Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
eHoldings Sprint 88, eHoldings Sprint 89
-
8
-
Spitfire
Description
To support the "Single tenant multiple EBSCO KBs" feature the existing endpoint
POST /loadHoldings
should be re-named to
POST /eholdings/loading/kb-credentials/{credentialsId}
as in the current implementation endpoint loads holdings records for only one KB credentials.
Updates will affect database i.e. holdings, holdings_status, holdings_audit tables. retry _status and transactions_ids assumed to be updated in MODKBEKBJ-428 and MODKBEKBJ-427
More details can be found in the dedicated section of "Spike: MODKBEKBJ-390 - describe design for "Single tenant multiple EBSCO KBs" scenario"
Requirements
- post credentials by id loads holdings for certain KB credentials
- repeated call of the endpoint with same KB credentials id within refresh period (24h) should not trigger a snapshot creation
- old POST /loadHoldings endpoint removed, respective permission is also removed
Acceptance Criteria
- the endpoint updated and works according to the requirements
- the endpoint is covered with unit tests
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-1994 eholdings app | Single Tenant w/ Multiple Libraries Support
-
- Closed
-
- has to be done before
-
MODKBEKBJ-430
Support POST /eholdings/loading/kb-credentials to load holdings for all KB Credentials
-
- Closed
-
- is defined by
-
MODKBEKBJ-390
Spike: describe design for "Single tenant multiple EBSCO KBs" scenario
-
- Closed
-
- relates to
-
MODKBEKBJ-400 Spike "Single tenant + KBs": Updating the process of holdings loading
-
- Closed
-