Florida Arrest Affidavit Data Dictionary Version 1.3, Lecture notes of Criminal Justice

Download Florida Arrest Affidavit Data Dictionary Version 1.3 and more Lecture notes Criminal Justice in PDF only on Docsity!

Criminal Justice Analytics Bureau

Uniform Crime Reporting

Florida Arrest Affidavit

Data Dictionary

Version 1. 3

Contents

Version Control

Version Description of Change Date Action 1.0 Initial Version 9 /16/2019 Approved by CJJIS Council 1.1 Expanded/added definitions Added X-Path Reorganized elements Included CJJIS Council amendment for victim confidentiality indicator 12 /17/19 Approved by CJJIS Council 1.2 Updated name from Uniform Arrrest Affidavit to Florida Arrest Affidavit Updated to synchronized with FDLE IEPD version 1. Added ICD reference Expanded elements for officer affirming, addresses, victim organization, statute-related elements, Special Operations, DUI/Chemical Test Removed Bond DateUpdated definitions Added Appendices 7/29/20 Approved by CJJIS Council 1.2 rev1 Updated Height and Arresting Agency Person Identifier 7/ 19 /2 1 Approved by CJJIS Council 1.3 Added Data Elements: Arrestee Sequence Number and Arrestee Armed with Code Updated State Identification Number (SID) Expanded elements for Special Operations Added Appendix M 11/30/2021 Approved by CJJIS Council

Guide for Use

This document encompasses the data elements the Florida Department of Law Enforcement (FDLE) needs to support 943.6871(10), F.S. This statute, known as Criminal Justice Data Transparency (CJDT) created the Florida Arrest Affidavit, also known as the uniform arrest affidavit, so each state, county, and municipal law enforcement agency can facilitate complete, accurate, and timely collection and reporting of data from each criminal offense arrest. This document is focused on the data elements required for inclusion in the Florida Arrest Affidavit. This requirement is based on statute and workgroup input as well as related elements needed to increase uniformity and completeness of the data. Each element has a definition and data format type. The dictionary elaborates on data format types and the XPath. Business rules are also included. The Criminal Justice and Juvenile Information Systems (CJJIS) Council has adopted the data dictionary elements as the standard. Where applicable to the individual arrest, agencies should share the entirety of the collected data for the data fields defined in this document. Format Types Each field contains a format type. The following list contains the types of formats that may be found in this document. XML Data Type Format Type Description/Example xs:string Alphabetic Only characters A through Z unless otherwise noted Alphanumeric Only number and characters A through Z unless otherwise noted Code Value* A list of values – only values listed will be valid xs:decimal Decimal A number that allows decimals; example:

xs:integer Number Only numbers 0123456789 xs:boolean True or False Two values only; example: Yes or No or a check box xs:date YYYY-MM-DD Only Date; example: 2002- 05 - 30 xs:dateTime YYYY-MM-DDThh:mm:ss Data and time are submitted together; example: 2000- 08 - 23T14:31:00Z xs:time hh:mm:ss Only Time; example: 09:30: *Some code values in the XML may include values not listed in this document. Only values that pertain to the arrest affidavit are recorded in this document.

Administrative Elements

These elements make-up the administratively tracked portions of the arrest affidavit to allow for easy identification of specific arrest events. The administrative related data elements are:

• Arresting Agency Originating Agency Identifier (ORI)
• Arresting Agency Case Number
• Arrest Transaction Number
• Arrest Date
• Arrest Location*
• Arrest Type
• Booking Agency ORI
• Incident Date (range)
• Offense Date (range)
• Uniform Case Number (Court provided)
• Evidence Confiscated
• Special Operations
• Arrest Narrative
• Court Name
• Court Date and Time
• Court Location*
• Arresting Officer and Witnessing Signature The definitions for each element are provided on the following pages.

• Location elements are defined in the Address Elements section of this document.

Arresting Agency Originating Agency Identifier (ORI)

Definition: The Arresting Agency Originating Agency Identifier (ORI) that made the arrest. ORI is a nine-character identifier assigned to an agency. Format: Alphanumeric, maximum characters 9 Example: FL Value Options: Must be a valid Florida ORI. Additional Information: The Arresting Agency ORI must be provided for each arrest. X-Path: //fdle:Submission/fdle:Report/j:Arrest/j:ArrestAgency/j:OrganizationAugmentation/j:Organization ORIIdentification/nc:IdentificationID

