Atlas project production

CCGI Data Integration and Validation Pipeline

Synchronizes district data with CCGI and supports transcript, graduation, and validation work needed for college and career readiness records.

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

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

Purpose

Synchronizes district data with CCGI and supports transcript, graduation, and validation work needed for college and career readiness records.

Current state

Integr8r materially strengthens this entry. The enabled `CCGI` job generates `student.csv`, `course_grade.csv`, `test_grade.csv`, `manifest.csv`, `graduates.csv`, and `course_catalog.csv` from dedicated SQL files, then uploads them in a deliberate sequence where the manifest is last because it triggers downstream processing. The `BOUSD-CCGI-Student.sql` export also shows concrete data elements such as CDS code, State ID, GPA, parent consent, race fields, enrollment dates, and district-assigned student email. This confirms a production-grade file submission pipeline rather than only a vague validation workflow. Current registry state: Production / Active / Mission Critical. Postsecondary-readiness data integration, transcript and validation workflow. Trigger / frequency: recurring submission windows and validation cycles [validate exact scheduler and operational calendar]..

Next step

exact schedule, validation owner, and retry expectations are still not centralized in one SOP. Yes - capture exact schedule windows, runbook steps, and correction ownership. The manifest-last upload ordering is important because the config notes it acts as the processing trigger.

Interfaces

Inputs

Aeries SIS, transcript and course data, graduation-related logic, and consent state.

Outputs

CCGI.

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, transcript and course data, graduation-related logic, and consent state. remain the authoritative upstream inputs for this workflow.
CCGI. 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 file-generation checks and ordered upload sequencing are concrete runtime controls, but the end-to-end runbook and alerting model still need documentation. Failure impact: inaccurate college-readiness records, transcript representation issues, and more manual correction burden. Manual fallback: manual data review, manual vendor follow-up, and correction cycles..

Observability

Integr8r file-generation checks and ordered upload sequencing are concrete runtime controls, but the end-to-end runbook and alerting model still need documentation.
Failure impact: inaccurate college-readiness records, transcript representation issues, and more manual correction burden..
Manual fallback: manual data review, manual vendor follow-up, and correction cycles..

Security and privacy

secure vendor file transfer and district-admin controls. Classification: restricted student academic records. transcript and outcome data are highly sensitive student records.

Dependencies

Upstream

Aeries data quality, course mapping accuracy, transcript logic, and secondary-site coordination.

Downstream

CCGI.

Ownership

Owners

Technology Services with counseling and secondary administration, Josh Barton / Technology Services

Users

Technology Services with counseling and secondary administration, BOHS, BCHS, BJHS counseling and college or career readiness stakeholders

CCGI Data Integration and Validation Pipeline

Operational Notes

Method: SQL-based multi-file extract, secure file upload, and manifest-trigger processing.
Implementation: Integr8r job key CCGI in Config/Config.ps1 with SQL under CCGI/SQL/ and ordered upload behavior in the config.
Trigger / frequency: recurring submission windows and validation cycles [validate exact scheduler and operational calendar].
Failure impact / fallback: inaccurate college-readiness records, transcript representation issues, and more manual correction burden. Manual fallback: manual data review, manual vendor follow-up, and correction cycles..
Related references: README.md, Config/Config.ps1, CCGI/SQL/, docs/automation-integration-architecture.md, docs/technology-ecosystem-overview.md, Weekly Reports/Perpetual Weekly Reports.md, research/weekly-reports-presentation-enrichment-2024-2026.md.

Registry Alignment

Mapped registry entry: INT-026
Registry clarified: Integr8r materially strengthens this entry.
Validation gaps: exact schedule, validation owner, and retry expectations are still not centralized in one SOP.