Arizona Ed-Fi Data v3.5 - Student Discipline Incident Associations

Classic View: System Administration > Ed-Fi 

Search Terms: 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

This table describes logic for triggering syncing of this object.

ActionTrigger
PostReports when a Behavior Resolution is added to an incident that is marked as Complete and is aligned to a reported Behavior Event.
  • Incident must have at least 1 behavior event associated and the event is mapped to an Ed-Fi Value.
  • Incident must be tied to a Behavior Incident that has at least one Behavior Resolution that is mapped to an Ed-Fi Value.
  • Student must be in SPED on the date of the reported behavior event that is identified by:
    1. Student has a locked IEP that overlaps the dates of the reported behavior event.
    2. Student has NO IEPs and has a flag with a state code of '999' (IEP) that overlaps the dates of the reported behavior event.
  • Posting can occur if a new event is added after Incident is marked as "Complete".
  • 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 or State Exclude.
  • Do not send if the student is in a calendar marked as Exclude.
  • Do not send if the student is in a School marked as  Exclude.
  • Do not send if a student's enrollment is marked as No Show.
Put

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

  • When Submitted By is changed on the incident.
  • When a new behavior event is added, changed or removed.
  • When the incident date is changed.
Delete/PostWhen 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/PostWhen a student's SPED IEP is changed.
  • Delete when the IEP is unlocked.
  • Post when the IEP is locked.
  • Delete if the IEP dates are updated to no longer overlap the behavior incident.
  • Post if the IEP dates are updated to now overlap the behavior incident.
Delete/PostWhen student's flag with a state code of 999 (IEP) is changed.
  • Delete if flag dates are updated to no longer overlap the behavior incident.
  • Post if flag dates are updated to now overlap the behavior incident.
  • Delete when a flag with dates that overlaps the behavior incident is deleted.
  • Post when the flag with dates that overlap the behavior incident has the program updated to 999 (IEP) or new flag is added with a program state code of 999 (IEP).
DeleteWhen an incident is deleted.
DeleteWhen the associated student enrollment is deleted.
Delete

When all non-excluded enrollments in the school and year are deleted.

DeleteWhen all Student Discipline Incident Associations  that are associated with this Disciple Incident record.

Resource Toggle/Resync

Action

Business Rule

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, Deletes

Action

Business Rule

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
  • Discipline Actions

Scope Year

Business Rules
Discipline records will only send to the school year they are aligned to.
Data will only send for the years that have valid configuration.

Resource Preferences

Data Element LabelMapping Needed
Behavior Event RoleStudent Participation Code Descriptor

Identity Mapping Object Key

Data Element LabelMapping Needed
BehaviorRoleincidentID-personID

Event Queue Detail

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 LabelBusiness RequirementBusiness RuleM, C, or OData Source GUI PathDatabse Field
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

behaviorsAn unordered collection of disciplineIncidentBehaviors. 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.

See array section below for logic.

O

student Participation Code DescriptorThe role or type of participation of a student in a discipline incident; for example: Victim Perpetrator Witness Reporter.Report the mapped Ed-Fi Code from the Role that is selected for the Student being reported:
  1. If the student has more than one role with different Ed-Fi Code values, the last one to sync sends.
  2. If the role is not mapped, do not report.
MBehavior > Behavior Management > Participant details > Rolebehaviorevent.role
etagA unique system-generated value that identifies the version of the resource.
O

Arrays

Behaviors

Data Element LabelBusiness RequirementBusiness RulesM, C or O

Data Source GUI Path

Database Field
Behavior Descriptor

This descriptor holds the categories of behavior describing a discipline incident.

  1. Only report behaviors the student being reported is associated with.
  2. Report the Ed-Fi code value from the mapped Behavior Event on the Discipline Incident Resource Preferences:
    • If the Behavior Event is not mapped, do not report.
 OBehavior> Behavior Management> Event TypebehaviorType.code

behaviorType.name

Detailed DescriptionSpecifies a more granular level of detail of a behavior involved in the incident.

This is optional, does not report 

 O


Descriptors

Behavior Event Roles

Ed-Fi Code
Description
Perpetrator: Perpetrator
O: Offender
Victim: Victim
V: Victim
Witness: Witness
W: Witness
Recipient: Recipient
R: Recipient