CEDS Alignment and Crosswalk
Create a shared vocabulary across local systems, standards, and data exchanges.
Crosswalking documents how a local field, definition, code set, or relationship corresponds to another model. Done well, it makes integration decisions visible, testable, and maintainable instead of burying them in one-off scripts.
Four Different Layers
CEDS
A broad education vocabulary, option sets, models, and tools for aligning data across P–20W domains.
Primary role: shared definitions and reference models.
Ed-Fi
A CEDS-aligned K–12 data standard and exchange ecosystem built around an operational model.
Primary role: operational interoperability and APIs.
OneRoster
A 1EdTech standard for exchanging roster, gradebook, and resource information through CSV or REST services.
Primary role: defined exchanges between systems.
Local Systems
The SIS, LMS, assessment, HR, and reporting schemas where district data is created and managed.
Primary role: operational source and destination data.
Architecture check: These layers do not have to form one fixed pipeline. A district may map a local SIS directly to OneRoster, use Ed-Fi as an operational exchange layer, align a data dictionary to CEDS, or combine these approaches. Start with the business purpose and required exchange—not a predetermined technology chain.
Understand the Standards Landscape
Before mapping fields, establish what each standard covers and which version the project will use.
Begin with the integration question
- What decision, service, report, or application exchange must the data support?
- Which system is authoritative for each concept?
- Who is permitted to receive the data?
- Does the project require vocabulary alignment, operational storage, or a defined exchange format?
Inventory the source and target
Record system, database, table or resource, field name, definition, data type, length, allowable values, keys, null behavior, and ownership. Capture the source and target versions before comparing them.
Choose the appropriate reference
Use CEDS when…
You need shared definitions, option sets, a broad P–20W reference, data-dictionary alignment, or comparisons across collections and systems.
Use Ed-Fi when…
You need a CEDS-aligned operational K–12 model and standardized API-based exchanges.
Use OneRoster when…
You need a defined CSV or REST exchange for rostering, gradebook, or resource services supported by participating systems.
Retain local definitions when…
A local concept has no appropriate standard equivalent. Document the extension and its intended scope rather than forcing a false match.
Build the Crosswalk
A useful crosswalk records semantics, structure, code translations, transformation rules, unresolved gaps, and ownership—not just similar-looking field names.
Create or upload the data dictionary
CEDS Align can create or upload a data dictionary and associate local property names, definitions, and option sets with CEDS properties. Begin with a bounded domain or exchange rather than attempting the entire SIS at once.
Document field-level decisions
| Concept | Local SIS example | CEDS reference | Possible exchange target | Decision |
|---|---|---|---|---|
| Student identifier | student_id | Student identifier property | Ed-Fi student unique identifier or OneRoster user sourcedId | Define key strategy |
| Name | first_name, last_name | Person name properties | Target given and family name fields | Usually direct |
| Grade level | grade_code | Grade-level option set | Target grade descriptor or code | Translate codes |
| Section | section_id | Course-section concepts | Ed-Fi section or OneRoster class | Compare structure |
| Enrollment | Schedule or roster row | Person-to-course-section relationship | Target enrollment or association | Define dates and roles |
| Academic term | term_code | Session and term concepts | Target session or academic-session type | Map hierarchy |
Record transformations and gaps
- Preserve the source value and document every transformation.
- Version code maps for grades, roles, terms, demographic options, and status values.
- Document one-to-many, many-to-one, derived, conditional, and unmapped relationships.
- Identify local extensions explicitly instead of disguising them as standard elements.
- Assign an owner and approval status to each unresolved semantic question.
Validate and Govern
A mapping is not complete when every row has a target. It is complete when the exchange preserves intended meaning, passes technical checks, and has an accountable change process.
Technical validation
- Required fields and relationships are present.
- Types, lengths, formats, and cardinality are valid.
- Identifiers remain stable and unique.
- Code values conform to the chosen version.
Semantic validation
- Business owners agree with the mapped meaning.
- Counts and distributions are plausible.
- Representative records survive round-trip review.
- Important distinctions are not lost in translation.
Test from totals to individual records
- Compare source and target record counts by school, role, grade, term, and status.
- Review null rates, invalid code rates, duplicates, and rejected records.
- Trace a small set of representative records end to end.
- Ask operational staff to review ambiguous definitions and exceptions.
- Record known limitations before production use.
Treat crosswalks as governed assets
- Record the source, target, and vocabulary versions.
- Use change control for mapping and code-set revisions.
- Retain test evidence and approval history.
- Review mappings when the SIS, standard, vendor interface, or reporting purpose changes.
- Retire obsolete mappings without erasing the history needed to explain prior exchanges.
Success looks like traceability: A future analyst should be able to determine where a target value came from, which rule transformed it, which standard version defined it, who approved the decision, and which tests demonstrated that it worked.
Why Alignment Work Matters
Less reinvention
Reusable definitions and mappings reduce repeated interpretation across projects.
Better quality
Explicit rules expose code mismatches, missing values, and inconsistent meaning earlier.
Faster onboarding
Standards-aware systems can begin from documented mappings instead of undocumented scripts.
Stronger governance
Versioned crosswalks create an auditable record of how data meaning changes over time.
Use the Authoritative Standards
Confirm current properties, versions, implementation rules, and conformance requirements before building a production exchange.