Offense Extract (Massachusetts)

Last Modified on 12/16/2024 9:46 am CST

Tool Search: Extracts

The Offense Extract collects records of Offenses that included Offender participants. 

Screenshot of Offense Extract Editor.Offense Extract Editor

Report Logic

A record reports 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
  • 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

  1. Select Offense Extract as the Extract Type.
  2. 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.
  3. 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.
  4. Mark the Header Off checkbox if the header row should not be included in the extract.
  5. Select an Ad hoc Filter to limit report results.
  6. 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.

Screenshot of State Format (CSV).State Format (CSV) 

SCreenshot of HTML Format. 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 Management > Incident > Incident ID

OFF DATE

The date the Offense occurred.

Date field, 10 character

MM/DD/YYYY

BehaviorEvent.timestamp

Behavior Management > Incident > Date of Incident

SCH NAMEThe name of the school reporting the Offense.Alphanumeric, 40 charactersSchool.name School Information > Name
SCH CODE

Reports the 8-digit Incident Calendar ID Number. This is the calendar the Incident was created in.

  • The first 4 characters is the District Number (left fill with zeros)
  • Characters 5-8 are the first 4 characters of the School Number (left fill with zeros).

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 

School Information > Number
OFF INDReports as Y.Alphanumeric, YBehaviorEvent.code1 - .code5Behavior Management > Incident > Event > Event ID
DISC INDReports as Y if a Resolution of 1-6 is assigned to a participant in the Offense. Otherwise reports as N.Alphanumeric, Y or NBehaviorResolution. codeBehavior 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

  • Valid codes = 1010, 1020, 1030, 1040, 1050, 1097, 1100, 1300, 1400, 1610, 1620, 1630, 1640, 1650, MA02, 1660, MA01, MA03, 1670, 1680, 1697, 1700, 1810, 1820, 1897, 1900, 2000, 2110, 2120, 2300, 2600, 2710, 2720, 2730, 2740, 2797, 2800, 2900, 3010, 3020, 3097, 3110, 3120, 3197, 3210, 3220, 3230, 3240, 3297, 3310, 3320, 3330, 3340, 3350, 3397, 3400, 3510, 3520, 3597, MA05, MA19, 0011, 0012, 0013, 0021, 0023, 0029, 0030, 0040, 0050, MA51, 0090
  • If the student has a Behavior Event associated with an Event Type with State Event Mapping Code = 3700, report the 4-digit Standard Code selected for Weapon Type.

For Standard code 9000 (old code 18):

  • When a Behavior Resolution mapped to 1 through 5 is NOT connected to the Behavior Event mapped to standard code 9000, this Behavior Event must not be considered to report.
  • When OT1 = 9000, OT2 - OT5 reports 500.

Code 9000 may only be reported in OT1. OT1 cannot report the same value as OT2-OT5.

Alphanumeric, 3 charactersBehaviorEvent.code1Behavior 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

  • Valid codes = 1010, 1020, 1030, 1040, 1050, 1097, 1100, 1300, 1400, 1610, 1620, 1630, 1640, 1650, MA02, 1660, MA01, MA03, 1670, 1680, 1697, 1700, 1810, 1820, 1897, 1900, 2000, 2110, 2120, 2300, 2600, 2710, 2720, 2730, 2740, 2797, 2800, 2900, 3010, 3020, 3097, 3110, 3120, 3197, 3210, 3220, 3230, 3240, 3297, 3310, 3320, 3330, 3340, 3350, 3397, 3400, 3510, 3520, 3597, MA05, MA19, 0011, 0012, 0013, 0021, 0023, 0029, 0030, 0040, 0050, MA51, 0090
  • If the student has a Behavior Event associated with an Event Type with State Event Mapping Code = 3700, report the 4-digit Standard Code selected for Weapon Type.
  • If Standard Code = 9000 for OT2, report 500.
  • When there is no second valid Standard state code, report 500.
  • OT2 cannot report the same value as any other OT field unless they report as 500.
