Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-1002

SIP2: Protocol for self-checkout - initial implementation

    XMLWordPrintable

Details

    • XXL < 30 days
    • Hide
      Assuming front-end only for settings.
      CB: Needs to be re-estimated, as the estimates for this were for BOTH NCIP and SIP2
      MMZ: Re-estimated based on the Chalmers needs. It seems that the library currently supports checking out and checking in only. All the required configuration will be handled by the back end for now.
      Show
      Assuming front-end only for settings. CB: Needs to be re-estimated, as the estimates for this were for BOTH NCIP and SIP2 MMZ: Re-estimated based on the Chalmers needs. It seems that the library currently supports checking out and checking in only. All the required configuration will be handled by the back end for now.
    • Prokopovych
    • R4
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1

    Description

      Standard Interchange Protocol (SIP) was originally developed by 3M. SIP2 (version 2 of the protocol) is the most commonly adopted by library automation vendors standard for communication between ILS and self-service kiosks.

      The specification: http://multimedia.3m.com/mws/media/355361O/sip2-protocol.pdf

      Initial implementation includes:

      • Tenant level configuration (through API calls to mod-configuration)
      • Kiosk level configuration (through API calls to mod-configuration)
      • Check-in, check-out operation
      • Support following self-service kiosk requests and FOLIO responses:
        • Login
        • Request ACS Resend
        • Patron Status
        • Patron Information
        • Check-out
        • Check-in

      TestRail: Results

        Attachments

          Issue Links

            clones

            New Feature - New feature requests UXPROD-557 NCIP: Protocol for ILL, Resource Sharing and Self Checkout

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            defines

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. UXPROD-1001 SIP2: Protocol for self-checkout

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed
            is defined by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-1 SIP2: Spike Task

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-2 SIP2: Define Edge API

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-3 SIP2: Github Project Basics

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-4 SIP2: Define Edge API

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-5 SIP2: Github Project Basics for Edge

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-8 SIP2: SC Status

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-9 SIP2: FOLIO Status - Startup and shutdown of SC

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-10 SIP2: Login

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-11 SIP2: Login - startup of SC with Sockets connection

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-12 SIP2: Request ACS Resend

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-15 SIP2: Patron Status Response

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-16 SIP2: Patron Information

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-17 SIP2: Patron Information Response

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-18 SIP2: Checkout

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-19 SIP2: Checkout Response

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-20 SIP2: Checkin

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-28 SIP2: Backend Configuration - store configs per tenant

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-30 SIP2: API test setup and cleanup

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-31 SIP2: Normal Item Checkout

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-32 SIP2: Normal Item Checkin

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-36 SIP2: Item Checkout - Item not available for checkout

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-37 SIP2: Item Checkout - Patron is not allowed to checkout item

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-38 SIP2: Encryption of the messages exchanged between SC and FOLIO

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-44 SIP2: Setup test environment for exchanging messages between SC and ASC

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SIP2-46 SIP2: Test happy path for item check in

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UXPROD-21 SIP2: Checkin Response

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UXPROD-1360 SIP2: Edge API tests

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            relates to

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. UXPROD-1764 ILL between FOLIO libraries

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Open

            New Feature - New feature requests UXPROD-1799 SIP2: Protocol for self-checkout - bug fixes and enhancements

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-1895 SIP2: Protocol for self-checkout - additional features

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open

            New Feature - New feature requests UXPROD-1898 SIP2: Protocol for self-checkout - Block Patron

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open

            New Feature - New feature requests UXPROD-1899 SIP2: Protocol for self-checkout - Fee Paid

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open

            Activity

              People

                magdaz Magda Zacharska
                cboerema Cate Boerema
                Jakub Skoczen Jakub Skoczen
                Jakub Skoczen Jakub Skoczen
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases