Atlas project production

Follett Destiny Patron Import

Generates and imports patron records into Follett Destiny so student library accounts stay aligned to current SIS data.

Internal-only entry. Do not publish externally without review.

Type: System
Lifecycle: Active
Last touched: 2026-03-24
Visibility: Internal

Purpose

Generates and imports patron records into Follett Destiny so student library accounts stay aligned to current SIS data.

Current state

The enabled `Destiny` job exports `patrons.csv` from `BOUSD-FollettDestiny-Students.sql`, converts the file to XML with Follett's command-line converter, and then uploads it with `UpdatePatrons.exe`. This is one of the clearest examples in Integr8r of a vendor-specific command-line workflow rather than a generic SFTP upload. Current registry state: Production / Active / Medium. Library-platform integration. Trigger / frequency: enabled production workflow [validate exact scheduler]..

Next step

exact scheduler and recovery steps need documentation. Yes - document the current scheduler, support owner, and vendor CLI upgrade procedure.

Interfaces

Inputs

Aeries SIS student, school, teacher, room, and contact fields.

Outputs

Follett Destiny.

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Not in scope.

Automation Engines

Not in scope.

Human Interfaces

Not in scope.

Operational Adoption

Not in scope.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Data integrity and contracts

Source of truth rules

Aeries SIS student, school, teacher, room, and contact fields. remain the authoritative upstream inputs for this workflow.
Follett Destiny. should be treated as downstream copies, recipients, or operational consumers rather than the authoring system.

Safe handling

Protect credentials, generated files, logs, and any transient export artifacts.
Treat student identifiers, rosters, and related records as FERPA-restricted data.
Limit staff identity, employment, or account data to approved administrators and business owners.

Operational notes

Reliability posture

Integr8r logging plus vendor CLI behavior provide some operational traceability, but formal retry and error-report routing are not documented. Failure impact: stale patron records and more manual library-account maintenance. Manual fallback: manual import through Destiny admin tooling..

Observability

Integr8r logging plus vendor CLI behavior provide some operational traceability, but formal retry and error-report routing are not documented.
Failure impact: stale patron records and more manual library-account maintenance..
Manual fallback: manual import through Destiny admin tooling..

Security and privacy

vendor-provided command-line tooling and locally managed configuration files. Classification: restricted student operational data. FERPA-relevant student and guardian contact data.

Dependencies

Upstream

Aeries data quality and vendor CLI compatibility.

Downstream

Follett Destiny.

Ownership

Owners

Technology Services, Josh Barton / Technology Services

Users

Technology Services, library or site media-center stakeholders

Follett Destiny Patron Import

Operational Notes

Method: Aeries SQL export plus vendor-specific CLI conversion and upload.
Implementation: Integr8r job key Destiny, Destiny/SQL/BOUSD-FollettDestiny-Students.sql, Destiny/cmdline/PatronImportConverter.exe, and Destiny/cmdline/UpdatePatrons.exe.
Trigger / frequency: enabled production workflow [validate exact scheduler].
Failure impact / fallback: stale patron records and more manual library-account maintenance. Manual fallback: manual import through Destiny admin tooling..
Related references: README.md, Config/Config.ps1, Destiny/SQL/BOUSD-FollettDestiny-Students.sql, Destiny/cmdline/.

Registry Alignment

Mapped registry entry: INT-061
Registry clarified: The enabled Destiny job exports patrons.csv from BOUSD-FollettDestiny-Students.sql, converts the file to XML with Follett’s command-line converter, and then uploads it with UpdatePatrons.exe.
Validation gaps: exact scheduler and recovery steps need documentation.