Purpose
Exports current student demographic and residence data from Aeries into DecisionInsite for planning and demographic-analysis workflows.
Current state
The enabled `DecisionInsite` job generates `bousd-students-current.csv` from `BOUSD-DecisionInsite-Students.sql` and uploads it through the Integr8r secure transfer path. The SQL fields show a planning-oriented data contract centered on grade, race or ethnicity, and residence address information. This is strong evidence of a live vendor export, not just a planning note. Current registry state: Production / Active / Medium. Enrollment-planning and demographic analysis export. Trigger / frequency: enabled but batch-disabled, suggesting a separately scheduled or operator-run job..
Next step
exact planning use case and business owner should be documented. Yes - confirm current planning reports and business owner relying on the DecisionInsite feed.
Interfaces
Inputs- Aeries SIS student identity, school, grade, and address data.
Reality to Action trace
Reality IngestionContributes in this stage.
Canonical StorageNot in scope.
Automation EnginesNot in scope.
Human InterfacesNot in scope.
Operational AdoptionNot 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 identity, school, grade, and address data. remain the authoritative upstream inputs for this workflow.
- DecisionInsite. 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
Integr8r file-generation checks provide some runtime control, but scheduler and downstream reconciliation are not yet documented. Failure impact: stale planning data and weaker demographic-analysis visibility. Manual fallback: manual export and upload..
Observability
- Integr8r file-generation checks provide some runtime control, but scheduler and downstream reconciliation are not yet documented.
- Failure impact: stale planning data and weaker demographic-analysis visibility..
- Manual fallback: manual export and upload..
Security and privacy
secure vendor transfer with host-managed credentials. Classification: restricted student demographic data. FERPA-relevant demographic and residence data.
Dependencies
Upstream- current address quality and vendor ingest expectations.
DownstreamOwnership
OwnersTechnology Services, Josh Barton / Technology Services
UsersTechnology Services, district planning and enrollment stakeholders
DecisionInsite Student Demographics Export
Operational Notes
- Method: Aeries SQL extract plus secure file upload.
- Implementation: Integr8r job key
DecisionInsite in Config/Config.ps1 and DecisionInsite/SQL/BOUSD-DecisionInsite-Students.sql. - Trigger / frequency: enabled but batch-disabled, suggesting a separately scheduled or operator-run job.
- Failure impact / fallback: stale planning data and weaker demographic-analysis visibility. Manual fallback: manual export and upload..
- Related references:
README.md, Config/Config.ps1, DecisionInsite/SQL/BOUSD-DecisionInsite-Students.sql. - Related Atlas pages: perpetual data reports portal
Registry Alignment
- Mapped registry entry:
INT-060 - Registry clarified: The enabled
DecisionInsite job generates bousd-students-current.csv from BOUSD-DecisionInsite-Students.sql and uploads it through the Integr8r secure transfer path. - Validation gaps: exact planning use case and business owner should be documented.
