PATH: MA State Reporting > Extracts > Offense Extract
The Offense Extract collects records of Offenses that included Offender participants.
Image 1: Offense Extract Editor
Report Logic
A record will report for each Offense that meets the following conditions:
- The Date of Incident is on or after the first instructional day of the selected calendar.
- The Date of Incident is on or before the extract Effective Date.
- The participant has a Primary enrollment record on the 'Date of Incident'
- The participant is not enrolled in a grade level with Exclude marked.
- There is a participant involved in the Offense with a Role of O: Offender AND
- A Behavior Event mapped to a State Code
OR - A Behavior Resolution with a state-mapped resolution
- A Behavior Event mapped to a State Code
- Only report incidents within Behavior Management (Do not generate objects for any Behavior Referral).
- One record will populate for each Incident ID.
- Data is only reported for the Primary enrollment record.
- If more than one participant is assigned a Role of O: Offender, only 1 record will report per Incident ID.
Days are calculated between the Resolution Start Date and the End Date. When End Date is null, calculates the difference between Resolution Date and Enrollment End Date or the Resolution Start Date and the Return Date, whichever field has an earlier date. When Return Date is null, calculates the difference between the Resolution Start Date and the Enrollment End Date. When Enrollment End Date is null, calculates the difference between the Resolution Start Date and the extract Effective Date.
Generating the Extract
- Select Offense Extract as the Extract Type.
- Enter an Effective Date in mmddyyyy format or by clicking the calendar icon and selecting a date. This field will auto-populate to the current date.
- Select the Format in which the report should generate. Select State Format (CSV) for submission to the state or HTML format for data review and verification.
- Mark the Header Off checkbox if the header row should not be included in the extract.
- Select an Ad hoc Filter to limit report results.
- Click Generate Extract to view the report in the selected format or Submit to Batch to schedule when the report will generate.
Users have the option of submitting an Offense report request to the batch queue by clicking Submit to Batch instead of Generate Extract. This process allows larger reports to generate in the background, without disrupting the use of Campus. For more information about submitting a report to the batch queue, see the Batch Queue article.
Image 2: State Format (CSV)
Image 3: HTML Format
Extract Layout
Element Name |
Description |
Type, Format and Length |
Campus Database |
Campus Location |
---|---|---|---|---|
OFF ID |
The Incident Number. |
Numeric, 6 digits |
BehaviorEvent.incidentID |
Behavior > Behavior Management > Incident > Incident ID |
OFF DATE |
The date the Offense occurred. |
Date field, 10 character MM/DD/YYYY |
BehaviorEvent.timestamp |
Behavior > Behavior Management > Incident > Date of Incident |
SCH NAME | The name of the school reporting the Offense. | Alphanumeric, 40 characters | School.name | System Administration > Resources > School > Name |
SCH CODE |
Reports the 8-digit Incident Calendar ID Number. This is the calendar the Incident was created in.
The SCH Code and SCH Name fields are aligned. The SCH Code must always report the calendar ID for the SCH Name. |
Numeric, 8 digits | School.number |
System Administration > Resources > School > Number |
OFF IND | Reports as Y. | Alphanumeric, Y | BehaviorEvent.code1 - .code5 | Behavior > Behavior Management > Incident > Event > Event ID |
DISC IND | Reports as Y if a Resolution of 1-6 is assigned to a participant in the Offense. Otherwise reports as N. | Alphanumeric, Y or N | BehaviorResolution. code | Behavior > Behavior Management > Incident > Resolution |
OT1 |
Reports the State Event Mapped Code for the 1st Behavior Event. From across all Behavior Events associated with this Incident, logic reports the Standard Code for the State Event Mapped Code of the first valid Event Type Code. This Code should report from the lowest Event ID that has a valid Standard state code. Valid codes are any Behavior Event that has a value of "1" OR any code with a resolution mapped to state event codes 1-6
For Standard code 9000 (old code 18):
Code 9000 may only be reported in OT1. OT1 cannot report the same value as OT2-OT5. |
Alphanumeric, 3 characters | BehaviorEvent.code1 | Behavior > Behavior Management > Incident > Event > State Code |
OT2 | Reports the State Event Mapped Code for the 2nd Behavior Event. From across all Behavior Events associated with this Incident, logic reports the Standard Code for the State Event Mapped Code of the second valid Event Type Code. This Code should report from the 2nd lowest Event ID that has valid Standard state code. Valid codes are any Behavior Event that has a value of "1" OR any code with a resolution mapped to state event codes 1-6
|
Alphanumeric, 3 characters | BehaviorEvent.code2 | Behavior > Behavior Management > Incident > Event > State Code |
OT3 | Reports the State Event Mapped Code for the 3rd Behavior Event. From across all Behavior Events associated with this Incident, logic reports the Standard Code for the State Event Mapped Code of the third valid Event Type Code. This Code should report from the 3rd lowest Event ID that has a valid Standard state code. Valid codes are any Behavior Event that has a value of "1" OR any code with a resolution mapped to state event codes 1-6
|
Alphanumeric, 3 characters | BehaviorEvent.code3 | Behavior > Behavior Management > Incident > Event > State Code |
OT4 | Reports the State Event Mapped Code for the 4th Behavior Event. From across all Behavior Events associated with this Incident, logic reports the Standard Code for the State Event Mapped Code of the fourth valid Event Type Code. This Code should report from the 4th lowest Event ID that has a valid Standard state code. Valid codes are any Behavior Event that has a value of "1" OR any code with a resolution mapped to state event codes 1-6
|
Alphanumeric, 3 characters | BehaviorEvent.code4 | Behavior > Behavior Management > Incident > Event > State Code |
OT5 | Reports the State Event Mapped Code for the 5th Behavior Event. From across all Behavior Events associated with this Incident, logic reports the Standard Code for the State Event Mapped Code of the fifth valid Event Type Code. This Code should report from the 5th lowest Event ID that has a valid Standard state code. Valid codes are any Behavior Event that has a value of "1" OR any code with a resolution mapped to state event codes 1-6
|
Alphanumeric, 3 characters | BehaviorEvent.code5 | Behavior > Behavior Management > Incident > Event > State Code |
VS | Reports the number of victims who were students.
|
Numeric, 3 digits | BehaviorEvent. studentVictims | Participant Path: Student Information > General > Behavior > Behavior Management > Events and Participants > Participant(s) Detail Event Type Mapping Event Type Mapping Path: System Administration > Behavior > Event Types > Behavior Event Type Editor > Behavior Event Type Detail > State Event Code (Mapping) |
VSCHP | Reports the number of victims who were school personnel.
|
Numeric, 3 digits | BehaviorEvent. schVictims | Student Information > General > Behavior > Behavior Management > Incident Management Editor > Detail Information > Number of School Personnel Victims Participant Path: Student Information > General > Behavior > Behavior Management > Events and Participants > Participant(s) Detail Event Type Mapping Path: System Administration > Behavior > Event Types > Behavior Event Type Editor > Behavior Event Type Detail > State Event Code (Mapping) |
VNSCHP | Reports the number of victims who were non-school personnel.
|
Numeric, 3 digits | BehaviorEvent. nonschVictims | Behavior > Behavior Management > Incident > Event > Number of Non-Sch Personnel Victims Participant Path: Student Information > General > Behavior > Behavior Management > Events and Participants > Participant(s) Detail Event Type Mapping Path: System Administration > Behavior > Event Types > Behavior Event Type Editor > Behavior Event Type Detail > State Event Code (Mapping) |
VU | Reports the number of victims who were unknown.
|
Numeric, 3 digits | BehaviorEvent. unknownVictims | Behavior > Behavior Management > Incident > Event > Number of Unknown Victims Participant Path: Student Information > General > Behavior > Behavior Management > Events and Participants > Participant(s) Detail Event Type Mapping Path: System Administration > Behavior > Event Types > Behavior Event Type Editor > Behavior Event Type Detail > State Event Code (Mapping) |
OFFES | Reports the number of offenders who were students.
|
Numeric, 3 digits | BehaviorEvent. studentOffenders | Behavior > Behavior Management > Incident > Event > Number of Student Offenders Participant Path: Student Information > General > Behavior > Behavior Management > Events and Participants > Participant(s) Detail Event Type Mapping Path: System Administration > Behavior > Event Types > Behavior Event Type Editor > Behavior Event Type Detail > State Event Code (Mapping) |
OFFENS | Reports the number of offenders who were non-students.
|
Numeric, 3 digits | BehaviorEvent. nonstudentOffenders | Behavior > Behavior Management > Incident > Event > Number of Non-Student Offenders Participant Path: Student Information > General > Behavior > Behavior Management > Events and Participants > Participant(s) Detail Event Type Mapping Path: System Administration > Behavior > Event Types > Behavior Event Type Editor > Behavior Event Type Detail > State Event Code (Mapping) |
OFFEU | Reports the number of offenders who were unknown.
|
Numeric, 3 digits | BehaviorEvent. unknownOffenders | Behavior > Behavior Management > Incident > Event > Number of Unknown Offenders Participant Path: Student Information > General > Behavior > Behavior Management > Events and Participants > Participant(s) Detail Event Type Mapping Path: System Administration > Behavior > Event Types > Behavior Event Type Editor > Behavior Event Type Detail > State Event Code (Mapping) |
OFF DESC | Reports any additional comments about the Offense (OT1).
|
Alphanumeric | BehaviorEvent. comments | Behavior > Behavior Management > Incident > Event > Comments |
PHYS INJ | Indicates if the Offense resulted in physical injury.
|
Alphanumeric, 1 character | BehaviorEvent. injury | Behavior > Behavior Management > Incident > Event > Physical Injury |
OFF DESC2 | Reports additional comments for OT2.
|
Alphanumeric | BehaviorEvent. comments | Behavior > Behavior Management > Incident > Event > Comments |
OFF DESC3 | Reports additional comments for OT3. When OT3 = 1097, 1650, 1660, 1697, 1897, 2197, 2797, 3097, 3197, 3297, 3397, 3597, 3600, 9000, MA05, MA19, 3700, logic reports the value entered in the Behavior > Behavior Management > Event > Comments field.
|
Alphanumeric | BehaviorEvent. comments | Behavior > Behavior Management > Incident > Event > Comments |
OFF DESC4 | Reports additional comments for OT4. When OT4 = 1097, 1650, 1660, 1697, 1897, 2197, 2797, 3097, 3197, 3297, 3397, 3597, 3600, 9000, MA05, MA19, 3700, logic reports the value entered in the Behavior > Behavior Management > Event > Comments field.
|
Alphanumeric | BehaviorEvent. comments | Behavior > Behavior Management > Incident > Event > Comments |
OFF DESC5 | Reports additional comments for OT5. When OT5 = 1097, 1650, 1660, 1697, 1897, 2197, 2797, 3097, 3197, 3297, 3397, 3597, 3600, 9000, MA05, MA19, 3700, logic reports the value entered in the Behavior > Behavior Management > Event > Comments field.
|
Alphanumeric | BehaviorEvent. comments | Behavior > Behavior Management > Incident > Event > Comments |
INC DESC | Reports a general description of the incident.
|
Alphanumeric | BehaviorDetail. details | Behavior > Behavior Management > Incident Detail Information > Details |
RETALIATION | Report whether offense is retaliation related or not.
|
Alphanumeric, 3 | Behavior > Behavior Management > Incident > Event Details > Retaliation - Related |
Previous Versions
Offense Extract (Massachusetts) [.1929 - .2024]