Alphanumeric, 3 characters BehaviorEvent.code2Behavior 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

  • Valid codes = 1010, 1020, 1030, 1040, 1050, 1097, 1100, 1300, 1400, 1610, 1620, 1630, 1640, 1650, MA02, 1660, MA01, MA03, 1670, 1680, 1697, 1700, 1810, 1820, 1897, 1900, 2000, 2110, 2120, 2300, 2600, 2710, 2720, 2730, 2740, 2797, 2800, 2900, 3010, 3020, 3097, 3110, 3120, 3197, 3210, 3220, 3230, 3240, 3297, 3310, 3320, 3330, 3340, 3350, 3397, 3400, 3510, 3520, 3597, MA05, MA19, 0011, 0012, 0013, 0021, 0023, 0029, 0030, 0040, 0050, MA51, 0090
  • If the student has a Behavior Event associated with an Event Type with State Event Mapping Code = 3700, report the 4-digit Standard Code selected for Weapon Type.
  • If Standard Code = 9000 for OT3, report 500.
  • When there is no third valid Standard state code, report 500.
  • OT3 cannot report the same value as any other OT field unless they report as 500.
Alphanumeric, 3 characters BehaviorEvent.code3Behavior 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

  • Valid codes = 1010, 1020, 1030, 1040, 1050, 1097, 1100, 1300, 1400, 1610, 1620, 1630, 1640, 1650, MA02, 1660, MA01, MA03, 1670, 1680, 1697, 1700, 1810, 1820, 1897, 1900, 2000, 2110, 2120, 2300, 2600, 2710, 2720, 2730, 2740, 2797, 2800, 2900, 3010, 3020, 3097, 3110, 3120, 3197, 3210, 3220, 3230, 3240, 3297, 3310, 3320, 3330, 3340, 3350, 3397, 3400, 3510, 3520, 3597, MA05, MA19, 0011, 0012, 0013, 0021, 0023, 0029, 0030, 0040, 0050, MA51, 0090
  • If the student has a Behavior Event associated with an Event Type with State Event Mapping Code = 3700, report the 4-digit Standard Code selected for Weapon Type.
  • If Standard Code = 9000 for OT4, report 500.
  • When there is no fourth valid Standard state code, report 500.
  • OT4 cannot report the same value as any other OT field unless they report as 500.
Alphanumeric, 3 characters BehaviorEvent.code4Behavior 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

  • Valid codes = 1010, 1020, 1030, 1040, 1050, 1097, 1100, 1300, 1400, 1610, 1620, 1630, 1640, 1650, MA02, 1660, MA01, MA03, 1670, 1680, 1697, 1700, 1810, 1820, 1897, 1900, 2000, 2110, 2120, 2300, 2600, 2710, 2720, 2730, 2740, 2797, 2800, 2900, 3010, 3020, 3097, 3110, 3120, 3197, 3210, 3220, 3230, 3240, 3297, 3310, 3320, 3330, 3340, 3350, 3397, 3400, 3510, 3520, 3597, MA05, MA19, 0011, 0012, 0013, 0021, 0023, 0029, 0030, 0040, 0050, MA51, 0090
  • If the student has a Behavior Event associated with an Event Type with State Event Mapping Code = 3700, report the 4-digit Standard Code selected for Weapon Type.
  • If Standard Code = 9000 for OT5, report 500.
  • When there is no fifth valid Standard state code, report 500.
  • OT5 cannot report the same value as any other OT field unless they report as 500.
Alphanumeric, 3 characters BehaviorEvent.code5Behavior Management > Incident > Event > State Code
VS

Reports the number of victims who were students.

  • From across all Behavior Events associated with the Incident ID, report the number of UNIQUE (by personID) Participants with a Relationship To School selection with dictionary Value of student, and a Role = Victim.
  • When there are no students that meet the counting criteria, this field must report 0 (instead of Null).
Numeric, 3 digitsBehaviorEvent. studentVictims

Participant Path: 

Behavior > Behavior Management > Events and Participants > Participant(s) Detail Event Type Mapping


