Student Attendance Information

Core Conceptual Architecture

 

High-level structure:

Student

 └── StudentSchoolAssociation

      └── StudentSchoolAttendance Events

 

Attendance records require:

  • StudentSchoolAssociation
  • Calendar dates
  • Section associations (optional)

 

Critical Architectural Principle

Ed-Fi separates:

  • school membership
  • instructional attendance events.

This distinction is extremely important.

Student School Attendance Events – Guidance:

This is the primary daily attendance entity.

 

It models:

student attendance at the school level.

Typical Use Cases

  • Full-day attendance
  • Half-day absence
  • Excused/unexcused absence

 

Days are reported in half-day instances, so for example:

 

  • Student attends the whole school day – report a single StudentSchoolAttendanceEvents record with a AttendanceEventCategoryDescriptor of ‘In Attendance’ and a EventDuration of 1.00

     

  • Student attends a half school day and absent the other half – report two separate StudentSchoolAttendanceEvent records.
    • One with the AttendanceEventCategoryDescriptor of “In Attendance’ and a EventDuration of .50
    • One with the AttendanceEventCategoryDescriptor of ‘Excused/Unexcused Absence’ and a EventDuration of .50

This event entity represents the recording of whether a student is in attendance for a school day.

 

Student School Attendance Events - Fields:

Contact Us

Questions or Comments

keds@ksde.gov

KEDS Guidance Document

KEDS 4.0.00 Guidance Document v1.0