Skip to:

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

All work

Go to all work items
Select view

Select search mode

 
50 of 431

SIP2: FOLIO Status - Startup and shutdown of SC

Done

CSP Request Details

None

CSP Rejection Details

None

CSP Approved

None

Description

FOLIO must send this message in response to a SC Status message.
Do health check of the Folio modules that will be used.
For this user story we assume that most the values are hardcoded.

Senario 1
1. Library staff starts up self-checkout system
2. Self-checkout system sends SC Status (99) message
3. FOLIO sends Status (98) message

Senario 2
1. Library staff shuts down self-checkout system
2. Self-checkout system sends SC Status (99) message
3. FOLIO sends Status (98) message

Environment

None

Potential Workaround

None

Attachments

1

Checklist

hide

TestRail: Results

Details

Assignee

Reporter

Tester Assignee

Labels

Priority

Story Points

Sprint

Parent

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created November 19, 2018 at 4:43 PM
Updated June 25, 2019 at 2:15 PM
Resolved April 9, 2019 at 3:18 PM

Activity

Show:

Martin TranApril 9, 2019 at 3:18 PM

  • Laid out basic request handling structures

  • Provided a temporary hard-coded configuration for ACS status. Values will need to be finalized

  • Used Freemarker template to generate SIP responses

  • At this moment doesn't do anything with the request. Maybe in the future we could save the SCStatus request's pertinent information, such as max print width to properly trim/format the messages, and respond dynamically to protocol version.

Martin TranApril 8, 2019 at 6:24 PM

4/8 - Developer's notes:

  • Laid out basic request handling structures

  • Provided a temporary hard-coded configuration for ACS status. Values will need to be finalized

  • Used Freemarker template to generate SIP responses

  • At this moment doesn't do anything with the request. Maybe in the future we could save the SCStatus request's pertinent information, such as max print width to properly trim/format the messages, and respond dynamically to protocol version.

patty.wanningerApril 4, 2019 at 7:36 PM

, this ticket is marked "In-reveiw," but we (the manual testing team) have no way to test it. Can you assign yourself as tester?

Magda ZacharskaApril 4, 2019 at 1:27 PM

Let's discuss the best approach and prioritize the work.

Matt RenoApril 4, 2019 at 12:13 PM

From a protocol perspective, that is true. But from a practical standpoint we cannot accept SC status without a login first in a multi-tenant setup. With Chalmers, sure they are the only one, but this wouldn't work when another tenant is on the system. Though, I think there are bigger issues here with respect to multi-tenant support.

TestRail: Cases
TestRail: Runs

Flag notifications