DRAFT Scan In Consortial Barcode

At a glance 

 · Status: Inactive / not yet built for production use · Environment / Tags: Community Use Case · Applies consortium-wide?: Yes · Runs on: Member Alma institutions · Trigger: Staff submit a form with an item barcode · Primary outcome: Eventually, this workflow will scan in a WRLC item automatically at the circulation desk where the user is physically located. · Who receives results: The staff member submitting the form sees either a success or error message. 

 Why this exists 

 This workflow is intended to make it faster and easier for member library staff to scan in consortial items. Instead of manually determining where an item belongs, staff would enter or scan a barcode into a simple form. The workflow would then identify the item and scan it in through Alma. 

 This workflow is different from other cataloged workflows because it is not ready for rollout yet. WRLC has requested an update to the CloudApp form API so the form submission can include the user’s location. That location is needed so the item can be scanned in at the correct circulation desk automatically. 

 What it does 

 · Presents a simple form titled “Scan in Consortial Barcode.” · Collects one input from the user: Barcode . · Uses the barcode prefix to identify the owning WRLC institution. · Looks up the item in Alma; uses network-level Alma logic to retrieve item information from the owning institution. · Then accesses the user's Institution Zone in Alma; scans the item in using Alma’s item scan-in API. · Shows a success message if the scan-in step completes. · Shows an error message if the item lookup encounters an Alma error. · Currently uses a placeholder circulation desk value, so it cannot fully function as intended until user location is available from the form API. 

 Where it runs 

 · Alma IZ(s): Multiple WRLC member institutions, determined by barcode prefix and location of user · Systems touched:  Alma APIs  · Reports / queries used: None · Credentials referenced: · NZ Production - Alma APIs - Read & Write 

 How it works 

 Logic overview 

 · If the barcode maps to a WRLC institution: the workflow assigns the matching institution code and continues to item lookup. · If the item is found: the workflow retrieves bibliographic, holdings, and item data, then attempts to scan in the item. · If scan-in succeeds: the user sees a success screen. · If Alma returns an error during item lookup: the user sees an error screen with the Alma error message. 

 Artifacts produced: None. 

 Pending dependency 

 Full rollout depends on a CloudApp form API update that provides user location at form access time. This location will be used to determine the circulation desk for scan-in.