Search
Login
|
Funded by the Bill & Melinda Gates Foundation and conducted by
the Center for Educational Leadership and Technology (CELT)
Home
Building a Valid TSDL
Key TSDL Components
Use and Purpose of Teacher-Student Data Link
Data Governance Structure
Unique Student Identifier
Unique Educator Identifier
Courses and Schedules
Daily Attendance/ Membership
Assessments and Outcomes Data
Data Linkages, Flow, and Integration
Interagency Data Systems
Policies and Definitions for TSDL
TSDL Discussion Questions
Teacher of Record (TOR)
How to Use TOR Definition
TOR Framework
Data Model
Roster Verification
Quick Links
How to Use TOR Definition
Key TSDL Components
TOR Framework
Sample Data Model
TSDL Infographic
TSDL Use and Purpose
TSDL Discussion Questions
TSDL Reports/Resources
Roster Verification Resources
State Final Reports
Data Quality Campaign (DQC) Resources
Additional Resources
About TSDL Project
Project Description
Participating States
Participating School Districts
Phase I Pilot Projects
Phase I Project Brochure (.pdf)
Contact Us
Contact Information
Directory
TSDL "On the Go"
Key TSDL Components
TSDL Discussion Questions
Teacher of Record (TOR)
Data Model
Roster Verification
Home
>
Building a Valid TSDL
> Data Model
Email / Username:
*
Password:
*
Remember me.
Forgot your password?
Data Model
The data model is just one example from a transactional system perspective (normalized - operational). It shows the data elements required to support a
Teacher of Record
(TOR) definition and whether these can be gathered in a cost-effective manner.
--
Click to view the example P20W data model
--
This model focuses only on core elements and relationships required to make the teacher-student link.
Specific data needs will vary based on Teacher of Record definition and specific uses for the link.
The structure will vary based on use, e.g., normalized vs. de-normalized.
Fields such as "Birthdate” may not be required to make the link but support matching/validation/quality assurance.
Naming convention and element definitions used here generally follow Common Data Standards Initiative.
Elements identified as "NCES” should use or map to NCES options sets, e.g., NCES Service Setting Code.
The model assumes student assessment data will be linked to the student and learning standards. The assessment data and structure of that data may vary.
The model supports non-traditional linkages, e.g., "Class” could capture "Instances of Learning” outside of the traditional course-section.
Summary fields may be replaced by links to more detailed data, e.g., daily attendance details may be linked to ClassMembership instead of "Number of Days Absent” and "Number of Days In Attendance”.
>> continue
*