Discipline Data and Report Writer

Modified on Mon, Apr 24, 2023 at 10:53 AM

The following is a summary that was created to help understand how the discipline data is organized. This is for the purpose of building custom reports in the Code of Conduct module.

Incidents in Code of Conduct

This section refers to the incidents you might find on the Code of Conduct > Incidents > Incident List screen. There are 7 main tables that make up an overall discipline incident. Note: Be aware, not all of these tables are specific to one student, so they may not contain a Student ID field. Here is a list of the tables, and examples of the data you'll find in them:

Discipline Incident

Discipline Incident - General information about the conduct incident overall. Each incident added in code of conduct will have only one record in this table. There is no specific data about the student here, because there could be any number of students (or staff) listed on one single incident. There is also no mention of the Infraction (conduct violation) committed, as there can be multiple infractions on one single incident.

Primary Key Fields	Other Important Data
School Year Incident Number	Date of Incident Time, Period, Location of incident School code Incident reporter Incident description and note fields Lists HIB incident number if conduct incident is attached to an HIB incident Lists Attendance Rule that was violated if incident was created automatically by attendance to conduct

Incident Infraction

Incident Infraction - This is the list of all Infractions committed (ex: 'Running in the halls') on the incident. In this data table, you will find one record per each infraction that was recorded on each conduct incident. Again, we do not see specific students listed here. An incident could involve multiple offenders charged with the same infraction, but we would still see only one occurrence of that infraction here.

Primary Key Fields	Other Important Data
School Year Incident Number Infraction Group Code Infraction Code Infraction Type Code	If an infraction is listed on the incident as the 'Primary Infraction' or 'Secondary Infraction' - only one infraction can be the primary. Useful for reporting a total for each infraction that occurred during a school year.

Offender Information

Offender Information - This table lists every offender that was added to an incident, and contains one record per incident, per each student (or staff). This is useful when reporting all incidents for a given student, or simply finding the total number of incidents per student. Each student will have one record in this table, per each conduct incident they were involved in.

Primary Key Fields	Other Important Data
object ID	School Year Incident Number Student ID / Teacher ID Student Name + Demographics (ex: Race, ELL, Special Ed, 504, etc.) Caused or Incurred Injury Remedial Actions Fields used to complete Student Safety Data reporting for NJ

Victim Information

Victim Information - This table lists all victims on an incident, and contains one record per incident. You will find one record per incident, per each student or staff member who was reported as a 'victim' on the incident.

Primary Key Fields	Other Important Data
object ID	School Year Incident Number Student ID / Teacher ID Student Name + Demographics (ex: Race, ELL, Special Ed, 504, etc.) Caused or Incurred Injury Victim Type Code Transfer Information Fields used to complete Student Safety Data reporting for NJ

Student Infraction

Student Infraction - This table lists all infractions committed by an offender, per each conduct incident. This is useful for reporting total number of infractions per student, or total occurrences of a specific infraction, per student.

Primary Key Fields	Other Important Data
Object ID	Offender Object ID School Year Student ID / Teacher ID Incident Number Infraction Group Code Infraction Code Infraction Type Code

Discipline Action

Discipline Action - Contains all disciplinary actions posted to offenders. One record per offender, for every disciplinary action applied. Ex: an incident with one student who was assigned lunch detention and community service will create 2 records.

Primary Key Fields	Other Important Data
School Year Student ID Incident Number Action Group Code Action Code	Numbers of days for an action (ex: 5 days of suspension) Useful for reporting total number of disciplinary actions per student Useful for reporting total number of suspensions given for the school year, or total days of suspension

Discipline Action Date

Discipline Action Date - Lists specific dates an offender was assigned a disciplinary action. One record per action date, per offender, per incident.

Primary Key Fields	Other Important Data
School Year Student ID Incident Number Action Group Code Action Code Action Date	Completed (yes / no) Completed On (date) Useful in reporting student discipline, and if a disciplinary action was completed (ex: student attended their assigned detention)