Discipline Incident File
Contents
Introduction
This report generates the file needed to upload to the ODE portal. The data to be filled for this report cannot be extracted directly from the database. By default, all of these fields are assumed to be zero. It is recommended to check the Save as Default checkbox for those fields that you specifically enter a value in order to save time when rerunning the report.
See Incident Management Quick Setup for steps to set up Incident Management within PowerSchool. See Incident Management Quick Entry for steps to create incidents in PowerSchool. These can be accessed on PowerSource.
This report is available for extracting incidents based on the codes and subcodes defined as state reportable within IM. The output format matches the ODE layout.
The report includes the following features:
- The extract output is a comma delimited .csv file.
- The report can be run at the school level or district-wide, for a selection of students or for all students.
The report includes the following logic:
- Only incidents directly associated with students are reported. If a state reportable incident exists but does not have a student association, that incident is not reported.
- Only students in the Offenders category are included in the output.
- The Incident Management module allows multiple Actions to be associated directly to a student or to the student’s Behavior. The ODE layout allows only one action per student per incident so the following logic is used to select the Action to report:
- An action associated with a student’s behavior will be considered first.
- If there is no action under any behavior, then an action associated directly with the student is considered.
- Non-state reportable actions are not considered.
- When multiple actions are found the first action will be reported.
Recommendation: For incidents with multiple actions for one student, modify actions to a local code/subcode, except the one that should be reported to the state. That one should remain state reportable.
- If there is no state reportable action for the incident, the report outputs a blank.
- Primary behavior is required data entry. When no behavior codes are attached to a student, the report defaults to 0000 as the primary, secondary, and tertiary codes.
- Currently the IM module cannot distinguish between primary, secondary, and tertiary objects. The extract logic will determine weapon objects (primary, secondary, tertiary) depending on the order of the data entry (first-entered-first-selected).
Selection Criteria
Selection criteria determine which database records are used in the report. Refer to selection criteria for analysis when the report does not return the correct records.
Incident Selection
The report selects records from the database based on the following criteria:
- The incident must occur between the dates supplied at report run time, usually 7/1/YYYY and 6/30/YYYY of the reporting school year, as selected at the top of the page when running the report. The report can be run for any period of time, such as monthly, or for the school year.
- The incident type must be State Reportable.
- The student's school must not be excluded from state reporting.
- The student must not be excluded from state reporting.
Report Input
To generate the Discipline Incident Extract File, do the following:
For help with navigation and running the report, see How to Find and Generate a Report.
Field | Description |
Select Schools | Choose one of the following:
Note: The All Schools option is only available when running the report from the District Office. |
Students to Include | Indicate which students to include in the report by selecting one of the following options:
Note: If running the report for a single student, or group of students, select the students prior to running report. |
Report Start Date and End Date | Enter the start date and end date to restrict incidents. Only incidents occurring within this date range will be included in the extract. |
File Name | OR_Discipline_[SchoolID/DistrictNumber]_[Timestamp].csv |
Destination | The report defaults to the Reporting Queue. |
Scheduling | Choose a time to run the report from following options:
|
Report Output
Each of the fields displayed in the output of the report are described below. See Understanding the Report Output Table for a definition of each column in the table.
Item # | FieldName | Description | [Table]FieldName | Data Type | Field Length |
This report is a student-level Consolidated Collections report using the “core fields query” to gather student details and assure consistent data submissions to ODE. SEE THE SSID REPORT OUTPUT FOR A LISTING OF THE CORE ELEMENTS OF THIS STUDENT-LEVEL CONSOLIDATED COLLECTION REPORT. | |||||
48 | TAGFg (Academically Talented or Intellectually Gifted) | Indicates that the student is identified as Academically Talented or Intellectually Gifted as determined by school district policy. | [S_OR_STU_X]TAGFg | char | 1 |
49 | AddnLangCd Additional Language Code | Code indicating any additional language a student uses to communicate that is not the language of origin. | [Student]AddnLangCd | varchar | 4 |
57 | SECCPrimDsbltyCd | Indicates the primary disability of the student. In PowerSchool, this is one of the subcodes for the Participant Attribute code: State Disability Code. | [Incident_LU_Subcode]State_Detail_Report_Code [Incident_LU_Code]Code_Type = attributecode [Incident_LU_Code]IncidentCategory=State Disability Code | varchar | 2 |
58 | Discipline Date | Date that disciplinary action was taken against the student as a result of the incident, may or may not be the same as the Discipline Incident Date. Reported in the format MMDDYYYY | [Incident_Action]Action_Plan_Begin_Dt | datetime | 8 |
59 | Discipline Action Type Code | The disciplinary action taken as a result of the incident. In PowerSchool, this is one of the subcodes for the Action code: State Discipline Action Type. | [Incident_LU_Subcode]State_Detail_Report_Code=1, 2, 3, 4, or 5 [Incident_LU_Code]Code_Type=actioncode [Incident_LU_Code]IncidentCategory=State Discipline Action Type | varchar | N/A |
60 | District Incident ID | The identifier assigned by the district to uniquely identify the incident leading to the disciplinary action. | [Incident]Incident_ID | varchar | |
61 | PrimOffnsTypCd | The primary offense perpetrated by the student during the incident. In PowerSchool, this is one of the subcodes for the Behavior code: State Offense Type. When a single state offense is associated with an incident it is assumed to be the Primary Offense. | [Incident_LU_Sub_Code]State_Detail_Report_Code = 1 (Primary Offense) [Incident_LU_Code]Code_Type=behaviorcode [Incident_LU_Code]IncidentCategory=State Offense Type | varchar | 4 |
62 | SecOffnsTypCd | The secondary offense perpetrated by the student during the incident. In PowerSchool, this is one of the subcodes for the Behavior code: State Offense Type. The default code value is 0000 (Not Applicable) if no secondary offense is assigned to the student. | [Incident_LU_Sub_Code]State_Detail_Report_Code = 2 (Secondary Offense) [Incident_LU_Code]Code_Type=behaviorcode [Incident_LU_Code]IncidentCategory=State Offense Type | varchar | 4 |
63 | TertOffnsTypCd | The tertiary offense perpetrated by the student during the incident. In PowerSchool, this is one of the subcodes for the Behavior code: State Offense Type. The default code value is 0000 (Not Applicable) if no tertiary offense is assigned to the student. | [Incident_LU_Sub_Code]State_Detail_Report_Code = 3 (Tertiary Offense) [Incident_LU_Code]Code_Type=behaviorcode [Incident_LU_Code]IncidentCategory=State Offense Type | varchar | 4 |
64 | PrimWpnTypCd | The primary weapon in the student’s possession during the incident. When weapons are associated with an incident the first weapon entered is assumed to be the primary weapon. The default code value is 0098 (No Weapon) if no primary weapon is assigned to the student. | [Incident_LU_Sub_Code]State_Detail_Report_Code = 1 (Primary Weapon) [Incident_LU_Code]Code_Type=objectcode [Incident_LU_Code]State_Aggreagate_Rpt_Code = 2 (State Weapon Type) | varchar | 4 |
65 | SecWpnTypCd | The secondary weapon in the student’s possession during the incident. In PowerSchool, this is one of the subcodes for the Object code: State Weapon Type. When weapons are associated with an incident the second weapon entered is assumed to be the secondary weapon. The default code value is 0098 (No Weapon) if no second weapon is assigned to the student. | [Incident_LU_Sub_Code]State_Detail_Report_Code = 2 (Secondary Weapon) [Incident_LU_Code]Code_Type=objectcode [Incident_LU_Code]IncidentCategory=State Weapon Type | varchar | 4 |
66 | TertWpnTypCd | The tertiary weapon in the student’s possession during the incident. In PowerSchool, this is one of the subcodes for the Object code: State Weapon Type. When weapons are associated with an incident the third weapon entered is assumed to be the tertiary weapon. The default code value is 0098 (No Weapon) if no third weapon is assigned | [Incident_LU_Sub_Code]State_Detail_Report_Code = 3 (Tertiary Weapon) [Incident_LU_Code]Code_Type=objectcode [Incident_LU_Code]IncidentCategory=State Weapon Type | varchar | 4 |
67 | DsplnModCd | The code indicating special circumstances in which the disciplinary action taken was modified. In PowerSchool, this is one of the subcodes for the Action Change code: State Discipline Modification. | [Incident_LU_Sub_Code]State_Detail_Report_Code=0, 1, or 2 [Incident_LU_Code]Code_Type=actionchangecode [Incident_LU_Code]IncidentCategory=State Discipline Modification | Char | 1 |
68 | Discipline Days | The number of days associated with the disciplinary action taken, reported with one decimal point (either .0 or .5). Partial Discipline Days are rounded up to the nearest half-day. The actual duration is reported, if available. Otherwise, the assigned duration | [Incident_Action]Duration_Actual [Incident_Action]Duration_Assigned | varchar | N/A |
69 | Interim Educational Services Flag | Indicates if the district provided interim educational services during the discipline days. In PowerSchool, this is the Participant Attribute code, State Interim Ed Services (IES)=Yes. | [Incident_LU_Code]Code_Type=participantattributecode [Incident_LU_Code]IncidentCategory=State Interim Ed Services (IES)=Yes | Char | 1 |
70 | Violent Criminal Offense Arrest Flag | Indicates if the incident resulted in the student’s arrest for a violent criminal offense, including assault, manufacture or delivery of a controlled substances, sexual crimes using force, threatened use of force or force used against an incapacitated person, arson, robbery, hate/bias crime, coercion, or kidnapping. In PowerSchool, this is the Object code, State Violent Criminal Offense Arrest=Yes. If this object code is associated to the student offender in the incident then Y is reported, otherwise N. | [Incident_LU_Code]Code_Type=objectcode [Incident_LU_Code]IncidentCategory=State Violent Criminal Offense Arrest=Yes | Char | 1 |
71 | Discipline Incident Date | Date that disciplinary incident occurred, may or may not be same as Discipline Action Date. Reported in the format MMDDYYYY | [Incident]Incident_TS | datetime | 8 |
71 | Discipline Filler | Reserved for future use. | N/A | Varchar | 50 |