Project Atlas AetherDev project hub
Atlas project production

TransTraks Student Export

Generates a student demographic and contact export for a TransTraks downstream workflow.

Internal-only entry. Do not publish externally without review.
Type
System
Lifecycle
Active
Last touched
2026-03-26
Visibility
Internal

Purpose

Generate a student demographic/contact export for a TransTraks-related downstream workflow while preserving strict validation around delivery status.

Current state

Repo evidence now supports a more specific stance: `TransTraks` is enabled in `Config/Config.ps1`, uses `BOUSD-TransTraks-Students.sql`, and builds a `users.csv` contract with explicit demographic, address, guardian, phone, grade, school, language, and handicap fields plus default-fallback values for blanks. `BatchRunEnabled` is not explicitly set, and Integr8r runner docs indicate omitted values default to batch-enabled. Scheduler artifact evidence now shows `Integr8r - Batch` task presence on `saw-01.bousd.us` invoking `C:\Integr8r\Integr8r.ps1` at two daily start boundaries (07:00 and 17:00), which likely covers this batch-default job. This establishes technical runtime/operator context for export generation on `saw-01`, but not downstream delivery authority. Delivery remains unresolved because job-level `UploadData` is disabled and SFTP values are placeholder-level, even though the broader runner supports upload workflows.

Next step

Close remaining governance fields through the [Owner, Escalation, and Fallback Matrix](../owner-escalation-and-fallback-matrix/): downstream destination/sign-off owner, upload activation authority, manual-delivery fallback operator, and escalation owner while upload stays disabled.

Interfaces

Inputs
  • Aeries SIS demographic and contact data
Outputs
  • TransTraks `users.csv` export artifact

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 demographic and contact data remain the authoritative upstream inputs for this workflow.
  • TransTraks or related downstream workflow [validate] 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.

Operational notes

Reliability posture

Export generation is strongly evidenced (`Enabled = $True`, SQL file present, explicit `users.csv` file contract), and runtime host/scheduler context is now partially evidenced via Integr8r on `saw-01.bousd.us`. Delivery remains unresolved because job-level `UploadData = $False` and transport settings are placeholder-level in config.

Observability

  • Integr8r main runner logs (`logs/main.log`)
  • File-generation evidence under `TransTraks/DATA/users.csv` when run
  • Config-state evidence in `Config/Config.ps1` (`UploadData = $False`)

Security and privacy

no active upload path is currently configured; placeholder transfer settings remain in config. Classification: restricted student operational data. student demographic and contact data.

Dependencies

Upstream
  • Aeries data quality and downstream business process validation
Downstream
  • TransTraks or related downstream workflow [validate]

Ownership

Owners

Technology Services

Users

Technology Services, transportation or student-services stakeholders

TransTraks Student Export

Operational Notes

  • Method: Aeries SQL export with configurable SFTP delivery currently disabled in repo config.
  • Implementation: Integr8r job key TransTraks in Config/Config.ps1 and TransTraks/SQL/BOUSD-TransTraks-Students.sql.
  • SQL shaping includes explicit fallback defaults for missing address/phone fields, indicating a downstream consumer that expects non-null string values.
  • Trigger / frequency: enabled job; BatchRunEnabled is omitted, so runner behavior defaults to batch-enabled per repo docs. Windows Task Scheduler artifact evidence on saw-01 shows an active Integr8r - Batch task with two daily start boundaries (07:00 and 17:00), providing stronger cadence context for this job family.
  • Failure impact / fallback: failure primarily risks stale downstream export data; with upload disabled, fallback is manual delivery handling, but execution owner, approval authority, and escalation owner are not documented.
  • Governance note: unresolved role fields are tracked in the Owner, Escalation, and Fallback Matrix.
  • Related references: README.md, Config/Config.ps1, TransTraks/SQL/BOUSD-TransTraks-Students.sql.

Registry Alignment

  • Mapped registry entry: INT-069
  • Registry clarified: Integr8r contains an enabled TransTraks job with BOUSD-TransTraks-Students.sql producing users.csv from Aeries student, address, guardian, phone, grade, school, language, and handicap fields.
  • Validation gaps: runtime host/task presence and export-generation behavior are now strongly evidenced; unresolved destination/sign-off/fallback/escalation fields are tracked in the Owner, Escalation, and Fallback Matrix, including upload-activation authority and approved transfer method.