Arrest Transaction Number

Definition: The number assigned by the arresting agency to an arrest event to identify it uniquely. Format: Alphanumeric Example: MB Value Options : The valid characters are numeric values 0 through 9 and alphabetic values A through Z. Additional Information: This element is sometimes referred to as Arrest Report Number. This number is typically assigned by the Records Management System. Arrest Transaction Number must be provided for each arrest. X-Path: //fdle:Submission/fdle:Report/j:Arrest/j:ArrestAgencyRecordIdentification/nc:IdentificationID

Arrest Date

Definition: The arrest date (and time) when a law enforcement officer takes a person into custody. Format: Date YYYY - MM-DD or DateTime: YYYY-MM-DDThh:mm:ss Example: 2019 - 05 - 16 2019 - 05 - 26T 09 :30:10Z Value Options : Values of the year (YYYY) must be 20 00 through current year. Cannot be a future date. Additional Information: Arrest Date must be provided for each arrest. Arrest Date cannot be earlier that Incident Date, Incident Date Start, Offense Date, or Offense Date Start. Either the Date or the DateTime field may be submitted. One is required, both cannot be submitted. X-Path: //fdle:Submission/fdle:Report/j:Arrest/nc:ActivityDate/nc:Date Or //fdle:Submission/fdle:Report/j:Arrest/nc:ActivityDate/nc:DateTime

Booking Agency Originating Agency Identifier (ORI)

Definition: The ORI of the agency that will complete the booking process at the appropriate facility for the defendant. ORI is a nine-character identifier assigned to an agency. Format: Alphanumeric, maximum characters 9 Example: FL Value Options: Must be a valid Florida ORI. X-Path: //fdle:Submission/fdle:Report/j:Booking/j:BookingAgency/j:OrganizationAugmentation/j:Organiza tionORIIdentification/nc:IdentificationID

Incident Date

Definition: The date (and time) the alleged incident occurred. Format: Date : YYYY - MM-DD DateTime: YYYY-MM-DDThh:mm:ss Example: 2015 - 05 - 27 or 2015 - 05 - 07T14:30:04Z Value Options: Values of the year (YYYY) must be 1900 through current year. Additional information: This date cannot be a future date. If Incident Date provided, then Incident Date Range is not allowed. The date cannot exceed the current system date. Either the Date or the DateTime format may be submitted, not both. X-Path: /fdle:Submission/fdle:Report/j:Incidentnc:ActivityDate/nc:Date Or //fdle:Submission/fdle:Report/j:Incident/nc:ActivityDate/nc:DateTime

Date of Incident End Range

Definition : The last possible incident date (and time) if the incident date is unknown, or if the incident was beyond a single calendar day. Format : Date : YYYY - MM-DD DateTime: YYYY-MM-DDThh:mm:ss Example : If the incident date is unknown but a range is estimated, record the range. For a date of April to May of 2019 at the time of the crime, record the end date as 2019- 05 - 31. Value Options : Date of Incident may be provided as a single value or range (Date Start Range /Date End Range) but not as a combination of value and range. Additional information: Date Start Range must be less than Date End Range. This date cannot be a future date. If Incident Range provided, then Incident Date is not allowed. Either the Date or the DateTime format may be submitted, not both. X-Path: /fdle:Submission/fdle:Report/j:Incident/nc:ActivityDate/nc:DateRange/nc:EndDate/nc:Date Or /fdle:Submission/fdle:Report/j:Incident/nc:ActivityDate/nc:DateRange/nc:EndDate/nc:DateTime

Offense Date

Definition: The date (and time) the offense occurred. Format: Date : YYYY - MM-DD DateTime: YYYY-MM-DDThh:mm:ss Example: 2015 - 05 - 27 2015 - 05 - 27T04:30:26Z Value Options: Values of the year (YYYY) must be 1900 through current year. Additional information: This date cannot be a future date. If Offense Date provided, then Offense Date Range is not allowed. Either the Date or the DateTime format may be submitted, not both. X-Path: //fdle:Submission/fdle:Report/j:Offense/nc:ActivityDate/nc:Date Or //fdle:Submission/fdle:Report/j:Offense/nc:ActivityDate/nc:DateTime