Details
-
New Feature
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
-
Medium < 5 days
-
XL < 15 days
-
XXL < 30 days
-
Spitfire
-
-
R5
-
R5
-
R5
-
R5
-
R1
-
R1
-
R2
-
R5
-
R5
-
R5
Description
- Support a single tenant with multiple libraries that have multiple EBSCO KB API credentials.
- The following apps and components must be updated:
- eholdings
- Agreements
- Notes
- Tags
In Progress Documentation: https://docs.google.com/presentation/d/1qRvA-bLgGvZaY3-YgWvz64lo44Od6Y8kzDBBNTqUKi8/edit#slide=id.p
TestRail: Results
Attachments
Issue Links
- is defined by
-
MODCXEKB-103 Storing multiple EBSCO KBs in one tenant > Ensure Codex is not broken
-
- Closed
-
-
MODKBEKBJ-347 SPIKE: Design high-level flows and diagrams for tenant management functionality.
-
- Closed
-
-
MODKBEKBJ-358 SPIKE: Investigate OKAPI request routing implementation
-
- Closed
-
-
MODKBEKBJ-382 PoC: multi-tenancy support
-
- Closed
-
-
MODKBEKBJ-383 PoC MTS: create simple tenant resolution component
-
- Closed
-
-
MODKBEKBJ-390 Spike: describe design for "Single tenant multiple EBSCO KBs" scenario
-
- Closed
-
-
MODKBEKBJ-393 Spike "Single tenant + KBs": Managing KB Credentials in MOD KB EBSCO module
-
- Closed
-
-
MODKBEKBJ-394 Spike "Single tenant + KBs": Assigning users to KB credentials
-
- Closed
-
-
MODKBEKBJ-395 Spike "Single tenant + KBs": Associating access status types with KB credentials
-
- Closed
-
-
MODKBEKBJ-396 Spike "Single tenant + KBs": Associating custom lables with KB credentials
-
- Closed
-
-
MODKBEKBJ-397 Spike "Single tenant + KBs": Associating root proxy with KB credentials
-
- Closed
-
-
MODKBEKBJ-398 Spike "Single tenant + KBs": Updating existing endpoints for providers/packages/resources/titles
-
- Closed
-
-
MODKBEKBJ-399 Spike "Single tenant + KBs": Data migration
-
- Closed
-
-
MODKBEKBJ-400 Spike "Single tenant + KBs": Updating the process of holdings loading
-
- Closed
-
-
MODKBEKBJ-402 Update GET /eholdings/access-types to support multiple KB credentials
-
- Closed
-
-
MODKBEKBJ-403 Update POST /eholdings/access-types to support multiple KB credentials
-
- Closed
-
-
MODKBEKBJ-404 Update GET /eholdings/access-types/{id} to support multiple KB credentials
-
- Closed
-
-
MODKBEKBJ-405 Update PUT /eholdings/access-types/{id} to support multiple KB credentials
-
- Closed
-
-
MODKBEKBJ-406 Update DELETE /eholdings/access-types/{id} to support multiple KB credentials
-
- Closed
-
-
MODKBEKBJ-407 Single Tenant + Multiple KBs: Prepare data migration scripts for Access Types
-
- Closed
-
-
MODKBEKBJ-408 Support GET /eholdings/kb-credentials/{credId}/users to retrieve users associated with KBs
-
- Closed
-
-
MODKBEKBJ-410 Support POST /eholdings/kb-credentials/{credId}/users to associate user with KB
-
- Closed
-
-
MODKBEKBJ-411 Support PUT /eholdings/kb-credentials/{credId}/users/{userId} to update details of user associated with KB
-
- Closed
-
-
MODKBEKBJ-412 Support DELETE /eholdings/kb-credentials/{credId}/users/{userId} to remove association between user and KB
-
- Closed
-
-
MODKBEKBJ-413 Update mapping and filtering by access types for packages and resources
-
- Closed
-
-
MODKBEKBJ-414 Update GET /eholdings/custom-labels to support multiple KB credentials
-
- Closed
-
-
MODKBEKBJ-415 Update PUT /eholdings/custom-labels to support multiple KB credentials
-
- Closed
-
-
MODKBEKBJ-416 Update GET /eholdings/proxy-types to support multiple KB credentials
-
- Closed
-
-
MODKBEKBJ-417 Update GET /eholdings/root-proxy to support multiple KB credentials
-
- Closed
-
-
MODKBEKBJ-418 Update PUT /eholdings/root-proxy to support multiple KB credentials
-
- Closed
-
-
MODKBEKBJ-419 Support GET /eholdings/kb-credentials to retrieve KB credentials list
-
- Closed
-
-
MODKBEKBJ-420 Support POST /eholdings/kb-credentials to create new KB credentials entry
-
- Closed
-
-
MODKBEKBJ-421 Support GET /eholdings/kb-credentials/{credentialsId} to retrieve particular KB credential entry
-
- Closed
-
-
MODKBEKBJ-422 Support PUT /eholdings/kb-credentials{credentialsId} to update existing KB credentials entry
-
- Closed
-
-
MODKBEKBJ-423 Support DELETE /eholdings/kb-credentials/{credentialsId} to delete KB credentials entry
-
- Closed
-
-
MODKBEKBJ-424 Support GET /eholdings/user-kb-credential to retrieve KB credentials entry for user
-
- Closed
-
-
MODKBEKBJ-425 Support holdingsIQ client library to work with mod-kb-ebsco-java
-
- Closed
-
-
MODKBEKBJ-427 Update GET /loadHoldings/status to support getting status for certain credentials
-
- Closed
-
-
MODKBEKBJ-428 Set loading status "Not Started" on KB Credentials creation
-
- Closed
-
-
MODKBEKBJ-429 Support POST /eholdings/loading/kb-credentials/{credentialsId} to load holdings for certain KB Credentials
-
- Closed
-
-
MODKBEKBJ-430 Support POST /eholdings/loading/kb-credentials to load holdings for all KB Credentials
-
- Closed
-
-
MODKBEKBJ-431 Create data migration script(s)
-
- Closed
-
-
MODKBEKBJ-432 Modify configuration routine to support user related KB credentials
-
- Closed
-
-
MODKBEKBJ-433 Update RMAPITemplate to use new configuration routine
-
- Closed
-
-
MODKBEKBJ-434 Apply credentials to services that work with local data of packages, providers, resources, titles
-
- Closed
-
- relates to
-
UIEH-810 Ability to view multiple institutions eholdings app
-
- Closed
-
-
UIEH-857 New/Edit Assign users page: Allow a user to assign a user(s) to an EBSCO KB
-
- Closed
-
-
UIEH-869 Settings > eholdings > List of created Knowledge Base configurations
-
- Closed
-
-
UIEH-870 eholdings app: Validate user access to eholdings and affiliated EBSCO KB credentials.
-
- Closed
-
-
UIEH-871 eholdings app: Access denied messaging
-
- Closed
-
-
UIEH-879 Settings > eholdings > Fetch Knowledge Base configurations collection
-
- Closed
-
-
UIEH-881 Settings > eholdings > Update endpoints for Root Proxy, Custom Labels and Access Status Types
-
- Closed
-
-
UIEH-899 Settings > eholdings > KB credentials page | UI updates
-
- Closed
-
-
UIEH-900 Settings > eholdings > Assigned Users > Attempting to add a user to a second set of credentials results in a length loading indicator
-
- Closed
-
-
MODKBEKBJ-331 SPIKE - How to store multiple HoldingsIQ/RM API credentials in mod-configuration
-
- Closed
-
-
MODKBEKBJ-332 SPIKE: Supporting notes, tags, agreements, licenses for institutions in a consortia
-
- Closed
-
- requires
-
UIEH-855 Settings | eholdings | Knowledge base | Add a Name field
-
- Closed
-
-
UIEH-856 Settings > eholdings > Ability to create multiple Knowledge base configurations
-
- Closed
-
-
UIEH-885 Settings > eholdings > Updates to the second and third panes
-
- Closed
-
- links to