Purpose
Submits prior-year graduate records to National Student Clearinghouse StudentTracker to support postsecondary tracking and related reporting workflows.
Current state
The enabled `NSCHStudentTracker` job is batch-disabled and explicitly documented in config as a previous-year graduate upload run between September and October of the new school year. It uses the prior-year Aeries database connection, generates a tab-delimited `.CLR.txt` file with headers suppressed, and uploads it through the secure transfer path. This is strong evidence of a real seasonal production workflow, not merely a conceptual connector. Current registry state: Production / Active / Medium. Postsecondary reporting and graduate-tracking integration. Trigger / frequency: seasonal annual run between September and October..
Next step
exact business owner and annual validation checklist still need documentation. Yes - document the annual operating window, backup owner, and downstream reporting use. Integr8r shows this is intentionally pointed at the prior-year database, which is an important operational nuance.
Interfaces
Inputs- previous-year Aeries graduate records.
Outputs- National Student Clearinghouse StudentTracker.
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
- previous-year Aeries graduate records. remain the authoritative upstream inputs for this workflow.
- National Student Clearinghouse StudentTracker. 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 report details provide useful evidence, but the annual checklist and backup owner are not yet documented. Failure impact: delayed or missing graduate-tracking submissions and weaker postsecondary reporting visibility. Manual fallback: manual file generation and upload..
Observability
- Integr8r report details provide useful evidence, but the annual checklist and backup owner are not yet documented.
- Failure impact: delayed or missing graduate-tracking submissions and weaker postsecondary reporting visibility..
- Manual fallback: manual file generation and upload..
Security and privacy
secure file transfer with host-managed credentials. Classification: restricted student academic and outcome data. graduate and outcome records are sensitive student data.
Dependencies
Upstream- correct prior-year DB selection, graduation data quality, and annual timing discipline.
Downstream- National Student Clearinghouse StudentTracker.
Ownership
OwnersTechnology Services, Josh Barton / Technology Services
UsersTechnology Services, district data or postsecondary-readiness stakeholders
NSCH Student Tracker Graduate Submission
Operational Notes
- Method: prior-year Aeries SQL extract plus secure file upload.
- Implementation: Integr8r job key
NSCHStudentTracker in Config/Config.ps1, backed by NSCHStudentTracker/SQL/BOUSD-Graduates.sql. - Trigger / frequency: seasonal annual run between September and October.
- Failure impact / fallback: delayed or missing graduate-tracking submissions and weaker postsecondary reporting visibility. Manual fallback: manual file generation and upload..
- Related references:
README.md, Config/Config.ps1, NSCHStudentTracker/SQL/BOUSD-Graduates.sql.
Registry Alignment
- Mapped registry entry:
INT-064 - Registry clarified: The enabled
NSCHStudentTracker job is batch-disabled and explicitly documented in config as a previous-year graduate upload run between September and October of the new school year. - Validation gaps: exact business owner and annual validation checklist still need documentation.
