Student Discipline
This category carries information about student discipline incidents and disciplinary actions as published within the Student Discipline category. The Student Discipline category includes the following data views and resources:
Discipline Incident
This view captures information about discipline incidents occurring at each school as published in the DisciplineIncident resource within the Student Discipline category. The layout includes the School Name, Incident Identifier, Incident Date, Last Publish Date, and Publishing ID.
disciplineIncident
This event resource represents an occurrence of an infraction ranging from a minor behavioral problem that disrupts the orderly functioning of a school or classroom (such as tardiness) to a criminal act that results in the involvement of a law enforcement official (such as robbery). A single event (for example, a fight) is one incident regardless of how many perpetrators or victims are involved. Discipline incidents are events classified as warranting a discipline action.
Primary PowerSchool Source Data
- [S_MI_Log_GC_X]
- [Log]
Selection Criteria
Records are published if the following criteria are met:
- The school where the incident occurred must not be excluded from state reporting.
- The incident date falls within the year for the Term selected in the PowerSchool UI.
- The incident includes at least one state-reportable Behavior based on the district's BehaviorDescriptor Ed-Fi mapping.
Resource Output
- A separate DisciplineIncident record is published for each unique incident based on IncidentIdentifier that contains at least one reportable Behavior code.
- The DisciplineIncident resource is dependent on the prior publishing of the following entities: Student
- LEAs and Schools may upload (publish) data to the Ed-Fi ODS in real-time or on-demand (Run Now button).
Note: Click Export to export the data collection results to an Excel spreadsheet.
Data Element | Description | Data Type | Stored in [Table]Field | Req'd |
---|---|---|---|---|
schoolID | Relates the incident to the school where the incident occurred. | Integer | Adminunit | R |
incidentIdentifier | A locally assigned unique identifier (within the school or school district) to identify each specific incident or occurrence. The same identifier should be used to document the entire incident even if it included multiple offenses and multiple offenders. | String | [S_MI_Log_GC_X]IncidentNbr | R |
incidentDate | The month, day, and year on which the incident occurred. | Date | [Log]Discipline_IncidentDate | R |
Students / Discipline Incidents
This view captures details about student involvement in discipline incidents as published in the StudentDiscipline Association resource within the Student Discipline category. The layout includes the School Name, Student Number, Student Name, Incident Identifier, Incident Date, Incident Type, State Student Number, Last Publish Date, and Publishing ID.
studentDisciplineIncidentAssociation
This association indicates those students who were victims, perpetrators, witnesses, and/or reporters for a discipline incident.
Primary PowerSchool Source Data
- [S_MI_Log_GC_X]
- [Log]
Selection Criteria
Records are published if the following criteria are met:
- The incident must refer to an incident published in a preceding DisciplineIncident resource.
- StudentUniqueId is populated in PowerSchool.
- The student must not be excluded from state reporting.
- The school where the incident occurred must not be excluded from state reporting.
- The incident includes at least one state-reportable Behavior based on the district's BehaviorDescriptor Ed-Fi mapping.
- The incident date falls within the year for the Term selected in the PowerSchool UI.
Resource Output
- A separate StudentDisciplineIncidentAssociation record is published for each student associated with a reportable incident.
- Based on StudentParticipationCode, included students may have a role of Perpetrator, Victim, Witness, or Reporter.
- The StudentDisciplineIncidentAssociation resource is dependent on the prior publishing of the following entities: Student and DisciplineIncident.
- LEAs and Schools may upload (publish) data to the Ed-Fi ODS in real-time or on-demand (Run Now button).
Note: Click Export to export the data collection results to an Excel spreadsheet.
Data Element | Description | Data Type | Stored in [Table]Field | Req'd |
---|---|---|---|---|
disciplineIncidentReference | R | |||
/schoolID | Relates the incident to the school where the incident occurred. | Integer | Adminunit | R |
/incidentIdentifier | A locally assigned unique identifier (within the school or school district) to identify each specific incident or occurrence. The same identifier should be used to document the entire incident even if it included multiple offenses and multiple offenders. | String | [S_MI_Log_GC_X]IncidentNbr | R |
studentIdentity | StudentUniqueId - Relates the student associated with the discipline incident. | Integer | [Students]State_StudentNumber | R |
studentParticipationCodeType | The role or type of participation of a student in a discipline incident, for example, Victim, Perpetrator, Witness, Reporter. | Type | 'Perpetrator' | R |
Behavior (1-many) | O | |||
/behaviorDescriptor | This descriptor holds the categories of behavior describing a discipline incident. | Descriptor | [S_MI_Log_GC_X]IncidentType |
|
/behaviorDetailedDescription | Specifies a more granular level of detail of the behavior involved in the incident. | String | [Log]Entry |
|
followUps | O | |||
/followUpDescriptors | The follow-up and/or educational services provided to the student after the discipline incident. | Descriptor | [S_MI_Log_GC_X]IncidentExpel |
|
Discipline Action
This view captures information about the disciplinary actions associated with incidents and students as published in the DisciplineAction resource within the Student Discipline category. The layout includes the School Name, Student Number, Student Name, Incident Identifier, Incident Date, Action Taken, State Student Number, Last Publish Date, and Publishing ID.
disciplineAction
This event resource represents actions taken by an education organization after a disruptive event that is recorded as a discipline incident.
Primary PowerSchool Source Data
- [S_MI_Log_GC_X]
- [Log]
Selection Criteria
Records are published if the following criteria are met:
- The discipline action record must refer to an incident published in a preceding DisciplineIncident and StudentDisciplineIncidentAssociation entities.
- StudentUniqueId is populated in PowerSchool.
- The student must not be excluded from state reporting.
- The school where the incident occurred must not be excluded from state reporting.
- The incident and discipline action dates fall within the year for the Term selected in the PowerSchool UI.
- The incident includes at least one state-reportable Discipline based on the district's DisciplineDescriptor Ed-Fi mapping.
Resource Output
- A separate DisciplineAction record is published for each reportable action associated with at least one student for the incident for up to three actions per student, per incident.
- The DisciplineAction resource is dependent on the prior publishing of the following entities: Student, DisciplineIncident, and StudentDisciplineIncidentAssociation.
- LEAs and Schools may upload (publish) data to the Ed-Fi ODS in real-time or on-demand (Run Now button).
Note: Click Export to export the data collection results to an Excel spreadsheet.
Data Element | Description | Data Type | Stored in [Table]Field | Req'd |
---|---|---|---|---|
schoolId | School responsible for student's discipline. | Integer | Adminunit | R |
studentIdentity | StudentUniqueId - The student(s) disciplined by the discipline action. | String | [Students]State_StudentNumber | R |
identifier | DisciplineActionIdentifier - Identifier assigned by the education organization to the discipline action. | String | Generated value | R |
disciplineDate | Month, day, and year of the discipline action. | Date | [S_MI_Log_GC_X]DisciplineDate1 | R |
length | DisciplineActionLength - The length of time in school days for the Discipline Action, for example, removal, detention, if applicable. | Integer | [S_MI_Log_GC_X]DisciplineDays1 | O |
lengthDecimal | Indicates the actual length in school days of a student's disciplinary assignment. | Integer | [S_MI_Log_GC_X]DisciplineDays1 | O |
disciplineDescriptors | Type of action, such as removal from the classroom, used to discipline the student involved as a perpetrator in a discipline incident. | Descriptor | [S_MI_Log_GC_X]ActionTaken1 | O |
DisciplineIncidentReference | O | |||
/schoolID | Relates the incident to the school where the incident occurred. | Integer | Adminunit |
|
/incidentIdentifier | A locally assigned unique identifier (within the school or school district) to identify each specific incident or occurrence. The same identifier should be used to document the entire incident even if it included multiple offenses and multiple offenders. | Varchar(20) | [S_MI_Log_GC_X]IncidentNbr |
|
Student Restrain Events
This view captures information about restraint actions taken by a school or district after a disruptive discipline event. The layout includes the Student Number, Student Name, UIC, Restraint Event Identifier, Event Date, Restraint Event Type, Event Count, Last Publish Date, and Publishing ID.
restraintEvent
This event resource represents the instances where a special education student was physically or mechanically restrained due to imminent serious physical harm to themselves or others, imminent serious property destruction or a combination of both imminent serious physical harm to themselves or others and imminent serious property destruction.
Primary PowerSchool Source Data
- [S_MI_STU_SecRest_C]
Selection Criteria
Records are published if the following criteria are met:
- StudentUniqueId is populated in PowerSchool.
- The student must not be excluded from state reporting.
- The school where the restraintEvent occurred must not be excluded from state reporting.
- The restraint eventDate falls within the year for the Term selected in the PowerSchool UI.
Resource Output
- A separate restraintEvent record is published for:
- the total number of restraints that occurred on the eventDate
- the total number of seclusions that occurred on the eventDate
- The restraintEvent resource is dependent on the prior publishing of the following entities: Student.
- LEAs and Schools may upload (publish) data to the Ed-Fi ODS in real-time or on-demand (Run Now button).
Note: Click Export to export the data collection results to an Excel spreadsheet.
Data Element | Description | Data Type | Stored in [Table]Field | Req'd |
---|---|---|---|---|
schoolReference | ||||
/schoolID | The school responsible for the restraint event. | Integer | Derived from: | R |
studentReference | R | |||
/studentUniqueId | The student associated with the restraint event. | String | [Students]State_StudentNumber |
|
identifier | The identifier to the restraint event assigned by the education organization. | String | Derived from: [S_MI_STU_SecRest_C]SecludedCount [S_MI_STU_SecRest_C]RestrainedCount Seclusion: 'S' + [S_MI_STU_SecRest_C]ID is reported Restraint: 'R' + [S_MI_STU_SecRest_C]ID is reported | R |
eventDate | Month, day, and year of the restraint event. | Date | [S_MI_STU_SecRest_C]SecRestDate | R |
restraintEventRestraintCategory | ||||
/restraintCategoryDescriptor | Indicates whether the event was seclusion or restraint. | String | Derived from: [S_MI_STU_SecRest_C]SecludedCount [S_MI_STU_SecRest_C]RestrainedCount Seclusion: '01' is reported Restraint: '02' is reported | R |
/eventCount | Indicates the total number of times the restraint category event occurred on the event date. | Integer | [S_MI_STU_SecRest_C]SecludedCount [S_MI_STU_SecRest_C]RestrainedCount | R |