Skip to:

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

Patron cancellation does not result in request being cancelled at supplying library

Description

Iteration 1

  • Given a DCB patron request is not yet LOANED (ie, is REQUEST_PLACED_AT_BORROWING_AGENCY, PICKUP_TRANSIT, RECEIVED_AT_PICKUP, READY_FOR_PICKUP)

  • When DCB detects that

    • either the request at borrowing library no longer exists

    • or a request at the borrowing library has been CANCELLED

  • Then attempt to apply(1) patron cancellation (eg, PatronRequestCancellationStateTransition), which should

    • transition patron request at supplier to CANCELLED

    • transition the DCB request to CANCELLED

    • add audit log including preconditions and triggers met, including local and DCB states

(1) implicit: apply action attempted, completed and failed audit logs

 

Iteration 2

  • Given DCB attempts to apply the patron cancellation transition

  • When it cannot transition patron request at supplier to CANCELLED

  • Then terminate the DCB request in an ERROR state

 

Original content:

Request in admin app for title “Black January”

supplying agency: 6wdmp

borrowing side hostLMS: SLOUC

cancelled in Polaris Leap by patron w/barcode: 0026949420

Transition from Confirmed to Cancelled, Confirmed to Missing and Cancelled to Missing…this doesn’t make sense to me. But, all that matters is that the supplying side did not received cancellation of the requests/holds.

Attachments

10

Activity

Show:

Tim Auger August 13, 2024 at 2:30 AM

After this went to production, I asked a couple of customers to test and it worked as expected.

Alex Scott July 8, 2024 at 8:31 AM

Dev testing progress: Sierra patron request successfully cancelled against a Polaris supplier. Details of the request can be found in the dev admin app: https://admin.dcbdev.lsphost.com/patronRequests/827c0719-b3c2-4129-9caf-8fdefa0106f3#auditlog

Jag Goraya July 1, 2024 at 11:15 AM
Edited

DCB is not reflecting that the local supplier request is cancelled

EDIT: noting here that following other conversations, this is to be expected, as CANCELLED and subsequent DCB statues will not trigger tracking updates, so subsequent changes in downstream systems will not be polled for. The verification result audit is the best confirmation we’ll get. Instead, on a cancelled request, users of DCB Admin should interpret local request and item status as a snapshot of what they were last known to be prior to cancellation.

Alex Scott July 1, 2024 at 9:56 AM

the local supplier request also looks to be cancelled in the Folio UI:

 

Alex Scott July 1, 2024 at 9:52 AM
Edited

 

it looks like on your test case, the local request status is also unchanged - still shows in DCB’s record as CONFIRMED rather than Closed - Cancelled

The verification result audit is showing that the local supplier request is CANCELLED:

https://admin.dcbdev.lsphost.com/patronRequests/audits/71c24fb9-19e1-447a-8391-a4b91c4f0cac

Fixed

Details

Assignee

Reporter

Labels

Components

Target Version

Fix versions

Sprint

Priority

Created May 28, 2024 at 3:29 AM
Updated August 13, 2024 at 2:30 AM
Resolved August 13, 2024 at 2:30 AM