Standardizing Longitudinal Student Retention Records
Establish a robust standardization framework to resolve historical SIS schema drifts and normalize cohort retention data.
Use this framework when merging disparate academic records across semesters or legacy SIS databases for institutional research. It ensures demographic consistency and privacy-compliant cohort tracking.
Role: Principal Academic Data Architect and Higher Education Systems Specialist
Context
- Educational Institution: {{institution_name}}
- Source Systems: {{source_sis_platforms}}
- Analysis Cohort Window: {{retention_cohort_window}}
- Demographic Taxonomy: {{demographic_attribute_standards}}
- Target Warehouse Schema: {{target_reporting_schema}}
- Privacy & Governance Policy: {{pii_sanitization_policy}}
Task
Develop a comprehensive data cleaning framework that reconciles legacy schema discrepancies, standardizes demographic identifiers, and resolves student enrollment status anomalies across {{retention_cohort_window}} to enable accurate longitudinal retention modeling for {{institution_name}}.
Method
- Profile ingested tables from {{source_sis_platforms}} to catalog historical schema shifts, missing keys, and column drift.
- Map disparate status codes (e.g., withdraw, leave of absence, stop-out) to unified state categories defined by {{target_reporting_schema}}.
- Establish deterministic deduplication logic using fuzzy matching across hashed IDs adhering to {{pii_sanitization_policy}}.
- Reconcile temporal demographic changes against {{demographic_attribute_standards}} to maintain longitudinal data fidelity.
- Audit credit hour accumulation records to identify and flag impossible semester progression or phantom registrations.
- Formulate deterministic rules to handle transfer credits, dual-enrollment flags, and concurrent degree programs.
- Generate validation rules and unit tests to ensure final dataset aligns with {{target_reporting_schema}}.
Constraints
- MUST maintain full idempotency so re-running cleaning scripts preserves deterministic primary keys.
- MUST NOT destroy raw historical state; all transformations must produce reversible transformation audit logs.
- Transformations must preserve null semantics between genuine zero-credit terms and unrecorded terms.
- PII handling must strictly conform to {{pii_sanitization_policy}} without unmasked token leakage.
Output format
Provide the framework across four structured sections:
- Ingestion & Schema Reconciliation Matrix (table mapping source columns to target).
- Anomaly Resolution & Deduplication Logic (numbered rules).
- State Normalization Rules (status code crosswalk).
- Post-Cleaning Data Quality Test Suite (at least 5 automated validation checks).
Self-review
- Confirm every variable ({{institution_name}}, {{source_sis_platforms}}, {{retention_cohort_window}}, {{demographic_attribute_standards}}, {{target_reporting_schema}}, {{pii_sanitization_policy}}) is meaningfully utilized.
- Verify all 4 constraints are explicitly addressed in the logic.
- Ensure no placeholder text or unexpanded templates exist.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.