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

SIP2: Protocol for self-checkout

    XMLWordPrintable

    Details

    • Template:
    • Epic Name:
      SIP2: Protocol for self-checkout
    • Front End Estimate:
      Small < 3 days
    • Back End Estimate:
      XXL < 30 days
    • Estimation Notes and Assumptions:
      Assuming front-end only for settings.
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      80
    • Rank: Chalmers (Impl Aut 2019):
      R1
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: MO State (MVP June 2020):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R1

      Description

      Standard Interchange Protocol (SIP, originally developed by 3M) SIP2 refers to version 2 of the protocol and it is the most commonly used communication mechanism used between an ILS and a self-check/self-service device. (See: http://www.niso.org/workrooms/sip/sip_nwi/) Even though NCIP also supports self-checkout functionality, most self service kiosks still use SIP2.

      The standard is defined at http://multimedia.3m.com/mws/media/355361O/sip2-protocol.pdf

      ARL: This must be in place from the get go. OLE partners rely on it for self-check, D2D, etc. Also, it is vital that FOLIO demonstrate that it will be standards complaint from the outset. THis really depends on the 1st libraries to adopt FOLIO. THis is very important, but could be delayed if the 1st library does not need it.

      FMID: ID492, ID493

      Scope/requirements:

      All code Apache v2 license and contributed back to FOLIO
      “Always on” service that allows longterm connection to a SelfCheck system
      Makes use of FOLIO circulation APIs

      Configuration interface allowing:

      • Tenant
      • Available collections (default “all” for initial release)
      • Logging of all access via ACS
      • Performance limiting to control loads on hardware (Stretch goal)

      Included stories representing messages are minimum for V1 support.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                magdaz Magda Zacharska
                Reporter:
                cboerema Cate Boerema
                Front End Estimator:
                Magda Zacharska Magda Zacharska
                Back End Estimator:
                Magda Zacharska Magda Zacharska
                Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:
                  Start date:
                  End date:

                    TestRail: Runs

                      TestRail: Cases