Event Type Mapping Path:

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.

  • Report the highest number entered in (Student Info > General > Behavior > Behavior Management > Incident Management Editor > Detail Info > Number of School Personnel Victims) from across all Events.
  • When Number of School Personnel Victims = Null across all viewed Events, report 0 (instead of Null).
Numeric, 3 digitsBehaviorEvent. schVictims

Behavior > Behavior Management > Incident Management Editor > Detail Information > Number of School Personnel Victims

Participant Path: 

Behavior > Behavior Management > Events and Participants > Participant(s) Detail

Event Type Mapping Path:

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.

  • Report the highest number entered in (Student Information > General > Behavior > Behavior Management > Incident Management Editor > Detail Information > Number of Non-Sch Personnel Victims) from across all Events.
  • When Number of Non-School Personnel Victims = Null across all viewed Events, report 0 (instead of Null).


Numeric, 3 digitsBehaviorEvent. nonschVictims

Behavior Management > Incident > Event > Number of Non-Sch Personnel Victims

Participant Path: 

Behavior > Behavior Management > Events and Participants > Participant(s) Detail

Event Type Mapping Path:

Behavior > Event Types > Behavior Event Type Editor > Behavior Event Type Detail > State Event Code (Mapping)


VU

Reports the number of victims who were unknown.

  • Report the highest number entered in (Student Information > General > Behavior > Behavior Management > Incident Management Editor  >Detail Information > Number of Unknown Victims) from across all Events.
  • When Number of Unknown Victims = Null across all viewed Events, report 0 (instead of Null).



Numeric, 3 digitsBehaviorEvent. unknownVictims

Behavior Management > Incident > Event > Number of Unknown Victims

Participant Path: 

Behavior > Behavior Management > Events and Participants > Participant(s) Detail

Event Type Mapping Path:

Behavior > Event Types > Behavior Event Type Editor > Behavior Event Type Detail > State Event Code (Mapping)


OFFES

Reports the number of offenders who were students.

  • From across all Behavior Events associated with the Incident ID, report the number of UNIQUE (by personID) Participants with a Relationship To School selection with dictionary Value of student, and a Role = Offender WHEN the student has a Behavior Resolution associated to them for this event that has a State Resolution Code (Mapping) = 1 - 6.

  • When there are no students that meet the counting criteria, this field must report 0 (instead of Null).

Numeric, 3 digitsBehaviorEvent. studentOffenders

Behavior Management > Incident > Event > Number of Student Offenders

Participant Path: 

Behavior > Behavior Management > Events and Participants > Participant(s) Detail

Event Type Mapping Path:

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.

  • Report the highest number entered in (Student Information > General > Behavior > Behavior Management > Incident Management Editor > Detail Info > Number of Non-Student Offenders) from across all Events.
  • When Number of Non-Student Offenders = Null across all viewed Events, report 0 (instead of Null).
Numeric, 3 digitsBehaviorEvent. nonstudentOffenders

Behavior Management > Incident > Event > Number of Non-Student Offenders

Participant Path: 

Behavior > Behavior Management > Events and Participants > Participant(s) Detail

Event Type Mapping Path:

Behavior > Event Types > Behavior Event Type Editor > Behavior Event Type Detail > State Event Code (Mapping)


OFFEU

Reports the number of offenders who were unknown.

  • Report the highest number entered in (Student Information > General > Behavior > Behavior Management > Incident Management Editor > Detail Info > Number of Unknown Offenders) from across all Events.
  • When Number of Unknown Offenders = Null across all viewed Events, report 0 (instead of Null).
Numeric, 3 digitsBehaviorEvent. unknownOffenders

Behavior Management > Incident > Event > Number of Unknown Offenders

Participant Path: 

Behavior > Behavior Management > Events and Participants > Participant(s) Detail

