You are here

Student Section Association Begin and End Date

Student Section Association Begin and End Date: Roster

Roster app icon

Begin Date includes month, day, and year of the student's entry or assignment to the section. End Date includes month, day, and year of the withdrawal or exit of the student from the section. The begin and end dates on the student section association should fall within the enrollment period provided in the reference.  Begin date is always required; end date is required once the student has exited the section. Dates should be entered in the format dd/mm/yyyy.

Student Section Association connects a student to a section and gathers information about the course in which the student is enrolled. Student information is pulled from looking at records attached to the student's WISEid. All primary enrollment holders of a student should report Roster information to WISEdata. Report Roster data for all periods of time when a student is/was enrolled in your school/district.

Code Description/Comments
Day Day of the month when the student entered or exited a class section
Month Month of the year when the student entered or exited a class section
Year Year when the student entered or exited a class section

USES: This data element ensures specific students will be attached to the appropriate section at the appropriate times.

collection icon

Collection

*Note, all data elements flow into WISEdata at all times, not only during specified collection snapshots.

validations icon

Related Validations & Data Elements

WISEid, Session Begin and End Date, Session Name, Courses                          

 

FAQs, Details, and Points to Note

 

  1. FAQs: For more specific information and use cases, see the Roster FAQs page.
  2. Student Taking Courses in Multiple Schools:Students sometimes take multiple courses in multiple schools, such as students enrolled in a middle school taking most classes at the middle school but also taking a class at the high school. The student's primary school (the middle school) should submit Roster data for the courses the student is taking with them. Currently the high school will not be able to send Roster data because they cannot submit Student School Associations. At this time WISEdata is not able to handle this example, so we would not expect the high school class to be sent at this time. DPI is aware that course/section Roster data will not be submitted from the example high school in this use case for the "Cross-enrolled" student.
  3. Homeschool & Private School Students: Homeschool and private students taking two or fewer classes will not have WISEids currently assigned to your district and should not be included in the Roster data submission. 
  4. Tutoring: Tutoring activities are not recorded and should not be included in the Roster data submission.

Back

Submit Feedback About This Webpage