[UXPROD-4412] FOLIO SIP2 configuration Created: 11/Jan/23  Updated: 18/Jan/24

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: P3
Reporter: Tim Auger Assignee: Tim Auger
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by SIP2-162 SIP2 settings section in FOLIO UI Draft
Release: Sunflower (R3 2024)
Development Team: Volaris
PO Rank: 0

 Description   

Current situation or problem

Currently, FOLIO configuration of the SIP2 interface requires EBSCO FOLIO team members to directly edit configuration files. Since the direct edit approach doesn't have field-level validation the approach is error prone. Also, the current method of direct file editing is outside of FOLIO settings, customers are not able to configure or modify settings themselves. By creating a user interface with field-level validation within existing FOLIO settings, configuration errors can be reduced, if not eliminated, brings SIP2 configuration into alignment most other FOLIO settings and allows customer to perform self service.

In scope

Out of scope

  • n/a

Performance requirements

  • < 500 ms to save form values

User stories

Assumptions

Customers will want to maintain SIP2 configuration within FOLIO settings.

Stories

As an administrator, I need a way to create and maintain SIP2 configuration for our self-check kiosks so that I do not need to rely upon a vendor to do it for me.

As an administrator, I need a way for the settings application to validate my configuration values so that I am reassured that I have not made a mistake resulting in needless time troubleshooting.

As an administrator, I need a way for the application to have default configuration values set so that I need to modify or define the least number of values thus saving me time and effort.

As an administrator, I need the configuration elements to be logically grouped by function so that it aids in understanding how elements work together.



 Comments   
Comment by Tim Auger [ 11/Jan/23 ]

Hello Kimie Kester . I added a feature issue type to explain the background and the need. Please let me know if this meets your need and, if not, let me know what will help. I think the key to the last user story noted is following the groupings that are laid out in the configuration docs. 

Comment by Charlotte Whitt [ 29/May/23 ]

Hi Jakub Skoczen - please see this ticket. Does that some how overlap with current new work on SIP2?

Generated at Fri Feb 09 00:39:44 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.