Michigan Ed-Fi Data v3.1 - Student Discipline Incidents 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 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 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 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 No Show or State Exclude.
Put	When a change is made to: behaviors followUps
Delete/Post	When data that is not part of the Natural Key is changed. If the student's role is changed. If the Event Type is changed and saved.
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 (Note: When a user deletes Student Discipline Incident Associations using the Delete Tool, the associated Discipline Actions are also deleted when Discipline Actions are auto selected because of the dependency. The user would need 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

(Note: When a user deletes Student Discipline Incident Associations using the Delete Tool, the associated Discipline Actions are also deleted when Discipline Actions are auto selected because of the dependency.

The user would need 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 based on the School Year Start and End dates. If School Year Start Date is NULL, 7/1/xxxx will be the default start date used. If School Year End Date is NULL, 6/30/xxxx will be the default end date used. 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 based on the School Year Start and End dates.

If School Year Start Date is NULL, 7/1/xxxx will be the default start date used.
If School Year End Date is NULL, 6/30/xxxx will be the default end date used.
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)

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	Data Source GUI Path	Database Field
id	The 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
studentReference	A reference to the related Student resource.	Reports the data that is part of the Natural Key for the Student resource.	M
behaviors	An 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 ParticipationCode Descriptor	The 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. If the student has more than 1 role with different Ed-Fi Code values, the last one to sync wins. If the role is not mapped, do not report.	M	Behavior > Behavior Management > Participant details > Role	behaviorevent.role
followUps	An unordered collection of studentDisciplineIncidentAssociationFollowUps. The follow-up and/or educational services provided to the student after the 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...

Student Discipline Incident Association Behaviors

Data Element Label	Business Requirements	Business Rules	M, C or O	Data Source GUI Path
behaviorDescriptor	The ID of the Behavior Descriptor.	Report all behavior events that are associated with the student Report the Ed-Fi code value from the state code on the event. If the event is not mapped to a state code or the Ed-Fi Code is blank, report '02'.	M	Behavior> Behavior Management> Event Type
behaviorDetailedDescription	Specifies a more granular level of detail of a behavior involved in the incident	Does not report.	O
disciplineIncidentBehavior SubTypeDescriptor	(MI EXT) Discipline Incident Behavior SubTypes.	Does not report.	O
orderOfBehavior	(MI) Order of the behavior of the referral.	Report based on earliest eventID found on incident. The earliest record ID reports '1'. Second earliest reports '2'. Etc.	M

Student Discipline Incident Association Follow Up

Data Element Label	Business Requirement	Business Rules	M, C or O	Data Source GUI Path	Database Field
followUpDescriptor	A unique identifier used as Primary Key, not derived from business logic, when acting as Foreign Key, references the parent table.	Report Follow Up from behavior resolution(s). All unique Follow Up codes related to the student should report from the incident resolutions. Resolution must be mapped to an Ed-Fi Code.	O	Behavior > Behavior Management > Resolution > Follow Up

Type/Descriptors