Purpose
A PowerShell workflow updates Aeries CSE records from SEIS Student.csv and emails a detailed summary. A SQL query exports Aeries student data in the SEIS Student.csv layout.
Current state
Last touched: 2025-08-13. Functionality and completeness: Example sync script exists; full operational runbook is pending.
Next step
Add baseline automated tests to cover critical flows; Add CI pipeline for build/test/lint; Document deployment/runtime environment (or add Dockerfile); Document interfaces (CLI flags, API endpoints, file formats); Add structured logging and basic health checks.
Interfaces
Inputs- Aeries SQL Server CSE/STU/SSD tables
- SEIS Student.csv export
- Aeries SQL Server tables
- SMTP settings for notifications
Outputs- Aeries CSE updates, SEIS export CSV fields, HTML email report, log file
Reality to Action trace
Reality IngestionContributes in this stage.
Canonical StorageNot in scope.
Automation EnginesContributes in this stage.
Human InterfacesNot in scope.
Operational AdoptionContributes in this stage.
Core workflow
TBD. Document the 5-10 steps that define the core workflow.
Artifacts
- SEIS Student.csv fields map to Aeries CSE columns; SQL export defines SEIS fields such as LocalID, SSID, name, ethnicity/race, and guardian contacts
Operational notes
Constraints and scars
- Requires accurate SEIS CSV formatting and stable Aeries CSE schema.
Reliability posture
Failure modes and safe behavior: SQL connection failures or CSV mismatches abort updates; debug mode disables writes and increases report detail. Idempotency / retries / batching behavior: Re-running updates based on SEIS data; no retries.
Observability
- Logs: Script log file plus optional verbose/debug output
- Metrics/health checks: None documented
- Logs: PowerShell script writes a log file and can email summary reports.
Security and privacy
Script contains placeholders for SQL/SMTP credentials and email recipients; store real credentials securely and avoid committing them.
Ownership
OwnersJosh Barton
UsersJosh Barton (owner)
SEIS-Aeries-Examples
Architecture & Major Components
High-level diagram (text):
- Entry/trigger -> core logic -> outputs (details per docs below)
Entry/trigger
→core logic
→outputs
Entry points: SEIS-Aeries-Examples/Modify-Students-Aeries-From-SEIS.ps1
Top-level folders: none (files only)
Key abstractions: Configured input path for SEIS Student.csv, apply-updates toggle, skip list for known IDs, and HTML email report sections
Setup / Build / Run
- Build system(s): None (PowerShell + SQL).
- Update configuration variables (SQL/SMTP/paths), then run the PowerShell script.