Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Update Settings > eholdings > Knowledgebase UI design

Description

Currently, we allow a user to set up EBSCO KB API configuration via Settings > eholdings > Knowledge base

Requirement
We want to change the design to support the following

  • User can setup EBSCO KB API configuration

  • User can remove EBSCO KB API configuration

  • User can setup multiple EBSCO KB API configurations based on Locations setup in Settings > Tenant > Location

Environment

None

Potential Workaround

None

Attachments

6

Checklist

hide

TestRail: Results

Activity

Show:

Kimie Kester December 17, 2019 at 3:13 PM

Hi I just updated the mocks to use a "larger" Save button which is more similar in size to what is seen on the bottom of the user record in the Users app.

Kimie Kester December 12, 2019 at 3:41 PM

I just made a few small edits to the mocks - moved Save button to the bottom and removed the dropdown that I had inadvertently put on the original mocks for Cust ID and API key. If you notice anything I have forgotten, let me know. Thanks!

Kimie Kester December 12, 2019 at 3:25 PM
Edited

I was thinking we could have a message at the top when the Institution has not been set up yet.

The style of the message box can be found on Storybook

Let's remove all the fields and the Save button at the bottom when there is nothing they can do on this screen and just give them the message.

Kimie Kester December 12, 2019 at 2:46 PM

Remind me again, where are they supposed to go to configure their credentials before they can set up this area?

Khalilah Gambrell December 12, 2019 at 2:38 PM

Hey , looks good to me. What should happen when library has not configured credentials? My thought is the API endpoint dropdown should have a value of null/Not selected value.

Thoughts?

Done

Details

Assignee

Reporter

Labels

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created November 6, 2019 at 5:48 PM
Updated February 5, 2020 at 5:27 PM
Resolved February 5, 2020 at 5:27 PM
TestRail: Cases
TestRail: Runs