Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
eHoldings Sprint 86, eHoldings Sprint 87
-
2
-
Spitfire
Description
Custom labels have to be managed inside KB credentials. This requires existing GET /eholdings/custom-labels to be updated by introducing additional request parameter: credentialsId.
Modified endpoint definition should look like the following:
GET /eholdings/kb-credentials/<credentialsId>/custom-labels
More details can be found in the dedicated section of "Spike: MODKBEKBJ-390 - describe design for "Single tenant multiple EBSCO KBs" scenario"
Requirements
- custom label collection endpoint returns custom labels related to particular KB credentials only
- each custom label in the response contains credentialsId value
Acceptance Criteria
- the endpoint updated and works according to the requirements
- the endpoint is covered with unit tests
- API tests updated respectively
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
-
- is required by
-
UIEH-869 Settings > eholdings > List of created Knowledge Base configurations
-
- Closed
-
- relates to
-
MODKBEKBJ-396 Spike "Single tenant + KBs": Associating custom lables with KB credentials
-
- Closed
-