Create WRLC Long Lost CLS Data Table

At a glance


Why this exists

The Long Lost CLS workflow consists of several independent workflows that all operate on the same set of patron and loan data. Rather than querying Alma Analytics repeatedly, this workflow creates a centralized data table at the beginning of each semester containing every active Long Lost CLS item.

By establishing a single working dataset, subsequent workflows can update, enrich, and track records throughout the semester while ensuring they are all referencing the same information.


What it does


Where it runs

Alma environment

Systems touched

Reports and data sources


How it works

Logic overview
  1. A scheduled trigger starts the workflow at the beginning of a semester.
  2. The workflow identifies which semester is beginning and names the new data table accordingly.
  3. A new data table is created with all columns required for downstream Long Lost CLS processing.
  4. The workflow retrieves the current Long Lost CLS records from Alma Analytics.
  5. Loan and due dates are reformatted for reporting purposes.
  6. Each patron's home institution code is added by referencing the WRLC Institution Information table.
  7. A subworkflow retrieves the patron's home account information (Retrieve Patron Home Account Through Linked Account)
  8. All data is standardized into the LibOW data table schema.
  9. Every record is inserted into the newly created data table.
  10. WRLC HQ staff receive a confirmation email with the table name, number of imported rows, and creation timestamp.
If results exist

Each Long Lost CLS record becomes a row in the semester's data table, creating the working dataset used by downstream Long Lost CLS workflows.

If no results exist

A new data table is still created, but no rows are inserted. A confirmation email is still sent indicating that the workflow completed successfully.

Artifacts produced


Revision #2
Created 8 July 2026 13:34:52 by Jackie Saavedra
Updated 8 July 2026 13:51:20 by Jackie Saavedra