Student Discipline Incident Behavior Associations (Texas v4.0)

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.
  • 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.
Put

When data that is not part of the Natural Key is changed.

  • If the student's role is changed.
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 event is deleted.
DeleteWhen 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.

ActionTrigger
NoneIf a resource is toggled to 'OFF' after data has sent, all sent data will remain in the ODS but no new data will send.
ResyncIf 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.
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 will be deleted from the ODS.
ResyncIf 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.

ActionTrigger
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/PostIf the Incident is deleted all dependent resources will delete.
Dependent ResourcesDiscipline 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

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 RoleStudent Participation Code Descriptor
Behavior Event TypeBehavior Descriptor (Info message only)

Identity Mapping Object Key

Campus Object Type

Object Key Data Source

BehaviorRoleincidentID-eventID-personID

Event Queue Detail

Campus TableEd-Fi ActionFields
behaviorEventPost/Put/DeleteThe 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 LabelBusiness RequirementBusiness RulesM, C or O

Location

idThe unique identifier of the resource.
M
discipline Incident Reference A reference to the related Discipline Incident resource.

Reports the fields that are part of the Natural Key for the Discipline Incident resource.

M
studentReferenceA reference to the related Student resource.

Reports the data that is part of the Natural Key for the Student resource.

M
behaviorDescriptorDescribes behavior by category.
  1. Only reports behaviors with which the student being reported is associated.
  2. 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.
MBehavior > Behavior Management > Event Type

behaviorType.code

behaviorType.name


behaviorDetailed Description
Specifies a more granular level of detail of a behavior involved in the incident.This is optional, does not report.O
disciplineIncident ParticipationCodeAn 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.This is optional, does not report.O
etagA unique system-generated value that identifies the version of the resource.
O

Type/Descriptors

Click here to expand...

Behavior descriptors

Code ValueDescriptionNamespaceShort Description
OtherOtheruri://ed-fi.org/BehaviorDescriptorOther
School Code of ConductSchool Code of Conducturi://ed-fi.org/BehaviorDescriptorSchool Code of Conduct
School ViolationSchool Violationuri://ed-fi.org/BehaviorDescriptorSchool Violation
State OffenseState Offenseuri://ed-fi.org/BehaviorDescriptorState Offense