WI DPI WISEdata Ed-Fi Docs
/studentDisciplineIncidentBehaviorAssociation
Effective 2024-25 and later, the StudentDisciplineIncidentBehaviorAssociation endpoint establishes a connection between students and /disciplineIncident entities, specifying the behavior exhibited by students during that incident.
This endpoint is NOT expected from Choice schools.
Data Properties:
# | Property Name | Data Type | Public (Required/ Optional/ Conditional) | Choice (Required/ Optional/ Conditional) | Business Definition | Data Element Page |
|---|---|---|---|---|---|---|
1.0 | behaviorDescriptor | string | REQ’D | NOT REQ’D | Describes behavior by category. | |
2.0 | incidentIdentifier* | string | REQ’D | NOT REQ’D | A locally assigned unique identifier (within the school or school district) to identify each specific Discipline Incident or occurrence. The same identifier should be used to document the entire DisciplineIncident even if it included multiple offenses and multiple offenders. | |
3.0 | schoolId | big integer | REQ’D | NOT REQ’D | The identifier assigned to a school. Format change from Integer to Big Integer (2025-26 SY and later) | |
4.0 | studentUniqueId | string | REQ’D | NOT REQ’D | A unique alphanumeric code assigned to a student. | |
5.0 | behaviorDetailedDescription | string | REQ’D | NOT REQ’D | Specifies a more granular level of detail of a behavior involved in the incident. | |
6.0 | disciplineIncidentParticipationCodeDescriptor | string | NOT REQ’D | NOT REQ’D | The role or type of participation of a student in a discipline incident. Valid values is: Perpetrator | |
7.0 | seriousBodilyInjury | boolean | REQ’D | NOT REQ’D | Incident resulted in serious bodily injury. Serious Bodily Injury involves a substantial risk of death; extreme physical pain; protracted and obvious disfigurement; or protracted loss or impairment of the function of a bodily member, organ, or faculty (18 USC Section 1365 (3)(h)). |
Descriptors:
NameSpace | Code Value | Short Description | Long Description |
|---|
NameSpace | Code Value | Short Description | Long Description |
|---|---|---|---|
uri://dpi.wi.gov/BehaviorDescriptor | 1 | Handgun | Handgun means any weapon designed or redesigned, or made or remade, and intended to be fired while held in one hand and to use the energy of an explosive to expel a projectile through a smooth or rifled bore. s.175.35(1)(b), Wis Stats |
2 | Shotgun or Rifle | Shotgun means a weapon designed or redesigned, made or remade, and intended to be fired from the shoulder and designed or redesigned and made or remade to use the energy of the explosive in a fixed shotgun shell to fire through a smooth bore either a number of ball shot or a single projectile for each single pull of the trigger. "Rifle" means a weapon designed or redesigned, made or remade, and intended to be fired from the shoulder and designed or redesigned and made or remade to use the energy of the explosive in a fixed metallic cartridge to fire only a single projectile through a rifled bore for each single pull of the trigger. USC Title 18, Section 921(a) | |
3 | Other Firearm | Other Firearm is a "Firearm" that's not a handgun, shotgun, or rifle. Firearm is any weapon which will, or is designed to, or may be converted to, expel a projectile by the action of an explosive; frame or receiver of such weapon; firearm muffler or silencer; or destructive device. Destructive device includes: explosive, incendiary, or poison gas, including bomb, grenade, rocket with propellant charge of more than four ounces, missile with explosive or incendiary charge of more than one-quarter ounce, mine, or similar device; any weapon that will, or that may be converted to, expel a projectile by the action of explosive or other propellant, and has any barrel with a bore of more than half inch in diameter; any combination or parts designed or intended for use in converting a device into a destructive device described in the two immediately preceding examples, and from which a destructive device may be readily assembled. Antique firearms and common fireworks aren’t included in the definition of firearm. | |
4 | Dangerous Weapon - Not Firearm | Dangerous weapon - not firearm is any dangerous weapon that is not a firearm. This would include any weapon, device, instrument, or material, or substance, animate or inanimate, that is used for, or is readily capable of causing death or serious bodily injury, except that such a term does NOT include a pocket knife with a blade of less than 2 ½ inches in length (18 U.S.C. Section 930(g)(2)). | |
5 | Assault | Assault means behavior that causes bodily harm to another person if that behavior was carried out with intent to cause harm, or without the consent of that individual. Assault includes but is not limited to sexual assault of another individual, without that individual's consent. To use this incident type as a reason for removal the behavior must occur while on school grounds or while under the supervision of school authorities. | |
6 | Endangering Behavior | Endangering Behavior is behavior causing the threat of or potential for bodily harm to another person, due to circumstances which show utter disregard to the well being of such individuals. To use this incident type as a reason for removal the behavior must occur while on school grounds or while under the supervision of school authorities. | |
7 | Drug-Related | Drug-Related means related to use, possession, sale, or solicitation of drugs identified in 21 USC Section 812(c). These offenses do NOT include use, possession, sale, or solicitation of alcohol or tobacco. | |
8 | Alcohol-Related | Alcohol-Related means related to alcohol. | |
9 | Other Violation of School Rules | Other Violation of School Rules means a violation of any other school rules not covered above. This code includes, but is not limited to, tobacco use or possession on school property. | |
uri://dpi.wi.gov/StudentParticipationCodeDescriptor NOT REQUIRED FOR THE 2023-24 SY AND AFTER | 01 | Perpetrator | Perpetrator |
Use Cases:
These are the same use cases for /disciplineIncident and /disciplineAction.
# | Use Case Title | Use Case Description | What to Submit/retrieve |
|---|
# | Use Case Title | Use Case Description | What to Submit/retrieve |
|---|---|---|---|
1.0 | Deprecating the /studentDisciplineIncidentAssociation (For 2023-24 and later) | The /studentDisciplineIncidentAssociation endpoint should not be used for 2023-24 and later. This endpoint has been replaced by /studentDisciplineIncidentBehaviorAssociation. | For 2022-23 and prior, vendors are expected to use the /studentDisciplineIncidentAssociation endpoint. |
2.0 | Sending discipline incident data on /studentDisciplineIncidentBehaviorAssociation (For 2023-24 and later) | Vendor should update their code and integration to use the /studentDisciplineIncidentBehaviorAssociation endpoint starting on 23/24 SY. | For 2023-24 and after, vendors are expected to use the /StudentDisciplineIncidentBehaviorAssociation endpoint POST on /studentDisciplineIncidentBehaviorAssociation: |
3.0 | Sending behavior | In v6, only one behaviorDescriptor can be submitted under the /studentDisciplineIncidentBehaviorAssociation endpoint.
| POST on /disciplineIncident POST on /studentDisciplineIncidentBehaviorAssociation - Record 1: POST on /studentDisciplineIncidentBehaviorAssociation - Record 2: POST on /disciplineActions - Record 1: POST on /disciplineActions - Record 2: |
4.0 | Sending one student with one discipline action | This is the most common scenario for discipline. One student is the perpetrator in an incident. For this student only one discipline action occurs which must be submitted to WISEdata. Recall that only a subset of discipline incident, discipline type, and behavior information should be submitted to DPI:
| POST on /studentDisciplineIncidentBehaviorAssociation disciplineIncidentReference: |
4.0 | Sending behavior | Only one behaviorDescriptor can be submitted under the /studentDisciplineIncidentBehaviorAssociation endpoint. One behavior (studentDisciplineIncidentBehaviorAssociation) may be associated to one or more action (disciplineActions). | POST on /disciplineIncident POST on /studentDisciplineIncidentBehaviorAssociation - Record 1 POST on /studentDisciplineIncidentBehaviorAssociation - Record 2 POST on /disciplineActions - Record 1 POST on /disciplineActions - Record 2: |
5.0 | Sending behavior and behavior detailed description | Behavior Description is always required. Behavior detailed descriptor has to be submitted only for incidents where:
For firearm-related incidents meeting the above criteria, this description must provide the reason why the student did not receive the mandatory expulsion. | POST on /studentDisciplineIncidentBehaviorAssociation: |
6.0 | Sending a discipline incident at the end of school year with expulsion in the next school year | The API is school year based. Submit the incident, association, and action resources in the same school year as the incident. NOTE: Even though the expulsion begins in the next school year, no resources for the incident, association, or action are submitted in next school year. Expulsions are the only discipline actions which may occur in a school year later than the incident. For an incident near the end of the school year that school board may not meet until after the end of the school year or the student may be suspended for the remaining days of the year. In these cases the expulsion discipline date is in the next school year. As there are no days removed for the expulsion in the year of the incident, discipline length is zero. Actual discipline action length should be greater than zero, identifying the total number of school days for this student from the expulsion start date to end date. | POST one records on /disciplineIncident, disciplineActions, and /studentDisciplineIncidentAssociation |
One student and multiple discipline incidents | |||
7.0 | Sending one student with one discipline incidents on a single day (for suspensions or IAES removals) | As a suspension or IAES removal must be at least ½ of the student’s day and an expulsion requires a school board hearing, meeting the requirements for two incidents to be reported on the same is very unlikely. In most cases only one incident is submitted. For example, incident A occurs for an IDEA-eligible student who is removed from the classroom for more than ½ their regular day by in-school suspension. For the same student a second Incident (B) occurs later in the day for which the student receives an out of school suspension for the remainder of that day and the next school day. | Incident A Incident B |
8.0 | Sending one student with one discipline incidents on a single day, but only one discipline incident counts | Consider the example where incident A occurs for an IDEA-eligible student who is removed from the classroom for 1 period in the morning. This is an in-school suspension with less than ½ day discipline length. For the same student a second Incident (B) occurs later in the morning. The student receives an out of school suspension for the rest of the day. | Incident A Incident B POST on /disciplineIncident, |
One student multiple discipline actions | |||
9.0 | Sending one student with multiple discipline actions (out-of-school suspension and expulsion) | Often, an expulsion is preceded by an out-of-school suspension for the days the student is removed while awaiting the expulsion hearing.
| POST on /disciplineIncident |
Wisconsin Department of Public Instruction