Event Type Mapping Path:

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).

  • When OT1 = 1097, 1650, 1660, 1697, 1897, 2197, 2797, 3097, 3197, 3297, 3397, 3597, 3600, 9000, MA05, MA19, 3700, logic reports the value entered in Behavior > Behavior Management > Event > Comments
    • Any characters not 0-9 or A-Z are replaced by a space.
    • If a weapon with a Standard Code = 0013 or 0040 is reported for the incident, the weapon description is reported.
      • If the weapon description is null, the Event > Comments is reported.
  • If no value is entered in the Comments field, the field reports as null.
AlphanumericBehaviorEvent. commentsBehavior Management > Incident > Event > Comments
PHYS INJ

Indicates if the Offense resulted in physical injury.

  • When OT1, OT2, OT3, OT4, or OT5 = 1300, 1700, 1810, 1820, 2000, 2300, 2600, 2800, 3010, 3020 AND Physical Injury = Checked on any Behavior Event associated with the Incident that has a valid 4-digit Standard Code for the State Event Mapping code, a value of Y is reported.
  • When OT1, OT2, OT3, OT4, or OT5 = 1300, 1700, 1810, 1820, 2000, 2300, 2600, 2800, 3010, 3020, AND AND Physical Injury = NOT Checked on any Behavior Event associated with the Incident that has a valid 4-digit Standard Code for the State Event Mapping code, a value of N is reported.
  • When OT1, OT2, OT3, OT4, or OT5  has a valid Standard Code for the State Event Mapping but none of OT1, OT2, OT3, OT4, or OT5 = 1300, 1700, 1810, 1820, 2000, 2300, 2600, 2800, 3010, 3020, a value of X is reported.
  • If none of the criteria above is met, a value of X is reported.
Alphanumeric, 1 characterBehaviorEvent. injuryBehavior Management > Incident > Event > Physical Injury
OFF DESC2

Reports additional comments for OT2.

  • When OT2 = 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.

      • Any characters not 0-9 or A-Z are replaced by a space.
      • If a weapon with a Standard Code = 0013 or 0040 is reported for the incident, the weapon description is reported.
        • If the weapon description is null, the Event > Comments is reported.
    • If no value is entered in the Comments field, the field reports as null.
AlphanumericBehaviorEvent. commentsBehavior 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.


    • Any characters not 0-9 or A-Z are replaced by a space.
    • If a weapon with a Standard Code = 0013 or 0040 is reported for the incident, the weapon description is reported.
      • If the weapon description is null, the Event > Comments is reported.
  • If no value is entered in the Comments field, the field reports as null.
AlphanumericBehaviorEvent. commentsBehavior 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.


    • Any characters not 0-9 or A-Z are replaced by a space.
    • If a weapon with a Standard Code = 0013 or 0040 is reported for the incident, the weapon description is reported.
      • If the weapon description is null, the Event > Comments is reported.
  • If no value is entered in the Comments field, the field reports as null.
AlphanumericBehaviorEvent. commentsBehavior 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.


    • Any characters not 0-9 or A-Z are replaced by a space.
    • If a weapon with a Standard Code = 0013 or 0040 is reported for the incident, the weapon description is reported.
      • If the weapon description is null, the Event > Comments is reported.
  • If no value is entered in the Comments field, the field reports as null.
AlphanumericBehaviorEvent. commentsBehavior Management > Incident > Event > Comments
INC DESC

Reports a general description of the incident.

  • Logic reports the text entered in the Behavior Management > Incident Management Editor > Incident Detail Information > Details field.
    • Any characters not 0-9 or A-Z are replaced by a space.
AlphanumericBehaviorDetail. detailsBehavior Management > Incident Detail Information > Details
RETALIATIONReport whether offense is retaliation related or not.
  • If any offense on the incident has Retaliation-Related checked, report Yes.
  • Else report No.
Alphanumeric, 3
Behavior Management > Incident > Event Details > Retaliation - Related


Previous Versions

Offense Extract (Massachusetts) [.1929 - .2024]

Save

Save

Related Articles

Was this helpful?
Thank you for your feedback!
User Icon

Thank you!

Copyright ©️ 2010-2023 Infinite Campus, Inc. All rights reserved. | Terms of Use | Privacy Policy | infinitecampus.com