Introduction
This guide explains the Edlink Education Data Model: how districts, schools, people, coursework, schedules, attendance, and supporting types relate to each other. The model is designed to support the varying options that Learning Management Systems and Student Information Systems provide.
For design guidance when building integrations, see Design Considerations, Identifiers, Code Mappings, and Dates.
The following diagram shows how the seven API groups connect:
Before reading category-specific pages, it helps to understand the cardinalities of data models. Technically, cardinality is the numerical relationship between rows of one table and rows in another.
One-To-Many
For example, a district can have many schools, but each school belongs to one district. We describe this relationship as a one-to-many relationship.
One-To-One
In the United States, you can only be married to one person at a time. We describe this relationship as a one-to-one relationship.
Many-To-Many
Another type of relationship is group membership. A person can belong to many groups, and each group can have many members. We describe this relationship as a many-to-many relationship.
Symbols
We use the following symbols to represent these relationships in our category diagrams. More specific symbols represent the relationships more accurately, but we will ignore those other details for simplicity.
Explore By Category
Each API reference group has its own page with an ER diagram and model descriptions:
- Rostering — districts, schools, people, courses, classes, and enrollments
- Scheduling — calendars, school years, periods, and bell schedules
- Attendance — meetings, attendance records, and code mappings
- School Operations — facilities, rooms, assets, fees, and incidents
- Coursework — assignments, modules, submissions, and class content
- Transportation — routes, stops, and vehicles