All work

Select view

Select search mode

 
47 of 47

SIP2: Normal Item Checkin

Done

CSP Request Details

None

CSP Rejection Details

None

CSP Approved

None

Description

Scenario

  1. Patron places item on SC

  2. SC reads item barcode

  3. SC sends Checkin Requests (09) to FOLIO

  4. FOLIO returns Checkin Response (10)

For details of each message refer to the SIP2 Protocol Definition: http://multimedia.3m.com/mws/media/355361O/sip2-protocol.pdf

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Details

Assignee

Reporter

Priority

Story Points

Sprint

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created March 21, 2019 at 2:53 AM
Updated June 25, 2019 at 2:15 PM
Resolved April 22, 2019 at 5:41 PM

Activity

Show:

Matt RenoApril 22, 2019 at 5:41 PM

See: PR #9

Matt RenoApril 12, 2019 at 1:00 PM

at some point we will need to figure out what to do with requests (checkin and others) that have the "no block" field set. This means that the transaction already occurred on the SC but the ACS was offline. When the ACS is back online, these requests are sent and they need to succeed since they already happened and the item may be outside the library. I don't know if any libraries allow the SC to operate when the ACS is offline, but it is a possibility. Perhaps the solution is we don't allow it?

I don't think we have an endpoints that will always succeed. We do have an override endpoint for renew that might be what we use for renew with "no block" set, but the checkin/checkout don't have an override endpoint.

Magda ZacharskaApril 11, 2019 at 10:00 PM

For now I would only concentrate as you suggest on the required fields only.
I'll follow up with Chalmers regarding the alert and resensitize fields. I don't think FOLIO tracks if a material is a magnetic media or not so for now I think we should set it to U.

Matt RenoApril 11, 2019 at 8:41 PM
Edited

What should we do for the following response fields (with respect to supporting Chalmers):

  • resensitize (Should we set it to Y all the time except if the checkin fails?)

  • magnetic media (Should we set it to U?)

  • alert (should we just set it to N?)

  • item identifier (SC will send the ACS a barcode as the item identifier in the Checkin message, I suspect the ACS will want to send back the barcode as the item identifier and not the UUID of the item in the Checkin Response message)

  • title identifier (should we use the instance UUID here? Its actually optional, so we can probably ignore it for now)

  • sort bin (optional, so we can probably ignore for now)

  • media type (optional, so we can probably ignore for now)

Magda ZacharskaApril 4, 2019 at 1:16 PM
Edited

Chalmers confirmed that if the item is checked in at the station at the library where the book belongs the status of the item is Available (or, if the item is requested to be picked up at this library, the status is On holdshelf)

If the item is checked in at the station at another library than that where the book belongs (or is requested to be picked up): the status is In transit

TestRail: Cases
TestRail: Runs