Student Discipline Incident Behavior Associations (Indiana v3.6)

Tool Search: Ed-Fi

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

This table describes logic for triggering syncing of this object.

Action	Trigger
Post	Reports a behavior incident when the incident's Status is marked and saved as "Complete". Incident must have at least 1 behavior event associated. Posting can occur if a new event is added after Incident is marked as "Complete". Do not send if the student is in a calendar marked as Exclude. Do not send if the student's enrollment is in a school marked as Exclude. Do not send if the student's enrollment is marked as State Exclude. Do not send if the student's grade is marked as State Exclude. Do not send if the student's enrollment is marked as No Show.
Put Post/Delete	When the following information is changed on the incident: Event Type Criminal Gang Related Gang Related Descriptor Student's Role
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.
Delete	When an event is deleted.
Delete	When all non-excluded enrollments in the school and year are deleted.

School Exclude, Calendar Exclude, Resource Toggle and Resync Logic

This table describes the School Exclude, Calendar Exclude, Resource Toggle and Resync logic of this object.

Action	Trigger
None	If a resource is toggled to 'OFF' after data has sent, all sent data will remain in the ODS but no new data will send.
Resync	If a record is in the Ed-Fi Identity Mapping table and not in the ODS, it will be deleted from the Ed-Fi Identity Mapping table.
Resync	If a record is in the ODS and it does not have a matching record in Campus or the Ed-Fi Identity Mapping table, it will be deleted from the ODS.
Resync	If a mapping is changed in Resource Preferences, a resync will need to be done to reflect the changes.

Natural Key Changes, Cascading Updates, and Deletes Logic

This table describes the Natural Key Changes/Cascading Updates and Deletes logic of this object.

Action	Trigger
Post/Delete	Natural Key changes: If an Ed-Fi ID changes, this will happen with the cascading deletes from the Ed-Fi ID Change trigger.
Delete/Post	If the Incident is deleted all dependent resources will delete.
Dependent Resources	Discipline Action When a user deletes Student Discipline Incident Behavior Associations using the Delete Tool, the associated Discipline Actions are also deleted when Discipline Actions are auto selected because of the dependency. The user needs to resync the Discipline Actions after this type of delete.

Action

Trigger

Post/Delete

Natural Key changes:

If an Ed-Fi ID changes, this will happen with the cascading deletes from the Ed-Fi ID Change trigger.

Delete/Post

If the Incident is deleted all dependent resources will delete.

Dependent Resources

Discipline Action

When a user deletes Student Discipline Incident Behavior Associations using the Delete Tool, the associated Discipline Actions are also deleted when Discipline Actions are auto selected because of the dependency. The user needs to resync the Discipline Actions after this type of delete.

Scope Year Logic

This table describes scope year logic of this object.

Logic
Discipline records will only send to the school year that the incident date is aligned to. Data will only send for the years that have valid configuration.

Logic

Discipline records will only send to the school year that the incident date is aligned to.

Data will only send for the years that have valid configuration.

Resource Preferences

Data Element Label	Mapping Needed
Behavior Event Role	Student Participation Code Descriptor
Behavior Event Type	Behavior Descriptor (Info message only)

Identity Mapping Object Key

Campus Object Type	Object Key Data Source
BehaviorRole	incidentID-eventID-personID

Event Queue Detail

This table describes the Event Queue Detail of this object.

Campus Table	Ed-Fi Action	Fields
behaviorEvent	Post/Put/Delete	The primary table for sending data for this resource.

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.

Data Element Label	Business Requirement	Business Rules	M, C or O	Location
id	The unique identifier of the resource.		M
disciplineIncident Reference	Reference to the discipline incident.	incidentIdentifier: Reports the 'Incident ID' from the Incident Detail Information. schoolId: Reports as 10+District#+School#	M
studentReference	A reference to the related Student resource.	Reports the data that is part of the Natural Key for the Student resource.	M
behaviorDescriptor	Describes behavior by category.	Only reports behaviors with which the student being reported is associated. Reports the Ed-Fi code value from the mapped Behavior Event on the Discipline Incident Resource Preferences. If the Behavior Event is not mapped, does not report.	M	Behavior > Behavior Management > Event Type behaviorType.code behaviorType.name
criminalGangRelatedEventDescriptor	The criminal gang related participation of a student in a discipline incident.	Reports 0: Not Criminal Gang-Related if 'Criminal Gang Related' is not checked. Reports 1: Criminal Gang Related - Investigation Disposed of Internally if 'Criminal Gang Related' is checked and 'Referred to Local Law Enforcement' is not checked. Reports 2: Criminal Gang Related - Case Referred to Local Law Enforcement if 'Criminal Gang Related' is checked and 'Referred to Local Law Enforcement' is checked. Reports based on the following priority order when a student is involved in multiple events of an incident, and those events differ in their calculated criminalGangRelatedEventDescriptor status: 2 > 1 > 0 Example: A student is involved in three events of an incident. Event #1 calculates to Code 0. Event #2 calculates to Code 1. Event #3 calculates to Code 2. Code 2 will report because it takes priority over the other codes.	M	Behavior > Behavior Management > Incident Details > Event Details > Criminal Gang Related + Referred to Local Law Enforcement
behaviorDetailed Description	Specifies a more granular level of detail of a behavior involved in the incident.	This is optional, does not report.	O
disciplineIncident ParticipationCode	An unordered collection of student Discipline Incident Behavior Association Discipline Incident Participation Codes. The role or type of participation of a student in a discipline incident.	See array section below for logic.	O
etag	A unique system-generated value that identifies the version of the resource.		O

Arrays

Click here to expand...

Data Element Label	Business Requirement	Business Rules	M, C or O	Location
disciplineIncident ParticipationCode Descriptor	This descriptor holds the role or type of participation of a student in a discipline incident.	Reports the mapped Ed-Fi Code from the Role that is selected for the Student being reported. Does not report if the role is not mapped.	M	Behavior > Behavior Management > Participant details > Role behaviorevent.role

Type/Descriptors