Staff Discipline Incident Associations (Core v3.X)

Tool Search: Ed-Fi

This association indicates those staff who were victims, perpetrators, witnesses, and reporters for a discipline incident.

Object Triggering Logic

This table describes logic for triggering syncing of this object.

ActionTrigger

Reports only when the person involved in an incident have district assignment or district employment (staff).
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 and a Role that is mapped to an Ed-Fi Value.
  • Posting can occur if a new event is added after Incident is marked as "Complete".
  • Do not send if the staff's district assignment or district employment is in a calendar marked as Exclude.
  • Do not send if the staff's district assignment or district employment is in a school marked as Exclude.
Put

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

  • If the staff'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 district assignments or district employment in the school and year are deleted.

Note: When both student and staff are involved in the same discipline incident, both student discipline incident association and staff discipline incident association resources must be mapped to an Ed-Fi Value.

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 ResourcesSchool, Staff, Discipline Incident



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.


Resource Preferences

Data Element Label

Mapping Needed

Discipline Incident Participation Code
Behavior Event Role
Staff Relationship to School


Identity Mapping Object Key

Campus Object Type

Object Key Data Source

BehaviorRoleincidentID-personID


Event Queue Detail

This table describes the Event Queue Detail of this object.

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

Data Source GUI Path

Database Field
idThe unique identifier of the resource.
M

disciplineIncident
ParticipationCodes  
An unordered collection of staff Discipline Incident Association Discipline Incident Participation Codes. The role or type of participation of a person in a discipline incident; for example: Victim, Perpetrator, Witness, Reporter.

See array section below for logic.

M

disciplineIncident
Reference
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.Reports the fields that are part of the Natural Key for the Discipline Incident resource.M

staffReferenceA reference to the related Staff resource.

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

M

etagA unique system-generated value that identifies the version of the resource.



Arrays

Click here to expand...
Data Element LabelBusiness RequirementBusiness RulesM, C or O

Data Source GUI Path

Database Field
disciplineIncident ParticipationCode Descriptor

The role or type of participation of a person in a discipline incident; for example: Victim, Perpetrator, Witness, Reporter.

  1. Report the mapped Ed-Fi Code from the Role that is selected for the Staff being reported.
    • If the role is not mapped, do not report.
  2. Do not report if Relationship to School is:
    • Non School Person
    • Student
    • Student from Another School
 M

Behavior> Behavior Management> Participant details> Role


Behavior> Behavior Management> Participant details> Relationship to School


BehaviorRole.relationshipToSchool

BehaviorRole.role



Type/Descriptors

Click here to expand...

Behavior descriptors

Code ValueDescriptionNamespaceShort Description
Perpetrator
Perpetrator
uri://ed-fi.org/DisciplineIncidentParticipationCodeDescriptor
Perpetrator
Reporter
Reporter
uri://ed-fi.org/DisciplineIncidentParticipationCodeDescriptor
Reporter
Victim
Victim
uri://ed-fi.org/DisciplineIncidentParticipationCodeDescriptor
Victim
Witness
Witness
uri://ed-fi.org/DisciplineIncidentParticipationCodeDescriptor
Witness