• Home
  • State Specific Information
  • Indiana
  • Indiana Ed-Fi v3.6

Discipline Incidents (Indiana v3.6)

You are viewing a previous version of this article. See the Indiana Ed-Fi article for the most current information.

This event entity 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 (e.g., a fight) is one incident regardless of how many perpetrators or victims are involved. Discipline incidents are events classified as warranting discipline action.

Object Triggering Logic

ActionTrigger
Post

Reports a behavior incident when the incident's Status is marked and saved as "Complete".

  • Incident must have at least one behavior event associated and the event is mapped to an Ed-Fi Value.
  • Incident must have at least one student associated to an Event to report.
  • Posting can occur if a new event is added after Incident is marked as "Complete".
  • Does not send if the student is in a calendar marked as Exclude.
  • Does not send if the student is in a School marked as Exclude.
Put
Post/Delete

When data is change on the incident:

  • Incident Details
  • Date of Incident
  • Event Type
Delete/Post

When the incident's status is changed.

  • Delete when the status is changed from Completed to In Progress.
  • Post when the status is changed from In Progress to Completed.
DeleteWhen an incident is deleted.
DeleteWhen all of the Student Discipline Incident Behavior Associations records associated with this Disciple Incident record are deleted.


School Exclude, Calendar Exclude, Resource Toggle and Resync Logic

ActionTrigger
NoneIf a resource is toggled to 'OFF' after data has sent, all sent data remains in the ODS but no new data sends.
ResyncIf a record is in the Ed-Fi Identity Mapping table and not in the ODS, it is deleted from the Ed-Fi Identity Mapping table.
ResyncIf a record is in the ODS and it does not have a matching record in Campus or the Ed-Fi Identity Mapping table, it is deleted from the ODS.
ResyncIf a mapping is changed in Resource Preferences, a resync needs to be done to reflect the changes.


Natural Key Changes, Cascading Updates, and Deletes Logic

ActionTrigger
Post/Delete

Natural Key changes:

  • If the School Number/Ed-Fi School Number changes, a delete/post occurs with the cascading deletes from the School ID Change triggers. If an Ed-Fi ID changes, this will happen with the cascading deletes from the Ed-Fi ID Change trigger.
Delete/PostIf the Incident is deleted all dependent resources delete.
Dependent ResourcesStudent Discipline Incident Associations, Discipline Action


Scope Year Logic

Logic

Discipline records only send to the school year to which they are aligned.

Data only sends for the years that have valid configuration.


Resource Preferences

Data Element Label

Mapping Needed

Behavior Incident Location of IncidentIncident Location Descriptor
Behavior Event TypeBehavior Descriptor
(Information: Only show events that overlap the configured year with the ability to view/map inactive events. Show both events that do not overlap and events that are archived.)
Behavior Event Referring PartyReporter Description Descriptor
Do you want to report the Details on the Incident to populate the Behavior Detailed Descriptor?Behavior Detailed Description

Identity Mapping Object Key

campusObjectType

Object Key Data Source

BehaviorIncidentincidentID

Event Queue Detail

Campus TableEd-Fi ActionFields
behaviorIncidentPost/Put/DeleteThe primary table for sending data for this resource.
behaviorEventPutReferring Party

Object Data Elements

Data Element Labels in bold are part of the Natural Key and are required data elements for Data to send to Ed-Fi.

Click here to expand...

Arrays

Click here to expand...


Type/Descriptors

Click here to expand...