Subworkflow – Add WRLC Retention

This subworkflow applies a WRLC retention commitment to a specified item by setting the retention-related fields in Alma for a given barcode and institution.

At a glance


Why this exists

WRLC retention commitments must be recorded consistently on Alma items. For items whose bibliographic records are linked to the Network Zone, the commitment can also be represented by a 583 field on the shared bibliographic record. This subworkflow gives calling workflows a reusable way to make those updates.


What it does


Where it runs


How it works

Logic overview
  1. A calling workflow supplies Barcode and Institution Code.
  2. The workflow retrieves the item in the selected Institution Zone. It applies the WRLC retention values and saves the item. A retention note of exactly Duplicate is cleared; any other note remains.
  3. The workflow retrieves the Institution Zone bibliographic record. It proceeds with a Network Zone update only if the linked record type is NZ and the supplied institution code is not 01WRLC_SCF.
  4. For an eligible record, it retrieves the institution’s OCLC code from the WRLC Institution Information data table, retrieves the Network Zone bibliographic record, adds a 583 field, and saves the record. The field includes the OCLC code, the supplied barcode, and the workflow’s configured retention statement.
  5. After that update, the final node returns Barcode and Institution Code to the calling workflow.

If results exist

The item is marked for WRLC retention. If the bibliographic record also meets the Network Zone conditions, the workflow adds a 583 field to that record. The workflow contains no check for an existing matching 583 field before adding one.

If no results

If the bibliographic record is not linked to the Network Zone, or the institution code is 01WRLC_SCF, the Network Zone update path does not run. The item update has already been attempted, but that path has no separate final output node.

Item retrieval, item update, and the retention code nodes are configured to continue with regular output on error. The export does not establish that a missing item or failed update will be handled successfully; the calling workflow should inspect the result. An error workflow is configured, but its behavior is Unknown (not in workflow export).


Artifacts produced


Revision #4
Created 19 February 2026 20:22:50 by Jackie Saavedra
Updated 22 September 2026 18:56:52 by Jackie Saavedra