Tool Search: Extracts
The Discipline Extract collects Resolution assigned to Offenders in behavior Offenses.
Discipline Extract Editor
Report Logic
A record will report for each student with a Role = 'Offender' and a Relationship to school with a dictionary value of 'student' on the Behavior Event that also meets the following criteria:
- A Participant has a Primary enrollment on the 'Date of Incident' in order to report a record.
- A Behavior Resolution is connected to the student offender with:
- The Resolution Start Date is between the 1st instructional day of the Incident calendar and the Effective Date, AND a resolution is mapped to a proper state code (Behavior > Admin > Resolution Type > State Resolution Code (Mapping))
OR - The student offender has a Behavior Event mapped to state event code
- The Resolution Start Date is between the 1st instructional day of the Incident calendar and the Effective Date, AND a resolution is mapped to a proper state code (Behavior > Admin > Resolution Type > State Resolution Code (Mapping))
One record will report per resolution with a valid State Resolution Code mapped.
Generating the Extract
- Select Discipline 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 a Discipline 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.
Example of the Report in HTML Format
Extract Layout
Element Name | Description | Location |
|---|---|---|
OFF ID | The Incident Number. Numeric, 6 digits | BehaviorEvent.incidentID Behavior Management > Incident > Incident ID |
OFF DATE | The date the incident occurred. Date field, 10 character (MM/DD/YYYY) | BehaviorEvent.timestamp Behavior Management > Incident > Date of Incident |
SASID | The state-assigned identification number of the student. Numeric, 10 digits | Person.stateID Demographics > State ID |
FN | The participant's first name. Alphanumeric, 50 characters | Identity.firstName Demographics > First Name |
LN | The participant's last name. Logic reports the student's last name. Only hyphens, periods or apostrophes will report for the last name. Alphanumeric, 50 characters | Identity.lastName Demographics > Last Name |
DOB | The participant's date of birth. Date field, 10 characters (MM/DD/YYYY ) | Identity.birthDate Demographics > Date of Birth |
PST | Indicates if the participant is involved in special education according to the Primary enrollment active on the Date of Incident.
The enrollment viewed is the enrollment that was active on the Date of Incident, with priority given to the Primary enrollment. Numeric, 1 digit | Calculated, not dynamically stored Special Ed > Documents; Enrollments > Special Ed Fields > Special Ed Setting |
DAT | Reports the Disciplinary action taken (Behavior Resolution) code. Logic reports the code with the highest calculated DM value, when the resolution is mapped to a state code of 1-5. If more than one resolution is mapped to a state code of 1-5 qualifies as the highest DM value, reports the highest mapped state code. If the resolution is mapped to a state code of 6, reports as 6. Numeric, 1 digit | BehaviorResolution.code Behavior Management > Incident > Resolution |
BI OFF | This field reports blank. | N/A |
SD | The Start Date of the disciplinary action. Report 1 record per resolution with a State Resolution Code Mapping 1-6. Date field, 10 characters (MM/DD/YYYY) | BehaviorRevolution. discAssignDate Behavior Management > Incident > Resolution > Resolution Date |
RD | The date the participant returned to school. Reporting logic is as follows:
Date field, 10 characters (MM/DD/YYYY) | BehaviorResolution. endDate Behavior Management > Incident Management Editor > Events and Participants > Resolution Details > Resolution End Date |
ERD | Reports as blank. | N/A |
DM | This field reports number of school days missed based on the calculations below
Numeric, 3 digits | BehaviorResolution. Behavior > Behavior Resolution > Resolution Date |
AEINC | This field reports blank. | N/A |
AE | Report the Education Services provided.
| BehaviorResolution.serviceProvided Behavior Behavior Resolution > Ed Services Provided Code |
| ARREST | Indicates a school-related arrest referring to an arrest of a student for any activity conducted on school grounds, or during off-campus activities (including while taking school transportation), or due to a referral by any school official. All school-related arrests are considered referrals to law enforcement.
Alphanumeric, 1 character (Y or N) | dbo.BehaviorResoltuion. stateResCode dbo.CampusAttribute WHERE object = 'BehaviorResolution' AND element = 'lawEnforcement' Behavior Management > Add/Edit Resolution > Resolution Details > Arrest |
| LAWENFREF |
Alphanumeric, 2 characters | BehaviorResolution.code Behavior > Behavior Resolution > Behavior Resolution |
| APPEAL | Reports a null value. | N/A |
| AEX | Reports a null value. | N/A |
| SOT1 | Reports the first valid Offense ID (Event Type Code). 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 reports from the lowest Event ID that has a state valid code.
For Standard Code 9000 (old code of 18):
Standard Code 9000 may only be reported in SOT1. SOT1 cannot report the same value as any other SOT field. Field reports the same value reported in OT1 of the Offense Report. Alphanumeric, 3 characters | BehaviorEvent.code1 Behavior Management > Incident > Event > State Code |
| SOT2 | ||
| SOT3 | Reports the 3rd valid Offense ID. 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 third lowest Event ID that has a valid Standard state code.
When there is no third valid standard state code, report 500. Field reports the same value reported in OT3 of the Offense Report. Alphanumeric, 3 characters | BehaviorEvent.code3 Behavior Management > Incident > Event > State Code |
| SOT4 | Reports the 4th valid Offense ID. From across all Behavior Events associated with this Incident, logic reports 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 state valid code.
When there is no fourth valid standard state code, report 500. Field reports the same value reported in OT4 of the Offense Report. Alphanumeric, 3 characters | BehaviorEvent.code4 Behavior Management > Incident > Event > State Code |
| SOT5 | Reports the 5th valid Offense ID. 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 fifth lowest Event ID that has a valid Standard state code.
When there is no fifth valid standard state code, report 500. Field reports the same value reported in OT5 of the Offense Report. Alphanumeric, 3 characters | BehaviorEvent.code5 Behavior Management > Incident > Event > State Code |
