Student Discipline
This category carries information about student discipline incidents and disciplinary actions as published within the Student Discipline category. The Student Discipline Data category includes the following data views and resources:
Discipline Incident
This data view captures a detailed list of Discipline Incidents successfully published to the ODS. This 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 discipline action. The layout includes the School Name, Incident Identifier, Incident Date, Last Publish Date, Publishing ID, and Resource ID.
disciplineIncidents
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 discipline action.
Primary PowerSchool Source Data
- [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.
Entity Output
- A separate disciplineIncident record is published for each unique incident based on incident identifier that contains at least one reportable behavior code.
- The disciplineIncident resource is dependent on the prior publishing of the following resources: schools.
- 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 A reference to the related School resource. | R | |||
/schoolId | Relates the incident to the school where the incident occurred. | Integer | Derived from: | 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 | NEED INFO | R |
incidentDate | The month, day, and year on which the incident occurred. | Date | [Log]IncidentDate | R |
incidentLocationType | Identifies where the incident occurred and whether or not it occurred on campus. | String | [Log]incidentLocation, if populated Otherwise: 'On campus' | O |
incidentDescription | The description of the incident. | String | [Log]IncidentDescription | O |
disciplineIncidentBehavior An unordered collection of disciplineIncidentBehaviors. The categories of behavior describing a discipline incident | ||||
/behaviorDescriptor | This descriptor holds the categories of behavior describing a discipline incident. | String | When [S_IN_LOG_X]Event_Type = 1, 2, 3, or 4: 'State Offense' | R |
/behaviorDetailedDescription | Specifies a more granular level of detail of a behavior involved in the incident. | String | O |
Student Discipline Incident
This view captures a detailed list of Student Discipline Incidents successfully published to the ODS. This association indicates those students who were victims, perpetrators, witnesses, and/or reporters for a discipline incident. Records are published if the incident was published in the preceding Discipline Incident data, the student's Michigan unique identification code (UIC) is populated in PowerSchool, the student is not excluded from state reporting, the incident includes at least one state-reportable behavior type code and the incident date falls within the year of the Term selected in the PowerSchool. . The layout includes the School Name, Student Number, Student Name, WISER ID, Incident Identifier, Incident Date, Last Publish Date, Publishing ID, and Resource ID.
studentDisciplineIncidentAssociation
This association indicates those students who were victims, perpetrators, witnesses, and/or reporters for a discipline incident.
Primary PowerSchool Source Data
- [Log]
Selection Criteria
Records are published if the following criteria are met:
- The incident must refer to an incident published in a preceding Discipline Incident 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-reportablebehavior based on the district’s behaviorDescriptor Ed-Fi mapping.
- The incident date falls within the year for the Term selected in the PowerSchool UI.
Entity Output
- A separate studentDisciplineIncidentAssociation record is published for each student associated with a reportable incident.
- The studentDisciplineIncidentAssociation resource is dependent on the prior publishing of the following entities: student and disciplineIncidents.
- 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 A reference to the related DisciplineIncident resource. | R | |||
/schoolID | Relates the incident to the school where the incident occurred. | Integer | [Students]DCID | 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 | NEED INFO | R |
studentReference A reference to the related Student resource. | R | |||
/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. | Type | 'Perpetrator' | R |
studentDisciplineIncidentAssociationBehavior An unordered collection of studentDisciplineIncidentAssociationBehaviors | O | |||
/behaviorDescriptor | This descriptor holds the categories of behavior describing a discipline incident. | Descriptor | When [S_IN_LOG_X]Event_Type = 1, 2, 3, or 4: 'State Offense' | R |
/behaviorDetailedDescription | Specifies a more granular level of detail of a behavior involved in the incident. | String | Derived from: [Log]Entry | O |
Student Discipline Action
This view captures a detailed list of Student Discipline Actions successfully published to ODS. This represents actions taken by a school or district after a disruptive event that is recorded as a discipline incident. Records are published if the discipline action record refers to an incident published in the preceding discipline incident and the student discipline incident categories, the student's Michigan unique identification code (UIC) is populated in PowerSchool, the student is not excluded from state reporting, the incident and discipline action dates fall within the year of the Term selected in PowerSchool and the incident includes at least one state-reportable disciplinary action (1 - 5).The layout includes the School Name, Student Number, Student Name, WISER ID, Incident Identifier, Action Identifier, Discipline Date, Action Taken, Last Publish Date, Publishing ID, and Resource ID.
disciplineActions
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
- [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.
Entity 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 |
---|---|---|---|---|
schoolReference A reference to the related School resource. | R | |||
/schoolId | The school responsible for student's discipline. | Integer | [Students]DCID | R |
studentReference A reference to the related Student resource. | R | |||
/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 | NEED INFO | R |
disciplineDate | Month, day, and year of the discipline action. | Date | [S_IN_LOG_X]Event_Start_Date, if populated Otherwise: [Log]ActionDate | R |
disciplineActionDiscipline An unordered collection of disciplineActionDisciplines. Type of action, such as removal from the classroom, used to discipline the student involved as a perpetrator in a discipline incident. | R | |||
/disciplineDescriptor | Type of action, such as removal from the classroom, used to discipline the student involved as a perpetrator in a discipline incident. | String | When [S_IN_LOG_X]Event_Type =
Otherwise: value as recorded in [S_IN_LOG_X]Event_Type | R |
disciplineActionDisciplineIncident An unordered collection of disciplineActionDisciplineIncidents | R | |||
/disciplineIncidentReference A reference to the related DisciplineIncident resource. | 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 | NEED INFO | R |
//schoolId | The school associated with the discipline incident. | Integer | Derived from: [Prefs]Name=DistrictNumber [Prefs]Value If subdistricts are configured ([Prefs]Value = '1' where name = 'PSSR_SubDistrict'), then: [CST_SubDistricts]Subdistrict_Number | R |