diff --git a/.github/workflows/preview.yml b/.github/workflows/preview.yml new file mode 100644 index 0000000..236967d --- /dev/null +++ b/.github/workflows/preview.yml @@ -0,0 +1,23 @@ +name: Deploy PR Previews +on: + push: + branches: + - master + pull_request: + types: + - opened + - synchronize +concurrency: preview-${{ github.ref }} +jobs: + deploy-preview: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v3 + - name: Deploy PR Preview + uses: teisdbr/pr-preview-action@v1.4.7 + with: + token: ${{ secrets.PR-Preview-Action }} + preview-branch: master + source-dir: . + umbrella-dir: pr-preview + action: auto \ No newline at end of file diff --git a/.github/workflows/static.yml b/.github/workflows/static.yml new file mode 100644 index 0000000..0ba8230 --- /dev/null +++ b/.github/workflows/static.yml @@ -0,0 +1,43 @@ +# Simple workflow for deploying static content to GitHub Pages +name: Deploy static content to Pages + +on: + # Runs on pushes targeting the default branch + push: + branches: ["master"] + + # Allows you to run this workflow manually from the Actions tab + workflow_dispatch: + +# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages +permissions: + contents: read + pages: write + id-token: write + +# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued. +# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete. +concurrency: + group: "pages" + cancel-in-progress: false + +jobs: + # Single deploy job since we're just deploying + deploy: + environment: + name: github-pages + url: ${{ steps.deployment.outputs.page_url }} + runs-on: ubuntu-latest + steps: + - name: Checkout + uses: actions/checkout@v4 + - name: Setup Pages + uses: actions/configure-pages@v5 + - name: Upload artifact + uses: actions/upload-pages-artifact@v3 + with: + # Upload entire repository + path: '.' + - name: Deploy to GitHub Pages + id: deployment + uses: actions/deploy-pages@v4 diff --git a/Gemfile.lock b/Gemfile.lock index 4616af0..07ec899 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -199,22 +199,22 @@ GEM rb-inotify (~> 0.9, >= 0.9.7) ruby_dep (~> 1.2) mercenary (0.3.6) - mini_portile2 (2.8.1) + mini_portile2 (2.8.7) minima (2.5.0) jekyll (~> 3.5) jekyll-feed (~> 0.9) jekyll-seo-tag (~> 2.1) minitest (5.13.0) multipart-post (2.1.1) - nokogiri (1.14.3) - mini_portile2 (~> 2.8.0) + nokogiri (1.15.6) + mini_portile2 (~> 2.8.2) racc (~> 1.4) octokit (4.14.0) sawyer (~> 0.8.0, >= 0.5.3) pathutil (0.16.2) forwardable-extended (~> 2.6) public_suffix (3.1.1) - racc (1.6.2) + racc (1.8.0) rb-fsevent (0.10.3) rb-inotify (0.10.0) ffi (~> 1.0) diff --git a/_data/data-element-defs.json b/_data/data-element-defs.json index 8402c1a..d492426 100644 --- a/_data/data-element-defs.json +++ b/_data/data-element-defs.json @@ -2319,7 +2319,7 @@ }, { "de_num": "52", "name": "DISPOSITION OF ARRESTEE UNDER 18", - "definition": "Used only if the arrestee was 16 years of age or younger at the time of arrest.", + "definition": "Mandatory field for ANY Arrestee that is 17 years of age or younger. The Federal UCR program considers juveniles as under 18 years of age regardless of state law. The LIBRS program will stay aligned with the FBI and collect this field for arrestees 17 and younger even though this differs from the latest state Juvenile Age Definition.\n\nIf the arrestee is 17 and considered an adult in Louisiana after April 19, 2024, please use A – Referred to Criminal or Adult Court.", "length": "1", "format": "A", "comment": "", diff --git a/_data/error.json b/_data/error.json index ff8df06..71279f3 100644 --- a/_data/error.json +++ b/_data/error.json @@ -1945,7 +1945,7 @@ "err_no": 16052, "err_message": "DISPOSITION MUST BE ENTERED WHEN AGE IS 17 AND YOUNGER", "err_desc": { - "52": "If Age of Arrestee (DE 47) is under 18 (17 and younger), then Disposition of Arrestee Under 18 (DE 52) must be entered.

Note: As of January 1st, 2020, all offenders under the age of 18 are considered juveniles." + "52": "If Age of Arrestee (DE 47) is under 18 (17 and younger), then Disposition of Arrestee Under 18 (DE 52) must be entered.

The Federal UCR program considers juveniles as under 18 years of age regardless of state law. The LIBRS program will stay aligned with the FBI even though the Juvenile Age definition has changed. If the arrestee is 17 and considered an adult in Louisiana after April 19, 2024, please use A – Referred to Criminal or Adult Court." } }, "16053": { @@ -2393,9 +2393,10 @@ "22100": { "active": "true", "err_no": 22100, - "err_message": "AGE MUST BE '01' - '17' FOR JUVENILE OFFENSES", + "err_message": "AGE MUST BE '01' - '16' FOR JUVENILE OFFENSES", "err_desc": { - "47": "When Juvenile Qualifiers are used, Age of Arrestee (DE 47) must be '01' thru '17' (this includes 17) for the following Juvenile Qualifiers:{::nomarkdown}{:/}Note: As of January 1st, 2020, all offenders under the age of 18 are considered juveniles." + "47": "When Juvenile Qualifiers are used, Age of Arrestee (DE 47) must be '01' thru '16' (this includes 16) for the following Juvenile Qualifiers:{::nomarkdown}{:/}The Louisiana Juvenile Age definition has changed over the years. LIBRS uses the age along with the incident date to validate the Juvenile Qualifiers according to the following rules:", + "37": "When Juvenile Qualifiers are used, Age of Offender [At Time of Incident] (37) must be ‘01’ thru ‘16’ (this includes 16) for the following Juvenile Qualifiers:{::nomarkdown}{:/}The Louisiana Juvenile Age definition has changed over the years. LIBRS uses the age along with the incident date to validate the Juvenile Qualifiers according to the following rules:" } }, "22105": { diff --git a/data-element-values.md b/data-element-values.md index 1f3a849..97bef43 100644 --- a/data-element-values.md +++ b/data-element-values.md @@ -3,9 +3,9 @@ title: LIBRS Data Element Available Values layout: default permalink: /data-element-values --- - # LIBRS Data Element Available Values -____ + +--- @@ -32,7 +32,7 @@ ____ {% for values in subsection.values %} - + {% endfor %} @@ -46,13 +46,13 @@ ____
{{values.code}} -  -  {{values.desc}}
-

+`

` # Allowable Property Loss Types (DE 14) By NIBRS and Attemped/Completed -___ +--- -The following table outlines the values that are allowed to be used for data Element 14, Property Loss Type, when an Offense of a particular NIBRS Code is either Attempted or Completed. +The following table outlines the values that are allowed to be used for data Element 14, Property Loss Type, when an Offense of a particular NIBRS Code is either Attempted or Completed. @@ -79,4 +79,4 @@ The following table outlines the values that are allowed to be used for data Ele {% endfor %} -
\ No newline at end of file + diff --git a/librs-spec.md b/librs-spec.md index 44a7c02..7765793 100644 --- a/librs-spec.md +++ b/librs-spec.md @@ -3,34 +3,33 @@ title: LIBRS Validation Specifications layout: default permalink: /librs-spec --- - - # LIBRS Specifications Documentation + This document contains information about the Segments, Data Elements, Requirements, Errors, and Warnings that LIBRS uses in the validation of Incident Data. ## Required Segments -The LIBRS Flat File is a space-delimited file generated by following the requirements in this document. Each section of this document outlines individual Segments. Each Segment is an individual lines in the LIBRS Flat File that contain varying information about the incident. Those bits of information are bound by the LIBRS Data Elements and their definitions/available values. +The LIBRS Flat File is a space-delimited file generated by following the requirements in this document. Each section of this document outlines individual Segments. Each Segment is an individual lines in the LIBRS Flat File that contain varying information about the incident. Those bits of information are bound by the LIBRS Data Elements and their definitions/available values. The information from an RMS needs to be output to the LIBRS Flat File in the exact specifications that are listed in this document. If not, a number of errors will occur. These errors and their common causes and resolutions can be found in the [Data Elements Defintions](./librs-spec/#librs-data-element-definitions) section of this page. In the event that no incident data is present for submission, the LIBRS Flat File should contain two Segments followed by a blank line (three lines in total): - Submission Header (00) + Submission Header (00) Submission Trailer (99) [Blank Line] Alternative Zero Submission Format (Both behave the same way, use whatever works best for you): - Submission Header (00) + Submission Header (00) Zero Record (01) Submission Trailer (99) Whenever you are submitting a file with data, however, the following segments should always be included for all Incidents that have a value of 'I' for [DE C5](./librs-spec#action-type-c5): - 00 - Submission Header + 00 - Submission Header 10 - Administrative Segment 20 - Offense Segment 40 - Offender Segment @@ -40,80 +39,83 @@ Whenever you are submitting a file with data, however, the following segments sh Whenever you want to submit a Deletion to us (used to either permanently remove an Incident from being reported, or simply to delete and re-add because there are changes that have been made to the Incident that need to be reflected) you need to ensure the following is included: - 00 - Submission Header + 00 - Submission Header 10 - Administrative Segment (With DE C5 - Action Type = 'D') 99 - Submission Trailer Please note in all of these cases, the Submission Header and Trailer should only occur once per file. You can use any of the action types in the same Flat File. For instance, you can include all of the Deletes you'd like to make and the top of the file (after the Submission Header) and then follow it up with all of the Insertions that you'd like to make, or if you prefer include the Delete line just before the Insertion Segments for the Incident; it's purely personal preference. -___ +--- ## Data Types in this Document + In the tables that describe the Segment Layouts, you will find the following Formats listed: - Format Symbol | Format Meaning -:-------------:|---------------- -N | Numeric -A | Alphabetic -A/N | Alpha/Numeric -D | Date -G (Space) | Blank Space +| Format Symbol | Format Meaning | +| :-----------: | -------------- | +| N | Numeric | +| A | Alphabetic | +| A/N | Alpha/Numeric | +| D | Date | +| G (Space) | Blank Space |

-___ +--- # LIBRS Segments -___ +--- LIBRS, like NIBRS, it built up on Segments that contain different information about the Incidents that are being reported. This portion of this document outlines the LIBRS Segments, and the building blocks (Referred to as Data Elements) That make them up. ## Submission Header (00) -___ + +--- ### Description + The Submission Header contains the information related to the Agency that is submitting the LIBRS Flat File, as well as information about the file itself, such as the Reporting Period it encompasses and the Spec Version that it was generated with (Currently we are only accepting LIBRS Spec 2.5) ### Segment Layout - Data Element Number | Description of Data Element | Position(s) | Length | Format - :----------------------------------:|-------------------------------------------|:-----------------:|:------------:|:--------: - [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor - **00** | 1-2 | 2 | N - [C2](./librs-spec#submitting-agency-c2) | Submitting Agency | 3-22 | 20 | A - [C3](./librs-spec#submission-date-c3) | Submission Date | 23-30 | 8 | D - [C4](./librs-spec#reporting-period-c4) | Reporting Period | 31-36 | 6 | D - [C10](./librs-spec#software-id-c10) | Software ID | 37-41 | 5 | A/N - [C11](./librs-spec#software-version-c11) | Software Version | 42-51 | 10 | A/N - [C12](./librs-spec#librs-spec-indicator-c12) | LIBRS Spec Indicator | 52-54 | 3 | A/N - \*\* | Future Expansion Buffer | 55-56 | 2 | G (Space) - [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 57-58 | 2 | A - [C9](./librs-spec#padding-c9) | Padding | 59-150 | \*\* | G (Space) +| Data Element Number | Description of Data Element | Position(s) | Length | Format | +| :---------------------------------------: | -------------------------------- | :---------: | :----: | :-------: | +| [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor -**00** | 1-2 | 2 | N | +| [C2](./librs-spec#submitting-agency-c2) | Submitting Agency | 3-22 | 20 | A | +| [C3](./librs-spec#submission-date-c3) | Submission Date | 23-30 | 8 | D | +| [C4](./librs-spec#reporting-period-c4) | Reporting Period | 31-36 | 6 | D | +| [C10](./librs-spec#software-id-c10) | Software ID | 37-41 | 5 | A/N | +| [C11](./librs-spec#software-version-c11) | Software Version | 42-51 | 10 | A/N | +| [C12](./librs-spec#librs-spec-indicator-c12) | LIBRS Spec Indicator | 52-54 | 3 | A/N | +| \*\* | Future Expansion Buffer | 55-56 | 2 | G (Space) | +| [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 57-58 | 2 | A | +| [C9](./librs-spec#padding-c9) | Padding | 59-150 | \*\* | G (Space) |
- - ### Segment 00 Errors and Explanations -Error Number | Error Message | Explaination of Error -------------------|-------------------|-------------------------- -{% assign error = site.data.error["1"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["00"]}} -{% assign error = site.data.error["10003"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["00"]}} -{% assign error = site.data.error["10050"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["00"]}} -{% assign error = site.data.error["90038"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["00"]}} +| Error Number | Error Message | Explaination of Error | +| ---------------------------------------------- | ----------------------- | ------------------------ | +| {% assign error = site.data.error["1"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["00"]}} | +| {% assign error = site.data.error["10003"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["00"]}} | +| {% assign error = site.data.error["10050"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["00"]}} | +| {% assign error = site.data.error["90038"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["00"]}} | -___ +--- ## Zero Record (01) -___ + +--- ### Description + Segment 01 is used when there are no Incidents to report; IE a Zero Report. The segment can only be used when there are no Incidents present in the Flat File; there cannot be any Segments present other than 00, 01, and 99: * -Header Segment- @@ -122,159 +124,164 @@ Segment 01 is used when there are no Incidents to report; IE a Zero Report. The ### Segment Layout - Data Element Number | Description of Data Element | Position(s) | Length | Format - :---------------------------------:|-------------------------------------------------|:-------------:|:--------:|:---------: - [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor -- **01** | 1-2 | 2 | N - [2](./librs-spec#incident-number-2) | Incident Number - All Zeroes \"000000000000\" | 3-14 | 12 | N - [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 15-16 | 2 | A - [C9](./librs-spec#padding-c9) | Padding | 17-150 | \*\* | A/N +| Data Element Number | Description of Data Element | Position(s) | Length | Format | +| :--------------------------------------: | -------------------------------------------- | :---------: | :----: | :----: | +| [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor --**01** | 1-2 | 2 | N | +| [2](./librs-spec#incident-number-2) | Incident Number - All Zeroes\"000000000000\" | 3-14 | 12 | N | +| [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 15-16 | 2 | A | +| [C9](./librs-spec#padding-c9) | Padding | 17-150 | \*\* | A/N |
### Segment 01 Errors and Explanations + None -___ +---
## Administrative (10) -___ + +--- ### Description + The Administrative Segment contains basic information about the Incident that is being reported. It acts as the indication for LIBRS that a the next portion of Information is for a different incident from the previous on that was processed. This segment should always be included when: -* Performing an Action Type of 'I - Insertion' for an Incident. +* Performing an Action Type of 'I - Insertion' for an Incident. * Performing a 'D - Deletion' Action Type for an Incident. - * If you desire to delete and resubmit the Incident (easiest way to process changes for us), then simply insert a Segment 10 with a 'D' as [DE C5](./librs-spec#action-type-c5) , followed by the whole incident again (including another Segment 10 with a 'I' for [C5](./librs-spec#action-type-c5)). + * If you desire to delete and resubmit the Incident (easiest way to process changes for us), then simply insert a Segment 10 with a 'D' as [DE C5](./librs-spec#action-type-c5) , followed by the whole incident again (including another Segment 10 with a 'I' for [C5](./librs-spec#action-type-c5)). ### Segment Layout -| Data Element Number |Description of Data Element |Position(s)|Length|Format| -|:------------------------------------------------:|------------------------------------------------|:-----------:|:------:|:------:| -|[C1](./librs-spec#segment-descriptor-c1) |Segment Descriptor - **10** | 1-2 | 2 | N | -|[C5](./librs-spec#action-type-c5) |Action Type | 3 | 1 | A | -|[1](./librs-spec#ori-number-1) |ORI Number | 4-12 | 9 | A | -|[2](./librs-spec#incident-number-2) |Incident Number | 13-24 | 12 | A | -|[L53](./librs-spec#location-of-incident-geographical-coordinates-l53) |Location of Incident (Geographical Coordinates) | 25-36 | 12 | A/N | -|[L54](./librs-spec#stationdivisionprecinct-identifier-l54) |Station/Division/Precinct Identifier | 37-42 | 6 | A | -|[3](./librs-spec#incident-datehour-3) |Incident Date/Hour | 43-53 | 11 | A | -|[4](./librs-spec#cleared-exceptionally-4) |Cleared Exceptionally | 54 | 1 | A | -|[5](./librs-spec#exceptional-cleared-date-5) |Exceptional Clearance Date | 55-62 | 8 | D | -|\*\* |Future Expansion Buffer | 63-82 | 20 | G (Space) | -|[C8](./librs-spec#end-of-segment-marker-c8) |End of Segment Marker | 83-84 | 2 | A | -|[C9](./librs-spec#padding-c9) |Padding | 85-150 | \*\* | G (Space) | +| Data Element Number | Description of Data Element | Position(s) | Length | Format | +| :----------------------------------------------------------------: | ----------------------------------------------- | :---------: | :----: | :-------: | +| [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor -**10** | 1-2 | 2 | N | +| [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A | +| [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A | +| [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A | +| [L53](./librs-spec#location-of-incident-geographical-coordinates-l53) | Location of Incident (Geographical Coordinates) | 25-36 | 12 | A/N | +| [L54](./librs-spec#stationdivisionprecinct-identifier-l54) | Station/Division/Precinct Identifier | 37-42 | 6 | A | +| [3](./librs-spec#incident-datehour-3) | Incident Date/Hour | 43-53 | 11 | A | +| [4](./librs-spec#cleared-exceptionally-4) | Cleared Exceptionally | 54 | 1 | A | +| [5](./librs-spec#exceptional-cleared-date-5) | Exceptional Clearance Date | 55-62 | 8 | D | +| \*\* | Future Expansion Buffer | 63-82 | 20 | G (Space) | +| [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 83-84 | 2 | A | +| [C9](./librs-spec#padding-c9) | Padding | 85-150 | \*\* | G (Space) |
### Segment 10 Errors and Explanations -Error Number | Error Message | Explaination of Error -------------------|-------------------|-------------------------- -{% assign error = site.data.error["10055"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["10"]}} -{% assign error = site.data.error["10075"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["10"]}} +| Error Number | Error Message | Explaination of Error | +| ---------------------------------------------- | ----------------------- | ------------------------ | +| {% assign error = site.data.error["10055"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["10"]}} | +| {% assign error = site.data.error["10075"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["10"]}} | -___ +---
## Administrative Modification (11) -___ + +--- ### Description + Segment 11, Administrative Modification, is only used when performing an update to a Time Window Submission Incident (DE C5, Action Type = ‘M’). Agencies should be aware that information submitted via time windows is stored separately by the FBI and is not combined back in with normal submissions and may or may not be reported in some publications nor counted towards overall totals. ### Segment Layout - Data Element Number |Description of Data Element | Position(s) | Length | Format - :-----------------------------------:|----------------------------------|:-------------:|:--------:|:---------: - [C1](./librs-spec#segment-descriptor-c1) |Segment Descriptor -- **11** | 1-2 | 2 | N - [C5](./librs-spec#action-type-c5) |Action Type | 3 | 1 | A - [1](./librs-spec#ori-number-1) |ORI Number | 4-12 | 9 | A - [2](./librs-spec#incident-number-2) |Incident Number | 13-24 | 12 | A - [6](./librs-spec#louisiana-revised-statute-6) |Louisiana Revised Statute Number | 25-36 | 12 | A - \*\* |Future Expansion Buffer | 37-56 | 20 |G (Space) - [C8](./librs-spec#end-of-segment-marker-c8) |End of Segment Marker | 57-58 | 2 | A - [C9](./librs-spec#padding-c9) |Padding | 59-150 | \*\* |G (Space) - +| Data Element Number | Description of Data Element | Position(s) | Length | Format | +| :----------------------------------------: | --------------------------------- | :---------: | :----: | :-------: | +| [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor --**11** | 1-2 | 2 | N | +| [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A | +| [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A | +| [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A | +| [6](./librs-spec#louisiana-revised-statute-6) | Louisiana Revised Statute Number | 25-36 | 12 | A | +| \*\* | Future Expansion Buffer | 37-56 | 20 | G (Space) | +| [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 57-58 | 2 | A | +| [C9](./librs-spec#padding-c9) | Padding | 59-150 | \*\* | G (Space) |
### Segment 11 Errors and Explanations -Error Number | Error Message | Explaination of Error -------------------|-------------------|-------------------------- -{% assign error = site.data.error["11017"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["11"]}} -{% assign error = site.data.error["11097"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["11"]}} +| Error Number | Error Message | Explaination of Error | +| ---------------------------------------------- | ----------------------- | ------------------------ | +| {% assign error = site.data.error["11017"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["11"]}} | +| {% assign error = site.data.error["11097"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["11"]}} | - -___ +---
-## Offense (20) -___ +## Offense (20) + +--- ### Description + Segment 20, Offense Segment, contains information about the particular Offenses that occurred in the Incident. Note that only one Victim can be tied to an Offense, so if you have multiple Victims of the same Offense you will need to include multiple Segment 20's to link those Victims to the Offense. We get a lot of questions about this Segment, and have included more information about it in the FAQ, which can be found [here](./faq#offenses-segment-20). ### Segment Layout - Data Element Number | Description of Data Element | Position(s) | Length | Format - :--------------------------------------------------------------------:|--------------------------------------------------------|:-------------:|:--------:|:---------: - [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor - **20** | 1-2 | 2 | N - [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A - [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A - [2](./librs-spec#submitting-agency-c2) | Incident Number | 13-24 | 12 | A - [L6](./librs-spec#offense-sequence-number-l6) | Offense Sequence Number | 25-27 | 3 | N - [6](./librs-spec#louisiana-revised-statute-6) | Louisiana Revised Statute Number | 28-39 | 12 | A - [7](./librs-spec#offense-attemptedcompleted-7) | Offense Attempted/Completed | 40 | 1 | A - [24](./librs-spec#offense-connected-to-victim-sequence-number-24) | Offense Connected to Victim Sequence Number | 41-43 | 3 | N - [9](./librs-spec#location-type-9) | Location Type | 44-45 | 2 | N - [10](./librs-spec#number-of-premises-entered-10) | Number of Premises Entered | 46-47 | 2 | A/N - [11](./librs-spec#method-of-entry-11) | Method of Entry | 48 | 1 | A - [12](./librs-spec#type-of-criminal-activitygang-information-12) | Type of Criminal Activity/Gang Information Nos. 1, 2 and 3 | 49-51 | 1 (3x) | A - [13](./librs-spec#type-of-weaponforce-involved-nos-1-2-and-3-13) | Type of Weapon/Force Involved Nos. 1, 2, and 3 | 52-60 | 3 (3x) | A - [N6](./librs-spec#agency-supplied-nibrs-code-n6) | Agency Supplied NIBRS Code | 61-63 | 3 | A - [70](./librs-spec#inchoates-70) | Inchoate Modifier | 64-65 | 2 | A - \*\* | Future Expansion Buffer | 66-80 | 14 | G (Space) - [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 81-82 | 2 | A - [C9](./librs-spec#padding-c9) | Padding | 83-150 | \*\* | G (Space) +| Data Element Number | Description of Data Element | Position(s) | Length | Format | +| :------------------------------------------------------------: | ---------------------------------------------------------- | :---------: | :----: | :-------: | +| [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor -**20** | 1-2 | 2 | N | +| [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A | +| [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A | +| [2](./librs-spec#submitting-agency-c2) | Incident Number | 13-24 | 12 | A | +| [L6](./librs-spec#offense-sequence-number-l6) | Offense Sequence Number | 25-27 | 3 | N | +| [6](./librs-spec#louisiana-revised-statute-6) | Louisiana Revised Statute Number | 28-39 | 12 | A | +| [7](./librs-spec#offense-attemptedcompleted-7) | Offense Attempted/Completed | 40 | 1 | A | +| [24](./librs-spec#offense-connected-to-victim-sequence-number-24) | Offense Connected to Victim Sequence Number | 41-43 | 3 | N | +| [9](./librs-spec#location-type-9) | Location Type | 44-45 | 2 | N | +| [10](./librs-spec#number-of-premises-entered-10) | Number of Premises Entered | 46-47 | 2 | A/N | +| [11](./librs-spec#method-of-entry-11) | Method of Entry | 48 | 1 | A | +| [12](./librs-spec#type-of-criminal-activitygang-information-12) | Type of Criminal Activity/Gang Information Nos. 1, 2 and 3 | 49-51 | 1 (3x) | A | +| [13](./librs-spec#type-of-weaponforce-involved-nos-1-2-and-3-13) | Type of Weapon/Force Involved Nos. 1, 2, and 3 | 52-60 | 3 (3x) | A | +| [N6](./librs-spec#agency-supplied-nibrs-code-n6) | Agency Supplied NIBRS Code | 61-63 | 3 | A | +| [70](./librs-spec#inchoates-70) | Inchoate Modifier | 64-65 | 2 | A | +| \*\* | Future Expansion Buffer | 66-80 | 14 | G (Space) | +| [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 81-82 | 2 | A | +| [C9](./librs-spec#padding-c9) | Padding | 83-150 | \*\* | G (Space) |
### Important Notes + * Only one Victim can be related to an Offense Segment. If you have multiple Victims of the same offense, you need to include multiple Offense Segments that link to those Victims. * Please note that DE's 12 and 13 are actually three Data Elements Combined into one. Each instance of the Data Element is either 1 or 3 characters long and can include up to 3 instances, so long as mutually exclusive values are not used. - * See [Type of Criminal Activity/Gang Information Nos. 1, 2 and 3](./librs-spec#type-of-criminal-activitygang-information-12) and [Type of Weapon/Force Involved Nos. 1, 2, and 3 ](./librs-spec#type-of-weaponforce-involved-nos-1-2-and-3-13) for more details. + * See [Type of Criminal Activity/Gang Information Nos. 1, 2 and 3](./librs-spec#type-of-criminal-activitygang-information-12) and [Type of Weapon/Force Involved Nos. 1, 2, and 3 ](./librs-spec#type-of-weaponforce-involved-nos-1-2-and-3-13) for more details.
### Segment 20 Errors and Explanations -Error Number | Error Message | Explaination of Error -------------------|-------------------|-------------------------- -{% assign error = site.data.error["10075"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["20"]}} -{% assign error = site.data.error["14058"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["20"]}} -{% assign error = site.data.error["20000"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["20"]}} +| Error Number | Error Message | Explaination of Error | +| ---------------------------------------------- | ----------------------- | ------------------------ | +| {% assign error = site.data.error["10075"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["20"]}} | +| {% assign error = site.data.error["14058"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["20"]}} | +| {% assign error = site.data.error["20000"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["20"]}} | - -___ +---
@@ -282,10 +289,11 @@ ___ ## Property (30) -___ +--- ### Description -Segment 30, Property Segment, is used to identify that Properties are involved in the listed Offenses. It only contains general information about these Properties, such as the number of Stolen or Recovered Vehicles. Further Details are expected to be entered in Segments 31, 32, and 33. + +Segment 30, Property Segment, is used to identify that Properties are involved in the listed Offenses. It only contains general information about these Properties, such as the number of Stolen or Recovered Vehicles. Further Details are expected to be entered in Segments 31, 32, and 33. We get a lot of questions about this Segment, and have included more information about it in the FAQ, which can be found [here](./faq#properties-segments-30-31-32-and-33). @@ -293,106 +301,110 @@ We get a lot of questions about this Segment, and have included more information ### Segment Layout - Data Element Number | Description of Data Element | Position(s) | Length | Format - :----------------------------------------------:|--------------------------------------|:-------------:|:--------:|:---------: - [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor - **30** | 1-2 | 2 | N - [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A - [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A - [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A - [18](./librs-spec#number-of-stolen-vehicles-18) | Number of Stolen Motor Vehicles | 25-26 | 2 | A/N - [19](./librs-spec#number-of-recovered-motor-vehicles-19) | Number of Recovered Motor Vehicles | 27-28 | 2 | A/N - \*\* | Future Expansion Buffer | 29-48 | 20 | G (Space) - [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 49-50 | 2 | A - [C9](./librs-spec#padding-c9) | Padding | 51-150 | \*\* | G (Space) +| Data Element Number | Description of Data Element | Position(s) | Length | Format | +| :---------------------------------------------------: | ---------------------------------- | :---------: | :----: | :-------: | +| [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor -**30** | 1-2 | 2 | N | +| [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A | +| [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A | +| [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A | +| [18](./librs-spec#number-of-stolen-vehicles-18) | Number of Stolen Motor Vehicles | 25-26 | 2 | A/N | +| [19](./librs-spec#number-of-recovered-motor-vehicles-19) | Number of Recovered Motor Vehicles | 27-28 | 2 | A/N | +| \*\* | Future Expansion Buffer | 29-48 | 20 | G (Space) | +| [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 49-50 | 2 | A | +| [C9](./librs-spec#padding-c9) | Padding | 51-150 | \*\* | G (Space) |
### Segment 30 Errors and Explanations -Error Number | Error Message | Explaination of Error -------------------|-------------------|-------------------------- -{% assign error = site.data.error["10074"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["30"]}} -{% assign error = site.data.error["10076"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["30"]}} +| Error Number | Error Message | Explaination of Error | +| ---------------------------------------------- | ----------------------- | ------------------------ | +| {% assign error = site.data.error["10074"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["30"]}} | +| {% assign error = site.data.error["10076"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["30"]}} | -___ +---
## Property Description (31) -___ + +--- ### Description -Segment 31, Property Description, includes specific details about the Properties that are involved in the Incident. One Segment 31 should be included for each Property that is involved in the Incident. + +Segment 31, Property Description, includes specific details about the Properties that are involved in the Incident. One Segment 31 should be included for each Property that is involved in the Incident. We get a lot of questions about this Segment, and have included more information about it in the FAQ, which can be found [here](./faq#properties-segments-30-31-32-and-33). ### Segment Layout - Data Element Number | Description of Data Element | Position(s) | Length | Format - :------------------------------------:|--------------------------------|:-------------:|:--------:|:---------: - [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor - **31** | 1-2 | 2 | N - [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A - [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A - [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A - [14](./librs-spec#type-of-property-loss-14) | Type of Property Loss / Etc. | 25 | 1 | N - [15](./librs-spec#property-description-15) | Property Description Type | 26-27 | 2 | A/N - [16](./librs-spec#value-of-property-16) | Value of Property | 28-36 | 9 | N - [17](./librs-spec#date-recovered-17) | Date Recovered | 37-44 | 8 | D - [20](./librs-spec#suspected-drug-type-20) | Suspected Drug Type | 45-46 | 2 | A - [21](./librs-spec#estimated-drug-quantity-21) | Estimated Drug Quantity | 47-59 | 13 | A/N - [22](./librs-spec#type-drug-measurement-22) | Type Drug Measurement | 60-61 | 2 | A - [P1](./librs-spec#property-sequence-number-p1) | Property Sequence Number | 62-64 | 3 | N - \*\* | Future Expansion Buffer | 65-81 | 17 | G (Space) - [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 82-83 | 2 | A - [C9](./librs-spec#padding-c9) | Padding | 84-150 | \*\* | G (Space) +| Data Element Number | Description of Data Element | Position(s) | Length | Format | +| :-----------------------------------------: | -------------------------------- | :---------: | :----: | :-------: | +| [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor -**31** | 1-2 | 2 | N | +| [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A | +| [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A | +| [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A | +| [14](./librs-spec#type-of-property-loss-14) | Type of Property Loss / Etc. | 25 | 1 | N | +| [15](./librs-spec#property-description-15) | Property Description Type | 26-27 | 2 | A/N | +| [16](./librs-spec#value-of-property-16) | Value of Property | 28-36 | 9 | N | +| [17](./librs-spec#date-recovered-17) | Date Recovered | 37-44 | 8 | D | +| [20](./librs-spec#suspected-drug-type-20) | Suspected Drug Type | 45-46 | 2 | A | +| [21](./librs-spec#estimated-drug-quantity-21) | Estimated Drug Quantity | 47-59 | 13 | A/N | +| [22](./librs-spec#type-drug-measurement-22) | Type Drug Measurement | 60-61 | 2 | A | +| [P1](./librs-spec#property-sequence-number-p1) | Property Sequence Number | 62-64 | 3 | N | +| \*\* | Future Expansion Buffer | 65-81 | 17 | G (Space) | +| [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 82-83 | 2 | A | +| [C9](./librs-spec#padding-c9) | Padding | 84-150 | \*\* | G (Space) |
### Segment 31 Errors and Explanations -Error Number | Error Message | Explaination of Error -------------------|-------------------|-------------------------- -{% assign error = site.data.error["10074"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["31"]}} -{% assign error = site.data.error["10076"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["31"]}} +| Error Number | Error Message | Explaination of Error | +| ---------------------------------------------- | ----------------------- | ------------------------ | +| {% assign error = site.data.error["10074"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["31"]}} | +| {% assign error = site.data.error["10076"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["31"]}} | -___ +---
## Property Modification (32) -___ + +--- ### Description -Segment 32, Property Modification, is only used when performing a Time Window Submission (Action Type 'W') or a Modification (Action Type 'M') to a Time-Window Submission. +Segment 32, Property Modification, is only used when performing a Time Window Submission (Action Type 'W') or a Modification (Action Type 'M') to a Time-Window Submission. ### Segment Layout - Data Element Number | Description of Data Element | Position(s) | Length | Format - :-----------------------------------:|------------------------------------|:-------------:|:--------:|:---------: - [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor - **32** | 1-2 | 2 | N - [C5](./librs-spec#action-type-c5) | Action Type ("W" or "M", only) | 3 | 1 | A - [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A - [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A - [6](./librs-spec#louisiana-revised-statute-6) | Louisiana Revised Statute Number | 25-36 | 12 | - \*\* | Future Expansion Buffer | 37-56 | 20 | G (Space) - [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 57-58 | 2 | A - [C9](./librs-spec#padding-c9) | Padding | 59-150 | \*\* | G (Space) +| Data Element Number | Description of Data Element | Position(s) | Length | Format | +| :----------------------------------------: | -------------------------------- | :---------: | :----: | :-------: | +| [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor -**32** | 1-2 | 2 | N | +| [C5](./librs-spec#action-type-c5) | Action Type ("W" or "M", only) | 3 | 1 | A | +| [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A | +| [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A | +| [6](./librs-spec#louisiana-revised-statute-6) | Louisiana Revised Statute Number | 25-36 | 12 | | +| \*\* | Future Expansion Buffer | 37-56 | 20 | G (Space) | +| [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 57-58 | 2 | A | +| [C9](./librs-spec#padding-c9) | Padding | 59-150 | \*\* | G (Space) |
### Segment 32 Errors and Explanations + None -___ +---
@@ -400,11 +412,11 @@ ___ ## Property/Offense (33) -___ +--- ### Description -Segment 33, Property/Offense Relationship, is used to distinctly relate a Property to an Offense. This Segment is not mandatory, though you will most likely experience Errors if you do not include it. +Segment 33, Property/Offense Relationship, is used to distinctly relate a Property to an Offense. This Segment is not mandatory, though you will most likely experience Errors if you do not include it. When this segment is not included, LIBRS will perform a Cross Product between all Properties and all Offenses. We have measures in place to help limit incorrect Properties from being associted with Invalid Offenses (EG: Drugs being associated with Motor Vehicle Theft Offenses), however the best way to ensure that Properties are being appropriately linked up to their Offenses is by including a Segment 33 for each Property/Offense Relationship. @@ -412,77 +424,81 @@ We get a lot of questions about this Segment, and have included more information ### Segment Layout - Data Element Number | Description of Data Element | Position(s) | Length | Format - :----------------------------------------------------------:|-------------------------------------------------------|:-----------------:|:------------:|:---------: - [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor - **33** | 1-2 | 2 | N - [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A - [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A - [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A - [P1R](./librs-spec#property-sequence-number-reference-p1r) | Property Sequence Number Reference | 25-27 | 3 | A - [L6R](./librs-spec#offense-sequence-number-reference-l6r) | Offense Sequence Number Reference | 28-30 | 3 | A - \*\* | Future Expansion Buffer | 31-50 | 20 | G (Space) - [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 51-52 | 2 | A - [C9](./librs-spec#padding-c9) | Padding | 53-150 | \*\* | G (Space) +| Data Element Number | Description of Data Element | Position(s) | Length | Format | +| :-----------------------------------------------------: | ---------------------------------- | :---------: | :----: | :-------: | +| [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor -**33** | 1-2 | 2 | N | +| [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A | +| [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A | +| [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A | +| [P1R](./librs-spec#property-sequence-number-reference-p1r) | Property Sequence Number Reference | 25-27 | 3 | A | +| [L6R](./librs-spec#offense-sequence-number-reference-l6r) | Offense Sequence Number Reference | 28-30 | 3 | A | +| \*\* | Future Expansion Buffer | 31-50 | 20 | G (Space) | +| [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 51-52 | 2 | A | +| [C9](./librs-spec#padding-c9) | Padding | 53-150 | \*\* | G (Space) |
#### Important Notes: + * The Property/Offense Segment is used to connect incident property (stolen, retrieved, etc.) to an offense. This connection, or relationship, is established using the Property Sequence Number (Data Element P1) and the Offense Sequence Number (Data Element L6). * This Segment *is optional* in the sense that if it is missing LIBRS will interpret properties to offenses automatically using a cross product (EG all offenses are associated with all properties). Depending on the Offenses in the Incident, this can cause LIBRS to infer properties to incompatible Offenses. * LIBRS uses the NIBRS Code of the Offenses to determine if it should apply properties to them to minimize the cases that this happens in. However, there are some NIBRS Codes that include both 'Crimes Against People' and 'Crimes Against Property' Offenses. - * EG: 13B Contains both LRS 14:35 (Simple Battery - Crime Against Person) as well as LRS 14:60 (Aggravated Burglary - Crime Against Property) that break this assumption. Therefore it is always best to include this Segment when Properties are involved. + * EG: 13B Contains both LRS 14:35 (Simple Battery - Crime Against Person) as well as LRS 14:60 (Aggravated Burglary - Crime Against Property) that break this assumption. Therefore it is always best to include this Segment when Properties are involved. #### Successful Segment 33 Inference Example + An incident is submitted with a NIBRS 23H 'Crime Against Property' Offense, as well as a NIBRS 11A 'Crime Against Person' Offense, along with one or more properties that are intended to be linked to the 23H Offense. Since NIBRS 11A has no related Offenses that are a 'Crime Against Property', if Segment 33 is missing LIBRS knows that it should not apply the properties to the 11A Offense. As a result, LIBRS will only infer the properties to be related to the 23H Offense, successfully validating the Incident submission. #### Unsuccessful Segment 33 Inference Example -An incident is submitted with a NIBRS 23H 'Crime Against Property' Offense, as well as a NIBRS 13B 'Crime Against Person' Offense, along with one or more properties that are intended to be linked to the 23H Offense. Since 13B has some offenses that are 'Crime Against Property', if Segment 33 is missing LIBRS cannot know that it shouldn't apply the properties to the 13B Offense. As a result, LIBRS will interpret all properties to be related to all offenses, which in this case will throw validation errors. + +An incident is submitted with a NIBRS 23H 'Crime Against Property' Offense, as well as a NIBRS 13B 'Crime Against Person' Offense, along with one or more properties that are intended to be linked to the 23H Offense. Since 13B has some offenses that are 'Crime Against Property', if Segment 33 is missing LIBRS cannot know that it shouldn't apply the properties to the 13B Offense. As a result, LIBRS will interpret all properties to be related to all offenses, which in this case will throw validation errors.
### Segment 33 Errors and Explanations -Error Number | Error Message | Explaination of Error -------------------|-------------------|-------------------------- -{% assign error = site.data.error["90018"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["33"]}} -{% assign error = site.data.error["90023"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["33"]}} +| Error Number | Error Message | Explaination of Error | +| ---------------------------------------------- | ----------------------- | ------------------------ | +| {% assign error = site.data.error["90018"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["33"]}} | +| {% assign error = site.data.error["90023"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["33"]}} | -___ +---
### Ivalid Combinations of NIBRS Offense Codes and Property Descriptions -There are a number of illogical combinations for various NIBRS Offense Codes (Data Element 6) having certain Property Descriptions (Data Element 15). For example, it is illogical for Purse Snatching (NIBRS Code 23B) to be connected to property having a Property Description data value of Aircraft (01) or Livestock (18). - -The table below shows invalid combinations of NIBRS Offense Codes and Property Descriptions. X's on this table represent that the combination of the Property Description and NIBRS Code are incompatible and should **NOT** be used together. - - Invalid Property Descriptions | 220 | 23A | 23B | 23C | 23D | 23E | 23F | 23G | 23H | 240 - :-----------------------------------:|:-----------------:|:---------:|:---------:|:---------:|:---------:|:---------:|:---------:|:---------:|:---------:|:---------: - 01 |   | **X** | **X** | **X** | | | | | | - 03 |   | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | - 04 |   | **X** | **X** | | | | | | | - 05 |   | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | - 12 |   | **X** | **X** | **X** | | | | | | - 15 |   | **X** | **X** | **X** | | | | | | - 18 |   | **X** | **X** | **X** | | | | | | - 24 |   | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | - 28 |   | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | - 29 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | | **X** - 30 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | | **X** - 31 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | | **X** - 32 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | | **X** - 33 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | | **X** - 34 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | | **X** - 35 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | | **X** - 37 |   | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | - 39 |   | **X** | **X** | **X** | | | | | | - 78 |   | **X** | **X** | | | | | | | -___ +There are a number of illogical combinations for various NIBRS Offense Codes (Data Element 6) having certain Property Descriptions (Data Element 15). For example, it is illogical for Purse Snatching (NIBRS Code 23B) to be connected to property having a Property Description data value of Aircraft (01) or Livestock (18). + +The table below shows invalid combinations of NIBRS Offense Codes and Property Descriptions. X's on this table represent that the combination of the Property Description and NIBRS Code are incompatible and should **NOT** be used together. + +| Invalid Property Descriptions | 220 | 23A | 23B | 23C | 23D | 23E | 23F | 23G | 23H | 240 | +| :---------------------------: | :---------: | :---------: | :---------: | :---------: | :---------: | :---------: | :---------: | :---------: | :---------: | :---------: | +| 01 | | **X** | **X** | **X** | | | | | | | +| 03 | | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | | +| 04 | | **X** | **X** | | | | | | | | +| 05 | | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | | +| 12 | | **X** | **X** | **X** | | | | | | | +| 15 | | **X** | **X** | **X** | | | | | | | +| 18 | | **X** | **X** | **X** | | | | | | | +| 24 | | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | | +| 28 | | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | | +| 29 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | | **X** | +| 30 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | | **X** | +| 31 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | | **X** | +| 32 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | | **X** | +| 33 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | | **X** | +| 34 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | | **X** | +| 35 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | | **X** | +| 37 | | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | | +| 39 | | **X** | **X** | **X** | | | | | | | +| 78 | | **X** | **X** | | | | | | | | + +---
@@ -490,10 +506,11 @@ ___ ## Offender (40) -___ +--- ### Description -Segment 40, Offender Segment, is used to submit information about the suspected Offender(s) that are involved in an Incident. You should have as many Offender Segments as you have Suspects. + +Segment 40, Offender Segment, is used to submit information about the suspected Offender(s) that are involved in an Incident. You should have as many Offender Segments as you have Suspects. Offenders are linked to their Offenses by their Victims. Segment 20 - Offense Segment contains a Victim Sequence Number that denotes who the victim of the Offense was. Segment 52 - Victim/Offender Relationship then links the Offender to the Victim, which, in turn, links the Offender to the Offense. @@ -501,35 +518,35 @@ More information and common questions and errors can be found on the LIBRS FAQ f ### Segment Layout - Data Element Number | Description of Data Element | Position(s) | Length | Format - :------------------------------------------:|------------------------------------------|:-------------:|:--------:|:---------: - [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor - **40** | 1-2 | 2 | N - [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A - [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A - [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A - [36](./librs-spec#offender-sequence-number-36) | Offender Sequence Number | 25-27 | 3 | N - [37](./librs-spec#age-of-offender-37) | Age of Offender | 28-30 | 3 | A - [L37](./librs-spec#date-of-birth-of-offender-l37) | Date of Birth of Offender (LIBRS Only) | 31-38 | 8 | D - [38](./librs-spec#sex-of-offender-38) | Sex of Offender | 39 | 1 | A - [39](./librs-spec#race-of-offender-39) | Race of Offender | 40 | 1 | A - [8A](./librs-spec#bias-motivationbias-crime-type-8a) | Bias Motivation / Bias Crime Type | 41-42 | 2 | A - [39A](./librs-spec#ethnicity-of-offender-39a) | Ethnicity of Offender | 43 | 1 | A - \*\* | Future Expansion Buffer | 44-62 | 20 | G (Space) - [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 63-64 | 2 | A - [C9](./librs-spec#padding-c9) | Padding | 65-150 | \*\* | G (Space) +| Data Element Number | Description of Data Element | Position(s) | Length | Format | +| :-----------------------------------------------: | -------------------------------------- | :---------: | :----: | :-------: | +| [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor -**40** | 1-2 | 2 | N | +| [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A | +| [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A | +| [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A | +| [36](./librs-spec#offender-sequence-number-36) | Offender Sequence Number | 25-27 | 3 | N | +| [37](./librs-spec#age-of-offender-37) | Age of Offender | 28-30 | 3 | A | +| [L37](./librs-spec#date-of-birth-of-offender-l37) | Date of Birth of Offender (LIBRS Only) | 31-38 | 8 | D | +| [38](./librs-spec#sex-of-offender-38) | Sex of Offender | 39 | 1 | A | +| [39](./librs-spec#race-of-offender-39) | Race of Offender | 40 | 1 | A | +| [8A](./librs-spec#bias-motivationbias-crime-type-8a) | Bias Motivation / Bias Crime Type | 41-42 | 2 | A | +| [39A](./librs-spec#ethnicity-of-offender-39a) | Ethnicity of Offender | 43 | 1 | A | +| \*\* | Future Expansion Buffer | 44-62 | 20 | G (Space) | +| [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 63-64 | 2 | A | +| [C9](./librs-spec#padding-c9) | Padding | 65-150 | \*\* | G (Space) |
### Segment 40 Errors and Explanations -Error Number | Error Message | Explaination of Error -------------------|-------------------|-------------------------- -{% assign error = site.data.error["10075"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["40"]}} -{% assign error = site.data.error["16056"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["40"]}} +| Error Number | Error Message | Explaination of Error | +| ---------------------------------------------- | ----------------------- | ------------------------ | +| {% assign error = site.data.error["10075"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["40"]}} | +| {% assign error = site.data.error["16056"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["40"]}} | -___ +---
@@ -537,37 +554,38 @@ ___ ### Offender Using/Gaming Motivation (41) -___ +--- ### Description -Segment 41, Offender Using/Gaming, is used to denote additional aspects about the potential motive behind an Offender's behavior. + +Segment 41, Offender Using/Gaming, is used to denote additional aspects about the potential motive behind an Offender's behavior. More information and common questions and errors can be found on the LIBRS FAQ for this Segment [here](./faq#offenders-segments-40-and-41). ### Segment Layout - Data Element Number | Description of Data Element | Position(s) | Length | Format - :------------------------------------------------------:|-------------------------------------------------------|:-------------:|:--------:|:---------: - [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor -- **41** | 1-2 | 2 | N - [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A - [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A - [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A - [36](./librs-spec#offender-sequence-number-36) | Offender Sequence Number | 25-27 | 3 | N - [8](./librs-spec#offender-suspected-of-usinggaming-motivation-8) | Offender Suspected of Using / Gaming Motivation | 28 | 4 (4x 1 Char) | A - \*\* | Future Expansion Buffer | 32-48 | 20 | G (Space) - [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 49-50 | 2 | A - [C9](./librs-spec#padding-c9) | Padding | 51-150 | \*\* | G (Space) +| Data Element Number | Description of Data Element | Position(s) | Length | Format | +| :-----------------------------------------------------------: | ----------------------------------------------- | :---------: | :-----------: | :-------: | +| [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor --**41** | 1-2 | 2 | N | +| [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A | +| [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A | +| [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A | +| [36](./librs-spec#offender-sequence-number-36) | Offender Sequence Number | 25-27 | 3 | N | +| [8](./librs-spec#offender-suspected-of-usinggaming-motivation-8) | Offender Suspected of Using / Gaming Motivation | 28 | 4 (4x 1 Char) | A | +| \*\* | Future Expansion Buffer | 32-48 | 20 | G (Space) | +| [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 49-50 | 2 | A | +| [C9](./librs-spec#padding-c9) | Padding | 51-150 | \*\* | G (Space) |
### Segment 41 Errors and Explanations -Error Number | Error Message | Explaination of Error -------------------|-------------------|----------------------- -{% assign error = site.data.error["10075"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["41"]}} +| Error Number | Error Message | Explaination of Error | +| ---------------------------------------------- | ----------------------- | ------------------------ | +| {% assign error = site.data.error["10075"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["41"]}} | -___ +---
@@ -575,56 +593,58 @@ ___ ## Victim (50) -___ +--- ### Description -Segment 50, Victim Segment, is used to report the relevent personal attributes of the Victims of the Offenses in the Incident. You should have as many Segment 50's as you have unique Victims. This means you should not repeat Society as a Victim for each Offense that is a Crime Against Society, and instead only have a single Segment 50 to represent it. + +Segment 50, Victim Segment, is used to report the relevent personal attributes of the Victims of the Offenses in the Incident. You should have as many Segment 50's as you have unique Victims. This means you should not repeat Society as a Victim for each Offense that is a Crime Against Society, and instead only have a single Segment 50 to represent it. More information and common questions and errors can be found on the LIBRS FAQ for this Segment [here](./faq#victims-segments-50-51-and-52). ### Segment Layout - Data Element Number | Description of Data Element | Position(s) | Length | Format - :------------------------------------------------------------------:|-----------------------------------------------------------|:-----------:|:-------:|:--------: - [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor -- **50** | 1-2 | 2 | N - [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A - [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A - [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A - [23](./librs-spec#victim-sequence-number-23) | Victim Sequence Number | 25-27 | 3 | N - [25](./librs-spec#type-of-victim-25) | Victim Type | 28 | 1 | A - [26](./librs-spec#age-of-victim-26) | Age (At Time of Incident) | 29-31 | 3 | A - [L26](./librs-spec#date-of-birth-of-victim-l26) | Date of Birth (LIBRS Only) | 32-39 | 8 | D - [27](./librs-spec#sex-of-victim-27) | Sex | 40 | 1 | A - [28](./librs-spec#race-of-victim-28) | Race | 41 | 1 | A - [29](./librs-spec#ethnicity-of-victim-29) | Ethnicity | 42 | 1 | A - [30](./librs-spec#resident-status-of-victim-30) | Resident Status | 43 | 1 | A - [31](./librs-spec#nos.-1-and-2-31) | Aggravated Assault / Homicide Circumstance Nos. 1 and 2 | 44-47 | 2 (2x) | N - \*\* | Deprecated Data Element | 48-49 | 2 | G (Space) - [32](./librs-spec#additional-justifiable-homicide-circumstance-32) | Additional Justifiable Homicide Circumstance | 50 | 1 | A - [25A](./librs-spec#type-of-officer-activitycircumstance-25a) | Type of Officer Activity/Circumstance | 51-52 | 2 | N - [25B](./librs-spec#officer-assignment-type-25b) | Officer Assignment Type | 53 | 1 | A - [25C](./librs-spec#officer-ori-other-jurisdiction-25c) | Officer ORI, Other Jurisdiction | 54-62 | 9 | A - \*\* | Future Expansion Buffer | 63-68 | 6 | G (Space) - [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 69-70 | 2 | A - [C9](./librs-spec#padding-c9) | Padding | 71-150 | \*\* | G (Space) +| Data Element Number | Description of Data Element | Position(s) | Length | Format | +| :-------------------------------------------------------------: | ------------------------------------------------------- | :---------: | :----: | :-------: | +| [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor --**50** | 1-2 | 2 | N | +| [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A | +| [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A | +| [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A | +| [23](./librs-spec#victim-sequence-number-23) | Victim Sequence Number | 25-27 | 3 | N | +| [25](./librs-spec#type-of-victim-25) | Victim Type | 28 | 1 | A | +| [26](./librs-spec#age-of-victim-26) | Age (At Time of Incident) | 29-31 | 3 | A | +| [L26](./librs-spec#date-of-birth-of-victim-l26) | Date of Birth (LIBRS Only) | 32-39 | 8 | D | +| [27](./librs-spec#sex-of-victim-27) | Sex | 40 | 1 | A | +| [28](./librs-spec#race-of-victim-28) | Race | 41 | 1 | A | +| [29](./librs-spec#ethnicity-of-victim-29) | Ethnicity | 42 | 1 | A | +| [30](./librs-spec#resident-status-of-victim-30) | Resident Status | 43 | 1 | A | +| [31](./librs-spec#nos.-1-and-2-31) | Aggravated Assault / Homicide Circumstance Nos. 1 and 2 | 44-47 | 2 (2x) | N | +| \*\* | Deprecated Data Element | 48-49 | 2 | G (Space) | +| [32](./librs-spec#additional-justifiable-homicide-circumstance-32) | Additional Justifiable Homicide Circumstance | 50 | 1 | A | +| [25A](./librs-spec#type-of-officer-activitycircumstance-25a) | Type of Officer Activity/Circumstance | 51-52 | 2 | N | +| [25B](./librs-spec#officer-assignment-type-25b) | Officer Assignment Type | 53 | 1 | A | +| [25C](./librs-spec#officer-ori-other-jurisdiction-25c) | Officer ORI, Other Jurisdiction | 54-62 | 9 | A | +| \*\* | Future Expansion Buffer | 63-68 | 6 | G (Space) | +| [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 69-70 | 2 | A | +| [C9](./librs-spec#padding-c9) | Padding | 71-150 | \*\* | G (Space) |
### Important Notes + * [Data Element 31 - Aggrevated Assault/Homicide Circumstance](./librs-spec#nos.-1-and-2-31) is repeated twice. In the past this was repeated three times, however this has since been eliminated, which has resulted in a blank space on Characters 48 and 49.
### Segment 50 Errors and Explanations -Error Number | Error Message | Explaination of Error -------------------|-------------------|-------------------------- -{% assign error = site.data.error["10075"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["50"]}} -{% assign error = site.data.error["90044"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["50"]}} +| Error Number | Error Message | Explaination of Error | +| ---------------------------------------------- | ----------------------- | ------------------------ | +| {% assign error = site.data.error["10075"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["50"]}} | +| {% assign error = site.data.error["90044"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["50"]}} | -___ +---
@@ -632,13 +652,14 @@ ___ ## Victim Injury (51) -____ +--- ### Description -Segment 51, Victim Injury, includes information about the sustained Injuries of a Victim of an Offense. + +Segment 51, Victim Injury, includes information about the sustained Injuries of a Victim of an Offense. The main thing to note about it is that it required to be included when a Segment 50 (Victim Segment) is present with a Victim Type of 'I - Individual' or 'L - Law Enforcement', and the Offense is of one of the following NIBRS Codes: -{::nomarkdown}{:/} +{::nomarkdown}``{:/} Otherwise, it should NOT be included. Additionally, you should not supply a Segment 51 without an Injury Type (DE 33). @@ -646,28 +667,28 @@ More information and common questions and errors can be found on the LIBRS FAQ f ### Segment Layout - Data Element Number | Description of Data Element | Position(s) | Length | Format - :----------------------------------:|-------------------------------|:-------------:|:--------:|:---------: - [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor - **51** | 1-2 | 2 | N - [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A - [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A - [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A - [23](./librs-spec#victim-sequence-number-23) | Victim Sequence Number | 25-27 | 3 | N - [33](./librs-spec#type-of-injury-33) | Injury Type | 28 | 1 | A - \*\* | Future Expansion Buffer | 29-48 | 20 | G (Space) - [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 49-50 | 2 | A - [C9](./librs-spec#padding-c9) | Padding | 51-150 | \*\* | G (Space) +| Data Element Number | Description of Data Element | Position(s) | Length | Format | +| :---------------------------------------: | -------------------------------- | :---------: | :----: | :-------: | +| [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor -**51** | 1-2 | 2 | N | +| [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A | +| [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A | +| [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A | +| [23](./librs-spec#victim-sequence-number-23) | Victim Sequence Number | 25-27 | 3 | N | +| [33](./librs-spec#type-of-injury-33) | Injury Type | 28 | 1 | A | +| \*\* | Future Expansion Buffer | 29-48 | 20 | G (Space) | +| [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 49-50 | 2 | A | +| [C9](./librs-spec#padding-c9) | Padding | 51-150 | \*\* | G (Space) |
### Segment 51 Errors and Explanations -Error Number | Error Message | Explaination of Error -------------------|-------------------|-------------------------- -{% assign error = site.data.error["15020"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["51"]}} +| Error Number | Error Message | Explaination of Error | +| ---------------------------------------------- | ----------------------- | ------------------------ | +| {% assign error = site.data.error["15020"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["51"]}} | -___ +---
@@ -675,52 +696,55 @@ ___ ## Victim/Offender Relation (52) -___ +--- ### Description -Segment 52, Victim/Offender Relationship, is what links the Victims to the Offenders, and thereby links the Offenders to the Offenses. -If a Victim of Type 'I - Individual' or 'L - Law Enforcement' is present in the Incident, and the Offense is a Crime Against Person or a Robbery, then this Segment needs to be included. Otherwise it should NOT be included. +Segment 52, Victim/Offender Relationship, is what links the Victims to the Offenders, and thereby links the Offenders to the Offenses. + +If a Victim of Type 'I - Individual' or 'L - Law Enforcement' is present in the Incident, and the Offense is a Crime Against Person or a Robbery, then this Segment needs to be included. Otherwise it should NOT be included. More information and common questions and errors can be found on the LIBRS FAQ for this Segment [here](./faq#victims-segments-50-51-and-52). ### Segment Layout - Data Element Number | Description of Data Element | Position(s) | Length | Format - :----------------------------------------------:|--------------------------------------|:-------------:|:--------:|:---------: - [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor - **52** | 1-2 | 2 | N - [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A - [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A - [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A - [23](./librs-spec#victim-sequence-number-23) | Victim Sequence Number | 25-27 | 3 | N - [34](./librs-spec#offender-number-to-be-related-34) | Offender Number to be Related | 28-30 | 3 | N - [35](./librs-spec#relationship-of-victim-to-offender-35) | Relationship of Victim to Offender | 31-32 | 2 | A - \*\* | Future Expansion Buffer | 33-52 | 20 | G (Space) - [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 53-54 | 2 | A - [C9](./librs-spec#padding-c9) | Padding | 55-150 | \*\* | G (Space) +| Data Element Number | Description of Data Element | Position(s) | Length | Format | +| :---------------------------------------------------: | ---------------------------------- | :---------: | :----: | :-------: | +| [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor -**52** | 1-2 | 2 | N | +| [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A | +| [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A | +| [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A | +| [23](./librs-spec#victim-sequence-number-23) | Victim Sequence Number | 25-27 | 3 | N | +| [34](./librs-spec#offender-number-to-be-related-34) | Offender Number to be Related | 28-30 | 3 | N | +| [35](./librs-spec#relationship-of-victim-to-offender-35) | Relationship of Victim to Offender | 31-32 | 2 | A | +| \*\* | Future Expansion Buffer | 33-52 | 20 | G (Space) | +| [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 53-54 | 2 | A | +| [C9](./librs-spec#padding-c9) | Padding | 55-150 | \*\* | G (Space) |
### Segment 52 Errors and Explanations -Error Number | Error Message | Explaination of Error -------------------|-------------------|-------------------------- -{% assign error = site.data.error["15005"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["52"]}} -{% assign error = site.data.error["22081"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["52"]}} +| Error Number | Error Message | Explaination of Error | +| ---------------------------------------------- | ----------------------- | ------------------------ | +| {% assign error = site.data.error["15005"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["52"]}} | +| {% assign error = site.data.error["22081"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["52"]}} | -___ +---
## Arrestee (60) -___ + +--- ### Description -Segment 60, Arrestee Segment, is used to define whether or not an Offender was arrested for an Offense or not. Since Offenders can be known but not apprehended, there needs to be another Segment that details the information about their Arrest when the time comes. + +Segment 60, Arrestee Segment, is used to define whether or not an Offender was arrested for an Offense or not. Since Offenders can be known but not apprehended, there needs to be another Segment that details the information about their Arrest when the time comes. Segment 60 can also be used with Action Type 'A - Arrest' in order to add Arrest Information to an already submitted Incident. Though, it's recommended to simply generate a Delete for the Incident and then resubmit it. @@ -728,35 +752,36 @@ You should include an Arrestee Segment for each Offender that has been arrested ### Segment Layout - Data Element Number | Description of Data Element | Position(s) | Length | Format - :-----------------------------------------------:|--------------------------------------------------------------------|:-------------:|:--------:|:---------: - [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor - **60** | 1-2 | 2 | N - [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A - [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A - [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A - [40](./librs-spec#arrestee-sequence-number-40) | Arrest Sequence Number | 25-27 | 3 | N - [41](./librs-spec#local-booking-number-for-arrest-41) | Arrest Number/Local Booking Number for Arrest* | 28-39 | 12 | A - [L55](./librs-spec#arrest-transaction-number-l55) | Arrest Transaction Number | 40-54 | 15 | A/N - [L40](./librs-spec#arrestee-name-l40) | Arrestee Name | 55-74 | 20 | A - [42](./librs-spec#arrest-date-42) | Arrest Date | 75-82 | 8 | D - [43](./librs-spec#type-of-arrest-43) | Arrest Type | 83 | 1 | A - [44](./librs-spec#multiple-arrestee-segment-indicator-44) | Multiple Arrestee Segment Indicator | 84 | 1 | A - [47](./librs-spec#at-time-of-arrest-47) | Age (At Time of Arrest) | 85-87 | 3 | A - [L47](./librs-spec#date-of-birth-of-arrestee-l47) | Date of Birth | 88-95 | 8 | D - [48](./librs-spec#sex-of-arrestee-48) | Sex | 96 | 1 | A - [49](./librs-spec#race-of-arrestee-49) | Race | 97 | 1 | A - [50](./librs-spec#ethnicity-of-arrestee-50) | Ethnicity | 98 | 1 | A - [51](./librs-spec#resident-status-of-arrestee-51) | Resident Status | 99 | 1 | A - [52](./librs-spec#disposition-of-arrestee-under-18-52) | Disposition of Arrestee Under 18 | 100 | 1 | A - [C6](./librs-spec#clearance-indicator-c6) | Clearance Indicator (to be used for Time Window Submission only) | 101 | 1 | A - \*\* | Future Expansion Buffer | 102-118 | 17 | G (Space) - [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 119-120 | 2 | A - [C9](./librs-spec#padding-c9) | Padding | 121-150 | \*\* | G (Space) +| Data Element Number | Description of Data Element | Position(s) | Length | Format | +| :----------------------------------------------------: | ---------------------------------------------------------------- | :---------: | :----: | :-------: | +| [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor -**60** | 1-2 | 2 | N | +| [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A | +| [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A | +| [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A | +| [40](./librs-spec#arrestee-sequence-number-40) | Arrest Sequence Number | 25-27 | 3 | N | +| [41](./librs-spec#local-booking-number-for-arrest-41) | Arrest Number/Local Booking Number for Arrest* | 28-39 | 12 | A | +| [L55](./librs-spec#arrest-transaction-number-l55) | Arrest Transaction Number | 40-54 | 15 | A/N | +| [L40](./librs-spec#arrestee-name-l40) | Arrestee Name | 55-74 | 20 | A | +| [42](./librs-spec#arrest-date-42) | Arrest Date | 75-82 | 8 | D | +| [43](./librs-spec#type-of-arrest-43) | Arrest Type | 83 | 1 | A | +| [44](./librs-spec#multiple-arrestee-segment-indicator-44) | Multiple Arrestee Segment Indicator | 84 | 1 | A | +| [47](./librs-spec#at-time-of-arrest-47) | Age (At Time of Arrest) | 85-87 | 3 | A | +| [L47](./librs-spec#date-of-birth-of-arrestee-l47) | Date of Birth | 88-95 | 8 | D | +| [48](./librs-spec#sex-of-arrestee-48) | Sex | 96 | 1 | A | +| [49](./librs-spec#race-of-arrestee-49) | Race | 97 | 1 | A | +| [50](./librs-spec#ethnicity-of-arrestee-50) | Ethnicity | 98 | 1 | A | +| [51](./librs-spec#resident-status-of-arrestee-51) | Resident Status | 99 | 1 | A | +| [52](./librs-spec#disposition-of-arrestee-under-18-52) | Disposition of Arrestee Under 18 | 100 | 1 | A | +| [C6](./librs-spec#clearance-indicator-c6) | Clearance Indicator (to be used for Time Window Submission only) | 101 | 1 | A | +| \*\* | Future Expansion Buffer | 102-118 | 17 | G (Space) | +| [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 119-120 | 2 | A | +| [C9](./librs-spec#padding-c9) | Padding | 121-150 | \*\* | G (Space) |
### Important Notes -* [Data Element 52 - Disposition of Arrestee Under 18](./librs-spec#disposition-of-arrestee-under-18-52) must be included for any arrestee that is ***17 or younger***. + +* [Data Element 52 - Disposition of Arrestee Under 18](./librs-spec#disposition-of-arrestee-under-18-52) must be included for any arrestee that is ***17 or younger***. * Previously, Louisiana Law stated that 17 Year Olds were Adults rather than Juveniles, however this changed in 2020, which has led to a bit of confusion about this Data Element. * [Data Element 44 - Multiple Arrestee Indicator](./librs-spec#multiple-arrestee-segment-indicator-44) should be used when an Offender is Arrested and associated with more than one Incident. The arrest of the Individual will clear all Incidents that they are a part of, however it should not be counted that two arrests were made. The Multiple Arrestee Indicator allows you to specify that an individual was arrested for another Incident, which has cleared this Incident by arrest, but to not count this arrest for Crime Statistics. @@ -764,162 +789,171 @@ You should include an Arrestee Segment for each Offender that has been arrested ### Segment 60 Errors and Explanations -Error Number | Error Message | Explaination of Error -------------------|-------------------|-------------------------- -{% assign error = site.data.error["16056"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["60"]}} -{% assign error = site.data.error["16060"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["60"]}} +| Error Number | Error Message | Explaination of Error | +| ---------------------------------------------- | ----------------------- | ------------------------ | +| {% assign error = site.data.error["16056"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["60"]}} | +| {% assign error = site.data.error["16060"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["60"]}} |
## Arrestee Armed (61) -___ + +--- ### Description + Segment 61, Arrestee Armed, denoted the details about whether or not an Arrestee was armed with a weapon at the time of their arrest. This segment should appear for each Segment 60 (Arrestee) Segment that is present in the Incident Report. ### Segment Layout - Data Element Number | Description of Data Element | Position(s) | Length | Format - :------------------------------------------------------------------------:|-----------------------------------------|:-------------:|:--------:|:--------: - [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor - **61** | 1-2 | 2 | N - [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A - [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A - [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A - [40](./librs-spec#arrestee-sequence-number-40) | Arrestee Sequence Number | 25-27 | 3 | N - [46](./librs-spec#arrestee-was-armed-with-at-time-of-arrest-46) | Arrestee Armed With at Time of Arrest | 28-30 | 3 | A - \*\* | Future Expansion Buffer | 31-50 | 20 | G (Space) - [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 51-52 | 2 | A - [C9](./librs-spec#padding-c9) | Padding | 53-150 | \*\* | G (Space) +| Data Element Number | Description of Data Element | Position(s) | Length | Format | +| :----------------------------------------------------------: | ------------------------------------- | :---------: | :----: | :-------: | +| [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor -**61** | 1-2 | 2 | N | +| [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A | +| [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A | +| [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A | +| [40](./librs-spec#arrestee-sequence-number-40) | Arrestee Sequence Number | 25-27 | 3 | N | +| [46](./librs-spec#arrestee-was-armed-with-at-time-of-arrest-46) | Arrestee Armed With at Time of Arrest | 28-30 | 3 | A | +| \*\* | Future Expansion Buffer | 31-50 | 20 | G (Space) | +| [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 51-52 | 2 | A | +| [C9](./librs-spec#padding-c9) | Padding | 53-150 | \*\* | G (Space) |
### Segment 61 Errors and Explanations -Error Number | Error Message | Explaination of Error -------------------|-------------------|-------------------------- -{% assign error = site.data.error["16080"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["61"]}} -{% assign error = site.data.error["16099"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["61"]}} +| Error Number | Error Message | Explaination of Error | +| ---------------------------------------------- | ----------------------- | ------------------------ | +| {% assign error = site.data.error["16080"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["61"]}} | +| {% assign error = site.data.error["16099"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["61"]}} | -___ +---
## Arrestee Statute (62) -___ + +--- ### Description -Segmetn 62, Arrestee Statute, is what's used to say what Statute an Arrestee was Arrested for. At this time, Data Element [L45 - Arrest Connection to Offense](./librs-spec#arrest-connection-to-offense-l45) is optional, however if it is to be included there are particular requirements for it. Please review the definition of the Data Element to ensure that it's being correctly applied. + +Segmetn 62, Arrestee Statute, is what's used to say what Statute an Arrestee was Arrested for. At this time, Data Element [L45 - Arrest Connection to Offense](./librs-spec#arrest-connection-to-offense-l45) is optional, however if it is to be included there are particular requirements for it. Please review the definition of the Data Element to ensure that it's being correctly applied. ### Segment Layout - Data Element Number | Description of Data Element | Position(s) | Length | Format - :------------------------------------------:|--------------------------------------------------|:-------------:|:--------:|:---------: - [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor - **62** | 1-2 | 2 | N - [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A - [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A - [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A - [40](./librs-spec#arrestee-sequence-number-40) | Arrestee Sequence Number | 25-27 | 3 | N - [45](./librs-spec#of-arrest-45) | Louisiana Revised Statute Number of Arrest | 28-39 | 12 | A - [L45](./librs-spec#arrest-connection-to-offense-l45) | Arrest Connection to Offense | 40-54 | 15 | A - [N45](./librs-spec#for-arrest-n45) | Agency Supplied NIBRS Code | 55-57 | 3 | A - [70](./librs-spec#inchoates-70) | Inchoates Modifier | 58-59 | 2 | A - \*\* | Future Expansion Buffer | 60-74 | 15 | G (Space) - [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 75-76 | 2 | A - [C9](./librs-spec#padding-c9) | Padding | 77-150 | \*\* | G (Space) +| Data Element Number | Description of Data Element | Position(s) | Length | Format | +| :-----------------------------------------------: | ------------------------------------------ | :---------: | :----: | :-------: | +| [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor -**62** | 1-2 | 2 | N | +| [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A | +| [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A | +| [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A | +| [40](./librs-spec#arrestee-sequence-number-40) | Arrestee Sequence Number | 25-27 | 3 | N | +| [45](./librs-spec#of-arrest-45) | Louisiana Revised Statute Number of Arrest | 28-39 | 12 | A | +| [L45](./librs-spec#arrest-connection-to-offense-l45) | Arrest Connection to Offense | 40-54 | 15 | A | +| [N45](./librs-spec#for-arrest-n45) | Agency Supplied NIBRS Code | 55-57 | 3 | A | +| [70](./librs-spec#inchoates-70) | Inchoates Modifier | 58-59 | 2 | A | +| \*\* | Future Expansion Buffer | 60-74 | 15 | G (Space) | +| [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 75-76 | 2 | A | +| [C9](./librs-spec#padding-c9) | Padding | 77-150 | \*\* | G (Space) |
### Segment 62 Errors and Explanations -Error Number | Error Message | Explaination of Error -------------------|-------------------|-------------------------- -{% assign error = site.data.error["16081"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["62"]}} -{% assign error = site.data.error["16099"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["62"]}} +| Error Number | Error Message | Explaination of Error | +| ---------------------------------------------- | ----------------------- | ------------------------ | +| {% assign error = site.data.error["16081"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["62"]}} | +| {% assign error = site.data.error["16099"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["62"]}} | -___ +---
### Arrestee Modification (63) -___ + +--- ### Description -Segment 63, Arrestee Modification, is only used when making a Modification to an Arrestee's Information that was submitted as a Time-Window Submission. + +Segment 63, Arrestee Modification, is only used when making a Modification to an Arrestee's Information that was submitted as a Time-Window Submission. ### Segment Layout - Data Element Number | Description of Data Element | Position(s) | Length | Format - :-----------------------------------:|------------------------------------------------|:-------------:|:--------:|:---------: - [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor - **63** | 1-2 | 2 | N - [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A - [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A - [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A - [6](./librs-spec#louisiana-revised-statute-6) | Louisiana Revised Statute Number of Incident | 25-36 | 12 | A - \*\* | Future Expansion Buffer | 37-56 | 20 | A - [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 57-58 | 2 | A - [C9](./librs-spec#padding-c9) | Padding | 59-150 | \*\* | A/N +| Data Element Number | Description of Data Element | Position(s) | Length | Format | +| :----------------------------------------: | -------------------------------------------- | :---------: | :----: | :----: | +| [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor -**63** | 1-2 | 2 | N | +| [C5](./librs-spec#action-type-c5) | Action Type | 3 | 1 | A | +| [1](./librs-spec#ori-number-1) | ORI Number | 4-12 | 9 | A | +| [2](./librs-spec#incident-number-2) | Incident Number | 13-24 | 12 | A | +| [6](./librs-spec#louisiana-revised-statute-6) | Louisiana Revised Statute Number of Incident | 25-36 | 12 | A | +| \*\* | Future Expansion Buffer | 37-56 | 20 | A | +| [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 57-58 | 2 | A | +| [C9](./librs-spec#padding-c9) | Padding | 59-150 | \*\* | A/N |
### Segment 63 Errors and Explanations -Error Number | Error Message | Explaination of Error -------------------|-------------------|-------------------------- -{% assign error = site.data.error["11017"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["63"]}} -{% assign error = site.data.error["11097"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["63"]}} +| Error Number | Error Message | Explaination of Error | +| ---------------------------------------------- | ----------------------- | ------------------------ | +| {% assign error = site.data.error["11017"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["63"]}} | +| {% assign error = site.data.error["11097"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["63"]}} | -___ +---
## Submission Trailer (99) -___ + +--- ### Description -Segment 99, Submission Trailer, should be the last line in your Flat File, and should only appear once per file. + +Segment 99, Submission Trailer, should be the last line in your Flat File, and should only appear once per file. ### Segment Layout - Data Element Number | Description of Data Element | Position(s) | Length | Format - :------------------------------------------:|----------------------------------|:-------------:|:--------:|:---------: - [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor - **99** | 1-2 | 2 | N - [C7](./librs-spec#number-of-segments-transferred-c7) | Number of Segments Transferred | 3-8 | 6 | N - [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 9-10 | 2 | A - [C9](./librs-spec#padding-c9) | Padding | 11-150 | \*\* | A/N +| Data Element Number | Description of Data Element | Position(s) | Length | Format | +| :-----------------------------------------------: | -------------------------------- | :---------: | :----: | :----: | +| [C1](./librs-spec#segment-descriptor-c1) | Segment Descriptor -**99** | 1-2 | 2 | N | +| [C7](./librs-spec#number-of-segments-transferred-c7) | Number of Segments Transferred | 3-8 | 6 | N | +| [C8](./librs-spec#end-of-segment-marker-c8) | End of Segment Marker | 9-10 | 2 | A | +| [C9](./librs-spec#padding-c9) | Padding | 11-150 | \*\* | A/N |
### Important Notes + * [Data Element C7 - Number of Segments Transferred](./librs-spec#number-of-segments-transferred-c7) should be a six-digit long number that is front-padded with 0's that contains the number of lines in the Flat File (Including the Header and Trailer Segments). For instance, if Segment 99 appears on line number 512 in your Flat File, DE C7 should be '000512', and the full line would read '99000512ZZ' (plus Padding to make 150 characters). ### Segment 99 Errors and Explanations -Error Number | Error Message | Explaination of Error -------------------|-------------------|-------------------------- -{% assign error = site.data.error["19901"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["99"]}} -{% assign error = site.data.error["19902"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["99"]}} -{% assign error = site.data.error["19903"] -%} -{{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["99"]}} +| Error Number | Error Message | Explaination of Error | +| ---------------------------------------------- | ----------------------- | ------------------------ | +| {% assign error = site.data.error["19901"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["99"]}} | +| {% assign error = site.data.error["19902"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["99"]}} | +| {% assign error = site.data.error["19903"] -%} | | | +| {{error.err_no}} | {{ error.err_message }} | {{error.seq_desc["99"]}} | -___ +---
@@ -928,38 +962,41 @@ ___

- # LIBRS Data Element Definitions -____ + +--- This portion of the document contains information about the specific requirements that go into each of the LIBRS Data Elements. For the short list of available values for each Data Element, go [here](./data-element-values).
## ORI Number (1) -____ -**Description:** NCIC originating agency identifier number. This field should follow the format of 'LAXXXXXXX', where XXXXXXX is the 7-digit code for the Agency's ORI Number. +--- + +**Description:** NCIC originating agency identifier number. This field should follow the format of 'LAXXXXXXX', where XXXXXXX is the 7-digit code for the Agency's ORI Number. **Data Characteristics:** 9 Character Numeric/Alpha. Cannot be blank, and must start with 'LA'. ### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["1"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["10052"] -%} -2 | {{error.err_desc["1"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["10059"] -%} -3 | {{error.err_desc["1"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["90042"] -%} -4 | {{error.err_desc["1"]}} | {{error.err_no}} | {{ error.err_message }} +--- -___ +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ----------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["1"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["10052"] -%} | | | | +| 2 | {{error.err_desc["1"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["10059"] -%} | | | | +| 3 | {{error.err_desc["1"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90042"] -%} | | | | +| 4 | {{error.err_desc["1"]}} | {{error.err_no}} | {{ error.err_message }} | + +--- + +### Details: -### Details: * This is the 9-character NCIC Originating Agency Identifier (ORI) assigned to every law enforcement agency in Louisiana. For state or local agency submissions, the last two positions must be "00".
@@ -967,27 +1004,29 @@ ___
## Incident Number (2) -___ -**Description:** Agency unique, in-house assigned case number. It is used to link subsequent update submissions to the original submission. This number will be encrypted prior to any dissemination of data to ensure that the recipient cannot identify the actual case. The Incident Number should contain the current year as part of it when possible to prevent duplication/reuse of incident numbers across different years. EG 20-000001 for the first incident of 2020. +--- + +**Description:** Agency unique, in-house assigned case number. It is used to link subsequent update submissions to the original submission. This number will be encrypted prior to any dissemination of data to ensure that the recipient cannot identify the actual case. The Incident Number should contain the current year as part of it when possible to prevent duplication/reuse of incident numbers across different years. EG 20-000001 for the first incident of 2020. **Data Characteristics:** 12 Character Alpha. Cannot be Blank, and must be unique for each Agency (IE Agency A and B can both have an Incident Number 20-00001, but Agency A cannot have two Incidents with Incident Number 20-00001). + ### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["2"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["10016"] -%} -2 | {{error.err_desc["2"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["10056"] -%} -3 | {{error.err_desc["2"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["90042"] -%} -4 | {{error.err_desc["2"]}} | {{error.err_no}} | {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ----------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["2"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["10016"] -%} | | | | +| 2 | {{error.err_desc["2"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["10056"] -%} | | | | +| 3 | {{error.err_desc["2"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90042"] -%} | | | | +| 4 | {{error.err_desc["2"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Definitions: @@ -1001,119 +1040,126 @@ Acting in concert requires that the offenders actually commit or assist in the c Normally, the offenses must have occurred during an unbroken time duration and at the same or adjourning location(s). However, incidents can also be comprised of offenses which by their nature involve continuing criminal activity by the same offender(s) at different times and places, as long as the activity is deemed to constitute a single criminal transaction. Regarding these situations, the reporting agency will have to use its best judgment. -___ +---
## Incident Date/Hour (3) -___ -**Description:** Date and Time when the incident occurred or started, or at the beginning of the time period in which it occurred, or date of report if unknown. If an incident occurred before the agency's Base Date it should not be reported to LIBRS; it will be rejected if it is. For the most part, this really isn't an issue, as the Base Date for most agencies is from somewhere in 2012. However if you do run into an error regarding it, then you should remove that Incident from being reported. +--- + +**Description:** Date and Time when the incident occurred or started, or at the beginning of the time period in which it occurred, or date of report if unknown. If an incident occurred before the agency's Base Date it should not be reported to LIBRS; it will be rejected if it is. For the most part, this really isn't an issue, as the Base Date for most agencies is from somewhere in 2012. However if you do run into an error regarding it, then you should remove that Incident from being reported. **Data Characteristics:** 11 Character Alpha. If Unknown, Enter the Reporting Date (MMDDYYYY) followed by an 'R' to indicate the date is not the actual Incident Date, but rather the Reporting Date. Leave the Time blank in this case (Not 0's, but Blank Spaces) - **Format:** MMDDYYYYXHH, Where 'X' is either: * 'R' to denote that the Incident Date is not known, and the Report Date is being substituted for it -* Or ' ' (G - Blank Space) to denote that the supplied value is the actual Incident Date. +* Or ' ' (G - Blank Space) to denote that the supplied value is the actual Incident Date. ### Important Note: -* In the process to certify an agency as LIBRS-compliant, when an agency reaches the Certification and Production stages, please note the following: - * The "Base Date" for an agency is the date that agency starts sending actual, live data that both the State and FBI Retain. For most Agencies, this is the date in which they started sending UCR data. + +* In the process to certify an agency as LIBRS-compliant, when an agency reaches the Certification and Production stages, please note the following: + * The "Base Date" for an agency is the date that agency starts sending actual, live data that both the State and FBI Retain. For most Agencies, this is the date in which they started sending UCR data. * If an incident occurred before the agency's "Base Date", but was not reported to LIBRS until after your "Base Date" has been implemented; or this incident was already reported in the UCR summary reports, this incident will be REJECTED **(Error 11073)**. * If this happens, contact a member of the LIBRS staff at the Louisiana Commission on Law Enforcement. * If this incident was not reported until after your "Base Date" was implemented, your agency may have to submit an adjusted UCR summary form to capture these offenses. ### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11005"] -%} -1 | {{error.err_desc["3"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["11051"] -%} -2 | {{error.err_desc["3"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11052"] -%} -3 | {{error.err_desc["3"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11070"] -%} -4 | {{error.err_desc["3"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11072"] -%} -5 | {{error.err_desc["3"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11073"] -%} -6 | {{error.err_desc["3"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11076"] -%} -7 | {{error.err_desc["3"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11077"] -%} -6 | {{error.err_desc["3"]}} | {{error.err_no}}| {{ error.err_message }} +--- -___ +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ----------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["11005"] -%} | | | | +| 1 | {{error.err_desc["3"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11051"] -%} | | | | +| 2 | {{error.err_desc["3"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11052"] -%} | | | | +| 3 | {{error.err_desc["3"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11070"] -%} | | | | +| 4 | {{error.err_desc["3"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11072"] -%} | | | | +| 5 | {{error.err_desc["3"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11073"] -%} | | | | +| 6 | {{error.err_desc["3"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11076"] -%} | | | | +| 7 | {{error.err_desc["3"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11077"] -%} | | | | +| 6 | {{error.err_desc["3"]}} | {{error.err_no}} | {{ error.err_message }} | + +--- ### Details: * This data element is to be used to enter the month, day, year and hours when the Incident occurred or started, or the beginning of the time period in which it occurred. "Military" twenty-four (24) hour time is to be used. * If the Incident occurred on or between midnight and 0059, enter "00" for the hour; if on or between 0100 and 0159, enter "01" for the hour if on or between 2300 and 2359, enter "23" for the hour, etc. * If the Incident occurred at exactly midnight, it is considered to have occurred at the beginning of the next day. Therefore "00" should be entered for the hour, along with the next day's date. -* If the Incident Date is unknown, enter the date of the report with the indicator "R" = Report after the MMDDYYYY of the Report Date. +* If the Incident Date is unknown, enter the date of the report with the indicator "R" = Report after the MMDDYYYY of the Report Date. * If the Incident hour is unknown, leave the hour blank. * When LIBRS requires a Blank (G), it must be a Blank (G), NOT A ZERO. ### Examples: -___ -Example Number | Description -:-------------:|:----------- -1 | If a robbery occurred at 9:30 p.m. on July 2, 2014, the entry should be '07022014G21' (where 'G' is a blank). -2 | If a kidnaping started at 11:30 p.m. on November 1, 2014, and ended at 6:00 p.m., on November 16, 2014, the entry should be '11012014G23' (where 'G' is a blank). -3 | If the date and hour of the incident are unknown, but the date of the report was March 15, 2014, the entry should be '03152014RGG' (where 'G' is a blank). -4 | If a burglary occurred sometime between 11:15 A.M. on June 24, 2014, and 4:30 P.M. on June 26, 2014, the entry should be 06242014G11 (where "G" is a blank). -5 | If a rape occurred on November 15, 2013, but was not reported until January 15, 2014, this incident would reject if your agency's "Base Date" is December 1, 2013. This incident would not have been reported on your Return A (or whatever other forms would be applicable) for the month of November or for the month of December of 2013.

If your agency submits this incident to LIBRS with an incident date of 11/15/2013, it would REJECT. It would reject because the Incident Date is prior to the date your agency's data is being kept by the LIBRS and NIBRS databases.

Since this incident CANNOT be accepted into LIBRS and has not been reported to UCR summary, an adjustment would have to be made on UCR Summary forms that apply. +--- + +| Example Number | Description | +| :------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| 1 | If a robbery occurred at 9:30 p.m. on July 2, 2014, the entry should be '07022014G21' (where 'G' is a blank). | +| 2 | If a kidnaping started at 11:30 p.m. on November 1, 2014, and ended at 6:00 p.m., on November 16, 2014, the entry should be '11012014G23' (where 'G' is a blank). | +| 3 | If the date and hour of the incident are unknown, but the date of the report was March 15, 2014, the entry should be '03152014RGG' (where 'G' is a blank). | +| 4 | If a burglary occurred sometime between 11:15 A.M. on June 24, 2014, and 4:30 P.M. on June 26, 2014, the entry should be 06242014G11 (where "G" is a blank). | +| 5 | If a rape occurred on November 15, 2013, but was not reported until January 15, 2014, this incident would reject if your agency's "Base Date" is December 1, 2013. This incident would not have been reported on your Return A (or whatever other forms would be applicable) for the month of November or for the month of December of 2013.`

`If your agency submits this incident to LIBRS with an incident date of 11/15/2013, it would REJECT. It would reject because the Incident Date is prior to the date your agency's data is being kept by the LIBRS and NIBRS databases.`

`Since this incident CANNOT be accepted into LIBRS and has not been reported to UCR summary, an adjustment would have to be made on UCR Summary forms that apply. | -___ +---
## Cleared Exceptionally (4) -___ + +--- **Description:** Indicates whether the incident was cleared exceptionally. Note that Clearance of a single Offense will clear the entire Incident, as this data element is present in Segment 10 (Administrative Segment), of which there is only one for each Incident. **Data Characteristics:** 1 Character Alpha. Cannot be blank, if the Incident is not Cleared Exceptionally then you should use 'N'. ### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["4"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11004"] -%} -2 | {{error.err_desc["4"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["11053"] -%} -3 | {{error.err_desc["4"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11054"] -%} -4 | {{error.err_desc["4"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["10071"] -%} -5 | {{error.err_desc["4"]}} | {{error.err_no}}| {{ error.err_message }} +--- + +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ----------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["4"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11004"] -%} | | | | +| 2 | {{error.err_desc["4"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11053"] -%} | | | | +| 3 | {{error.err_desc["4"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11054"] -%} | | | | +| 4 | {{error.err_desc["4"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["10071"] -%} | | | | +| 5 | {{error.err_desc["4"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * The Cleared Exceptionally data element indicates if the incident has been cleared by an exceptional event such as the death of the offender, and if so, the reason for the clearance. In multiple offense incidents, the exceptional clearance of one offense clears the entire incident. An incident CANNOT BE CLEARED EXCEPTIONALLY if it was previously, or at the same time, cleared by an arrest, (that is, if an Arrestee Segment was or is being submitted). * In order to clear an offense by exceptional means, ALL of the following four conditions must be met: - * The investigation must have clearly and definitely established the identity of at least one offender. - * Sufficient probable cause must have been developed to support the arrest, charging, and prosecution of the offender. - * The exact location of the offender must be known so that an arrest could be made. - * There must be a reason outside the control of law enforcement that prevents arresting, charging, and prosecuting the offender. + * The investigation must have clearly and definitely established the identity of at least one offender. + * Sufficient probable cause must have been developed to support the arrest, charging, and prosecution of the offender. + * The exact location of the offender must be known so that an arrest could be made. + * There must be a reason outside the control of law enforcement that prevents arresting, charging, and prosecuting the offender. * DO NOT report exceptional clearance information for justifiable homicide, as no crimes have occurred, in reality. * The closing of a case or the clearing of it by an agency's policy does not permit exceptionally clearing an offense unless all four conditions are met. ### Allowed Entries -___ + +--- Enter one code per incident. @@ -1133,7 +1179,7 @@ Enter one code per incident. {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -1148,13 +1194,14 @@ Enter one code per incident. ____ ### Examples: -___ -Example Number | Description -:-------------:|:----------- -1 | A kidnapper holding a hostage killed himself when the building in which he barricaded himself was surrounded by police. The kidnaping is cleared exceptionally under, 'Death of the Offender'. +--- -___ +| Example Number | Description | +| :------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | A kidnapper holding a hostage killed himself when the building in which he barricaded himself was surrounded by police. The kidnaping is cleared exceptionally under, 'Death of the Offender'. | + +---
@@ -1169,33 +1216,35 @@ ___ **Format:** MMDDYYYY ### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11005"] -%} -1 | {{error.err_desc["5"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11055"] -%} -2 | {{error.err_desc["5"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11074"] -%} -3 | {{error.err_desc["5"]}} | {{error.err_no}}| {{ error.err_message }} +--- + +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ----------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["11005"] -%} | | | | +| 1 | {{error.err_desc["5"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11055"] -%} | | | | +| 2 | {{error.err_desc["5"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11074"] -%} | | | | +| 3 | {{error.err_desc["5"]}} | {{error.err_no}} | {{ error.err_message }} | ### Examples: -___ +--- -Example Number | Description -:-------------:|:----------- -1 | The incident was cleared on the books of the reporting agency on May 27. It was entered into the local computer on June 6, 2019, and was submitted to LIBRS sometime in July of 2019. The date '05272019' should be entered into this data element. +| Example Number | Description | +| :------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | The incident was cleared on the books of the reporting agency on May 27. It was entered into the local computer on June 6, 2019, and was submitted to LIBRS sometime in July of 2019. The date '05272019' should be entered into this data element. | -___ +---
## Offense Sequence Number (L6) -___ + +--- **Description:** The Offense Sequence Number is a Uniquely Identifying Value between 001 and 999 that is used throughout the LIBRS Data Segments to identify which particular Offense is being referenced for validation purposes. Each Offense Segment (Segment 20) in an Incident should contain a unique Sequence Number. @@ -1203,21 +1252,22 @@ ___ ### Requirements: -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["l6"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["12006"] -%} -2 | {{error.err_desc["l6"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15002"] -%} -3 | {{error.err_desc["l6"]}} | {{error.err_no}} | {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["l6"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12006"] -%} | | | | +| 2 | {{error.err_desc["l6"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15002"] -%} | | | | +| 3 | {{error.err_desc["l6"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +---
## Offense Sequence Number Reference (L6R) -___ + +--- **Description:** Offense Sequence Number Reference is used in Segment 33 to relate Properties and Offenses together. It has to match one of the Offense Sequence Numbers (DE L6) that are present in the Segment 20(s) of the Incident, and since it's used to relate Properties to Offenses, the same L6R can be used in Multiple Segment 33's to relate multiple Properties to the Offense. @@ -1225,29 +1275,30 @@ ___ ### Requirements: -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["90021"] -%} -1 | {{error.err_desc["l6r"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["90022"] -%} -2 | {{error.err_desc["l6r"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["90025"] -%} -3 | {{error.err_desc["l6r"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["90021"] -%} | | | | +| 1 | {{error.err_desc["l6r"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90022"] -%} | | | | +| 2 | {{error.err_desc["l6r"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90025"] -%} | | | | +| 3 | {{error.err_desc["l6r"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * There is no UNIQUE constraint for the Offense Sequence Number Reference (L6R). This allows for an Offense to relate to many properties if multiple Property/Offense segments are submitted within a single incident.
- ## Louisiana Revised Statute (6) -___ -**Description:** The Louisiana Revised Statute (LRS) Code is the State Statute that and Offender is being charged and/or Arrested for. The [Master LRS List](./lrs-master-list) contains the list of all available LRS Codes that LIBRS is able to have reported to it. Each of these LRS Codes have NIBRS Code(s) associated with them. This allows Officers to report the crime how they intended to the FBI. EG: LRS 14:59/A9 is used to denote that someone shot a firearm at a train. Depending on the circumstances, the Officer may want to report this crime as a Weapons Violation (520) or as a Descrution of Property/Vandalism (290). +--- + +**Description:** The Louisiana Revised Statute (LRS) Code is the State Statute that and Offender is being charged and/or Arrested for. The [Master LRS List](./lrs-master-list) contains the list of all available LRS Codes that LIBRS is able to have reported to it. Each of these LRS Codes have NIBRS Code(s) associated with them. This allows Officers to report the crime how they intended to the FBI. EG: LRS 14:59/A9 is used to denote that someone shot a firearm at a train. Depending on the circumstances, the Officer may want to report this crime as a Weapons Violation (520) or as a Descrution of Property/Vandalism (290). LRS Codes also have Subparts and Qualifiers that can be associated with them. These, similarly to the NIBRS Code, allow the Officer to more descriptively report what happened for Statutes that have a broad stroke of ways that it could be violated. More information on Subparts and Qualifiers is below. @@ -1255,194 +1306,194 @@ LRS Codes also have Subparts and Qualifiers that can be associated with them. Th **Format**: TT:SSSS.S/P-I -||Louisiana Revised Statute Format -:--------------------------------:|----------------------------------- -TT | Title -SSSS.S | Section -**PPP/I** | Subpart, **or**
Subpart with Qualifier, **or**
Qualifier, **or**
Juvenile Qualifier, **and** An Inchoate Modifier, if applicable, would be indicated
by a dash with a data value behind the LRS Code that defines the offense.** | +| | Louisiana Revised Statute Format | +| :-------------: | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| TT | Title | +| SSSS.S | Section | +| **PPP/I** | Subpart,**or**`
`Subpart with Qualifier, **or**`
`Qualifier, **or**`
`Juvenile Qualifier, **and** An Inchoate Modifier, if applicable, would be indicated`
`by a dash with a data value behind the LRS Code that defines the offense.** |
### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["6"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11004"] -%} -2 | {{error.err_desc["6"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["22086"] -%} -3 | {{error.err_desc["6"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["286753"] -%} -4 | {{error.err_desc["6"]}} | {{error.err_no}}| {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :---------------------------------------------: | ----------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["6"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11004"] -%} | | | | +| 2 | {{error.err_desc["6"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["22086"] -%} | | | | +| 3 | {{error.err_desc["6"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["286753"] -%} | | | | +| 4 | {{error.err_desc["6"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Qualifiers and Subparts + Qualifiers and Subparts are additional information that is added to the tail-end of an LRS Code to give more definition about it whenever a statute contains multiple cases that could be reported as different NIBRS Codes. For instance, LRS 14:67 is generally used for Theft, however the item that is being stolen can cause the NIBRS Code that should be used to change (EG: A 14:67 with a 240 NIBRS Code is for if a vehicle is stolen, while a 14:67 with a 23H) ### Examples: -___ -Example Number | Description -:-------------:|:----------- -1 | When 14:42 is submitted as a Louisiana Revised Statute LRS (6), LIBRS will need Qualifiers to determine if the offense should be classified as a forcible rape or as a forcible sodomy. If the offense is submitted as a **14:42/V**, this would translate to a forcible rape offense, whereas if this offense is submitted as a **14:42/A** this would translate to a forcible sodomy offense.

Without any Qualifiers, LIBRS has no way to determine which offense this LRS should be reported as, and the entire incident would be rejected. The agency will receive the following error message: 'This LRS Code must be submitted with a Qualifier to define offense applicable.' -2 | If an incident involved a robbery (14:64) and a forcible rape (**14:42.1/V**), two LRS offenses should be submitted. The 14:64 does not require any Qualifier, but the 14:42.1 does require a Qualifier. -3 | If two females were raped in an incident, two LRS offenses should be submitted for rape: One LRS should be reported for each victim -- in this case, both LRS codes should be submitted as 14:42.1/V for Victim 001 and **14:42.1/V** for Victim 002) -4 | 14:90/G -- "G" refers to a Qualifier (see Qualifier List) and would be reported to the FBI as the offense of Betting/Wagering (NIBRS 39A). -5 | If the LRS offense is Aggravated Assault (14:87.2/F) and the Offender or the Arrestee was responsible for Accessory After the Fact then the agency would submit the following: 14:87.2/F-A. This will be reported to the FBI as an Aggravated Assault, Accessory After the Fact as the offense and for LIBRS reporting this will be considered as All Other Offenses (NIBRS 90Z). +--- +| Example Number | Description | +| :------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | When 14:42 is submitted as a Louisiana Revised Statute LRS (6), LIBRS will need Qualifiers to determine if the offense should be classified as a forcible rape or as a forcible sodomy. If the offense is submitted as a**14:42/V**, this would translate to a forcible rape offense, whereas if this offense is submitted as a **14:42/A** this would translate to a forcible sodomy offense.`

`Without any Qualifiers, LIBRS has no way to determine which offense this LRS should be reported as, and the entire incident would be rejected. The agency will receive the following error message: 'This LRS Code must be submitted with a Qualifier to define offense applicable.' | +| 2 | If an incident involved a robbery (14:64) and a forcible rape (**14:42.1/V**), two LRS offenses should be submitted. The 14:64 does not require any Qualifier, but the 14:42.1 does require a Qualifier. | +| 3 | If two females were raped in an incident, two LRS offenses should be submitted for rape: One LRS should be reported for each victim -- in this case, both LRS codes should be submitted as 14:42.1/V for Victim 001 and**14:42.1/V** for Victim 002) | +| 4 | 14:90/G -- "G" refers to a Qualifier (see Qualifier List) and would be reported to the FBI as the offense of Betting/Wagering (NIBRS 39A). | +| 5 | If the LRS offense is Aggravated Assault (14:87.2/F) and the Offender or the Arrestee was responsible for Accessory After the Fact then the agency would submit the following: 14:87.2/F-A. This will be reported to the FBI as an Aggravated Assault, Accessory After the Fact as the offense and for LIBRS reporting this will be considered as All Other Offenses (NIBRS 90Z). |
**Refer to the Master LIBRS/LRS Code Table to determine:** + - LRS Codes that are accepted - What offense the LRS code was assigned: NIBRS Code determines offense to be reported. - Index Class assigned to each LRS - IBR and NIBRS rankings. -____ - +---
- #### Warning Messages will be returned for the following LRS codes: -LRS Code | Description | Warning Number | Warning Message -:-------:|:------------|:--------------:|:---------------- -{% assign error = site.data.error["22025"] -%} -14:32.1 | With no Qualifier will be reported to the FBI as Driving Under the Influence (NIBRS 90D) | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["22030"] -%} -14:44.1 | With no Qualifier will be reported to the FBI as Kidnaping (NIBRS 100) | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["22130"] -%} -14:60 | With no Qualifier will be reported to the FBI as a Robbery (NIBRS 120) | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["22035"] -%} -14:65.1 | With no Qualifier will be reported to the FBI as a Purse Snatching (NIBRS 23B) | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["22135"] -%} -14:70.4 | With no Qualifier will be reported to the FBI as a Credit Card/Automatic Teller Machine Fraud (NIBRS 26B) | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["22140"] -%} -14:70.5 | With no Qualifier will be reported to the FBI as Bribery (NIBRS 510) | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["22040"] -%} -14:93 | With no Qualifier will be reported to the FBI as a Family Offense Nonviolent (NIBRS 90F) | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["22045"] -%} -14:107.1 | With no Qualifier will be reported to the FBI as All Other Offenses (NIBRS 90Z) | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["22050"] -%} -14:129.1 | With no Qualifier will be reported to the FBI as a Simple Assault (NIBRS 13B) | {{error.err_no}}| {{ error.err_message }} +| LRS Code | Description | Warning Number | Warning Message | +| :--------------------------------------------: | :-------------------------------------------------------------------------------------------------------- | :--------------: | :---------------------- | +| {% assign error = site.data.error["22025"] -%} | | | | +| 14:32.1 | With no Qualifier will be reported to the FBI as Driving Under the Influence (NIBRS 90D) | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["22030"] -%} | | | | +| 14:44.1 | With no Qualifier will be reported to the FBI as Kidnaping (NIBRS 100) | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["22130"] -%} | | | | +| 14:60 | With no Qualifier will be reported to the FBI as a Robbery (NIBRS 120) | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["22035"] -%} | | | | +| 14:65.1 | With no Qualifier will be reported to the FBI as a Purse Snatching (NIBRS 23B) | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["22135"] -%} | | | | +| 14:70.4 | With no Qualifier will be reported to the FBI as a Credit Card/Automatic Teller Machine Fraud (NIBRS 26B) | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["22140"] -%} | | | | +| 14:70.5 | With no Qualifier will be reported to the FBI as Bribery (NIBRS 510) | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["22040"] -%} | | | | +| 14:93 | With no Qualifier will be reported to the FBI as a Family Offense Nonviolent (NIBRS 90F) | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["22045"] -%} | | | | +| 14:107.1 | With no Qualifier will be reported to the FBI as All Other Offenses (NIBRS 90Z) | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["22050"] -%} | | | | +| 14:129.1 | With no Qualifier will be reported to the FBI as a Simple Assault (NIBRS 13B) | {{error.err_no}} | {{ error.err_message }} | -___ +--- #### Hard-Coded Edits for LRS Codes Without a Property Description-Based Qualifier: -LRS Code | Description | Warning Number | Warning Message -:-------:|:------------|:--------------:|:---------------- -{% assign error = site.data.error["22055"] -%} -14:67 | When submitted with no Qualifier will be reported to the FBI as All Other Larceny-Theft (NIBRS 23H) | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["22060"] -%} -14:67 | When LRS 14:67 is submitted with no Qualifier AND Property Description (DE 15) is "38", the offense will be reported to the FBI as Theft of Motor Vehicle Parts (NIBRS 23G) | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["22065"] -%} -14:67 | When submitted with no Qualifier AND Property Description (DE 15) is other than: '03', '04', '05', '24', '28', '37' or '38', the Offense will be reported as Motor Vehicle Theft (NIBRS 240) | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["22070"] -%} -14:67 | When LRS 14:67 is submitted with no Qualifier AND Property Description (DE 15) is "04", the offense will be reported as Theft of a Bicycle | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["22071"] -%} -14:68 | LRS 14:68 will be reported to the FBI as All Other Larceny-Theft (NIBRS 23H) | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["22072"] -%} -14:68 | When LRS 14:68 is submitted AND Property Description (DE 15) is "03", "05", "24", "28" or "37", Motor Vehicle Theft (NIBRS 240) | {{error.err_no}}| {{ error.err_message }} +| LRS Code | Description | Warning Number | Warning Message | +| :--------------------------------------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :--------------: | :---------------------- | +| {% assign error = site.data.error["22055"] -%} | | | | +| 14:67 | When submitted with no Qualifier will be reported to the FBI as All Other Larceny-Theft (NIBRS 23H) | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["22060"] -%} | | | | +| 14:67 | When LRS 14:67 is submitted with no Qualifier AND Property Description (DE 15) is "38", the offense will be reported to the FBI as Theft of Motor Vehicle Parts (NIBRS 23G) | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["22065"] -%} | | | | +| 14:67 | When submitted with no Qualifier AND Property Description (DE 15) is other than: '03', '04', '05', '24', '28', '37' or '38', the Offense will be reported as Motor Vehicle Theft (NIBRS 240) | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["22070"] -%} | | | | +| 14:67 | When LRS 14:67 is submitted with no Qualifier AND Property Description (DE 15) is "04", the offense will be reported as Theft of a Bicycle | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["22071"] -%} | | | | +| 14:68 | LRS 14:68 will be reported to the FBI as All Other Larceny-Theft (NIBRS 23H) | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["22072"] -%} | | | | +| 14:68 | When LRS 14:68 is submitted AND Property Description (DE 15) is "03", "05", "24", "28" or "37", Motor Vehicle Theft (NIBRS 240) | {{error.err_no}} | {{ error.err_message }} | -____ +--- #### Allowed Entries for Juvenile Qualifiers: LIBRS accepts the following juvenile specific reportable offenses that are NOT part of the list of LRS codes. Agency should submit the following codes in this data element for juvenile specific offenses: -LRS Code | Description | NIBRS | Crime Against -:-------:|:------------|:-----:|:------------: -JU:CUR | Juvenile Curfew Violations will be reported to the FBI as Curfew/Loitering/Vagrancy violations | 90B | Society -JU:RUN | Juvenile Runaways will be reported to the FBI under Runaways offense | 90I | Society - Not a crime -JU:TRU | Juvenile Truancy will be reported to the FBI as All Other Offenses | 90Z | Society - Not a Crime -JU:UNG | Juvenile Ungovernables will be reported to the FBI under Disorderly Conduct Offense | 90C | Society +| LRS Code | Description | NIBRS | Crime Against | +| :------: | :--------------------------------------------------------------------------------------------- | :---: | :-------------------: | +| JU:CUR | Juvenile Curfew Violations will be reported to the FBI as Curfew/Loitering/Vagrancy violations | 90B | Society | +| JU:RUN | Juvenile Runaways will be reported to the FBI under Runaways offense | 90I | Society - Not a crime | +| JU:TRU | Juvenile Truancy will be reported to the FBI as All Other Offenses | 90Z | Society - Not a Crime | +| JU:UNG | Juvenile Ungovernables will be reported to the FBI under Disorderly Conduct Offense | 90C | Society | -___ +--- #### LRS Qualifiers List Qualifiers must be associated with the LRS codes as shown in the LIBRS/LRS Master Code Table. Only the combinations shown in the table below qualify as a valid entry in Data Element # 6 (LRS of Offense) and Data Element # 45 (LRS of Arrest Offense). An agency CANNOT append these Qualifiers to any LRS Code to classify offense to be reported, unless it is a valid LRS Code combination as classified on the LIBRS/LRS Master Code Table. -Qualifier | Description | NIBRS Description | NIBRS Code | Crime Against -:--------:|:------------|:------------------|:----------:|:-------------: -AA | Vehicular Homicide with Intent to Kill | Murder and Nonnegligent Manslaughter | 09A | Person -A | Anal penetration - Anal sexual intercourse with another person, forcibly and/or against that person's will; or not forcibly or against the persons will where the victim is incapable of giving consent because of his/her youth or because of his/her temporary or permanent mental or physical incapacity | Forcible Sodomy | 11B | Person -B | Theft from Building - A theft from within a building which is either open to the general public or where the offender has legal access. | Theft from Building | 23D | Property -C | Theft from Coin Operated Machine - Theft from a machine or device which is operated or activated by the use of coins. | Theft from Coin Operated Machine | 23E | Property -D | Drug/Narcotic Violations - Offender unlawfully distributes or dispenses a controlled dangerous substance to a recipient or to another who subsequently distributes or dispenses such controlled dangerous substance, which is the direct cause of the death of the person who ingested or consumed the controlled dangerous substance. | Drug/Narcotic Violations | 35A | Society -E | Embezzlement - Unlawful misappropriation by an offender to his/her own use or purpose of money, property, or some other thing of value entrusted to his/her care, custody, or control. |Embezzlement | 270 | Property -F | Actual Force Used Against a Victim or Threat of Force Displaying a Weapon - Might be used to determine if a purse snatching is to be reported as Strong Arm Robbery 14:65.1/F, or as Larceny Theft 14:65.1 | Aggravated Assault, Person, or Robbery | 13A or 120 | Person -FR | Fraud - False Pretense/Swindle/Confidence Game Intentional misrepresentation of existing fact or condition, or the use of some other deceptive scheme or device, to obtain money, goods, or other things of value. |False Pretense/Swindle/Confidence Game | 26A | Property -G | Betting and Wagering - To unlawfully stake money or something else of value on the happening of an uncertain event or on the ascertainment of a fact in dispute. |Betting/Wagering | 39A | Society -H | Inhabited Dwelling - Structure occupied as a place of settled residence or habitat lived in regularly or routinely. Arson reporting | Arson | 200 | Property -I | Immovable Structures - Fixed permanent or immovable things; include house trailer or houseboat if used as permanent dwelling.

Burglary: Unlawful entry into a building or other structure with intent to commit a felony or a theft

Trespass of Real Property: To unlawfully enter land, a dwelling, or other real property | Burglary or Trespass of Real Property | 220 or 90J | Property or Society -J | Self Inflicted Serious Bodily Injuries | All Other Offenses | 90Z | Person -JU:CUR | Juvenile Curfew Violations - will be reported to the FBI as curfew/loitering/ vagrancy violations | Curfew/Loitering/Vagrancy Violations | 90B | Society -JU:RUN | Juvenile Runaways - will be reported to the FBI under Runaways offense | Runaway | 90I | Society - Not a Crime -JU:TRU | Juvenile Truancy - Absent from school without permission. | All Other Offenses |90Z | Society - Not a Crime -JU:UNG | Juvenile Ungovernables - will be reported to the FBI as Disorderly Conduct |Disorderly Conduct | 90C | Society -K | Pocket Picking - Theft of articles from another person's physical possession by stealth where the victim usually does not become immediately aware of the theft |Pocket Picking | 23A | Property -L | Murder and Non Negligent Manslaughter - Willful nonnegligent killing of one human being by another human being live born not an embryo or fetus in utero |Murder and Non-Negligent Manslaughter | 09A | Person -M | Movable Structures - Tents, boats, airplanes, lawnmowers, hand tools, farm and construction equipment, etc... not permanent dwellings | Larceny Theft - All Other Larceny | 23H | Property -N | Rubbing/Touching - No actual penetration 'indecent liberties', 'child molesting', no elements of 11A, 11B or 11C were applicable | Forcible Fondling | 11D | Person -0 | Oral Intercourse - Oral sexual intercourse with another person, forcibly and/or against that person's will. Or, not forcibly or against the persons will where the victim is incapable of giving consent because of his/her youth or because of his/her temporary or permanent mental or physical incapacity |Forcible Sodomy | 11B | Person -P | Sexual Assault With an Object - To use an object or instrument to unlawfully penetrate, however slightly, the genital or anal opening of the body of another person, forcibly and/or against that person's will. Or, not forcibly or against the persons will where the victim is incapable of giving consent because of his/her youth or because of his/her temporary or permanent mental or physical incapacity |Sexual Assault With an Object | 11C | Person -Q | Victim Had Offender Inflict Serious Bodily Injuries to Him/Her - Victim made the offender inflict injuries to his/her person no intent on part of the offender |Aggravated Assault | 13A | Person -R | Operating/Assisting Gambling - To unlawfully operate, promote, or assist in the operation of a game of chance |Operating/Promoting/ Assisting Gambling | 39B | Property -S | Shoplifting - The theft, by someone other than an employee of the victim, of goods or merchandise exposed for sale |Shoplifting | 23C | Property -T | Threat of Force Used Against the Victim - No weapons and no physical attack used in this threat |Intimidation | 13C | Person -U | Uninhabited Dwelling - Structures uninhabited or abandoned or not normally in use. Arson reporting |Arson | 200 | Property -V | Vaginal Penetration - With force or without force where the victim is incapable of giving consent because of youth or because of temporary or permanent mental incapacity |Forcible Rape | 11A | Person -W | Fetal Death - Human embryo or fetus in utero |All Other Offenses | 90Z | Society -X | Falsified Records by Forgery or Counterfeiting - Altering, copying, or imitation of something, without authority or right, with the intent to deceive or defraud by passing the copy or thing altered or imitated as that which is original or genuine. Or, the selling, buying, or possession of an altered, copied, or imitated thing with the intent to deceive or defraud |Counterfeiting/Forgery | 250 | Property -Y | Destroyed Records or Property | Destruction/Damage/Vandalism of Property | 290 | Property -Z | Theft from a Motor Vehicle - Theft of articles from motor vehicle whether locked or unlocked |Theft from a Motor Vehicle | 23F | Property +| Qualifier | Description | NIBRS Description | NIBRS Code | Crime Against | +| :-------: | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :--------------------------------------- | :--------: | :-------------------: | +| AA | Vehicular Homicide with Intent to Kill | Murder and Nonnegligent Manslaughter | 09A | Person | +| A | Anal penetration - Anal sexual intercourse with another person, forcibly and/or against that person's will; or not forcibly or against the persons will where the victim is incapable of giving consent because of his/her youth or because of his/her temporary or permanent mental or physical incapacity | Forcible Sodomy | 11B | Person | +| B | Theft from Building - A theft from within a building which is either open to the general public or where the offender has legal access. | Theft from Building | 23D | Property | +| C | Theft from Coin Operated Machine - Theft from a machine or device which is operated or activated by the use of coins. | Theft from Coin Operated Machine | 23E | Property | +| D | Drug/Narcotic Violations - Offender unlawfully distributes or dispenses a controlled dangerous substance to a recipient or to another who subsequently distributes or dispenses such controlled dangerous substance, which is the direct cause of the death of the person who ingested or consumed the controlled dangerous substance. | Drug/Narcotic Violations | 35A | Society | +| E | Embezzlement - Unlawful misappropriation by an offender to his/her own use or purpose of money, property, or some other thing of value entrusted to his/her care, custody, or control. | Embezzlement | 270 | Property | +| F | Actual Force Used Against a Victim or Threat of Force Displaying a Weapon - Might be used to determine if a purse snatching is to be reported as Strong Arm Robbery 14:65.1/F, or as Larceny Theft 14:65.1 | Aggravated Assault, Person, or Robbery | 13A or 120 | Person | +| FR | Fraud - False Pretense/Swindle/Confidence Game Intentional misrepresentation of existing fact or condition, or the use of some other deceptive scheme or device, to obtain money, goods, or other things of value. | False Pretense/Swindle/Confidence Game | 26A | Property | +| G | Betting and Wagering - To unlawfully stake money or something else of value on the happening of an uncertain event or on the ascertainment of a fact in dispute. | Betting/Wagering | 39A | Society | +| H | Inhabited Dwelling - Structure occupied as a place of settled residence or habitat lived in regularly or routinely. Arson reporting | Arson | 200 | Property | +| I | Immovable Structures - Fixed permanent or immovable things; include house trailer or houseboat if used as permanent dwelling.`

`Burglary: Unlawful entry into a building or other structure with intent to commit a felony or a theft `

` Trespass of Real Property: To unlawfully enter land, a dwelling, or other real property | Burglary or Trespass of Real Property | 220 or 90J | Property or Society | +| J | Self Inflicted Serious Bodily Injuries | All Other Offenses | 90Z | Person | +| JU:CUR | Juvenile Curfew Violations - will be reported to the FBI as curfew/loitering/ vagrancy violations | Curfew/Loitering/Vagrancy Violations | 90B | Society | +| JU:RUN | Juvenile Runaways - will be reported to the FBI under Runaways offense | Runaway | 90I | Society - Not a Crime | +| JU:TRU | Juvenile Truancy - Absent from school without permission. | All Other Offenses | 90Z | Society - Not a Crime | +| JU:UNG | Juvenile Ungovernables - will be reported to the FBI as Disorderly Conduct | Disorderly Conduct | 90C | Society | +| K | Pocket Picking - Theft of articles from another person's physical possession by stealth where the victim usually does not become immediately aware of the theft | Pocket Picking | 23A | Property | +| L | Murder and Non Negligent Manslaughter - Willful nonnegligent killing of one human being by another human being live born not an embryo or fetus in utero | Murder and Non-Negligent Manslaughter | 09A | Person | +| M | Movable Structures - Tents, boats, airplanes, lawnmowers, hand tools, farm and construction equipment, etc... not permanent dwellings | Larceny Theft - All Other Larceny | 23H | Property | +| N | Rubbing/Touching - No actual penetration 'indecent liberties', 'child molesting', no elements of 11A, 11B or 11C were applicable | Forcible Fondling | 11D | Person | +| 0 | Oral Intercourse - Oral sexual intercourse with another person, forcibly and/or against that person's will. Or, not forcibly or against the persons will where the victim is incapable of giving consent because of his/her youth or because of his/her temporary or permanent mental or physical incapacity | Forcible Sodomy | 11B | Person | +| P | Sexual Assault With an Object - To use an object or instrument to unlawfully penetrate, however slightly, the genital or anal opening of the body of another person, forcibly and/or against that person's will. Or, not forcibly or against the persons will where the victim is incapable of giving consent because of his/her youth or because of his/her temporary or permanent mental or physical incapacity | Sexual Assault With an Object | 11C | Person | +| Q | Victim Had Offender Inflict Serious Bodily Injuries to Him/Her - Victim made the offender inflict injuries to his/her person no intent on part of the offender | Aggravated Assault | 13A | Person | +| R | Operating/Assisting Gambling - To unlawfully operate, promote, or assist in the operation of a game of chance | Operating/Promoting/ Assisting Gambling | 39B | Property | +| S | Shoplifting - The theft, by someone other than an employee of the victim, of goods or merchandise exposed for sale | Shoplifting | 23C | Property | +| T | Threat of Force Used Against the Victim - No weapons and no physical attack used in this threat | Intimidation | 13C | Person | +| U | Uninhabited Dwelling - Structures uninhabited or abandoned or not normally in use. Arson reporting | Arson | 200 | Property | +| V | Vaginal Penetration - With force or without force where the victim is incapable of giving consent because of youth or because of temporary or permanent mental incapacity | Forcible Rape | 11A | Person | +| W | Fetal Death - Human embryo or fetus in utero | All Other Offenses | 90Z | Society | +| X | Falsified Records by Forgery or Counterfeiting - Altering, copying, or imitation of something, without authority or right, with the intent to deceive or defraud by passing the copy or thing altered or imitated as that which is original or genuine. Or, the selling, buying, or possession of an altered, copied, or imitated thing with the intent to deceive or defraud | Counterfeiting/Forgery | 250 | Property | +| Y | Destroyed Records or Property | Destruction/Damage/Vandalism of Property | 290 | Property | +| Z | Theft from a Motor Vehicle - Theft of articles from motor vehicle whether locked or unlocked | Theft from a Motor Vehicle | 23F | Property | -___ +---
## Agency Supplied NIBRS Code (N6) -___ +--- -**Description:** The NIBRS Code that the Agency Supplies is what drives LIBRS Validation. The LRS Code is important to us for analytics purposes, however we use the NIBRS Code to effectively categroize LRS Codes into kinds of offenses, and then perform validation based on which category the LRS Code falls into. +**Description:** The NIBRS Code that the Agency Supplies is what drives LIBRS Validation. The LRS Code is important to us for analytics purposes, however we use the NIBRS Code to effectively categroize LRS Codes into kinds of offenses, and then perform validation based on which category the LRS Code falls into. -The NIBRS Code also allows Officers to report Offenses in a more specific manner without having to go through the trouble of Subparts and Qualifiers. +The NIBRS Code also allows Officers to report Offenses in a more specific manner without having to go through the trouble of Subparts and Qualifiers. **Data Characteristics:** 3 Character AlphaNumeric. Check [here](https://www.fbi.gov/file-repository/ucr/ucr-2019-1-nibrs-technical-specification.pdf) for a list of the current NIBRS Codes. ### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["n6"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["90034"] -%} -2 | {{error.err_desc["n6"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["86754"] -%} -23| {{error.err_desc["n6"]}} | {{error.err_no}} | {{ error.err_message }} +--- + +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["n6"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90034"] -%} | | | | +| 2 | {{error.err_desc["n6"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["86754"] -%} | | | | +| 23 | {{error.err_desc["n6"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +---
-
## Offense Attempted/Completed (7) -___ +--- -**Description:** Attempted/Completed is how to designate whether or not an Offense occurred to completion, or was merely attempted by the Offender. For instance, an Offender tries to steal a car, but is caught in the act by the police. Since the Offender didn't succeed in stealing the car, this offense would be Attempted. +**Description:** Attempted/Completed is how to designate whether or not an Offense occurred to completion, or was merely attempted by the Offender. For instance, an Offender tries to steal a car, but is caught in the act by the police. Since the Offender didn't succeed in stealing the car, this offense would be Attempted. The only thing to note about this is that Attempted Murder (Attempted 09A) should be reported as a Completed Aggravated Assault (Completed 13A). NIBRS does not allow for 09A Offenses to be Attempted, so instead it should be reported as a Completed Aggravated Assault -- Otherwise, the Offense is reported in the standard fashion. @@ -1452,24 +1503,25 @@ The only thing to note about this is that Attempted Murder (Attempted 09A) shoul * C - Completed ### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["7"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["12051"] -%} -2 | {{error.err_desc["7"]}} | {{error.err_no}} | {{ error.err_message }} +--- + +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ----------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["7"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12051"] -%} | | | | +| 2 | {{error.err_desc["7"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: -* This element is used to indicate whether each offense in the incident was completed or merely attempted. +* This element is used to indicate whether each offense in the incident was completed or merely attempted. ### Allowed Entries -___ +--- Enter one code per incident. @@ -1489,7 +1541,7 @@ Enter one code per incident. {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -1506,13 +1558,14 @@ ____
### Examples: -___ -Example Number | Description -:-------------:|:----------- -1 | During the same incident, Victim Number One (001) was raped and the Offender attempted to rape Victim Number Two (002), but had to leave the scene before the act was consummated due to the arrival of the police.

Offense 001 should be entered as Aggravated Rape (LRS 14:42/V) and have Completed ('C') entered in Offense Attempted/Completed (DE 7). Offense 002 should also be entered as Aggravated Rape (LRS 14:42/V), but will have Attempted ('A') entered in Offense Attempted/Completed (DE 7). +--- -___ +| Example Number | Description | +| :------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | During the same incident, Victim Number One (001) was raped and the Offender attempted to rape Victim Number Two (002), but had to leave the scene before the act was consummated due to the arrival of the police.`

`Offense 001 should be entered as Aggravated Rape (LRS 14:42/V) and have Completed ('C') entered in Offense Attempted/Completed (DE 7). Offense 002 should also be entered as Aggravated Rape (LRS 14:42/V), but will have Attempted ('A') entered in Offense Attempted/Completed (DE 7). | + +---
@@ -1520,33 +1573,36 @@ ___ ## Offender Suspected of Using/Gaming Motivation (8) -___ +--- **Description:** Offender Suspected of Using/Gaming Motivation gives more context to the Offenses that are being reported. It tells us if an Offender is suspected of being on Drugs/Narcotics or has consumed Alcohol either during or shortly before the Incident Occurred. It also gives context of whether Computer Equipment was used to perpetrate the Crime, and if a Gaming/Gambling activity was a motivating factor in committing the crime. **Data Characteristics:** Up to 4x, 1 Character Alpha. If you use 'N', then you cannot use any other values, and values cannot repeat (EG: AAGG and CGN are both invalid combinations). At least one value is required to be present, but the other three slots are optional and can be left blank if nothing else applies. If another value does apply, then the mutual exclusivity and duplicate rules need to be followed. ### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["8"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11004"] -%} -2 | {{error.err_desc["8"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["12006"] -%} -3 | {{error.err_desc["8"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["12007"] -%} -4 | {{error.err_desc["8"]}} | {{error.err_no}} | {{ error.err_message }} +--- -___ +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ----------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["8"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11004"] -%} | | | | +| 2 | {{error.err_desc["8"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12006"] -%} | | | | +| 3 | {{error.err_desc["8"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12007"] -%} | | | | +| 4 | {{error.err_desc["8"]}} | {{error.err_no}} | {{ error.err_message }} | + +--- ### Details: + * Offender Suspected of Using/Gaming Motivation (8) indicates that an Offender is suspected of consuming alcohol, or using drugs/narcotics during, or shortly before, the incident; or, of using a computer, computer terminal, or other computer equipment to perpetrate the crime. Can also indicate if an Offender's gaming activity was a motive in the commission of a crime. ### Allowed Entries -___ + +--- @@ -1564,7 +1620,7 @@ ___ {% for values in subsection.values %} - + {% endfor %} @@ -1581,54 +1637,58 @@ ___
### Examples: -___ -Example Number | Description -:-------------:|:----------- -1 | Witness to an assault reported that the Victim and Offender were in a bar drinking beer when an argument broke out and the Offender attacked the Victim with a knife. Alcohol ('A') should be entered in Offender Suspected of Using/Gaming Motivation (DE 8). -2 | A computer 'hacker' used his personal computer and the Internet to gain access to a company's computer system and steal proprietary data. Computer Equipment ('C') should be entered in Offender Suspected of Using/Gaming Motivation (DE 8). -3 | Offender robbed a bank and a police officer arrested him while trying to leave the bank. Under questioning, the Offender told the officer he needed money because he lost $10,000 that morning at the river boat casino. The officer also smelled alcohol on his breath. Both Alcohol ('A') and Gaming Activity Motive for Crime ('G') should be entered into Offender Suspected of Using/Gaming Motivation (DE 8). +--- + +| Example Number | Description | +| :------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| 1 | Witness to an assault reported that the Victim and Offender were in a bar drinking beer when an argument broke out and the Offender attacked the Victim with a knife. Alcohol ('A') should be entered in Offender Suspected of Using/Gaming Motivation (DE 8). | +| 2 | A computer 'hacker' used his personal computer and the Internet to gain access to a company's computer system and steal proprietary data. Computer Equipment ('C') should be entered in Offender Suspected of Using/Gaming Motivation (DE 8). | +| 3 | Offender robbed a bank and a police officer arrested him while trying to leave the bank. Under questioning, the Offender told the officer he needed money because he lost $10,000 that morning at the river boat casino. The officer also smelled alcohol on his breath. Both Alcohol ('A') and Gaming Activity Motive for Crime ('G') should be entered into Offender Suspected of Using/Gaming Motivation (DE 8). | -_____ +---
## Bias Motivation/Bias Crime Type (8A) -___ -**Description:** Bias Motivation/Crime Type gives insight into the motivation behind an Offender committing a crime. For instance, if the Offender committed the crime because of the Race or Religion of the Victim, that should be noted here. +--- + +**Description:** Bias Motivation/Crime Type gives insight into the motivation behind an Offender committing a crime. For instance, if the Offender committed the crime because of the Race or Religion of the Victim, that should be noted here. **Data Characteristics:** 2 Character Alpha. Must be present and can't be blank. If there is no reason to suspect the Offender had a Bias Type against the Victim use '88' for None, but if not enough information is known about the Offender to determine whether or not a Bias Type was a factor in them committing the crime, use '99' for Unknown. ### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["8a"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11004"] -%} -2 | {{error.err_desc["8a"]}} | {{error.err_no}} | {{ error.err_message }} +--- + +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["8a"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11004"] -%} | | | | +| 2 | {{error.err_desc["8a"]}} | {{error.err_no}} | {{ error.err_message }} | +--- -___ +### Details: -### Details: * Bias Motivation/Bias Crime Type (8) indicates an Offender's motivation to commit an offense because of their bias against a Victim's race, religion, ethnicity, national origin, sexual orientation, disability group, or other bias. * Because of the difficulty in ascertaining the Offender's subjective motivation, bias is to be reported only when an investigation reveals sufficient objective facts to lead a reasonable and prudent person to conclude that the Offender's actions were motivated, in whole or in part, by bias. * In LIBRS, incidents not having facts that indicate biased motivation on the part of the Offender are to be coded as None (88), while incidents involving ambiguous facts (that is, where some facts are present, but not conclusive) are to be coded Unknown (99). * If any Bias Motivation/Bias Crime Type codes are used, other than None (88) or Unknown (99), then the incident will be considered a hate crime, and the Louisiana Revised Statute (DE 6) probably should be appended with the Hate Crime Penalty Enhancer (-H) to represent enhanced penalties related to hate crimes in LRS 14:107.2. -___ +--- ### List of Allowed Entries for DE 8A is on the following page:
### Allowed Entries: -___ + +--- Enter only one code for each Offender Segment (40): @@ -1648,7 +1708,7 @@ Enter only one code for each Offender Segment (40): {% for values in subsection.values %} - + {% endfor %} @@ -1663,41 +1723,44 @@ Enter only one code for each Offender Segment (40):
- -___ +---
## Location Type (9) -___ + +--- **Description:** Location Type is used as a broad-strokes description of the Location in which an Incident Occurred. It's not meant to give particular location information about the location that an Incident occurred (EG: the Exact Address), but rather a short code that can be used for analytics purposes. **Data Characteristics:** 2 Character Alpha. Must be included and can't be blank. ### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["9"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11004"] -%} -2 | {{error.err_desc["9"]}} | {{error.err_no}} | {{ error.err_message }} +--- -___ +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ----------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["9"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11004"] -%} | | | | +| 2 | {{error.err_desc["9"]}} | {{error.err_no}} | {{ error.err_message }} | + +--- ### Details: + * This data element is to be used to report the type of location/ premises where each offense took place. Only one (1) location can be entered for each offense. -___ +--- ### List of Allowed Entries for DE 9 is on the following page:
### Allowed Entries: -___ + +--- Enter only one (1) code per Offense Segment: @@ -1717,7 +1780,7 @@ Enter only one (1) code per Offense Segment: {% for values in subsection.values %} - + {% endfor %} @@ -1733,19 +1796,20 @@ ___ ### Examples: -Example Number | Description -:-------------:|:----------- -1 | An assault started in a bar ('03'), continued into an adjoining parking lot ('18'), and ended in the street ('13'). As the bar was the location where the offense was initiated and best describes the circumstances of the crime, Bar/Night Club ('03') should be entered. -2 | Two Offenders robbed a bar. One of the Offenders raped a female customer in the bar while the other Offender stood at the door with a gun. In this case, there is one incident, with two offenses: robbery and forcible rape. The location of the robbery would be Bar/Night Club ('03'), and the location of the forcible rape would also be Bar/Night Club ('03'). +| Example Number | Description | +| :------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | An assault started in a bar ('03'), continued into an adjoining parking lot ('18'), and ended in the street ('13'). As the bar was the location where the offense was initiated and best describes the circumstances of the crime, Bar/Night Club ('03') should be entered. | +| 2 | Two Offenders robbed a bar. One of the Offenders raped a female customer in the bar while the other Offender stood at the door with a gun. In this case, there is one incident, with two offenses: robbery and forcible rape. The location of the robbery would be Bar/Night Club ('03'), and the location of the forcible rape would also be Bar/Night Club ('03'). | -___ +---
## Number of Premises Entered (10) -___ + +--- **Description:** Number of Premises Entered is only to be used if the Incident contains a NIBRS 220 (Burglary) Offense, and the Location Type (DE 9) is 14 or 19. It is the number of individual/separate dwellings or units that were stolen from in the 220 Offense. For instance, a single Hotel may have been burgled, but a dozen units in that hotel were stolen from. Rather than 12 Offenses with the same location, you should use one Offense with a 12 in this Data Element. @@ -1754,32 +1818,33 @@ This Data Element should be left blank if the 220 Offense did not happen in a Ho **Data Characteristics:** 2 Character Numeric. If the described conditions don't apply, then this value should be left as Blank Spaces (G). Otherwise it should include a two digit number, using 01, 02, 03, etc... for single-digit numbers. ### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["12002"] -%} -1 | {{error.err_desc["10"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["12052"] -%} -2 | {{error.err_desc["10"]}} | {{error.err_no}} | {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["12002"] -%} | | | | +| 1 | {{error.err_desc["10"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12052"] -%} | | | | +| 2 | {{error.err_desc["10"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * This data element is used only if the offense is burglary and the "Hotel Rule" is applicable. In such cases, the number of structures (premises) entered is to be reported. If the LRS offense (6) is not reportable as a Burglary (NIBRS 220), then this data element MUST be left blank. * In the Summary UCR Reporting System, the "Hotel Rule" is only applied to temporary lodging. It states: If a number of dwelling units under a single manager are burglarized, then the offenses are most likely to be reported to the police by the manager rather than the individual tenants. The burglary should be reported as a single offense. The total number of individual rooms, units, storage compartments, etc. entered is to be reported into this data element. * In LIBRS the "Hotel Rule" has been expanded to include rental storage facilities, i.e., "mini-storage" and "self storage" buildings. ### Examples: -___ +--- -Example Number | Description -:-------------:|:----------- -1 | A 'self-storage' building was burglarized and 11 rented storage compartments were forcibly entered. The number '11' (for eleven compartments) should be entered into Number of Premises Entered (DE 10). +| Example Number | Description | +| :------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | A 'self-storage' building was burglarized and 11 rented storage compartments were forcibly entered. The number '11' (for eleven compartments) should be entered into Number of Premises Entered (DE 10). | -___ +---
@@ -1787,33 +1852,35 @@ ___ ## Method of Entry (11) -___ +--- **Description:** Method of Entry should only be used when there is an Offense Type of NIBRS 220. Unlike Number of Premises Entered (DE 10), there is no restriction on if it can only be used with certain Location Types. Any location Type that is valid for use in a Burglary should include this Data Element. The available values are 'F' for Forced Entry (breaking of a window or door to gain access) and 'N' for Non-Forced Entry (picking a lock or going through an open window to gain access). **Data Characteristics:** 1 Character Alpha. Should be left blank unless the NIBRS Code is a 220 (Burglary) Offense. ### Requirements: -___ -Requirment | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["11"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["12054"] -%} -2 | {{error.err_desc["11"]}} | {{error.err_no}}| {{ error.err_message }} +--- +| Requirment | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["11"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12054"] -%} | | | | +| 2 | {{error.err_desc["11"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * This data element is to report whether force or no force was used by the burglar(s) to enter the structure. -* A forced entry is where force of any degree, or a mechanical contrivance of any kind (including a passkey or skeleton key), was used to unlawfully enter a building or other structure. +* A forced entry is where force of any degree, or a mechanical contrivance of any kind (including a passkey or skeleton key), was used to unlawfully enter a building or other structure. * An unforced entry is one where the unlawful entry was achieved without force through an unlocked door or window. * If both forced and unforced entries were involved in the crime, the entry should be reported as having been accomplished through "Force". ### Allowed Entries: -___ + +--- Enter only one (1) code per Offense Segment: @@ -1833,7 +1900,7 @@ Enter only one (1) code per Offense Segment: {% for values in subsection.values %} - + {% endfor %} @@ -1847,14 +1914,15 @@ Enter only one (1) code per Offense Segment:
{{values.code}} -  -  {{values.desc}}
{{values.code}} -  -  {{values.desc}}
{{values.code}} -  -  {{values.desc}}
{{values.code}} -  -  {{values.desc}}
___ -### Examples: -___ +### Examples: -Example Number | Description -:-------------:|:----------- -1 | Investigation of a burglary complaint disclosed that the Offender(s) entered the building through an unlocked street door, then forced a locked door to an office and stole a typewriter. Since one door was forced, the Method of Entry should be entered as Force ("F"). +--- -___ +| Example Number | Description | +| :------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | Investigation of a burglary complaint disclosed that the Offender(s) entered the building through an unlocked street door, then forced a locked door to an office and stole a typewriter. Since one door was forced, the Method of Entry should be entered as Force ("F"). | + +---
@@ -1862,42 +1930,44 @@ ___ ## Type of Criminal Activity/Gang Information (12) -Type of Criminal Activity and Gang Information are combined into a single Data Element. This portion is split into two sections to outline the requirements for each. Which aspect of the Data Element should be used is dependent on the NIBRS Code of the Offense. +Type of Criminal Activity and Gang Information are combined into a single Data Element. This portion is split into two sections to outline the requirements for each. Which aspect of the Data Element should be used is dependent on the NIBRS Code of the Offense. ## Type of Criminal Activity Nos. 1, 2 and 3 (12) -___ +--- **Description:** Type of Criminal Activity is used to add context to Offenses for when they're passed on to the FBI. For instance, a 35A Offense could just as easily be a single person with some Marijuana on them, or a major drug bust with millions of Dollars of narcotics involved. Adding a value here gives the FBI that context when it comes to Offenses that can be open-ended like that. **Data Characteristics**: Up to 3x, 1 Character Alpha. If none apply, then leave this Data Element blank. If more than one apply, then make sure that there aren't any duplicate values being reported (EG: BBB). ### Requirements (Criminal Activity): -___ + +--- The following requirements are for **Type of Criminal Activity Only**: -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|-------------| -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["12"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["12006"] -%} -2 | {{error.err_desc["12"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["12019"] -%} -3 | {{error.err_desc["12"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["90031"] -%} -4 | {{error.err_desc["12"]}} | {{error.err_no}} | {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["12"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12006"] -%} | | | | +| 2 | {{error.err_desc["12"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12019"] -%} | | | | +| 3 | {{error.err_desc["12"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90031"] -%} | | | | +| 4 | {{error.err_desc["12"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### List of Allowed Entries for DE 12 is on the following page:
### Allowed Entries (Criminal Activity) -___ -Up to three (3) of the following **Type of Criminal Activity** Codes can be entered for applicable Offenses. +--- + +Up to three (3) of the following **Type of Criminal Activity** Codes can be entered for applicable Offenses. @@ -1915,7 +1985,7 @@ Up to three (3) of the following **Type of Criminal Activity** Codes can be ente {% for values in subsection.values %} - + {% endfor %} @@ -1933,52 +2003,55 @@ ____
### Examples (Criminal Activity): -___ -Example Number | Description -:-------------:|:----------- -1 | The Offenders published and sold pornographic photographs of children. Therefore, up to three types of Criminal Activity can be entered: Cultivating/Manufacture/Publishing ("C"), Distributing/Selling ("D"), and Exploiting Children ("E"). +--- + +| Example Number | Description | +| :------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | The Offenders published and sold pornographic photographs of children. Therefore, up to three types of Criminal Activity can be entered: Cultivating/Manufacture/Publishing ("C"), Distributing/Selling ("D"), and Exploiting Children ("E"). | -___ +---
## Gang Information Nos. 1, 2 and 3 (12) -___ -**Description:** Gang Information is used to add context to Offenses for when they're passed on to the FBI, and is used with violent and more serious crimes (Rape, Murder, Robbery, Kidnapping, etc...). +--- -**Data Characteristics**: Up to 3x, 1 Character Alpha. If none apply, then use 'N' for None/Unknown. If more than one apply, then make sure that there aren't any duplicate values being reported (EG: JGJ). If 'N' for None or Unkonwn is used, then no other codes can be entered with it and the remaining two spaces for data must remain as Blank Spaces. +**Description:** Gang Information is used to add context to Offenses for when they're passed on to the FBI, and is used with violent and more serious crimes (Rape, Murder, Robbery, Kidnapping, etc...). +**Data Characteristics**: Up to 3x, 1 Character Alpha. If none apply, then use 'N' for None/Unknown. If more than one apply, then make sure that there aren't any duplicate values being reported (EG: JGJ). If 'N' for None or Unkonwn is used, then no other codes can be entered with it and the remaining two spaces for data must remain as Blank Spaces. ### Requirements (Gang Activity): -___ + +--- The following requirements are for **Gang Information Only**: -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|-------------| -{% assign error = site.data.error["12019"] -%} -1 | {{error.err_desc["12A"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["12007"] -%} -2 | {{error.err_desc["12A"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["12019"] -%} | | | | +| 1 | {{error.err_desc["12A"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12007"] -%} | | | | +| 2 | {{error.err_desc["12A"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * (Gang Information): This data element is used to provide Gang Information on Offender(s). * Definition of a Gang: A gang must meet the following criteria in order to be considered a gang: - * Be an ongoing organization, association, or group of three or more persons - * Have a common interest and/or activity characterized by the commission of or involvement in a pattern of criminal or delinquent conduct. + * Be an ongoing organization, association, or group of three or more persons + * Have a common interest and/or activity characterized by the commission of or involvement in a pattern of criminal or delinquent conduct. * If a value of 'N - None/Unknown' is entered, codes "J" and "G" cannot to be entered. - ### Allowed Values -Up to three (3) of the following **Gang Activity* Codes can be entered for applicable Offenses. -___ +Up to three (3) of the following **Gang Activity* Codes can be entered for applicable Offenses. + +---
{{values.code}} -  -  {{values.desc}}
@@ -1996,7 +2069,7 @@ ___ {% for values in subsection.values %} - + {% endfor %} @@ -2005,22 +2078,17 @@ ___
{{values.code}} -  -  {{values.desc}}
{% if forloop.last == false %}
{% endif %} - - {% endif %} -{% endfor %} - - - -___ +--- ### Examples (Gang Information): -___ -Example Number | Description -:-------------:|:----------- -1 | Two males, aged 19, were on bicycles riding through a neighborhood when they were approached by three males and forced to stop. Words were exchanged and one of the bicyclists was attacked. Each of the three attackers, one, aged 16 and the other two, aged 17, had identical tattoos on their upper arm. This marking was commonly associated with a local gang. The entry for Type of Criminal Activity/Gang Information should be Juvenile Gang ("J"). +--- + +| Example Number | Description | +| :------------: | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | Two males, aged 19, were on bicycles riding through a neighborhood when they were approached by three males and forced to stop. Words were exchanged and one of the bicyclists was attacked. Each of the three attackers, one, aged 16 and the other two, aged 17, had identical tattoos on their upper arm. This marking was commonly associated with a local gang. The entry for Type of Criminal Activity/Gang Information should be Juvenile Gang ("J"). | -___ +---
@@ -2028,50 +2096,51 @@ ___ ## Type of Weapon/Force Involved Nos. 1, 2 and 3 (13) -___ +--- -**Description:** Type of Weapon/Force Involved allows Officers to report what kind of weapons were used by an Offender to commit an Offense. It is restricted for use with Certain NIBRS Codes (listed in Requirement 4 below). If one of these NIBRS Codes is present, then this Data Element has to have a value, otherwise it cannot have a value and should be all blanks. +**Description:** Type of Weapon/Force Involved allows Officers to report what kind of weapons were used by an Offender to commit an Offense. It is restricted for use with Certain NIBRS Codes (listed in Requirement 4 below). If one of these NIBRS Codes is present, then this Data Element has to have a value, otherwise it cannot have a value and should be all blanks. **Data Characteristics:** Up to 3x, 3 Character Alpha/Numeric. First two characters should be a number that corresponds to the List of [Available Data Element Values](./data-element-values), and the third character is used as the Automatic Weapon Designator, which is and can only be used to designate if a Firearm was an Automatic Weapon or not. If 'N' for None is used, then no other Values can be included in the other slots for the Data Element. ### Requirements : -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["13"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["12006"] -%} -2 | {{error.err_desc["13"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["12007"] -%} -3 | {{error.err_desc["13"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["12019"] -%} -4 | {{error.err_desc["13"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["12055"] -%} -5 | {{error.err_desc["13"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["12058"] -%} -6 | {{error.err_desc["13"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["12065"] -%} -7 | {{error.err_desc["13"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["12067"] -%} -8 | {{error.err_desc["13"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["12069"] -%} -9 | {{error.err_desc["13"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13100"] -%} -10 | {{error.err_desc["13"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["90036"] -%} -11 | {{error.err_desc["13"]}} | {{error.err_no}}| {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["13"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12006"] -%} | | | | +| 2 | {{error.err_desc["13"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12007"] -%} | | | | +| 3 | {{error.err_desc["13"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12019"] -%} | | | | +| 4 | {{error.err_desc["13"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12055"] -%} | | | | +| 5 | {{error.err_desc["13"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12058"] -%} | | | | +| 6 | {{error.err_desc["13"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12065"] -%} | | | | +| 7 | {{error.err_desc["13"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12067"] -%} | | | | +| 8 | {{error.err_desc["13"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12069"] -%} | | | | +| 9 | {{error.err_desc["13"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13100"] -%} | | | | +| 10 | {{error.err_desc["13"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90036"] -%} | | | | +| 11 | {{error.err_desc["13"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * This data element is used to enter the Type of Weapon/Force Used (13) by an Offender. * Append an "A" if the weapon is automatic. * Any firearm that can fire more than one shot by a single pull of the trigger without manual reloading is classified as an Automatic Firearm. -* Something like a Bump Stock, which is designed to simulate Automatic Fire, should not be considered Automatic because it does not meet the requirement of a single trigger pull firing more than one round. Instead it is multiple trigger pulls that are in quick succession. +* Something like a Bump Stock, which is designed to simulate Automatic Fire, should not be considered Automatic because it does not meet the requirement of a single trigger pull firing more than one round. Instead it is multiple trigger pulls that are in quick succession. -___ +--- ### List of Allowed Entries for DE 13 is on the following page: @@ -2097,7 +2166,7 @@ Can enter up to three (3) codes for each offense: {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -2111,15 +2180,15 @@ Can enter up to three (3) codes for each offense: ___ - ### Examples: -___ -Example Number | Description -:-------------:|:----------- -1 | Three robbers held up a bank. One was armed with a revolver, the second had a sawed-off shotgun, and the third had an automatic machine gun. The entries would be: Handgun ('12'), Shotgun ('14') and Other Automatic Firearm ('15A'). +--- -___ +| Example Number | Description | +| :------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | Three robbers held up a bank. One was armed with a revolver, the second had a sawed-off shotgun, and the third had an automatic machine gun. The entries would be: Handgun ('12'), Shotgun ('14') and Other Automatic Firearm ('15A'). | + +---
@@ -2127,60 +2196,63 @@ ___ ## Property Sequence Number (P1) -___ +--- **Description:** Property Sequence Number is a uniquely identifying number for each Property that's included in the Incident. It is used to link Properties to Offenses in Segment 33's. The same Property Sequence Number can be used Multiple Times across Segment 33's in an Incident, because it's possible for a Property to be involved in more than one Offense. **Data Characteristics:** 3 Character Numeric. Must be front-padded with zeros to make a three-digit number (EG: 1 would be 001). Must be unique for each Segment 31. ### Requirements : -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["12006"] -%} -1 | {{error.err_desc["p1"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["90019"] -%} -2 | {{error.err_desc["p1"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["90020"] -%} -3 | {{error.err_desc["p1"]}} | {{error.err_no}}| {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["12006"] -%} | | | | +| 1 | {{error.err_desc["p1"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90019"] -%} | | | | +| 2 | {{error.err_desc["p1"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90020"] -%} | | | | +| 3 | {{error.err_desc["p1"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * Each property in an incident must be assigned a unique sequence number from "001" to "999". -___ +---
## Property Sequence Number Reference (P1R) -**Description:** Property Sequence Number Reference is only used in Segment 33 to link Properties to Offenses. It should be present in each Segment 33 in the Incident, and should refernce the value of one of the Property Seqence Numbers (DE P1) in the Property Description Segments (Segment 31). +**Description:** Property Sequence Number Reference is only used in Segment 33 to link Properties to Offenses. It should be present in each Segment 33 in the Incident, and should refernce the value of one of the Property Seqence Numbers (DE P1) in the Property Description Segments (Segment 31). **Data Characteristics:** 3 Character Numeric. Must be front-padded with zeros to make a three-digit number (EG: 1 would be 001). May repeat across multiple Segment 33's, as a single property can be involved in more than one Offense. ### Requirements : -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["90019"] -%} -1 | {{error.err_desc["p1r"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["90020"] -%} -2 | {{error.err_desc["p1r"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["90024"] -%} -3 | {{error.err_desc["p1r"]}} | {{error.err_no}}| {{ error.err_message }} +--- -___ +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["90019"] -%} | | | | +| 1 | {{error.err_desc["p1r"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90020"] -%} | | | | +| 2 | {{error.err_desc["p1r"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90024"] -%} | | | | +| 3 | {{error.err_desc["p1r"]}} | {{error.err_no}} | {{ error.err_message }} | + +--- ### Details: + * There is no UNIQUE constraint for the Property Sequence Number Reference. This allows for a Property to relate to many Offenses if multiple Property/Offense segments are submitted within a single incident.
-___ +---
@@ -2191,32 +2263,34 @@ ___ **Data Characteristics**: 1 Character Numeric. Mandatory for each Segment 31 (Property Description Segment) that is included in the Incident. ### Requirements : -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10072"] -%} -1 | {{error.err_desc["14"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["10077"] -%} -2 | {{error.err_desc["14"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["10081"] -%} -3 | {{error.err_desc["14"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11004"] -%} -4 | {{error.err_desc["14"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13019"] -%} -5 | {{error.err_desc["14"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13052"] -%} -6 | {{error.err_desc["14"]}} | {{error.err_no}}| {{ error.err_message }} +--- -____ +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10072"] -%} | | | | +| 1 | {{error.err_desc["14"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["10077"] -%} | | | | +| 2 | {{error.err_desc["14"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["10081"] -%} | | | | +| 3 | {{error.err_desc["14"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11004"] -%} | | | | +| 4 | {{error.err_desc["14"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13019"] -%} | | | | +| 5 | {{error.err_desc["14"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13052"] -%} | | | | +| 6 | {{error.err_desc["14"]}} | {{error.err_no}} | {{ error.err_message }} | + +--- ### Details: + * Type of Property Loss (14) describes the various type(s) of property loss that can occur during an incident, such as Recovery, Seizure, etc. * Every different type of property loss that occurs during an incident must be submitted in a separate Property Description Segment (31), when the incident involved one or more of the Offenses listed above. For instance if a Property is stolen and then recovered, there should be two Property Description Segments (Segment 31) that have a Property Loss Type of 7 for Stolen and 5 for Recovered. ### Allowed Entries: -___ +--- Enter only one (1) code for each Property Description Segment. However, as many property segments as applicable can be submitted per incident: @@ -2236,7 +2310,7 @@ Enter only one (1) code for each Property Description Segment. However, as many {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -2251,6 +2325,7 @@ Enter only one (1) code for each Property Description Segment. However, as many ___ ### Available Property Loss Types by NIBRS Code + To see a list of which Property Loss Types are available for each NIBRS Code based on their Attempted/Completed Status, you can find it here: [List of Available DE 14 NIBRS Values](./data-element-values#allowable-property-loss-types-de-14-by-nibrs-and-attempedcompleted)
@@ -2258,46 +2333,48 @@ To see a list of which Property Loss Types are available for each NIBRS Code bas
## Property Description (15) -___ -**Description:** Property Description is a value that corresponds to a list of the kinds of Properties that can be reported to the State and FBI. +--- + +**Description:** Property Description is a value that corresponds to a list of the kinds of Properties that can be reported to the State and FBI. **Data Characteristics:** 2 Character Numeric between 01 and 99 that corresponds to a value of the List of [Available Data Element Values](./data-element-values). Required field when Property Loss Type is not 1 or 8. ### Requirements : -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["15"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13072"] -%} -2 | {{error.err_desc["15"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13075"] -%} -3 | {{error.err_desc["15"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13087"] -%} -4 | {{error.err_desc["15"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13090"] -%} -5 | {{error.err_desc["15"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13101"] -%} -6 | {{error.err_desc["15"]}} | {{error.err_no}}| {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["15"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13072"] -%} | | | | +| 2 | {{error.err_desc["15"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13075"] -%} | | | | +| 3 | {{error.err_desc["15"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13087"] -%} | | | | +| 4 | {{error.err_desc["15"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13090"] -%} | | | | +| 5 | {{error.err_desc["15"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13101"] -%} | | | | +| 6 | {{error.err_desc["15"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * Property Description (DE 15) is to be used to enter descriptions of the property that was burned, counterfeited, destroyed/damaged/vandalized, etc., during, or as a result of, the incident. -### Allowed Entries: -___ +### Allowed Entries: -* Enter only one Property Description (DE 15) code per Property Description (31) Segment, entering multiple Property Description (31) Segments for multiple Properties. - * This also applies to multiples of Property Descriptions. You should submit a Segment 31 for each Property Involved in the Incident, even if it is the same as another Property. - * EG: Three TV's are stolen from Best Buy. Being the same Make and Model, they all will have the same Description and Value, however you should submit three Property Description Segments to LIBRS. -* Do NOT enter duplicate Property Sequence Numbers (DE P1) within an incident unless a different Type of Property Loss (DE 14) is used. - * EG: Just because those three TV's in the previous example are all the same make, model, and value, doesn't mean they should have the same Property Sequence Number. -* LIBRS will aggregate the counts of Property Descriptions and the Total Values associated with them for NIBRS Extraction. Therefore the FBI will not receieve this granular of data, however the State of Louisiana Will. +--- +* Enter only one Property Description (DE 15) code per Property Description (31) Segment, entering multiple Property Description (31) Segments for multiple Properties. + * This also applies to multiples of Property Descriptions. You should submit a Segment 31 for each Property Involved in the Incident, even if it is the same as another Property. + * EG: Three TV's are stolen from Best Buy. Being the same Make and Model, they all will have the same Description and Value, however you should submit three Property Description Segments to LIBRS. +* Do NOT enter duplicate Property Sequence Numbers (DE P1) within an incident unless a different Type of Property Loss (DE 14) is used. + * EG: Just because those three TV's in the previous example are all the same make, model, and value, doesn't mean they should have the same Property Sequence Number. +* LIBRS will aggregate the counts of Property Descriptions and the Total Values associated with them for NIBRS Extraction. Therefore the FBI will not receieve this granular of data, however the State of Louisiana Will. @@ -2315,7 +2392,7 @@ ___ {% for values in subsection.values %} - + {% endfor %} @@ -2339,53 +2416,51 @@ ___ **Data Characteristics:** 9 Character Numeric. Must be front-padded with Zero's (0) to make a nine-digit number. Cannot contain any blank spaces or periods (.) to act as Decimals. All Property Values should be rounded up to the nearest whole dollar value. ### Requirements : -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10084"] -%} -1 | {{error.err_desc["16"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13002"] -%} -2 | {{error.err_desc["16"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13042"] -%} -3 | {{error.err_desc["16"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13051"] -%} -4 | {{error.err_desc["16"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13053"] -%} -5 | {{error.err_desc["16"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13054"] -%} -6 | {{error.err_desc["16"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13073"] -%} -7 | {{error.err_desc["16"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13091"] -%} -8 | {{error.err_desc["16"]}} | {{error.err_no}}| {{ error.err_message }} - - - - +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10084"] -%} | | | | +| 1 | {{error.err_desc["16"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13002"] -%} | | | | +| 2 | {{error.err_desc["16"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13042"] -%} | | | | +| 3 | {{error.err_desc["16"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13051"] -%} | | | | +| 4 | {{error.err_desc["16"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13053"] -%} | | | | +| 5 | {{error.err_desc["16"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13054"] -%} | | | | +| 6 | {{error.err_desc["16"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13073"] -%} | | | | +| 7 | {{error.err_desc["16"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13091"] -%} | | | | +| 8 | {{error.err_desc["16"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * Value of Property (16) is to be used to enter the total dollar value of property that was burned (includes damage caused in fighting the fire), counterfeited, destroyed/damaged/ vandalized, recovered, seized, stolen, etc., as a result of the incident. * DO NOT INCLUDE partial dollar amounts (cents). Round values to the nearest whole dollar amounts. If the value is unknown, enter one dollar ($1.00), that is, "000000001". * If value is known and it is between $1.00 and $2.00 the reporting agency should enter $2.00, that is, "000000002". This is the minimum dollar value that can be entered in Value of Property (16), as "1" (or "000000001") is used for Unknown. ### Examples: -___ -Example Number | Description -:-------------:|:----------- -1 | A man purchases a new power saw from the hardware store. Later that same day someone breaks into his truck and steals the saw. The saw was purchased for $95.73. The value of the property would be rounded to the nearest whole dollar and reported as '000000096'- $96.00. +--- + +| Example Number | Description | +| :------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | A man purchases a new power saw from the hardware store. Later that same day someone breaks into his truck and steals the saw. The saw was purchased for $95.73. The value of the property would be rounded to the nearest whole dollar and reported as '000000096'- $96.00. |
## Date Recovered (17) -___ + +--- **Description:** Date Recovered is the date in with a Property that was previously stolen was recovered. Any Segment 31 that has a Property Loss Type os '5 - Recovered' needs to have a Date Recovered. Otherwise, the Data Element should be Blank Spaces. @@ -2395,61 +2470,63 @@ ___ ### Requirements: -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11005"] -%} -1 | {{error.err_desc["17"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13001"] -%} -2 | {{error.err_desc["17"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13007"] -%} -3 | {{error.err_desc["17"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13055"] -%} -4 | {{error.err_desc["17"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13056"] -%} -5 | {{error.err_desc["17"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["23235"] -%} -6 | {{error.err_desc["17"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11005"] -%} | | | | +| 1 | {{error.err_desc["17"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13001"] -%} | | | | +| 2 | {{error.err_desc["17"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13007"] -%} | | | | +| 3 | {{error.err_desc["17"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13055"] -%} | | | | +| 4 | {{error.err_desc["17"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13056"] -%} | | | | +| 5 | {{error.err_desc["17"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["23235"] -%} | | | | +| 6 | {{error.err_desc["17"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * If previously stolen property is recovered, the month, day, and year (MMDDYYYY) of its recovery should be entered into this data element. * If there is more than one Date Recovered (DE 17) for the same Property Description (DE 15), enter the earliest date. * If the Date Recovered is unknown, enter the date of the report. -____ +---
## Number of Stolen Vehicles (18) -___ +--- -**Description:** Number of Stolen Vehicles is the sum of the Segment 31's that have a Property Description containing a Vehicle and a Property Loss Type of '7 - Stolen'. For it to appear in Segment 30 with any value other than Zero (0), there must be Segment 31's present in the Incident that meet those conditions. +**Description:** Number of Stolen Vehicles is the sum of the Segment 31's that have a Property Description containing a Vehicle and a Property Loss Type of '7 - Stolen'. For it to appear in Segment 30 with any value other than Zero (0), there must be Segment 31's present in the Incident that meet those conditions. **Data Characteristics:** 2 Characters Numeric. If less than 10, a Zero (0) should be in the first character (EG: 01, 02, 03, etc...). ~~Should always have a value when Segment 30 is present, using '00' if no stolen vehicle are present in the Incident.~~ Update 07/2021 - This should only have a value if there is a Completed 240 - MV Theft Offense in the Incident. 00 does not represent 0 stolen vehicles, rather 'Unknown'. ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["13002"] -%} -1 | {{error.err_desc["18"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13057"] -%} -2 | {{error.err_desc["18"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13058"] -%} -3 | {{error.err_desc["18"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13050"] -%} -4 | {{error.err_desc["18"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["13002"] -%} | | | | +| 1 | {{error.err_desc["18"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13057"] -%} | | | | +| 2 | {{error.err_desc["18"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13058"] -%} | | | | +| 3 | {{error.err_desc["18"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13050"] -%} | | | | +| 4 | {{error.err_desc["18"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * Number of Stolen Vehicles (18) indicates how many motor vehicles were stolen in an incident reported as a Motor Vehicle Theft. -____ +---
@@ -2463,31 +2540,28 @@ ____ ### Requirements: -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10073"] -%} -1 | {{error.err_desc["19"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13002"] -%} -2 | {{error.err_desc["19"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13061"] -%} -3 | {{error.err_desc["19"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13050"] -%} -4 | {{error.err_desc["19"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["10079"] -%} -4 | {{error.err_desc["19"]}} | {{error.err_no}}| {{ error.err_message }} - - - +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10073"] -%} | | | | +| 1 | {{error.err_desc["19"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13002"] -%} | | | | +| 2 | {{error.err_desc["19"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13061"] -%} | | | | +| 3 | {{error.err_desc["19"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13050"] -%} | | | | +| 4 | {{error.err_desc["19"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["10079"] -%} | | | | +| 4 | {{error.err_desc["19"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * Number of Recovered Motor Vehicles (19) indicates how many motor vehicles were recovered in an incident that reported Motor Vehicle Thefts. -___ +---
@@ -2501,35 +2575,37 @@ ___ ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["20"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13064"] -%} -2 | {{error.err_desc["20"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13065"] -%} -3 | {{error.err_desc["20"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13092"] -%} -4 | {{error.err_desc["20"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["23201"] -%} -5 | {{error.err_desc["20"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["20"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13064"] -%} | | | | +| 2 | {{error.err_desc["20"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13065"] -%} | | | | +| 3 | {{error.err_desc["20"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13092"] -%} | | | | +| 4 | {{error.err_desc["20"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["23201"] -%} | | | | +| 5 | {{error.err_desc["20"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * Suspected Drug Type (20) identifies the type of drugs or narcotics Seized in a drug case. * If the Suspected Drug Type (20)is a Counterfeit, append an "X" to the drug code, otherwise leave the second character Blank (G). * Suspected Drug Type (20) is not to be used when drugs or narcotics were Burned, Stolen, etc., in connection with other offenses, such as Arson, Larceny/Theft, etc. -___ +--- ### List of Allowed Entries for DE 20 is on the following page:
-### Allowed Entries: +### Allowed Entries: + Enter one per Segment 31 that has a Property Description of '10 - Drugs/Narcotics'. There are no restrictions on multiple Segment 31's having the same Suspected Drug type (EG: You can report 1 lb of Marijuana, as well as 10 Marijuana Plants as two different Segment 31's, or if two people are found in possession of the same drug type on their person, you can report both of those containers as separate properties).
{{values.code}} -  -  {{values.desc}}
@@ -2548,7 +2624,7 @@ Enter one per Segment 31 that has a Property Description of '10 - Drugs/Narcotic {% for values in subsection.values %} - + {% endfor %} @@ -2576,28 +2652,29 @@ ___ ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["13002"] -%} -1 | {{error.err_desc["21"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13064"] -%} -2 | {{error.err_desc["21"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13065"] -%} -3 | {{error.err_desc["21"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13066"] -%} -4 | {{error.err_desc["21"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["13002"] -%} | | | | +| 1 | {{error.err_desc["21"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13064"] -%} | | | | +| 2 | {{error.err_desc["21"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13065"] -%} | | | | +| 3 | {{error.err_desc["21"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13066"] -%} | | | | +| 4 | {{error.err_desc["21"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * Estimated Drug Quantity (21) indicates the quantity of drugs or narcotics seized in a drug case, it is not to be used when drugs or narcotics were Burned, Stolen, etc. in connection with other Offenses, such as Arson, Burglary, Breaking and Entering, Larceny, Theft, etc. * Nine (9) characters are available to enter the number of WHOLE pounds, ounces, grams, etc., and three (3) more characters are available to enter the DECIMAL amount. A DECIMAL POINT must be entered to separate the whole and decimal amounts. Zero ('0') or space fill (G) should be added to the right or left of the value **to preserve the decimal's position as the tenth character in the field.** * When Estimated Drug Quantity (21) is Unknown enter '000000001.000', a value of '1', to signify that the value is not known or not reported. Also, Type Drug Measurement (22) MUST be entered as Not Reported/Unknown ('XX') and Value of Property (16) MUST be entered as Unknown (000000001). * If LRS Offense (6) is not reportable as a drug violation (35A), this data element MUST BE LEFT BLANK (G). -___ +---
@@ -2611,31 +2688,32 @@ ___ ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["22"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13064"] -%} -2 | {{error.err_desc["22"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13065"] -%} -3 | {{error.err_desc["22"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13067"] -%} -4 | {{error.err_desc["22"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["13084"] -%} -5 | {{error.err_desc["22"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["22"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13064"] -%} | | | | +| 2 | {{error.err_desc["22"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13065"] -%} | | | | +| 3 | {{error.err_desc["22"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13067"] -%} | | | | +| 4 | {{error.err_desc["22"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["13084"] -%} | | | | +| 5 | {{error.err_desc["22"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * Type Drug Measurement (22) indicates how Seized drugs and narcotics are quantified in a drug case. -___ +--- ### Allowed Entries: -___ +---
{{values.code}} -  -  {{values.desc}}
@@ -2653,7 +2731,7 @@ ___ {% for values in subsection.values %} - + {% endfor %} @@ -2664,10 +2742,9 @@ ___ {% endif %} {% endfor %} -
{{values.code}} -  -  {{values.desc}}
- + -___ +---
@@ -2675,7 +2752,7 @@ ___ ## Victim Sequence Number (23) -___ +--- **Description:** Victim Sequence Number is the uniquely identifying ID for each Victim in an Incident. This number cannot repeat in the same incident, and must be unique for each Segment 50 that is present. This data Element can never be ommitted and must always have a value between 001 and 999. @@ -2683,24 +2760,24 @@ ___ ### Requirements: -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["23"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15002"] -%} -2 | {{error.err_desc["23"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15051"] -%} -3 | {{error.err_desc["23"]}} | {{error.err_no}}| {{ error.err_message }} +--- -____ +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["23"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15002"] -%} | | | | +| 2 | {{error.err_desc["23"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15051"] -%} | | | | +| 3 | {{error.err_desc["23"]}} | {{error.err_no}} | {{ error.err_message }} | +--- ### Details: + * Each victim in an incident MUST be assigned a unique Victim Sequence Number (23) from '001' to '999'. -___ +---
@@ -2708,33 +2785,31 @@ ___ ## Offense Connected to Victim Sequence Number (24) -___ +--- -**Description:** Offense Connected to Victim Sequence Number is only used in Offense Segments Segmetn 20). Each Offense can only be related to a single Victim, so if there are multiple Victims of the same Offense, or Multiple Offenses for the same Victim, you'll need multiple Segment 20's to reference that. This Data Element is important because it's what's used to link the Offenders to their Offenses. +**Description:** Offense Connected to Victim Sequence Number is only used in Offense Segments Segmetn 20). Each Offense can only be related to a single Victim, so if there are multiple Victims of the same Offense, or Multiple Offenses for the same Victim, you'll need multiple Segment 20's to reference that. This Data Element is important because it's what's used to link the Offenders to their Offenses. **Data Characteristics:** 3 Character Numeric. Should be front-padded with Zero's (0) to make a three digit number. (EG: 1 would be 001). Needs to match a Victim Sequence Number (DE 23) that's present in a Segment 50 of the Incident. ### Requirements: -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["24"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["12090"] -%} -2 | {{error.err_desc["24"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15078"] -%} -3 | {{error.err_desc["24"]}} | {{error.err_no}}| {{ error.err_message }} - - -___ +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["24"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12090"] -%} | | | | +| 2 | {{error.err_desc["24"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15078"] -%} | | | | +| 3 | {{error.err_desc["24"]}} | {{error.err_no}} | {{ error.err_message }} | +--- ### Details: * This data element is to be used to link each offense to each victim. That is, the offense which was perpetrated against the victim during the incident. * If this data element does not match one of the values submitted in Data Element # 23 (Victim Segment Number), the submission will be returned with errors. -___ +---
@@ -2796,15 +2871,15 @@ The following chart shows Offenses that CANNOT occur to the same victim in the s ____ - ### Examples: -___ -Example Number | Description -:-------------:|:----------- -1 | Two victims, Victim 001 and Victim 002, were robbed, and Victim 001 was also taken hostage by the Offender with a hand gun in a parking lot. The incident's Offense Segments could be submitted as follows: {::nomarkdown}{:/} +--- -___ +| Example Number | Description | +| :------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | Two victims, Victim 001 and Victim 002, were robbed, and Victim 001 was also taken hostage by the Offender with a hand gun in a parking lot. The incident's Offense Segments could be submitted as follows: {::nomarkdown}``{:/} | + +---
@@ -2814,35 +2889,36 @@ ___ **Description:** Type of Victim dicates the classification of the Victim of an Offense. The descriptors that are available for selection are based on the NIBRS Code of the Offense. All Victim Types except for 'S - Society' are applicable to Crimes Against Property, while only Victim Types of 'I - Individual' and 'L - Law Enforcement' are applicable to Crimes Against Persons. On the contrary, Crimes Against Society can only have a Victim Type of 'S - Society'. -**Data Characteristics:** 1 Character Alpha. Must always be present and cannot be left blank. +**Data Characteristics:** 1 Character Alpha. Must always be present and cannot be left blank. ### Requirements: -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["25"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["10080"] -%} -2 | {{error.err_desc["25"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11004"] -%} -3 | {{error.err_desc["25"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15067"] -%} -4 | {{error.err_desc["25"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["22110"] -%} -5 | {{error.err_desc["25"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["90001"] -%} -6 | {{error.err_desc["25"]}} | {{error.err_no}} | {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["25"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["10080"] -%} | | | | +| 2 | {{error.err_desc["25"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11004"] -%} | | | | +| 3 | {{error.err_desc["25"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15067"] -%} | | | | +| 4 | {{error.err_desc["25"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["22110"] -%} | | | | +| 5 | {{error.err_desc["25"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90001"] -%} | | | | +| 6 | {{error.err_desc["25"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- Notes: + * NO ERROR NUMBER For Human Trafficking Offenses (NIBRS Codes 64A, 64B and 40C), the data value for Type of Victim (25) must be Individual ('I'). * One Type of Victim (25) code MUST be entered for each victim. * Definition of Law Enforcement Officer/Peace Officer: Deputy sheriffs, municipal police officers, probation and enforcement parole officers, wildlife enforcement agents, city marshals and deputies would be considered a Law Enforcement Officer if a Victim and should have a Type of Victim (25) code of "L". * The Officer should be "In-the-Line-of-Duty" when victimized in order to report Type of Victim (25) as Law Enforcement Officer ("L"). The same rules that apply to the LEOKA form in UCR Summary also apply to this Type of Victim (25). * This Type of Victim (25) can ONLY be used for simple assaults, aggravated assaults, negligent manslaughter, murders and non-negligent homicide offenses to a Law Enforcement Officer, that took place when the Officer was On Duty as a Law Enforcement Officer. -___ +--- ### List of Allowed Entries for DE 25 is on the following page: @@ -2868,7 +2944,7 @@ Enter only one (1) code per Type of Victim Segment (25): {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -2879,44 +2955,42 @@ Enter only one (1) code per Type of Victim Segment (25): {% endif %} {% endfor %} - +
-### Example: +### Example: -___ +--- -Example Number | Description -:-------------:|:----------- -1 | During a bank robbery *(Crime Against Property)*, the Offender pointed a gun at a teller and demanded and received money. The robber also pistol-whipped a customer who stood in his way as he made his getaway from the bank.

Assuming the facts above, there were **3** victims: {::nomarkdown}{:/} +| Example Number | Description | +| :------------: | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | During a bank robbery*(Crime Against Property)*, the Offender pointed a gun at a teller and demanded and received money. The robber also pistol-whipped a customer who stood in his way as he made his getaway from the bank.`

`Assuming the facts above, there were **3** victims: {::nomarkdown}``{:/} | -___ +---
## Type of Officer Activity/Circumstance (25A) -___ +--- -**Description:** Type of Officer Activity/Circumstance is used in LEOKA Circumstances only, and it indicates the activity in which the Law Enforcement Officer was engaged at the time the officer was either killed or assaulted in the line of duty. +**Description:** Type of Officer Activity/Circumstance is used in LEOKA Circumstances only, and it indicates the activity in which the Law Enforcement Officer was engaged at the time the officer was either killed or assaulted in the line of duty. **Data Characteristics:** 2 Character Alpha. Should only be used if Victim Type is 'L - Law Enforcement' and Offense is an 09A, 13A, 13B, or 13C. ### Requirements: -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["25a"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11004"] -%} -2 | {{error.err_desc["25a"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15082"] -%} -3 | {{error.err_desc["25a"]}} | {{error.err_no}}| {{ error.err_message }} - +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["25a"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11004"] -%} | | | | +| 2 | {{error.err_desc["25a"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15082"] -%} | | | | +| 3 | {{error.err_desc["25a"]}} | {{error.err_no}} | {{ error.err_message }} |
@@ -2940,7 +3014,7 @@ Enter only one (1) code for each Victim Segment: {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -2951,10 +3025,9 @@ Enter only one (1) code for each Victim Segment: {% endif %} {% endfor %} - - + -___ +---
@@ -2962,7 +3035,7 @@ ___ ## Officer Assignment Type (25B) -___ +--- **Description:** Officer Assignment Type is used to report the victim Officer's Type of Assignment when a LEOKA Offense occurred of which they were the Victim. @@ -2970,16 +3043,16 @@ ___ ### Requirements: -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["25b"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11004"] -%} -2 | {{error.err_desc["25b"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15082"] -%} -3 | {{error.err_desc["25b"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["25b"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11004"] -%} | | | | +| 2 | {{error.err_desc["25b"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15082"] -%} | | | | +| 3 | {{error.err_desc["25b"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +---
@@ -3003,7 +3076,7 @@ Enter only one (1) code for each Victim Segment: {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -3021,36 +3094,38 @@ ___ ## Officer ORI, Other Jurisdiction (25C) -___ +--- **Description:** Officer ORI, Other Jurisdiction is used to report the ORI Number of a Law Enforcement Officer's Agency when an officer from another jurisdiction is killed or assaulted in the line of duty in the reporting Agency's jurisdiction. No entry is required for LEOKA Offenses that occur in the Officer's own Agency jurisdiction. **Data Characteristics:** 9 Character Alpha ### Requirements: + Should be a Nine-Digit, valid ORI Number, or Blank Spaces (G) if Not requried -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["15082"] -%} -1 | {{error.err_desc["25c"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["15082"] -%} | | | | +| 1 | {{error.err_desc["25c"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * This is the 9-character NCIC Agency Identifier (ORI) assigned to every law enforcement agency in Louisiana. This ORI is used to record the ORI of a victim who is an officer involved in a multijurisdictional incident. -___ +--- ### Allowed Entries: Enter only (1) code for each Victim Segment: -### Acceptable Data Values: +### Acceptable Data Values: A thru Z (Uppercase letter only), or 0 thru 9 -___ +---
@@ -3058,40 +3133,40 @@ ___ ## Age of Victim [At Time Incident Occurred] (26) -___ +--- -**Description:** For Offenses in which a Person (I - Individual or L - Law Enforcement) are the Victim Type (DE 25), Age of Victim should be the two-digit age of the Victim when the Incident Occurred. Ages can be appended with an 'E' to represent an Estimated Age of the Victim if that actual Age is not known, otherwise the third character should remain a Blank Space. For ages that are less that one year, check the List of Available Values below. +**Description:** For Offenses in which a Person (I - Individual or L - Law Enforcement) are the Victim Type (DE 25), Age of Victim should be the two-digit age of the Victim when the Incident Occurred. Ages can be appended with an 'E' to represent an Estimated Age of the Victim if that actual Age is not known, otherwise the third character should remain a Blank Space. For ages that are less that one year, check the List of Available Values below. **Data Characteristics:** 3 Character Alpha/Numeric. Cannot be Blank and must always have a value. Use '00' if Age is Unknown. - ### Requirements: -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["26"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11004"] -%} -2 | {{error.err_desc["26"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["14022"] -%} -3 | {{error.err_desc["26"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15058"] -%} -4 | {{error.err_desc["26"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15081"] -%} -5 | {{error.err_desc["26"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["90045"] -%} -6 | {{error.err_desc["26"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["90046"] -%} -6 | {{error.err_desc["26"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["26"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11004"] -%} | | | | +| 2 | {{error.err_desc["26"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["14022"] -%} | | | | +| 3 | {{error.err_desc["26"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15058"] -%} | | | | +| 4 | {{error.err_desc["26"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15081"] -%} | | | | +| 5 | {{error.err_desc["26"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90045"] -%} | | | | +| 6 | {{error.err_desc["26"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90046"] -%} | | | | +| 6 | {{error.err_desc["26"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * If the Type of Victim (25) is a person (that is, Individual ('I') or Law Enforcement Officer ('L')), his/her age is to be entered into Age of Victim (26) either as an Exact Age, an Estimated Age, or as Unknown. * If the Type of Victim (25) is a person (that is, Individual ('I') or Law Enforcement Officer ('L')), then Age of Victim (26) is required to be entered. If Type of Victim (25) is not a person, then Age of Victim (26) MUST be left Blank (G). * If the Victim's Exact Age is not known, estimate the victim's age. Use one of the codes in the above table, and append an 'E',for Estimated. If it is impossible to determine even an Estimated Age of the victim, then enter Unknown ('00'). -___ +--- ### Allowed Entries: @@ -3113,7 +3188,7 @@ Enter only (1) code for each Victim Segment: {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -3124,18 +3199,18 @@ Enter only (1) code for each Victim Segment: {% endif %} {% endfor %} - + -### Example: +### Example: -___ +--- -Example Number | Description -:-------------:|:----------- -1 | If the victim was 18 years old, enter '18'. -2 | If the victim appeared 25 to 30 years old, **average the age range** to get 27.5, then **round down** and enter '27E'. +| Example Number | Description | +| :------------: | :-------------------------------------------------------------------------------------------------------------------------------- | +| 1 | If the victim was 18 years old, enter '18'. | +| 2 | If the victim appeared 25 to 30 years old,**average the age range** to get 27.5, then **round down** and enter '27E'. | -___ +---
@@ -3143,64 +3218,63 @@ ___ ## Date of Birth of Victim (L26) -___ +--- **Description:** DOB of Victim is not a required field, but if the Date of Birth is known then it can be entered here in the MMDDYYYY Format. If this field has a value, then you shouldn't be using an Estimated age in Data Element 26 (Age of Victim), however we don't stop that because it's possible the exact Incident Date is Unknown, and instead the Reporting Date is being used. For that reason we allow Estimated Ages to also have a Date of Birth present. - **Data Characteristics:** 8 Character Date. Optional, if not entered should be all Blank Spaces (Not Zeros) **Format:** MMDDYYYY ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11005"] -%} -1 | {{error.err_desc["l26"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["90046"] -%} -2 | {{error.err_desc["l26"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["11005"] -%} | | | | +| 1 | {{error.err_desc["l26"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90046"] -%} | | | | +| 2 | {{error.err_desc["l26"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * If Type of Victim (25) is a person (that is, Individual ('I') or Law Enforcement Officer ('L')), then his/her date of birth, if available, is to be indicated in Date of Birth of Victim (L26). -___ +---
## Sex of Victim (27) -___ +--- **Description:** Sex of Victim is used to indicate the sex of an Victim that is a Person (I - Individual or L - Law Enforcement). **Data Characteristics:** 1 Character Alpha. Must be entered for Victim Types I and L. Use U if Unknown, don't leave the field blank. - ### Requirements: -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["27"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["14060"] -%} -2 | {{error.err_desc["27"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15058"] -%} -3 | {{error.err_desc["27"]}} | {{error.err_no}}| {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["27"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["14060"] -%} | | | | +| 2 | {{error.err_desc["27"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15058"] -%} | | | | +| 3 | {{error.err_desc["27"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * If Type of Victim (25) is a person [(that is, Individual ('I') or Law Enforcement Officer ('L'), then his/her sex is to be indicated in Sex of Victim (27). -___ +---
@@ -3224,7 +3298,7 @@ Enter only (1) code for each Victim Segment: {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -3235,10 +3309,9 @@ Enter only (1) code for each Victim Segment: {% endif %} {% endfor %} - - + -___ +---
@@ -3246,30 +3319,30 @@ ___ ## Race of Victim (28) -___ +--- -**Description:** Race of Victim is used to indicate the race of an Victim that is a Person (I - Individual or L - Law Enforcement). Race is defined as persons that share similar *physical* characteristics. Ethinicity is defined as persons that share similar *cultural* characteristics. +**Description:** Race of Victim is used to indicate the race of an Victim that is a Person (I - Individual or L - Law Enforcement). Race is defined as persons that share similar *physical* characteristics. Ethinicity is defined as persons that share similar *cultural* characteristics. **Data Characteristics:** 1 Character Alpha. Must be entered for Victim Types I and L. Use U if Unknown, don't leave the field blank. - ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["28"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15058"] -%} -2 | {{error.err_desc["28"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["28"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15058"] -%} | | | | +| 2 | {{error.err_desc["28"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * If Type of Victim (25) is a person (that is, Individual ('I') or Law Enforcement Officer ('L')), then, his/her race is to be indicated in Race of Victim (28). -___ +---
@@ -3293,7 +3366,7 @@ Enter only (1) code for each Victim Segment: {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -3304,40 +3377,40 @@ Enter only (1) code for each Victim Segment: {% endif %} {% endfor %} - - + -___ +---
## Ethnicity of Victim (29) -___ +--- -**Description:** Ethnicity of Victim is used to indicate the ethnicity of an Victim that is a Person (I - Individual or L - Law Enforcement). Race is defined as persons that share similar *physical* characteristics. Ethinicity is defined as persons that share similar *cultural* characteristics. +**Description:** Ethnicity of Victim is used to indicate the ethnicity of an Victim that is a Person (I - Individual or L - Law Enforcement). Race is defined as persons that share similar *physical* characteristics. Ethinicity is defined as persons that share similar *cultural* characteristics. **Data Characteristics:** 1 Character Alpha. Must be entered for Victim Types I and L. Use U if Unknown, don't leave the field blank. ### Requirements: -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["29"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15058"] -%} -2 | {{error.err_desc["29"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["29"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15058"] -%} | | | | +| 2 | {{error.err_desc["29"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * If Victim is a person (that is, Individual ('I') or Law Enforcement Officer ('L')) is entered into Type of Victim (25), then his/her ethnic origin is to be indicated in Ethnicity of Victim (29).
### Allowed Entries: -___ +--- Enter only (1) code for each Victim Segment: @@ -3357,7 +3430,7 @@ Enter only (1) code for each Victim Segment: {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -3368,10 +3441,9 @@ Enter only (1) code for each Victim Segment: {% endif %} {% endfor %} - - + -___ +---
@@ -3385,24 +3457,25 @@ ___ ### Requirements: -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["30"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15058"] -%} -2 | {{error.err_desc["30"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["30"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15058"] -%} | | | | +| 2 | {{error.err_desc["30"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- + +### Details: -### Details: * If Type of Victim (25) is a person (that is, Individual ('I') or Law Enforcement Officer ('L'), then, whether he/she was a resident or nonresident, the Resident Status of Victim (30) is to be entered.) * A 'Resident' is a person who maintains his/her permanent home for legal purposes in the locality (i.e., town, city, or community) where the crime took place. -___ +--- ### Allowed Entries: -___ +--- Enter only (1) code for each Victim Segment: @@ -3422,7 +3495,7 @@ Enter only (1) code for each Victim Segment: {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -3433,10 +3506,9 @@ Enter only (1) code for each Victim Segment: {% endif %} {% endfor %} - - + -___ +---
@@ -3444,7 +3516,7 @@ ___ ## Aggravated Assault/Homicide Circumstance Nos. 1 and 2 (31) -___ +--- **Description:** Aggravated Assault/Homicide Circumstances is used to describe the circumstances of either an aggravated assault or a homicide. It's must be used with NIBRS 09A, 09B, 09C, and 13A, and should not be used with any other Offense (left Blank). Additionally the availablility of the codes DE 31 uses is subject the Victim Type (DE 25) and NIBRS Code of the Offense; not all codes are available for all conditions. @@ -3452,67 +3524,68 @@ ___ ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["31"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["12006"] -%} -2 | {{error.err_desc["31"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15019"] -%} -3 | {{error.err_desc["31"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15020"] -%} -4 | {{error.err_desc["31"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15056"] -%} -5 | {{error.err_desc["31"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15080"] -%} -6 | {{error.err_desc["31"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["90001"] -%} -7 | {{error.err_desc["31"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["90004"] -%} -8 | {{error.err_desc["31"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["31"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12006"] -%} | | | | +| 2 | {{error.err_desc["31"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15019"] -%} | | | | +| 3 | {{error.err_desc["31"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15020"] -%} | | | | +| 4 | {{error.err_desc["31"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15056"] -%} | | | | +| 5 | {{error.err_desc["31"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15080"] -%} | | | | +| 6 | {{error.err_desc["31"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90001"] -%} | | | | +| 7 | {{error.err_desc["31"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90004"] -%} | | | | +| 8 | {{error.err_desc["31"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +---
***Aggravated Assault and Non-Negligent Manslaughter Circumstances*** -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["90005"] -%} -9 | {{error.err_desc["31"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["90014"] -%} -10 | {{error.err_desc["31"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["90005"] -%} | | | | +| 9 | {{error.err_desc["31"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90014"] -%} | | | | +| 10 | {{error.err_desc["31"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +---
***Negligent Manslaughter Circumstances*** -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["22120"] -%} -11 | {{error.err_desc["31"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["22120"] -%} | | | | +| 11 | {{error.err_desc["31"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +---
***Justifiable Homicide Circumstances*** -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["12066"] -%} -12 | {{error.err_desc["31"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["12066"] -%} | | | | +| 12 | {{error.err_desc["31"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +---
### Details: + * DEFINITION: A Justifiable Homicide is the killing of a perpetrator of a serious criminal offense by a peace officer in the line of duty; or the killing, during the commission of a serious criminal offense, of the perpetrator by a private individual. * At MOST, TWO Assault Circumstances (31) are allowed. Beginning with LIBRS 2.5 Specifications, the third Assault Circumstance is ignored. *New Warning Message in LIBRS 2.5* * Aggravated Assault/Homicide Circumstances and Law Enforcement Officers Killed/Assaulted (InLine of Duty (31) describes the circumstances of either an Aggravated Assault or Homicide. @@ -3524,7 +3597,7 @@ ___ ### Allowed Entries: -___ +--- @@ -3542,7 +3615,7 @@ ___ {% for values in subsection.values %} - + @@ -3557,15 +3630,15 @@ ___
{{values.code}} -  -  {{values.desc}} {{values.comment}}
___ -### Examples: +### Examples: -___ +--- -Example Number | Description -:-------------:|:----------- -1 | Two rival juvenile street gangs rumble over 'turf' rights to sell drugs and one of the gang members is killed. Possible entries are: {::nomarkdown}{:/} While all three would apply, there is a *limit of two entries*. Therefore, the two most descriptive codes (as determined by the reporting agency) should be used. In this case, the reporting agency entered '03' and '05'. +| Example Number | Description | +| :------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | Two rival juvenile street gangs rumble over 'turf' rights to sell drugs and one of the gang members is killed. Possible entries are: {::nomarkdown}``{:/} While all three would apply, there is a *limit of two entries*. Therefore, the two most descriptive codes (as determined by the reporting agency) should be used. In this case, the reporting agency entered '03' and '05'. | -___ +---
@@ -3573,7 +3646,7 @@ ___ ## Additional Justifiable Homicide Circumstance (32) -___ +--- **Description:** Additional Justifiable Homicide Circumstances is used to describe the circumstances of a NIBRS 09C Offenses (Justifiable Homicide) only. It is not to be used with Victims of any Offense Code other than 09C. When more than one data value applies, enter the one that is most descriptive. @@ -3581,22 +3654,22 @@ ___ ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["32"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15055"] -%} -2 | {{error.err_desc["32"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15057"] -%} -3 | {{error.err_desc["32"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["32"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15055"] -%} | | | | +| 2 | {{error.err_desc["32"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15057"] -%} | | | | +| 3 | {{error.err_desc["32"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Allowed Entries for Justifiable Homicide: -___ +--- Enter only (1) code for Justifiable Homicide (NIBRS 09C): @@ -3616,7 +3689,7 @@ Enter only (1) code for Justifiable Homicide (NIBRS 09C): {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -3632,15 +3705,15 @@ ___
-### Examples: +### Examples: -___ +--- -Example Number | Description -:-------------:|:----------- -1 | In resisting arrest, a fugitive pulled a gun and fired two times in the direction of two police officers who were attempting to take him into custody. Neither officer was hit, but both drew their weapons and returned fire, killing the fugitive. As this was a Justifiable Homicide (NIBRS 09C), Criminal Killed by Police Officer ('21') should be entered into *Data Element 31*.

Assuming the facts above, the possible entries for *Data Element 32* are: {::nomarkdown}{:/}As only one code can be entered into this Data Element (32), the most descriptive code (as determined by the reporting agency) should be used. In this case, the reporting agency entered *Criminal Attached Police Officer and That Officer Killed Criminal('A')*. +| Example Number | Description | +| :------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | In resisting arrest, a fugitive pulled a gun and fired two times in the direction of two police officers who were attempting to take him into custody. Neither officer was hit, but both drew their weapons and returned fire, killing the fugitive. As this was a Justifiable Homicide (NIBRS 09C), Criminal Killed by Police Officer ('21') should be entered into*Data Element 31*.`

`Assuming the facts above, the possible entries for *Data Element 32* are: {::nomarkdown}``{:/}As only one code can be entered into this Data Element (32), the most descriptive code (as determined by the reporting agency) should be used. In this case, the reporting agency entered *Criminal Attached Police Officer and That Officer Killed Criminal('A')*. | -___ +---
@@ -3648,47 +3721,48 @@ ___ ## Type of Injury (33) -___ +--- -**Description:** Type of Injury is used to describe the condition of a Victims of a Crime Against Person after the Offense has been committed. Certain Injury Types are not applicable for certain NIBRS Codes. +**Description:** Type of Injury is used to describe the condition of a Victims of a Crime Against Person after the Offense has been committed. Certain Injury Types are not applicable for certain NIBRS Codes. **Data Characteristics:** 1 Character Alpha. Must be included for each Victim Injury Segment (Segment 51) that is present in the Incident, and cannot be left Blank. ### Requirements: -___ - -Requirment | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["33"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15019"] -%} -2 | {{error.err_desc["33"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15020"] -%} -3 | {{error.err_desc["33"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15079"] -%} -4 | {{error.err_desc["33"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["90029"] -%} -5 | {{error.err_desc["33"]}} | {{error.err_no}}| {{ error.err_message }} +--- +| Requirment | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["33"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15019"] -%} | | | | +| 2 | {{error.err_desc["33"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15020"] -%} | | | | +| 3 | {{error.err_desc["33"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15079"] -%} | | | | +| 4 | {{error.err_desc["33"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90029"] -%} | | | | +| 5 | {{error.err_desc["33"]}} | {{error.err_no}} | {{ error.err_message }} | ### Important Note: -13A, 13B, and 13C Offenses are all Mutually Exclusive to the same Victim in the same Incident. Meaning, LIBRS (and NIBRS, for that matter) will not allow you to submit a Victim who received Major Injuries from one Offender committing a 13A - Aggravated Assault Offenses, and Minor Injuries from another Offender committing a 13B - Simple Assault Offense. + +13A, 13B, and 13C Offenses are all Mutually Exclusive to the same Victim in the same Incident. Meaning, LIBRS (and NIBRS, for that matter) will not allow you to submit a Victim who received Major Injuries from one Offender committing a 13A - Aggravated Assault Offenses, and Minor Injuries from another Offender committing a 13B - Simple Assault Offense. If you have a case where a Victim applies to Mutually Exclusive Offenses, then you will need to submit those Offenses in Separate Incidents. You can see the chart here for [which Offenses are Mutually Exclusive](#offenses-that-cannot-occur-to-the-same-victim). -___ +--- ### Details: + * Notes: This Data Element (32) describes the type(s) of bodily injury suffered by a person. * Minor injury is described as an injury not requiring immediate medical attention. * Major injury is described as an injury requiring immediate medical attention. -___ +--- ### Allowed Entries: -___ +--- Enter only (1) code for each Victim Injury Segment; however, can submit as many Victim Injury Segments (51) as applicable: @@ -3708,7 +3782,7 @@ Enter only (1) code for each Victim Injury Segment; however, can submit as many {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -3728,94 +3802,96 @@ ___ ## Offender Number to be Related (34) -___ +--- **Description:** Offender Number to Be Related is only used in Segment 52, Victim/Offender Relationship, which should only be present with the Victim is associated with a Crime Against Person, or a Robbery. **Data Characteristics:** 3 Character Numeric. Should always be supplied in Segment 52 (when that segment is present). Value should be front-padded with Zeros (0) to make a three-digit number. EG: 1 would be 001. ### Requirements: -___ - -Requirment | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10070"] -%} -1 | {{error.err_desc["34"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15058"] -%} -2 | {{error.err_desc["34"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15059"] -%} -3 | {{error.err_desc["34"]}} | {{error.err_no}}| {{ error.err_message }} +--- +| Requirment | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10070"] -%} | | | | +| 1 | {{error.err_desc["34"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15058"] -%} | | | | +| 2 | {{error.err_desc["34"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15059"] -%} | | | | +| 3 | {{error.err_desc["34"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * If Offenders of Human Trafficking offenses (NIBRS Codes 64A, 64B and 40C) are *known*, then data value for Offender Number to be Related (Data Element 34) MUST be supplied as well. * If Offenders of Human Trafficking offenses (NIBRS Codes 64A, 64B and 40C) are *unknown*, then data value for Offender Number to be Related (Data Element 34) MUST be '000' (UNKNOWN) * Notes: Offender Number to be Related (34) along with Relationship of Victim to Offender (35) describe the relationship of each Victim to each Offender who has perpetrated a Crime Against Person or a Robbery against the Victim. If the Victim is related to the offender in more than one way, use the closest relationship. * Enter Offender Sequence Number (36) of the Offenders for whom Victim-to-Offender relationships are going to be reported in Relationship of Victim to Offender (35). * The Reporting Agency MUST report each Victim's relationship to EVERY Offender when the Offense is a Crime Against Person or a Robbery against the Victim. -___ +--- -### Examples: +### Examples: -___ +--- -Example Number | Description -:-------------:|:----------- -1 | If Victim 001's relationship to Offender 004 is to be reported, enter '004'. +| Example Number | Description | +| :------------: | :--------------------------------------------------------------------------- | +| 1 | If Victim 001's relationship to Offender 004 is to be reported, enter '004'. | -___ +---
-
## Relationship of Victim to Offender (35) -___ +--- **Description** Victim/Offender Relationship describes how the Victim and the Offender of an Offense are associated with one another, if at all. It is common for this Data Element to be used for statistics for Offenses like Domestic Violence. If should only be used when the Victim is associated with a Crime Against a Person. -**Data Characteristics:** 2 Character Alpha. Should only have a value if the Victim is associated with a Crime Against a Person. +**Data Characteristics:** 2 Character Alpha. Should only have a value if the Victim is associated with a Crime Against a Person. ### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["35"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["14050"] -%} -2 | {{error.err_desc["35"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["14053"] -%} -3 | {{error.err_desc["35"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["14054"] -%} -4 | {{error.err_desc["35"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15005"] -%} -5 | {{error.err_desc["35"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15020"] -%} -6 | {{error.err_desc["35"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15060"] -%} -7 | {{error.err_desc["35"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15068"] -%} -8 | {{error.err_desc["35"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15072"] -%} -9 | {{error.err_desc["35"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["15075"] -%} -10 | {{error.err_desc["35"]}} | {{error.err_no}}| {{ error.err_message }} +--- + +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["35"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["14050"] -%} | | | | +| 2 | {{error.err_desc["35"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["14053"] -%} | | | | +| 3 | {{error.err_desc["35"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["14054"] -%} | | | | +| 4 | {{error.err_desc["35"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15005"] -%} | | | | +| 5 | {{error.err_desc["35"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15020"] -%} | | | | +| 6 | {{error.err_desc["35"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15060"] -%} | | | | +| 7 | {{error.err_desc["35"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15068"] -%} | | | | +| 8 | {{error.err_desc["35"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15072"] -%} | | | | +| 9 | {{error.err_desc["35"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["15075"] -%} | | | | +| 10 | {{error.err_desc["35"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * Notes: If Offenders of Human Trafficking offenses (NIBRS Codes 64A, 64B and 40C) are *known*, then data value for Relationship of Victim to Offender (Data Element 34) MUST be supplied as well. * Relationship of Victim to Offender (35) is used ONLY with Offender Number to be Related (34), to report the relationship of a Victim to Offenders who have perpetrated a Crime Against Person, or a Robbery against the Victim. * Relationship of Victim to Offender (35) indicates the Victim's relationship with each Offender involved in the incident. * Relationship of Victim to Offender (35) is NOT required if Type of Victim (25) is equal to Society/Public ('S'). -___ + +--- ### List of Allowed Entries for DE 35 is on the following page: @@ -3823,7 +3899,7 @@ ___ ### Allowed Entries: -___ +--- MUST enter **ONE** code for each Victim Segment (50). MUST enter relationship of each Victim to each Offender when Offense is a *Crime Against Person* or a Robbery against a Victim: @@ -3843,7 +3919,7 @@ MUST enter **ONE** code for each Victim Segment (50). MUST enter relationship of {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -3858,29 +3934,26 @@ MUST enter **ONE** code for each Victim Segment (50). MUST enter relationship of
+### Examples: -### Examples: - -___ +--- -Example Number | Description -:-------------:|:----------- -1 | An employee assaulted his employer (a person) with his fists. Victim was Employer (ER) should be entered. -2 | Two unknown subjects rob a male and a female couple. Victim was Stranger ('ST') should be entered to indicate the relationship of each Victim to each Offender. +| Example Number | Description | +| :------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | An employee assaulted his employer (a person) with his fists. Victim was Employer (ER) should be entered. | +| 2 | Two unknown subjects rob a male and a female couple. Victim was Stranger ('ST') should be entered to indicate the relationship of each Victim to each Offender. | -___ +---
-
- ## Offender Sequence Number (36) -___ +--- -**Description:** Offender Sequence Number is the unique identifier for each Offender that is present in an Incident. Each Offender Segment (Segment 40) should have a unique value to identify them. Values for Offenders that aren't unknown should be between 001 and 999. If an Offender is unknown, then there should be a single Segment 40 with an Offender Sequence Number of '000'. +**Description:** Offender Sequence Number is the unique identifier for each Offender that is present in an Incident. Each Offender Segment (Segment 40) should have a unique value to identify them. Values for Offenders that aren't unknown should be between 001 and 999. If an Offender is unknown, then there should be a single Segment 40 with an Offender Sequence Number of '000'. An Unknown Offender Sequence Number '000' is different than an Unknown Age, Race, or Sex ('00' for Age, or 'U' for Race and Sex) of an Offender. Take the following examples: @@ -3890,47 +3963,48 @@ An Unknown Offender Sequence Number '000' is different than an Unknown Age, Race Case 1 would be a case where you use '000' for an Offender Sequence Number. When '000' is used as the Offender Sequence Number, it basically means "We have no idea who, or even how many people were involved in this crime". Because of that, there are two circumstances that should be accounted for with it: 1. If '000' is used as an Offender Sequence Number, then no other Offender Sequence Numbers can be entered. You either have an idea of how many people were invovled, or you don't. If you know something about any of the Offenders, or even just how many Offenders were involved, '000' should not be used. -2. '000' is not allowed for 09C Offenses because inherently you need to know who was involved in that Offense to deem it a Justifiable Homicide; if you don't know who was involved, then what evidence do you have that the homicide was justifiable? +2. '000' is not allowed for 09C Offenses because inherently you need to know who was involved in that Offense to deem it a Justifiable Homicide; if you don't know who was involved, then what evidence do you have that the homicide was justifiable? -Case 2 is a case where '000' Offender Sequence Number shouldn't be confused for not knowing anything about the *attributes* (Age, Sex, and Race) of the Offenders involved. In this case you may not be able to describe anything about the Offenders, but you have clear-cut evidence about the number of Offenders that were involved. Therefore you should use Offender Sequence Numbers other than '000' for them. +Case 2 is a case where '000' Offender Sequence Number shouldn't be confused for not knowing anything about the *attributes* (Age, Sex, and Race) of the Offenders involved. In this case you may not be able to describe anything about the Offenders, but you have clear-cut evidence about the number of Offenders that were involved. Therefore you should use Offender Sequence Numbers other than '000' for them. Just to note, you will get a Warning about those attributes being Unknown, but that's only there to warn the User in case that data was mistakenly forgotten, which is the most common occurance when all of those Data Elements are Unknown. -**Data Characteristics:** 3 Character Numeric. Should never be left blank and should be front-padded to make a three-digit number. EG: 1 would be 001. If unknown use '000' - If '000' is used then no other Offender Segments can be present. +**Data Characteristics:** 3 Character Numeric. Should never be left blank and should be front-padded to make a three-digit number. EG: 1 would be 001. If unknown use '000' - If '000' is used then no other Offender Segments can be present. ### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["36"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["12006"] -%} -2 | {{error.err_desc["36"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["14055"] -%} -4 | {{error.err_desc["36"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["14057"] -%} -5 | {{error.err_desc["36"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["14059"] -%} -6 | {{error.err_desc["36"]}} | {{error.err_no}}| {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["36"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12006"] -%} | | | | +| 2 | {{error.err_desc["36"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["14055"] -%} | | | | +| 4 | {{error.err_desc["36"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["14057"] -%} | | | | +| 5 | {{error.err_desc["36"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["14059"] -%} | | | | +| 6 | {{error.err_desc["36"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * Notes: Each Offender in an incident is assigned a UNIQUE Offender Sequence Number (36) from '001' to '999'. * If nothing is known about the Offender(s), enter '000' into this data element and LEAVE DATA ELEMENTS 37 THROUGH 39 BLANK (G). Also, Offender Suspected of Using (8) MUST be Not Applicable ('N') and Bias Motivation/Bias Crime Type (8A) MUST be None ('88'). +### Examples: -### Examples: -___ +--- -Example Number | Description -:-------------:|:----------- -1 | A corpse with five bullet holes in it was found in an abandoned warehouse. There were no witnesses to the crime, or suspects. {::nomarkdown}{:/} -2 | Two Offenders were seen fleeing the scene of a burglary, but because they were wearing ski masks, their Age, Sex, and Race could not be determined. {::nomarkdown}{:/} +| Example Number | Description | +| :------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| 1 | A corpse with five bullet holes in it was found in an abandoned warehouse. There were no witnesses to the crime, or suspects. {::nomarkdown}``{:/} | +| 2 | Two Offenders were seen fleeing the scene of a burglary, but because they were wearing ski masks, their Age, Sex, and Race could not be determined. {::nomarkdown}``{:/} | -___ +---
@@ -3938,35 +4012,37 @@ ___ ## Age of Offender [At Time of Incident] (37) -___ +--- -**Description:** Age of Offender is the age the Offender was on the Date of the Incident. Ages can be appended with an 'E' to represent an Estimated Age of the Offender if that actual Age is not known, otherwise the third character should remain a Blank Space. +**Description:** Age of Offender is the age the Offender was on the Date of the Incident. Ages can be appended with an 'E' to represent an Estimated Age of the Offender if that actual Age is not known, otherwise the third character should remain a Blank Space. **Data Characteristics:** 3 Digits Alpha/Numeric. Cannot be Blank and must always have a value. Use '00' if Age is Unknown. - ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["37"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["14008"] -%} -2 | {{error.err_desc["37"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["14009"] -%} -3 | {{error.err_desc["37"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["14022"] -%} -4 | {{error.err_desc["37"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["14052"] -%} -5 | {{error.err_desc["37"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["90045"] -%} -5 | {{error.err_desc["37"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["37"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["14008"] -%} | | | | +| 2 | {{error.err_desc["37"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["14009"] -%} | | | | +| 3 | {{error.err_desc["37"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["14022"] -%} | | | | +| 4 | {{error.err_desc["37"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["14052"] -%} | | | | +| 5 | {{error.err_desc["37"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90045"] -%} | | | | +| 5 | {{error.err_desc["37"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["22100"] -%} | | | | +| 6 | {{error.err_desc["37"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * Age of the Offender (37) is entered either as an exact number of years, an estimated age or as unknown. * If the Offender's Age is NOT KNOWN, estimate the Offender's Age and append an 'E' (Estimated). * If a range is given for the Offender's Age, enter the median (average) age of the range (rounded down). @@ -3974,7 +4050,7 @@ ___ ### Allowed Entries -___ +--- Enter only one code per Offender Segment (40): @@ -3994,7 +4070,7 @@ Enter only one code per Offender Segment (40): {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -4008,23 +4084,21 @@ Enter only one code per Offender Segment (40): ___ -### Examples: - +### Examples: -Example Number | Description -:-------------:|:----------- -1 | If the Victim, or a witness, reported the Offender's Age as between 25 and 30 years old, enter '27E' (the average of 25 and 30 is 27.5, round down to get an estimated age of 27). +| Example Number | Description | +| :------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | If the Victim, or a witness, reported the Offender's Age as between 25 and 30 years old, enter '27E' (the average of 25 and 30 is 27.5, round down to get an estimated age of 27). | -___ +---
-
## Date of Birth of Offender (L37) -___ +--- **Description:** DOB of Offender is not a required field, but if the Date of Birth is known then it can be entered here in the MMDDYYYY Format. If this field has a value, then you shouldn't be using an Estimated age in Data Element 37 (Age of Offender), however we don't stop that because it's possible the exact Incident Date is Unknown, and instead the Reporting Date is being used. For that reason we allow Estimated Ages to also have a Date of Birth present. @@ -4033,19 +4107,21 @@ ___ **Format:** MMDDYYYY ### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11005"] -%} -1 | {{error.err_desc["l37"]}} | {{error.err_no}}| {{ error.err_message }} +--- + +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["11005"] -%} | | | | +| 1 | {{error.err_desc["l37"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * If the Date of Birth of the Offender is known, it is to be indicated in this data element. -___ +---
@@ -4053,36 +4129,38 @@ ___ ## Sex of Offender (38) -___ +--- **Description:** The Sex of an Offender involved in the Incident. **Data Characteristics:** 1 Character Alpha. Must always have a value; use U if Unknown or Offender Sequence Number is '000', don’t leave the field blank. ### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["38"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11004"] -%} -2 | {{error.err_desc["38"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["14052"] -%} -3 | {{error.err_desc["38"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["14060"] -%} -3 | {{error.err_desc["38"]}} | {{error.err_no}}| {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["38"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11004"] -%} | | | | +| 2 | {{error.err_desc["38"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["14052"] -%} | | | | +| 3 | {{error.err_desc["38"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["14060"] -%} | | | | +| 3 | {{error.err_desc["38"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * This Data Element (38) indicates Sex of the Offender. -___ +--- ### Allowed Entries: -___ + +--- Enter only (1) code per Offender Segment (40): @@ -4102,7 +4180,7 @@ Enter only (1) code per Offender Segment (40): {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -4116,52 +4194,52 @@ Enter only (1) code per Offender Segment (40): ___ -### Examples: - -___ +### Examples: +--- -Example Number | Description -:-------------:|:----------- -1 | The witness caught only a fleeting glance of the Offender and, therefore, was unable to report the Offender's Sex. The entry should be Unknown ('U'). +| Example Number | Description | +| :------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | The witness caught only a fleeting glance of the Offender and, therefore, was unable to report the Offender's Sex. The entry should be Unknown ('U'). | -___ +---
-
- ## Race of Offender (39) -___ +--- **Description:** Race of Offender is used to indicate the race of an Offender involved in an Incident. Race is defined as persons that share similar physical characteristics. Ethinicity is defined as persons that share similar cultural characteristics. **Data Characteristics:** 1 Character Alpha. Must always have a value; use U if Unknown or Offender Sequence Number is '000', don’t leave the field blank. ### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["39"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11004"] -%} -2 | {{error.err_desc["39"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["14052"] -%} -3 | {{error.err_desc["39"]}} | {{error.err_no}}| {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["39"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11004"] -%} | | | | +| 2 | {{error.err_desc["39"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["14052"] -%} | | | | +| 3 | {{error.err_desc["39"]}} | {{error.err_no}} | {{ error.err_message }} | + +--- -___ ### Details: + * Race of an Offender is indicated in this Data Element (39). -___ +--- ### Allowed Entries: -___ + +--- Enter only (1) code per Offender Segment (40): @@ -4181,7 +4259,7 @@ Enter only (1) code per Offender Segment (40): {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -4199,7 +4277,7 @@ ___ ## Ethnicity of Offender (39A) -___ +--- **Description:** Ethnicity of Offender is used to indicate the ethnicity of an Offender involved in an Incident. Race is defined as persons that share similar physical characteristics. Ethinicity is defined as persons that share similar cultural characteristics. @@ -4207,24 +4285,24 @@ ___ ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["39A"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["39A"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: * This Data Element indicates the ethnic origin of the Arrestee. -___ +--- ### Allowed Entries -___ +--- Enter only (1) code per Offense Segment (40): @@ -4244,7 +4322,7 @@ Enter only (1) code per Offense Segment (40): {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -4262,44 +4340,46 @@ ___ ## Arrestee Sequence Number (40) -___ +--- **Description:** The Arrestee Sequence Number is a Uniquely Identifying Value between 001 and 999 that is used throughout the LIBRS Data Segments to identify which particular Arrestee is being referenced for validation purposes. Each Arrestee Segment (Segment 60) in an Incident should contain a unique Sequence Number. There is no Unknown Value for this Sequence Number like there is for Offender Sequence Number. -**Data Characteristics:** 3 Character Numeric. Must be front-padded with Zeros to make a three-digit number. EG: 1 would be 001. +**Data Characteristics:** 3 Character Numeric. Must be front-padded with Zeros to make a three-digit number. EG: 1 would be 001. ### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["16061"] -%} -1 | {{error.err_desc["40"]}} | {{error.err_no}} | {{ error.err_message }} +--- -___ +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["16061"] -%} | | | | +| 1 | {{error.err_desc["40"]}} | {{error.err_no}} | {{ error.err_message }} | + +--- ### Details: + * Each Arrestee reported is assigned a UNIQUE Sequence Number from '001' to '999'. -___ +--- ### Examples: -___ -Example Number | Description -:-------------:|:----------- -1 | If two persons were arrested in connection with a previously submitted incident, two Arrestee Segments should be submitted: one with Arrestee Sequence Number '001' and the other with '002'. +--- -_____ +| Example Number | Description | +| :------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | If two persons were arrested in connection with a previously submitted incident, two Arrestee Segments should be submitted: one with Arrestee Sequence Number '001' and the other with '002'. | -
+--- +
## Arrestee Name (L40) -___ +--- **Description:** Arrestee Name is the name of the individual being Arrested in connection with one of the Offenses present in the Incident. This field is purely optional, we do literally no validation on it and it doesn't go to the FBI for NIBRS Reporting. @@ -4311,113 +4391,116 @@ Suffix includes standard suffixes used to distinguish between generations (for e ### Requirements: -___ +--- None -___ +--- ### Details: + * If Arrestee's full name will not fit in the field, then enter as much as possible. DO NOT put periods behind suffix abbreviations or middle initial. -___ +---
## Arrest Number/Local Booking Number for Arrest (41) -___ +--- -**Description:** Arrest Number/Local Booking Number for Arrest is the unique identifier that the Agency has for the particular Arrest Record in their RMS. This is actually quite an important Data Element, as when we submit changes to NIBRS to arrests this is the value that is used to make modifications. +**Description:** Arrest Number/Local Booking Number for Arrest is the unique identifier that the Agency has for the particular Arrest Record in their RMS. This is actually quite an important Data Element, as when we submit changes to NIBRS to arrests this is the value that is used to make modifications. **Data Characteristics:** 12 Character Alpha. Cannot be completely blank, and must be unique for every Arrestee across all Incidents (IE: Number cannot be the same in two different Incidents). Cannot contain spaces *in between* any of the characters in this data element, but leading or trailing spaces are fine. ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["12006"] -%} -1 | {{error.err_desc["41"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["16015"] -%} -2 | {{error.err_desc["41"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["12006"] -%} | | | | +| 1 | {{error.err_desc["41"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["16015"] -%} | | | | +| 2 | {{error.err_desc["41"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * This Data Element (41) is a UNIQUE, IDENTIFYING number assigned by an agency to an Arrest Report. It may be the Incident Number of a reported incident relating to the Arrest, or it may be a separate Booking Number. -___ +---
-
## Arrest Date (42) -___ +--- **Description:** Arrest Date is the actual date that an Arrestee was brought into the LEA's custody. Since Incident Dates and Arrest Dates can be different, if there is a case where an Arrest is made for an Incident that occurred before the Agency's Base Date (Date where the agency began reporting either LIBRS or UCR data to the State), then the Arrest should not be sent to us. -**Data Characteristics:** 8 Character Date. Must be included and cannot be Blank or all Zeros. +**Data Characteristics:** 8 Character Date. Must be included and cannot be Blank or all Zeros. **Format:** MMDDYYYY ### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11005"] -%} -1 | {{error.err_desc["42"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["16065"] -%} -2 | {{error.err_desc["42"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["16066"] -%} -3 | {{error.err_desc["42"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["16082"] -%} -4 | {{error.err_desc["42"]}} | {{error.err_no}}| {{ error.err_message }} +--- -___ +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11005"] -%} | | | | +| 1 | {{error.err_desc["42"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["16065"] -%} | | | | +| 2 | {{error.err_desc["42"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["16066"] -%} | | | | +| 3 | {{error.err_desc["42"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["16082"] -%} | | | | +| 4 | {{error.err_desc["42"]}} | {{error.err_no}} | {{ error.err_message }} | + +--- ### Details: + * Arrest Date (42) is used to enter the month, day and year when the actual arrest took place. -___ +---
- ## Type of Arrest (43) -___ +--- -**Description:** Type of Arrest details how the arrest was initiated by the Officer, and if the individual was brought into custody or not. +**Description:** Type of Arrest details how the arrest was initiated by the Officer, and if the individual was brought into custody or not. **Data Characteristics**: 1 Character Alpha. This field is required for each Segment 60 present in the Incident. ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["43"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["43"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * Type of Arrest (43) indicates the type of apprehension. -___ +--- ### Allowed Entries: -___ +--- -Enter only one code per Arrest Segment: +Enter only ``one code per Arrest Segment: @@ -4435,7 +4518,7 @@ Enter only one code per Arrest S {% for values in subsection.values %} - + {% endfor %} @@ -4455,34 +4538,37 @@ ___ ## Multiple Arrestee Segment Indicator (44) -___ +--- -**Description:** The Multiple Arrestee Indicator is used to Identify if arresting an Offender for One Incident has cleared another Incident by arrest. In cases where an individual that is arrested is a suspect in more than one Incident, the Multiple Arrestee Indicator allows the agency to denote that one or more Incidents involving the Offender have been cleared by an Arrest, however the individual was not arrested multiple times. +**Description:** The Multiple Arrestee Indicator is used to Identify if arresting an Offender for One Incident has cleared another Incident by arrest. In cases where an individual that is arrested is a suspect in more than one Incident, the Multiple Arrestee Indicator allows the agency to denote that one or more Incidents involving the Offender have been cleared by an Arrest, however the individual was not arrested multiple times. For instance, if an Suspect already has a warrant out for their arrest, and they are then arrested for another Offense in a different Incident, the Incident that caused the warrant to be issued is now cleared by arrest, as well. However, the Suspect was only arrested one time. So the Multiple Arrestee Indicator allows the Agency to specify that both incidents have been cleared, but only one arrest was made. **Data Characteristics:** 1 Character Alpha. Required for Each Segment 60 (Arrest Segment) that is present in the Incident. ### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["44"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11004"] -%} -2 | {{error.err_desc["44"]}} | {{error.err_no}}| {{ error.err_message }} +--- -___ +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["44"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11004"] -%} | | | | +| 2 | {{error.err_desc["44"]}} | {{error.err_no}} | {{ error.err_message }} | + +--- ### Details: -* Multiple Arrestee Segment Indicator (44) ensures that an Arrestee is counted (scored) only once when the Arrestee's apprehension causes the Arresting Agency to submit two or more Arrestee Segments (60) concerning separate Incident Reports. That is, the Arrestee was involved in more than one crime incident and his/her arrest data are duplicated in each Incident Report.` - * In such a situation, Count Arrestee ("C") is to be entered into one of the Arrestee Segments (60), and Multiple (M) is to be entered into all of the remaining Arrestee Segments (60). + +* Multiple Arrestee Segment Indicator (44) ensures that an Arrestee is counted (scored) only once when the Arrestee's apprehension causes the Arresting Agency to submit two or more Arrestee Segments (60) concerning separate Incident Reports. That is, the Arrestee was involved in more than one crime incident and his/her arrest data are duplicated in each Incident Report.` + * In such a situation, Count Arrestee ("C") is to be entered into one of the Arrestee Segments (60), and Multiple (M) is to be entered into all of the remaining Arrestee Segments (60). * If the Arrestee's apprehension DOES NOT cause the Arresting Agency to submit multiple Arrestee Segments (60), enter Not Applicable ("N"). * Count Arrestee ("C") and Multiple ("M") codes are to be used in this Data Element (44) ONLYwhen the same agency submits two or more Arrestee Segments (for different incidents) relating to the same Arrestee. ### Allowed Entries: -___ + +--- Enter only one (1) code per Arrestee Segment: @@ -4502,7 +4588,7 @@ Enter only one (1) code per Arrestee Segment: {% for values in subsection.values %} - + {% endfor %} @@ -4518,15 +4604,14 @@ ___
-### Examples: - -___ +### Examples: +--- -Example Number | Description -:-------------:|:----------- -1 | After a suspect's apprehension for robbery, it was learned that he was also responsible for five additional robberies within the jurisdiction.{::nomarkdown}{:/} -2 | If the suspect's arrest did not clear additional incidents, the entry should be Not Applicable ("N"). +| Example Number | Description | +| :------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| 1 | After a suspect's apprehension for robbery, it was learned that he was also responsible for five additional robberies within the jurisdiction.{::nomarkdown}``{:/} | +| 2 | If the suspect's arrest did not clear additional incidents, the entry should be Not Applicable ("N"). |
@@ -4534,55 +4619,57 @@ Example Number | Description ## Louisiana Revised Statute Number of Arrest (45) -___ +--- -**Description:** The LRS Number of Arrest is the Statute in which the Offender was Arrested For. It needs to match one of the Statutes that are present in the Offense Segments (Segment 20). NIBRS Doesn't have this restriction, and allows you to submit an Arrest for an Offense not related to the Incident, but LIBRS does not have this leniency. +**Description:** The LRS Number of Arrest is the Statute in which the Offender was Arrested For. It needs to match one of the Statutes that are present in the Offense Segments (Segment 20). NIBRS Doesn't have this restriction, and allows you to submit an Arrest for an Offense not related to the Incident, but LIBRS does not have this leniency. **Data Characteristics:** 12 Character Alpha. Cannot be left blank and can only contain one (1) Hyphen (-). **Format**: TT:SSSS.S/P-I -||Louisiana Revised Statute Format -:--------------------------------:|----------------------------------- -TT | Title -SSSS.S | Section -**PPP/I** | Subpart, **or**
Subpart with Qualifier, **or**
Qualifier, **or**
Juvenile Qualifier, **and** An Inchoate Modifier, if applicable, would be indicated
by a dash with a data value behind the LRS Code that defines the offense.** | +| | Louisiana Revised Statute Format | +| :-------------: | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| TT | Title | +| SSSS.S | Section | +| **PPP/I** | Subpart,**or**`
`Subpart with Qualifier, **or**`
`Qualifier, **or**`
`Juvenile Qualifier, **and** An Inchoate Modifier, if applicable, would be indicated`
`by a dash with a data value behind the LRS Code that defines the offense.** |
### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["45"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["16069"] -%} -2 | {{error.err_desc["45"]}} | {{error.err_no}} | {{ error.err_message }} +--- + +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["45"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["16069"] -%} | | | | +| 2 | {{error.err_desc["45"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * This Data Element records the Louisiana Revised Statute that the Arrestee was charged with. * The structure of a Louisiana Revised Statute (LRS) is: Title (TT), followed by a colon, then a Section Number (SSSS.S), followed by optional Subparts, Qualifiers and Modifiers. Section and Subpart/Subpart with Qualifier/Qualifier/Juvenile Qualifier/Inchoate Modifier, should NOT be preceded by spaces or zeroes. * If there are no places after the decimal, then both the place after the decimal and the decimal point should be omitted. - * For example, the LRS for Murder is 14:30 – two spaces for the Title (14), a colon, two spaces for the Section (30) before the decimal, not four spaces - 14:GG30 - and dropping the space after the decimal. + * For example, the LRS for Murder is 14:30 – two spaces for the Title (14), a colon, two spaces for the Section (30) before the decimal, not four spaces - 14:GG30 - and dropping the space after the decimal. * The field should be LEFT JUSTIFIED WITH NO INCLUDED SPACES. Spaces are interpreted as the End-of-Data in this data element. * Subparts, Qualifiers, etc. are sometimes included for more specificity regarding those LRS codes requiring these identifiers. These parts of the field can be expanded or contracted as necessary to fill in the data. * All local ordinances must be reported with the appropriate state statute as the base offense, with any Subparts, Qualifiers, etc. added when applicable. * When a parish statute does not correspond to a state LRS, the parish statute must be reported with a "P:" for the title and the parish statute following the colon. - * If a city ordinance does not correspond to a state LRS, it must be reported by the police department with a "C:" substituted for the title portion of the data field, and the city ordinance following the colon. + * If a city ordinance does not correspond to a state LRS, it must be reported by the police department with a "C:" substituted for the title portion of the data field, and the city ordinance following the colon. * When it is a Sheriff's Office, or any other law enforcement agency who has jurisdiction in more than one city, reporting the city ordinance, it should be reported with a "C#:" substituted for the title portion of the data field, and the city ordinance following the colon, where the "#" is replaced with a unique number for each city as decided by the agency and agreed upon by the state. -___ +---
## Agency Supplied NIBRS Code For Arrest (N45) -___ +--- -**Description:** The Agency Supplied NIBRS Code For Arrest is the NIBRS Code with which the Agency would like to submit to the FBI as the Offense for the Arrest. +**Description:** The Agency Supplied NIBRS Code For Arrest is the NIBRS Code with which the Agency would like to submit to the FBI as the Offense for the Arrest. This Data Element was created before NIBRS Codes were mandatory, and we've since written code to use the NIBRS Code that's supplied in the Offense Segment if it's missing. However we would encourage you to include it as an extra measure to make certain the Arrest is being reported as desired. @@ -4590,15 +4677,14 @@ This Data Element was created before NIBRS Codes were mandatory, and we've since ### Requirements: -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["90017"] -%} -1 | {{error.err_desc["n45"]}} | {{error.err_no}}| {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["90017"] -%} | | | | +| 1 | {{error.err_desc["n45"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +---
@@ -4606,7 +4692,7 @@ ___ ## Arrest Connection to Offense (L45) -___ +--- **Description:** Arrest Connected to Offense is how an Arrestee gets linked to the Offense they were arrested for. It isn't just the Sequence Number. This Data Element allows you to link an Offense from Other Incidents, as well, to the Arrest performed in this one. Because of that the Incident Number in which the Offense was reported also needs to be included. @@ -4616,21 +4702,22 @@ The format is simply the Offense Sequence Number (DE ) followed by the Incident ### Requirements: -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["l45"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["90043"] -%} -2 | {{error.err_desc["l45"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["l45"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90043"] -%} | | | | +| 2 | {{error.err_desc["l45"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- **MUST be a valid Offense Sequence Number (L6). The Offense Segment (20) referred to by this Data Element (L45) MUST exist.** -___ +--- ### Details: -* Arrest Connection to Offense (L45) relates an Arrest with the Offense giving rise to the Arrest. Indirectly, it also relates an Offender to his Victim. All Offenses should be included if a charge was added for the particular Offense, even those from different previous incidents. + +* Arrest Connection to Offense (L45) relates an Arrest with the Offense giving rise to the Arrest. Indirectly, it also relates an Offender to his Victim. All Offenses should be included if a charge was added for the particular Offense, even those from different previous incidents. * The first three characters are the Offense Sequence Number (L6) of the Offense (6). * The next twelve characters are the Incident Number (2) of the Offense. * If Multiple Arrestee Segment Indicator (44) is anything except Not Applicable ("N") then this field will be connecting an Arrest to Offenses in two or more separate incidents. @@ -4638,7 +4725,7 @@ ___ * The combined Offense Sequence Number (L6) and the Incident Number (2) add together to give a unique identifier (15 characters) indicating which Offense gave rise to the Arrest. * The Incident Number (2) can be omitted if Multiple Arrestee Segment Indicator (44) is Not Applicable ("N"), because all Offenses will be in the same incident. And therefore, the Incident Number (2) can be assumed to be that of the incident with which the Arrestee Segment (60) was submitted. -___ +---
@@ -4646,39 +4733,39 @@ ___ ## Arrestee was Armed With [At Time of Arrest] (46) -___ +--- -**Description:** Arrestee was Armed With is used to report what, if anything, an Arrestee had on their person that was a Weapon whenever they were brought into custody. This Data Element is not as descriptive as Weapon/Type of Force Used (DE 13), but that's because it's limited to items that the Arrestee was *in possession of*. +**Description:** Arrestee was Armed With is used to report what, if anything, an Arrestee had on their person that was a Weapon whenever they were brought into custody. This Data Element is not as descriptive as Weapon/Type of Force Used (DE 13), but that's because it's limited to items that the Arrestee was *in possession of*. -***Please Note:*** Only one of each weapon type is currently reportable for each Arrestee. For instance, if an Arrestee had two Handguns on them at the time of Arrest, you should only list it once. Listing it twice will cause an error for Duplicate Values to be thrown. In the future we plan to add the ability to list the quantity of weapons found on the Arrestee, but at this time we can only allow a single one of each type to be reported. +***Please Note:*** Only one of each weapon type is currently reportable for each Arrestee. For instance, if an Arrestee had two Handguns on them at the time of Arrest, you should only list it once. Listing it twice will cause an error for Duplicate Values to be thrown. In the future we plan to add the ability to list the quantity of weapons found on the Arrestee, but at this time we can only allow a single one of each type to be reported. -**Data Characteristics:** 3 Character Alpha. Can't be blank, must have a selection. Third Character is reserved for the 'A - Automatic' designation, which is only to be used with Firearms. Otherwise, the third character is to be a Blank Space (G). +**Data Characteristics:** 3 Character Alpha. Can't be blank, must have a selection. Third Character is reserved for the 'A - Automatic' designation, which is only to be used with Firearms. Otherwise, the third character is to be a Blank Space (G). ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["46"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11004"] -%} -2 | {{error.err_desc["46"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["12058"] -%} -3 | {{error.err_desc["46"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["46"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11004"] -%} | | | | +| 2 | {{error.err_desc["46"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["12058"] -%} | | | | +| 3 | {{error.err_desc["46"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * If the Arrestee was in possession of a toy or play weapon this would be reported as being Unarmed ("01"). * Arrestee was Armed With (46) indicates if the Arrestee was armed with a commonly known weapon at the time of his/her apprehension. * If the weapon was an "automatic" firearm, an Automatic ('A') designation is added as a suffix code, (for example, Rifle Automatic ('13A'). * An "Automatic Firearm" is defined as any firearm that shoots, or is designed to shoot, more than one shot at a time by a single pull of the trigger without manual reloading. - ### Allowed Entries: -___ +--- Enter only one of the following codes: @@ -4698,7 +4785,7 @@ Enter only one of the following codes: {% for values in subsection.values %} - + {% endfor %} @@ -4714,17 +4801,16 @@ ___
-### Examples: - -___ +### Examples: +--- -Example Number | Description -:-------------:|:----------- -1 | When a man was arrested, he had in his possession a .357-Magnum handgun and a penknife. The entry should be Handgun ('12'). Because a small pocket knife is not generally considered to be a 'weapon', it does not qualify for reporting to LIBRS. -2 | A female resisted arrest using a liquor bottle and a chair as a weapon before being subdued. The entry for LIBRS should be Unarmed ('01'). Although the subject used items as weapons, they were not commonly known weapons. +| Example Number | Description | +| :------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | When a man was arrested, he had in his possession a .357-Magnum handgun and a penknife. The entry should be Handgun ('12'). Because a small pocket knife is not generally considered to be a 'weapon', it does not qualify for reporting to LIBRS. | +| 2 | A female resisted arrest using a liquor bottle and a chair as a weapon before being subdued. The entry for LIBRS should be Unarmed ('01'). Although the subject used items as weapons, they were not commonly known weapons. | -___ +---
@@ -4732,35 +4818,35 @@ ___ ## Age of Arrestee [At Time of Arrest] (47) -___ +--- -**Description:** Age of Arrestee is the age the Arrestee was on the Date of their Arrest. Ages can be appended with an 'E' to represent an Estimated Age of the Arrestee if that actual Age is not known, otherwise the third character should remain a Blank Space. +**Description:** Age of Arrestee is the age the Arrestee was on the Date of their Arrest. Ages can be appended with an 'E' to represent an Estimated Age of the Arrestee if that actual Age is not known, otherwise the third character should remain a Blank Space. **Data Characteristics:** 3 Digits Alpha/Numeric. Cannot be Blank and must always have a value. Use '00' if Age is Unknown. - ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["47"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["14008"] -%} -2 | {{error.err_desc["47"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["14009"] -%} -3 | {{error.err_desc["47"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["14022"] -%} -4 | {{error.err_desc["47"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["16064"] -%} -5 | {{error.err_desc["47"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["22100"] -%} -6 | {{error.err_desc["47"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["47"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["14008"] -%} | | | | +| 2 | {{error.err_desc["47"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["14009"] -%} | | | | +| 3 | {{error.err_desc["47"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["14022"] -%} | | | | +| 4 | {{error.err_desc["47"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["16064"] -%} | | | | +| 5 | {{error.err_desc["47"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["22100"] -%} | | | | +| 6 | {{error.err_desc["47"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * Age of the Arrestee (47) can be entered either as an exact number of years, an estimated age, or as unknown. * Note: Age at time of Arrest. * Note: (00) Unknown CANNOT have 'E' with this data value @@ -4768,9 +4854,9 @@ ___ ### Allowed Entries -___ +--- -Enter only one code per Arrest Segment (60): +Enter only ``one code per Arrest Segment (60):
{{values.code}} -  -  {{values.desc}}
{{values.code}} -  -  {{values.desc}}
{{values.code}} -  -  {{values.desc}}
@@ -4788,7 +4874,7 @@ Enter only one code per Arrest S {% for values in subsection.values %} - + {% endfor %} @@ -4802,13 +4888,13 @@ Enter only one code per Arrest S
{{values.code}} -  -  {{values.desc}}
___ -### Examples: +### Examples: -___ +--- -Example Number | Description -:-------------:|:----------- -1 | An Arrestee refused to give his Date of Birth, but he appeared to be 35 to 40 years old. Possible entries would be Unknown ('00') or an estimated 37 years old ('37E'). Use the latter when possible. +| Example Number | Description | +| :------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | An Arrestee refused to give his Date of Birth, but he appeared to be 35 to 40 years old. Possible entries would be Unknown ('00') or an estimated 37 years old ('37E'). Use the latter when possible. |
@@ -4816,7 +4902,7 @@ Example Number | Description ## Date of Birth of Arrestee (L47) -___ +--- **Description:** DOB of Arrestee is not a required field, but if the Date of Birth is known then it can be entered here in the MMDDYYYY Format. If this field has a value, then it's required that the Age of Arrestee have an Exact, not Estimated Value. @@ -4826,22 +4912,22 @@ ___ ### Requirements: -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11005"] -%} -1 | {{error.err_desc["l47"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["22105"] -%} -2 | {{error.err_desc["l47"]}} | {{error.err_no}}| {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["11005"] -%} | | | | +| 1 | {{error.err_desc["l47"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["22105"] -%} | | | | +| 2 | {{error.err_desc["l47"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * If Date of Birth of the Arrestee is Known, it should be entered into this Data Element. -___ +---
@@ -4849,7 +4935,7 @@ ___ ## Sex of Arrestee (48) -___ +--- **Description:** The Sex of the Arrestee. @@ -4857,25 +4943,26 @@ ___ ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["48"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11004"] -%} -2 | {{error.err_desc["48"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["48"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11004"] -%} | | | | +| 2 | {{error.err_desc["48"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * This Data Element (48) indicates the sex of the Arrestee. -___ +--- ### Allowed Entries -___ +--- Enter only (1) code per Arrest Segment: @@ -4895,7 +4982,7 @@ Enter only (1) code per Arrest Segment: {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -4913,34 +5000,34 @@ ___ ## Race of Arrestee (49) -___ +--- **Description:** Race of Arrestee is used to indicate the race of the Arrestee. Race is defined as persons that share similar physical characteristics. Ethinicity is defined as persons that share similar cultural characteristics. **Data Characteristics:** 1 Character Alpha. Must always have a value; use U if Unknown, don’t leave the field blank. - ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10001"] -%} -1 | {{error.err_desc["49"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["11004"] -%} -2 | {{error.err_desc["49"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10001"] -%} | | | | +| 1 | {{error.err_desc["49"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["11004"] -%} | | | | +| 2 | {{error.err_desc["49"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * Notes: Race of Arrestee (49) is indicated by this Data Element. -___ +--- ### Allowed Entries -___ +--- Enter only (1) code per Arrest Segment (60): @@ -4960,7 +5047,7 @@ Enter only (1) code per Arrest Segment (60): {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -4980,7 +5067,7 @@ ___ ## Ethnicity of Arrestee (50) -___ +--- **Description:** Ethnicity of Arrestee is used to indicate the Ethnicity of the Arrestee. Race is defined as persons that share similar physical characteristics. Ethinicity is defined as persons that share similar cultural characteristics. @@ -4988,23 +5075,24 @@ ___ ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["50"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["50"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * This Data Element indicates the ethnic origin of the Arrestee. -___ +--- ### Allowed Entries -___ +--- Enter only (1) code per Arrest Segment (60): @@ -5024,7 +5112,7 @@ Enter only (1) code per Arrest Segment (60): {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -5042,33 +5130,33 @@ ___ ## Resident Status of Arrestee (51) -___ +--- **Description:** Resident Status of Arrestee is used to indicate whether or not the Arrestee is a resident of the justidiction of the Arresting Agency. It is not meant to indicate whether or not the Arrestee is a US Citizen or Permanent Resident. **Data Characteristics:** 1 Character Alpha. Optional Value, but if supplied must conform to the List of Available Values. - ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["51"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["51"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * The Arrestee's Residency Status, whether Resident ('R') or Nonresident ('N'), is entered into this Data Element. * A 'Resident' is a person who maintains his/her permanent home for legal purposes in the locality (i.e., town, city, or community) where the crime took place. -___ +--- ### Allowed Entries -___ +--- Enter only (1) code per Arrest Segment (60): @@ -5088,7 +5176,7 @@ Enter only (1) code per Arrest Segment (60): {% for values in subsection.values %} {{values.code}} -  -  +  -  {{values.desc}} {% endfor %} @@ -5108,38 +5196,46 @@ ___ ## Disposition of Arrestee Under 18 (52) -___ +--- -**Description:** Disposition of Arrestee Under 18 denotes how Juvenile Arrestees are handled. It is a mandatory field for ANY Arrestee that is 17 AND Younger (Under 18, not including 18). +**Description:** Disposition of Arrestee Under 18 is a mandatory field for ANY Arrestee that is 17 AND Younger (Under 18, not including 18). -**Data Characteristics:** 1 Character Alpha. Required for Arrestees 17 and Younger. Should be left Blank for Arrestees that are not. +**Data Characteristics:** 1 Character Alpha. Required for Arrestees 17 and Younger. Should be left Blank for Arrestees that are 18 and older. ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["52"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["16052"] -%} -2 | {{error.err_desc["52"]}} | {{error.err_no}}| {{ error.err_message }} -{% assign error = site.data.error["16053"] -%} -3 | {{error.err_desc["52"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["52"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["16052"] -%} | | | | +| 2 | {{error.err_desc["52"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["16053"] -%} | | | | +| 3 | {{error.err_desc["52"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: -* Disposition of Arrestee Under 18 (52) is to be used ONLY if the Arrestee was 16 years of age or younger at the time of arrest. -* This will change to Arrestee under 18 on 01/01/2020 -___ +**Disposition of Arrestee Under 18** is a mandatory field for ANY Arrestee that is 17 years of age and younger. The Federal UCR program considers juveniles as under 18 years of age regardless of state law. The LIBRS program will stay aligned with the FBI and collect this field for arrestees 17 and younger. The Louisiana Juvenile Age definition has changed over the years to the following: + +- Prior to March 1, 2019, the Juvenile age is 16 and younger. + +- March 1, 2019 – April 18, 2024, the juvenile age is 17 and younger. + +- After April 19, 2024, the Juvenile age is 16 and younger + +After April 9, 2024 LIBRS will expect the 17 years old arrestees to have this data element and will reject the incident if this field is not provided.. + +--- ### Allowed Entries -___ +--- -Enter only (1) code per Arrest Segment (60) for Juveniles only: +Enter only (1) code per Arrest Segment (60): @@ -5157,7 +5253,7 @@ Enter only (1) code per Arrest Segment (60) for Juveniles only: {% for values in subsection.values %} - + {% endfor %} @@ -5171,15 +5267,14 @@ Enter only (1) code per Arrest Segment (60) for Juveniles only:
{{values.code}} -  -  {{values.desc}}
___ -### Examples: - -___ +### Examples: +--- -Example Number | Description -:-------------:|:----------- -1 | The Arrestee, age 13, was apprehended for vandalizing a school, then released to his parents with a warning. The entry should be Handled Within the Department and Released ('D'). -2 | The Arrestee, age 16, was arrested for rape, and turned over to the Adult Court to be tried as an adult. The entry would be Referred to Criminal or Adult Court ('A'). +| Example Number | Description | +| :------------: | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1 | The Arrestee, age 13, was apprehended for vandalizing a school, then released to his parents with a warning. The entry should be Handled Within the Department and Released ('D'). | +| 2 | The Arrestee, age 16, was arrested for rape, and turned over to the Adult Court to be tried as an adult. The entry would be Referred to Criminal or Adult Court ('A'). |
@@ -5187,11 +5282,11 @@ Example Number | Description ## Location of Incident (Geographical Coordinates) (L53) -___ +--- **Description:** Location of Incident is a purely Optional field that contains the Longitude and LAtitude of and Incident's Location. It is used for more advanced Analytics purposes, but at this time is not required and can be left blank. -**Data Characteristics:** 12 Character Numeric. +**Data Characteristics:** 12 Character Numeric. **Format:** DDMMSSDDMMSS @@ -5212,88 +5307,92 @@ ___ {:/} -____ +--- ### Requirements: + None. Value is taken on faith; we have no way to validate it. -___ +--- ### Details: + * Location of Incident (52) reports the geographical location of the incident. This field is not required and should be left blank if the agency does not track incidents with the use of geographical coordinates. * Optional: This field is not validated nor submitted to the FBI. -___ +--- ### Allowed Entries -___ +--- Not required for LIBRS Releases 1.0/1.1. or 2.0, unless agency uses geographical coordinates to track incidents. Entry should either be valid geographical coordinates, or Blank (G). If agencies submit zeroes, program will produce errors because zeroes are numeric. -___ +---
## Station/Division/Precinct Identifier (L54) -___ +--- + +**Description:** Station/Division/Precinct Identifier is a short code to identify which Precinct the Incident Report is coming from. It is not required, but may be useful for Analytics for the Agency down the line. At this time it is not being valudated or used, only stored. -**Description:** Station/Division/Precinct Identifier is a short code to identify which Precinct the Incident Report is coming from. It is not required, but may be useful for Analytics for the Agency down the line. At this time it is not being valudated or used, only stored. +**Data Characteristics:** 6 Character Alpha. Optional with no restrictions on Alpha/Numeric Characters, Spaces, or Hyphens. -**Data Characteristics:** 6 Character Alpha. Optional with no restrictions on Alpha/Numeric Characters, Spaces, or Hyphens. +### Requirements: -### Requirements: None. Value is taken on faith; we have no way to validate it. It can be used for an Agency to perform Analytics on their Incident reports, though, so if it's included it's recommended to be consistent for each Precinct. -___ +--- ### Details: + * This field is optional and is for the reporting agency's use in locating incidents. -___ +---
## Arrest Transaction Number (ATN) for Louisiana (L55) -___ +--- **Description:** ATN for Louisiana is the Unique Identifier of an Arrestee in AIFIS. **Data Characteristics:** 15 Character Alpha/Numeric -### Requirements: +### Requirements: MUST be present if fingerprints are submitted to the Bureau of Identification of the Louisiana State Police. -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["l55"]}} | {{error.err_no}}| {{ error.err_message }} - +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["l55"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * Arrest Transaction Number (L55) is generated by the live scan when fingerprinting an Arrestee or is a pre-assigned number generated and assigned at the time of the fingerprinting. This ATN number is defined as: - * Characters 1-4 4th, 5th, 6th, and 7th characters of the ORI number of the agency that made the arrest, or where the live scan device is housed. - * Character 5 live scan device number assigned to the device being used to generate this Arrestee's fingerprints. - * Characters 6-7 indicates the year this Arrestee's fingerprints are being scanned into this device. - * Characters 8-12 Arrest Sequence Number for this arrest event. This is a number counter that sequentially assigns a number to each arrest event - * Characters 13-15 indicates the number of charges being assigned to this Arrestee at the time these fingerprints are being scanned. For instance, if an Arrestee is being charged with five counts of Aggravated Battery for this arrest, the numbers generated would be "001" through "005." - * The Arrest Transaction Number (L55) is used to facilitate crime analysis. Arrest Transaction Number (L55) is the number assigned when an Arrestee is fingerprinted on the Automatic Finger Print Information System (AFIS). This data element can be sent on every Arrestee, but is only mandated if the Louisiana Revised Statute is a felony arrest or charges required fingerprints. + * Characters 1-4 4th, 5th, 6th, and 7th characters of the ORI number of the agency that made the arrest, or where the live scan device is housed. + * Character 5 live scan device number assigned to the device being used to generate this Arrestee's fingerprints. + * Characters 6-7 indicates the year this Arrestee's fingerprints are being scanned into this device. + * Characters 8-12 Arrest Sequence Number for this arrest event. This is a number counter that sequentially assigns a number to each arrest event + * Characters 13-15 indicates the number of charges being assigned to this Arrestee at the time these fingerprints are being scanned. For instance, if an Arrestee is being charged with five counts of Aggravated Battery for this arrest, the numbers generated would be "001" through "005." + * The Arrest Transaction Number (L55) is used to facilitate crime analysis. Arrest Transaction Number (L55) is the number assigned when an Arrestee is fingerprinted on the Automatic Finger Print Information System (AFIS). This data element can be sent on every Arrestee, but is only mandated if the Louisiana Revised Statute is a felony arrest or charges required fingerprints. -
+
-___ +---
# Inchoates (70) -___ +--- **Description:** The Inchoate Modifier is to be added to the end of the LRS Code (DE 6) present in Offense and Arrestee Offense Segments (Segments 20 and 41). It's used to add context to the charges laid against an Offender. EG: Hiring a person to commit a murder should be charged with Attempted Murder, however the Addition of the Inchoate Modifier of '-I' for 'Inciting a Felony' gives us extra context about exactly what happened. @@ -5301,90 +5400,95 @@ If you don't have an Inchoate Modifier to add, leave this Data Element Blank. If **Data Characteristics:** 2 Character Alpha, Fist Character is "-" -### Requirements: +### Requirements: -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["22085"] -%} -1 | {{error.err_desc["70"]}} | {{error.err_no}}| {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["22085"] -%} | | | | +| 1 | {{error.err_desc["70"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +---
# Control Data Elements -___ + +---
## Segment Descriptor (C1) -___ + +--- **Description:** The Segment Deescriptor is what tells LIBRS what data to expect in each line of the Flat File. It absolutely MUST be included in each line. **Data Characteristics:** 2 Character Numeric. First two characters of each line in a LIBRS Flat File. -### Requirements: - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["10051"] -%} -1 | {{error.err_desc["c1"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["20001"] -%} -2 | {{error.seq_desc["c1"]}} | {{error.err_no}} | {{ error.err_message }} +### Requirements: +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["10051"] -%} | | | | +| 1 | {{error.err_desc["c1"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["20001"] -%} | | | | +| 2 | {{error.seq_desc["c1"]}} | {{error.err_no}} | {{ error.err_message }} | ### Details: + * This two-digit identifier is used by LIBRS to determine the type of segment being processed. -___ +--- ### Allowed Entries for Data Element C1: -| Value | Segment Descriptors | Value | Segment Descriptors | -|:-----:|:-----------------------------|:--------:|:-----------------------------| -|00 | Submission Header | 41 | Offender Using | -|01 | Zero Records | 50 | Victim | -|10 | Administration | 51 | Victim Injury | -|11 | Administration Modification | 52 | Victim/Offender Relation | -|20 | Offense | 60 | Arrestee | -|30 | Property | 61 | Arrestee Armed | -|31 | Property Description | 62 | Arrestee Statute | -|32 | Property Modification | 63 | Arrestee Modification | -|33 | Property/Offense | 99 | Submission Trailer | -|40 | Offender | +| Value | Segment Descriptors | Value | Segment Descriptors | +| :---: | :-------------------------- | :---: | :----------------------- | +| 00 | Submission Header | 41 | Offender Using | +| 01 | Zero Records | 50 | Victim | +| 10 | Administration | 51 | Victim Injury | +| 11 | Administration Modification | 52 | Victim/Offender Relation | +| 20 | Offense | 60 | Arrestee | +| 30 | Property | 61 | Arrestee Armed | +| 31 | Property Description | 62 | Arrestee Statute | +| 32 | Property Modification | 63 | Arrestee Modification | +| 33 | Property/Offense | 99 | Submission Trailer | +| 40 | Offender | | |
## Submitting Agency (C2) -___ -**Description:** The Submitting Agency is the Name of the Agency (EG: East Baton Rouge Parish Sheriff's Office rather than EBRSO) that is Submitting the LIBRS Flat File. It's not Validated, but is useful for back-end purposes to keep consistent. +--- + +**Description:** The Submitting Agency is the Name of the Agency (EG: East Baton Rouge Parish Sheriff's Office rather than EBRSO) that is Submitting the LIBRS Flat File. It's not Validated, but is useful for back-end purposes to keep consistent. **Data Characteristics:** 20 Character Alpha. Only used in Header Segment (Segment 00) ### Requirements: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["20010"] -%} -1 | {{error.seq_desc["c2"]}} | {{error.err_no}} | {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["20010"] -%} | | | | +| 1 | {{error.seq_desc["c2"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * The name of the Submitting Agency is spelled out, and often abbreviated. This data field is found in the Header Segment, which is the first segment in all data submission files. -___ +---
## Submission Date (C3) -___ + +--- **Description:** Submission Date is the MMDDYYYY Format Date that the LIBRS Flat File was *generated*. Ideally it's the same day that it was Submitted to LIBRS, but we use it as a way to keep which files came in when to figure out which one to trust. @@ -5394,25 +5498,26 @@ ___ **Requirements:** -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11005"] -%} -1 | {{error.err_desc["c3"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["20001"] -%} -2 | {{error.seq_desc["c3"]}} | {{error.err_no}} | {{ error.err_message }} - +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11005"] -%} | | | | +| 1 | {{error.err_desc["c3"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["20001"] -%} | | | | +| 2 | {{error.seq_desc["c3"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * This data element provides LIBRS with the date that this data submission file was generated for submission. -___ +---
## Reporting Period (C4) -___ + +--- **Description:** Reporting Period is the MMYYYY Format Date of the LIBRS Reporting Period (Month) that the Flat File represents. It is used to test for Out of Sequence Errors, so it's very important to keep straight as submissions move forward. @@ -5422,83 +5527,87 @@ ___ **Requirements:** -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["20001"] -%} -1 | {{error.seq_desc["c4"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["20026"] -%} -3 | {{error.err_desc["c4"]}} | {{error.err_no}} | {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["20001"] -%} | | | | +| 1 | {{error.seq_desc["c4"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["20026"] -%} | | | | +| 3 | {{error.err_desc["c4"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: -* Reporting Period identifies the month and year that the Incident-Based data in a data submission file is being reported. All data in the data submission does not have to correspond to this date (i.e., Modifications and Time-Window Submissions will be from preceding months). -____ +* Reporting Period identifies the month and year that the Incident-Based data in a data submission file is being reported. All data in the data submission does not have to correspond to this date (i.e., Modifications and Time-Window Submissions will be from preceding months). +---
## Action Type (C5) -___ -**Description:** Action Type designates what LIBRS should do with the Line of data that it's about to read. For modern implementations we would recommend only using 'I - Insert' and 'D - Delete', however in order to maintain support for older systems, we do still allow all Five (5) Action Types to be submitted. +--- + +**Description:** Action Type designates what LIBRS should do with the Line of data that it's about to read. For modern implementations we would recommend only using 'I - Insert' and 'D - Delete', however in order to maintain support for older systems, we do still allow all Five (5) Action Types to be submitted. The Types Available are: + * I - Insert - * By far the most common Action Type you will use. - * Used to tell us that the data you're sending us is new and we need to save it in the database. - * Available for use on all Segments except for Header and Footer (Those don't have an Action Type). + * By far the most common Action Type you will use. + * Used to tell us that the data you're sending us is new and we need to save it in the database. + * Available for use on all Segments except for Header and Footer (Those don't have an Action Type). * D - Delete - * The next most common Action type used. - * Used to tell us that we need to delete an Incident from the Database. - * Is only used with Segment 10. Do delete an Incident you just send us the Segment 10 of the Incident, but change the I to a D in the third Character. + * The next most common Action type used. + * Used to tell us that we need to delete an Incident from the Database. + * Is only used with Segment 10. Do delete an Incident you just send us the Segment 10 of the Incident, but change the I to a D in the third Character. * W - Time Window Submission *(Legacy)* - * Used to submit data to the FBI for Incidents that occurred before the Agency's Base Date - * Really uncommon to be used. + * Used to submit data to the FBI for Incidents that occurred before the Agency's Base Date + * Really uncommon to be used. * A - Add Arrest *(Legacy)* - * You can use this to add an Arrest to an already reported Incident. - * We would recommend just passing us a Delete and then resubmitting the whole Incident as an Insert, though. It's less code for everyone to manage. + * You can use this to add an Arrest to an already reported Incident. + * We would recommend just passing us a Delete and then resubmitting the whole Incident as an Insert, though. It's less code for everyone to manage. * M - Arrest Modification *(Legacy)* - * This can be used to change details about an Arrestee that's already been submitted to LIBRS. - * Again, we recommend not using this in favor of deleting the Incident and re-inserting it. + * This can be used to change details about an Arrestee that's already been submitted to LIBRS. + * Again, we recommend not using this in favor of deleting the Incident and re-inserting it. **Data Characteristics:** 1 Character Alpha. Used on every segment in the Flat File Except for the Header and Footer Segments. **Requirements:** -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["16161"] -%} -1 | {{error.err_desc["c5"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["20001"] -%} -2 | {{error.seq_desc["c5"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["90042"] -%} -2 | {{error.err_desc["c5"]}} | {{error.err_no}} | {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["16161"] -%} | | | | +| 1 | {{error.err_desc["c5"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["20001"] -%} | | | | +| 2 | {{error.seq_desc["c5"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["90042"] -%} | | | | +| 2 | {{error.err_desc["c5"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * Action Type (C5) informs LIBRS of the type of action that LIBRS and NIBRS are required to take with incident data contained by the segment. -___ +--- **Allowed Entries for Data Element C5:** -| Action Type | Action Performed by LIBRS/NIBRS -|:---------------------------------:|---------------------------------- - I |**Incident Report**
Incident Reports submitted with an Action Type of "I" are new incidents that are being reported to the LIBRS/NIBRS databases for the first time) - A | **Add Arrest**
Action Type "A" submissions are used to add an arrest to an incident that has previously been reported with an Action Type of "I". Action Type "A" can only be used if incident has already been submitted and there are no changes in other segments of the incident, that is, the agency is simply adding an arrest segment to the already submitted incident - M | **Modify**
Action Type "M" segments are used for Time-Window Submission correction for an Exceptional Clearance, Recovered Property or Arrests). It can alsobe used to modify exceptional clearance indicator and/or exceptional clearance date when incident has already been submitted. - D | **Delete Action**
Type "D" segments are used to delete previously submitted incidents. It is often used when updates or changes are reported to a previously submitted incident. An Action Type "D" segment will delete all existing incident data, allowing the reporting agency to re-submit the incident containing the updated information - W | **Time-Window Submission**
Action Type "W" is used only when reporting an incident that occurred prior to the reporting agency's "base date" as defined in the Guidelines. An agency's base date is usually the date when the agency first started reporting incident-based data to LIBRS/NIBRS. The Time-Window Submission can report one of the following:
      - Exceptional Clearance
      - Exceptional Clearance Date
      - Recovered Property
      - An Arrest +| Action Type | Action Performed by LIBRS/NIBRS | +| :---------: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| I | **Incident Report** `
`Incident Reports submitted with an Action Type of "I" are new incidents that are being reported to the LIBRS/NIBRS databases for the first time) | +| A | **Add Arrest** `
`Action Type "A" submissions are used to add an arrest to an incident that has previously been reported with an Action Type of "I". Action Type "A" can only be used if incident has already been submitted and there are no changes in other segments of the incident, that is, the agency is simply adding an arrest segment to the already submitted incident | +| M | **Modify** `
`Action Type "M" segments are used for Time-Window Submission correction for an Exceptional Clearance, Recovered Property or Arrests). It can alsobe used to modify exceptional clearance indicator and/or exceptional clearance date when incident has already been submitted. | +| D | **Delete Action** `
`Type "D" segments are used to delete previously submitted incidents. It is often used when updates or changes are reported to a previously submitted incident. An Action Type "D" segment will delete all existing incident data, allowing the reporting agency to re-submit the incident containing the updated information | +| W | **Time-Window Submission** `
`Action Type "W" is used only when reporting an incident that occurred prior to the reporting agency's "base date" as defined in the Guidelines. An agency's base date is usually the date when the agency first started reporting incident-based data to LIBRS/NIBRS. The Time-Window Submission can report one of the following:`
`      - Exceptional Clearance`
`      - Exceptional Clearance Date`
`      - Recovered Property`
`      - An Arrest | -___ +---
-## Clearance Indicator (C6) -___ +## Clearance Indicator (C6) + +--- *For Time Window Submissions, ONLY* @@ -5508,36 +5617,37 @@ ___ **Requirements:** -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["11004"] -%} -1 | {{error.err_desc["c6"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["16058"] -%} -2 | {{error.err_desc["c6"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["20001"] -%} -3 | {{error.seq_desc["c6"]}} | {{error.err_no}} | {{ error.err_message }} - +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["11004"] -%} | | | | +| 1 | {{error.err_desc["c6"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["16058"] -%} | | | | +| 2 | {{error.err_desc["c6"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["20001"] -%} | | | | +| 3 | {{error.seq_desc["c6"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * Clearance Indicator (C6) is used in the Arrestee Segment (60) to indicate whether this arrest produced a clearance, or is an additional arrest on a previously cleared incident that is outside the agency's base date. -___ +--- **Allowed Entries for Data Element C6:** - ||Clearance Indicator | + ||Clearance Indicator | ||--------------------- | |Y |Yes - Submit "Y", if this is the first Arrestee Segment (60) submitted for an Incident. By submitting a "Y", the Arrest clears an Incident that happened prior to the date the agency began submitting Incident-Based Data to the LIBRS/NIBRS system (that is, a Time-Window case that is not on the LIBRS/NIBRS database). |N |No - Submit 'N', if a previous Arrest Segment (60) was already submitted for an Incident. (That is, the case has already been cleared for an Incident that occurred since the agency's base data, and is in the LIBRS/NIBRS database). -___ +---
## Number of Segments Transferred (C7) -___ + +--- **Description:** Number of Segments Transferred is quite literally the number of lines that are present in a LIBRS Flat File, including the Header and the Footer Segments. Effectively it is just the line number of the Footer Segment. @@ -5545,30 +5655,32 @@ ___ **Requirements:** -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["20001"] -%} -1 | {{error.seq_desc["c7"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["20031"] -%} -3 | {{error.seq_desc["c7"]}} | {{error.err_no}} | {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["20001"] -%} | | | | +| 1 | {{error.seq_desc["c7"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["20031"] -%} | | | | +| 3 | {{error.seq_desc["c7"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + * This field provides LIBRS with a count of segments submitted by the agency within the data submission file, including the header and trailer segments. This number is used as part of the data submission validation process. -___ +--- **Allowed Entries:** Any integer greater than or equal to 000003. -___ +---
## End of Segment Marker (C8) -___ + +--- **Description:** The End of Segment Marker us used to tell LIBRS where the data in a line ends, and if anything else is in the line to ignore it. It is an older data element that was brought forward for backwards compatibilty, however it is important that it is placed in the correct location and is the correct characters ('ZZ'). @@ -5576,29 +5688,30 @@ ___ **Requirements:** -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["20001"] -%} -1 | {{error.seq_desc["c8"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["20029"] -%} -2 | {{error.seq_desc["c8"]}} | {{error.err_no}} | {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["20001"] -%} | | | | +| 1 | {{error.seq_desc["c8"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["20029"] -%} | | | | +| 2 | {{error.seq_desc["c8"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- ### Details: + This field is used to provide LIBRS with a way to determine where an end of record occurs. In the event of an error in record length this will allow the LIBRS system to find the start of the next record and possibly recover from the error. The "End of Segment" marker is the same for all segments, two capitol Z's. -___ +--- **Allowed Entries:** "ZZ" only. -___ +---
## Padding (C9) -___ +--- **Description:** Padding is used to fill out unused area in a LIBRS Flat File to keep consistent formatting across each Segment. @@ -5606,57 +5719,59 @@ ___ **Requirements:** -Requirement | Requirement Description | -:-----------:|-------------------------| -1 | Must be Blank (G) if fixed length records are submitted. MUST be one newline character (ASCII 13; CR, LF, or CRLF) if variable length records are submitted. -2 | If Fixed-Length records are used, add padding from the End of Segment Marker (C8) to exactly column 150. -3 | Segment 00 MUST have both Padding to column 150 and a new line charachter (ASCII 13; CR, LF, or CRLF) +| Requirement | Requirement Description | +| :---------: | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| 1 | Must be Blank (G) if fixed length records are submitted. MUST be one newline character (ASCII 13; CR, LF, or CRLF) if variable length records are submitted. | +| 2 | If Fixed-Length records are used, add padding from the End of Segment Marker (C8) to exactly column 150. | +| 3 | Segment 00 MUST have both Padding to column 150 and a new line charachter (ASCII 13; CR, LF, or CRLF) | -___ +--- ### Details: -* This field is used to pad unused fields for systems that are unable to write variable length records. This padding will lengthen all segments to 150 characters. Previously there may have been some confusion about whether to use a New Line Character after the Segment End Marker - this is incorrect. Please Pad all Segments to 150 Characters long. -___ +* This field is used to pad unused fields for systems that are unable to write variable length records. This padding will lengthen all segments to 150 characters. Previously there may have been some confusion about whether to use a New Line Character after the Segment End Marker - this is incorrect. Please Pad all Segments to 150 Characters long. + +--- **Allowed Entries:** Blank spaces or the newline character (ASCII 13). -___ +---
## Software ID (C10) -___ +--- -**Description:** Software ID is used to tell LIBRS the RMS Software that was used to generate the LIBRS Flat File. This is useful because if we find an error that's being caused by something invalid in the Flat File it allows us to track down the Vendor/Agencies that are affected and help get the issue resolved. +**Description:** Software ID is used to tell LIBRS the RMS Software that was used to generate the LIBRS Flat File. This is useful because if we find an error that's being caused by something invalid in the Flat File it allows us to track down the Vendor/Agencies that are affected and help get the issue resolved. **Data Characteristics**: 5 Characters Alpha/Numeric. Only used in Header Segment (Segment 00) -**Requirements:** +**Requirements:** -Requirement | Requirement Description | -:-----------:|-------------------------| -1 | Contains Identification of software used to generate the LIBRS data submission +| Requirement | Requirement Description | +| :---------: | ------------------------------------------------------------------------------ | +| 1 | Contains Identification of software used to generate the LIBRS data submission | -___ +---
## Software Version (C11) -___ -**Description:** Software Version is used to tell LIBRS the Version RMS Software that was used to generate the LIBRS Flat File. This is useful because if we find an error that's being caused by something invalid in the Flat File it allows us to track down the Vendor/Agencies that are affected and help get the issue resolved. +--- + +**Description:** Software Version is used to tell LIBRS the Version RMS Software that was used to generate the LIBRS Flat File. This is useful because if we find an error that's being caused by something invalid in the Flat File it allows us to track down the Vendor/Agencies that are affected and help get the issue resolved. **Data Characteristics**: 10 Characters Alpha/Numeric. Only used in Header Segment (Segment 00) -**Requirements:** +**Requirements:** -Requirement | Requirement Description | -:-----------:|-------------------------| -1 | Contains Version of software used to generate the LIBRS data submission +| Requirement | Requirement Description | +| :---------: | ----------------------------------------------------------------------- | +| 1 | Contains Version of software used to generate the LIBRS data submission | -___ +---
@@ -5664,169 +5779,178 @@ ___ ## LIBRS Spec Indicator (C12) -___ +--- **Description:** As of 2019, the LIBRS Spec must be present in the Header Segment, and it must be equal to '2.5' **Data Characteristics**: 3 Characters Alpha/Numeric. Only used in Header Segment (Segment 00) -**Requirements:** - -Requirement | Requirement Description | -:-----------:|-------------------------| -1 | Indicates the LIBRS Spec is to be used by WinLIBRS when validating a data submission +**Requirements:** -___ +| Requirement | Requirement Description | +| :---------: | ------------------------------------------------------------------------------------ | +| 1 | Indicates the LIBRS Spec is to be used by WinLIBRS when validating a data submission | +--- # LIBRS/NIBRS Mandatories -____ + +--- # Error Messages -____ + +--- ## Structure for Numbering of Mandatory Error Messages -| 1st Character | 2nd Character | 3rd Character | 4th and 5th Characters | -|:-----------------------------------:|:--------------------:|:----------------------------------:|:------------------------------------------------------------:| -|8 |1 |0 |00: Overall Data Element Edits all Sections (Except Section 4)| -|**Denotes Mandatory Error Message** |Section with Mandatory| Error Message Number within Section| 01 - 21
Data Elemeber Specific Edits Within Section 4 | +| 1st Character | 2nd Character | 3rd Character | 4th and 5th Characters | +| :---------------------------------------: | :--------------------: | :---------------------------------: | :------------------------------------------------------------: | +| 8 | 1 | 0 | 00: Overall Data Element Edits all Sections (Except Section 4) | +| **Denotes Mandatory Error Message** | Section with Mandatory | Error Message Number within Section | 01 - 21`
`Data Elemeber Specific Edits Within Section 4 | -___ +--- ## Section (1) Error Message for: Initial Incident Reports Each incident MUST have the following data elements, or the ENTIRE incident will be REJECTED: -____ +--- #### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign errorNumbers = "81000,81100,81200a,81200b,81400" | split: ',' -%} -{% for errorNumber in errorNumbers -%} -{% assign error = site.data.error[errorNumber] -%} -{{ forloop.index0 }} | {{error.mandatory["1"]}} | {{error.err_no}} | {{ error.err_message }} -{% endfor %} +--- -___ +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign errorNumbers = "81000,81100,81200a,81200b,81400" | split: ',' -%} | | | +| {% for errorNumber in errorNumbers -%} | | | | +| {% assign error = site.data.error[errorNumber] -%} | | | | +| {{ forloop.index0 }} | {{error.mandatory["1"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% endfor %} | | | | + +--- #### Details: -**For Error Message 81000:** -* This edit should identify the missing data element, so the agency can determine which exact data element is missing. This edit applies to the following Data Elements:
- * ORI Number (1) - * Incident Number (2) - * Incident Date/Hour (3) - * Cleared Exceptionally (4) - * Offense Sequence Number (L6) - * Louisiana Revised Statute (6) - * Agency Supplied NIBRS Code (N6)* - * Offense Attempted/Completed (7) - * Offender Suspected of Using/Gaming Motivation (8) - * Bias Motivation/Bias Crime Type (8A) - * Location Type (9) - * Victim Sequence Number (23) - * Offense Connected to Victim Sequence Number (24) - * Type of Victim (25). - * *** New data element not in previous LIBRS Specifications.** +**For Error Message 81000:** + +* This edit should identify the missing data element, so the agency can determine which exact data element is missing. This edit applies to the following Data Elements:`
` + * ORI Number (1) + * Incident Number (2) + * Incident Date/Hour (3) + * Cleared Exceptionally (4) + * Offense Sequence Number (L6) + * Louisiana Revised Statute (6) + * Agency Supplied NIBRS Code (N6)* + * Offense Attempted/Completed (7) + * Offender Suspected of Using/Gaming Motivation (8) + * Bias Motivation/Bias Crime Type (8A) + * Location Type (9) + * Victim Sequence Number (23) + * Offense Connected to Victim Sequence Number (24) + * Type of Victim (25). + * *** New data element not in previous LIBRS Specifications.** **For Error Message 81200a:** -* This edit should identify the missing data elements(s), in order for the agency to determine the exact data element that is missing. Applies to the following Data Elements:
- * Age of Victim [At Time Incident Occurred] (26) - * Sex of Victim (27) - * Race of Victim (28) - * Ethnicity of Victim (29) - * Resident Status of Victim (30) - * Offender Sequence Number (36) + +* This edit should identify the missing data elements(s), in order for the agency to determine the exact data element that is missing. Applies to the following Data Elements:`
` + * Age of Victim [At Time Incident Occurred] (26) + * Sex of Victim (27) + * Race of Victim (28) + * Ethnicity of Victim (29) + * Resident Status of Victim (30) + * Offender Sequence Number (36) **For Error Message 81200b:** -* This edit should identify the missing data elements(s), in order for the agency to determine the exact data element that is missing. Applies to Data Elements:
- * Age of Offender [At Time Incident Occurred] (37) - * Sex of Offender (38) - * Race of Offender (39) +* This edit should identify the missing data elements(s), in order for the agency to determine the exact data element that is missing. Applies to Data Elements:`
` + * Age of Offender [At Time Incident Occurred] (37) + * Sex of Offender (38) + * Race of Offender (39)
## Section (2) Error Message for: Initial Incident Reports Containing Arrestee Segments -____ +--- #### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["82000"] -%} -0 | {{error.mandatory["2"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["82100"] -%} -1 | {{error.mandatory["2"]}} | {{error.err_no}} | {{ error.err_message }} +--- -___ +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["82000"] -%} | | | | +| 0 | {{error.mandatory["2"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["82100"] -%} | | | | +| 1 | {{error.mandatory["2"]}} | {{error.err_no}} | {{ error.err_message }} | + +--- #### Details: -**For Error Message 82000:** -* This edit should identify the missing data element(s), in order for the agency to determine which exact data element is missing. This edit applies to the following Data Elements: - * Arrestee Sequence Number (40) - * Arrest Number/Local Booking Number for Arrest (41) - * Arrest Date (42) - * Type of Arrest (43) - * Multiple Arrestee Segment Indicator (44) - * Louisiana Revised Statute of Arrest (45) - * Arrestee Armed With [At Time of Arrest] (46) - * Age of Arrestee [At Time of Arrest] (47) - * Sex of Arrestee (48) - * Race of Arrestee (49) - * Ethnicity of Arrestee (50) - * Resident Status of Arrestee (51) +**For Error Message 82000:** + +* This edit should identify the missing data element(s), in order for the agency to determine which exact data element is missing. This edit applies to the following Data Elements: + * Arrestee Sequence Number (40) + * Arrest Number/Local Booking Number for Arrest (41) + * Arrest Date (42) + * Type of Arrest (43) + * Multiple Arrestee Segment Indicator (44) + * Louisiana Revised Statute of Arrest (45) + * Arrestee Armed With [At Time of Arrest] (46) + * Age of Arrestee [At Time of Arrest] (47) + * Sex of Arrestee (48) + * Race of Arrestee (49) + * Ethnicity of Arrestee (50) + * Resident Status of Arrestee (51)
## Section (3) Error Message for: Subsequent Updates (ADD ARRESTs, MODIFYs, and DELETEs) to Previously Submitted Incidents -____ +--- #### Requirements: -___ -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["83100"] -%} -0 | {{error.mandatory["3"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["83200"] -%} -1 | {{error.mandatory["3"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["83000"] -%} -2 | {{error.mandatory["3"]}} | {{error.err_no}} | {{ error.err_message }} +--- -___ +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | ------------------------ | :--------------: | ----------------------- | +| {% assign error = site.data.error["83100"] -%} | | | | +| 0 | {{error.mandatory["3"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["83200"] -%} | | | | +| 1 | {{error.mandatory["3"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["83000"] -%} | | | | +| 2 | {{error.mandatory["3"]}} | {{error.err_no}} | {{ error.err_message }} | + +--- #### Details: **For Error Message 83100 and 83200:** -* Are for Updates (ADD ARREST/MODIFY/DELETE) of Arrestee Segments to the Initial Submission of Incident Data. -**For Error Message 83100:** -* This edit should identify the missing data element(s), in order for the agency to determine which exact data element is missing. This edit applies to the following Data Elements: - * Arrestee Sequence Number (40) - * Arrest Number/Local Booking Number for Arrest (41) - * Arrest Date (42) - * Type of Arrest (43) - * Multiple Arrestee Segment Indicator (44) - * Louisiana Revised Statute of Arrest (45) - * Arrestee Armed With [At Time of Arrest] (46) - * Age of Arrestee [At Time of Arrest] (47) - * Sex of Arrestee (48) - * Race of Arrestee (49) - * Ethnicity of Arrestee (50) - * Resident Status of Arrestee (51) +* Are for Updates (ADD ARREST/MODIFY/DELETE) of Arrestee Segments to the Initial Submission of Incident Data. + +**For Error Message 83100:** + +* This edit should identify the missing data element(s), in order for the agency to determine which exact data element is missing. This edit applies to the following Data Elements: + * Arrestee Sequence Number (40) + * Arrest Number/Local Booking Number for Arrest (41) + * Arrest Date (42) + * Type of Arrest (43) + * Multiple Arrestee Segment Indicator (44) + * Louisiana Revised Statute of Arrest (45) + * Arrestee Armed With [At Time of Arrest] (46) + * Age of Arrestee [At Time of Arrest] (47) + * Sex of Arrestee (48) + * Race of Arrestee (49) + * Ethnicity of Arrestee (50) + * Resident Status of Arrestee (51)
-___ +---
@@ -5834,575 +5958,552 @@ ___ # NIBRS Mandatories -___ +--- ### Subsection 01: ARSON (200) -___ +--- #### Requirements: Incidents submitted with an ARSON (Crime Against Property) offense (NIBRS Code "200") should receive **one** of the following two error messages, as appropriate. -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84001"] -%} -0 | {{error.mandatory["4s1"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84101"] -%} -1 | {{error.mandatory["4s1"]}} | {{error.err_no}} | {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | -------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84001"] -%} | | | | +| 0 | {{error.mandatory["4s1"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84101"] -%} | | | | +| 1 | {{error.mandatory["4s1"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +---
-___ +--- ### Subsection 02: AGGRAVATED ASSAULT, SIMPLE ASSAULT OR INTIMIDATION (13A, 13B and 13C) -___ +--- #### Requirements: Incidents submitted with an AGGRAVATED ASSAULT, SIMPLE ASSAULT OR INTIMIDATION (Crime Against Person) offense (NIBRS Code 13A, 13B or 13C) should receive one of the following **six** error messages, as appropriate. -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84002"] -%} -0 | {{error.mandatory["4s2"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84102"] -%} -1 | {{error.mandatory["4s2"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84202"] -%} -2 | {{error.mandatory["4s2"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84302"] -%} -3 | {{error.mandatory["4s2"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84402"] -%} -4 | {{error.mandatory["4s2"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84502"] -%} -5 | {{error.mandatory["4s2"]}} | {{error.err_no}} | {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | -------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84002"] -%} | | | | +| 0 | {{error.mandatory["4s2"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84102"] -%} | | | | +| 1 | {{error.mandatory["4s2"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84202"] -%} | | | | +| 2 | {{error.mandatory["4s2"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84302"] -%} | | | | +| 3 | {{error.mandatory["4s2"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84402"] -%} | | | | +| 4 | {{error.mandatory["4s2"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84502"] -%} | | | | +| 5 | {{error.mandatory["4s2"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ +---
### Subsection 03: BRIBERY (510) -___ +--- #### Requirements: Incidents submitted with an offense of BRIBERY (Crime Against Property) offense (NIBRS Code "510") should receive the following **five** error messages, as appropriate: -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84003"] -%} -0 | {{error.mandatory["4s3"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84103"] -%} -1 | {{error.mandatory["4s3"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84203"] -%} -2 | {{error.mandatory["4s3"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84303"] -%} -3 | {{error.mandatory["4s3"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84403"] -%} -4 | {{error.mandatory["4s3"]}} | {{error.err_no}} | {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | -------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84003"] -%} | | | | +| 0 | {{error.mandatory["4s3"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84103"] -%} | | | | +| 1 | {{error.mandatory["4s3"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84203"] -%} | | | | +| 2 | {{error.mandatory["4s3"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84303"] -%} | | | | +| 3 | {{error.mandatory["4s3"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84403"] -%} | | | | +| 4 | {{error.mandatory["4s3"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ - +--- ### Subsection 04: BURGLARY/BREAKING AND ENTERING (220) -___ +--- #### Requirements: Incidents submitted with a BURGLARY/BREAKING AND ENTERING (Crime Against Property) offense (NIBRS Code 220) should receive the following **six** error messages: -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84004"] -%} -0 | {{error.mandatory["4s4"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84104"] -%} -1 | {{error.mandatory["4s4"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84204"] -%} -2 | {{error.mandatory["4s4"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84304"] -%} -3 | {{error.mandatory["4s4"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84404"] -%} -4 | {{error.mandatory["4s4"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84504"] -%} -5 | {{error.mandatory["4s4"]}} | {{error.err_no}} | {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | -------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84004"] -%} | | | | +| 0 | {{error.mandatory["4s4"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84104"] -%} | | | | +| 1 | {{error.mandatory["4s4"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84204"] -%} | | | | +| 2 | {{error.mandatory["4s4"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84304"] -%} | | | | +| 3 | {{error.mandatory["4s4"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84404"] -%} | | | | +| 4 | {{error.mandatory["4s4"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84504"] -%} | | | | +| 5 | {{error.mandatory["4s4"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ +---
### Subsection 05: COUNTERFEITING/FORGERY (250) -___ +--- #### Requirements: Incidents submitted with a COUNTERFEITING/FORGERY (Crime Against Property) offense (NIBRS Code 250) should receive the following **four** error messages, as appropriate: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84005"] -%} -0 | {{error.mandatory["4s5"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84105"] -%} -1 | {{error.mandatory["4s5"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84205"] -%} -2 | {{error.mandatory["4s5"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84305"] -%} -3 | {{error.mandatory["4s5"]}} | {{error.err_no}} | {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | -------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84005"] -%} | | | | +| 0 | {{error.mandatory["4s5"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84105"] -%} | | | | +| 1 | {{error.mandatory["4s5"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84205"] -%} | | | | +| 2 | {{error.mandatory["4s5"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84305"] -%} | | | | +| 3 | {{error.mandatory["4s5"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ - +--- ### Subsection 06: DESTRUCTION/DAMAGE/VANDALISM (290) -___ +--- #### Requirements: Incidents submitted with a DESTRUCTION/DAMAGE/VANDALISM (Crime Against Property) offense (NIBRS Code 290) should receive one of the following **two** error messages, as appropriate: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84006"] -%} -0 | {{error.mandatory["4s6"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84106"] -%} -1 | {{error.mandatory["4s6"]}} | {{error.err_no}} | {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | -------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84006"] -%} | | | | +| 0 | {{error.mandatory["4s6"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84106"] -%} | | | | +| 1 | {{error.mandatory["4s6"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ +---
### Subsection 07: DRUG/NARCOTIC VIOLATION (35A) or DRUG EQUIPMENT VIOLATION (35B) -___ +--- #### Requirements: Incidents submitted with a DRUG/NARCOTIC VIOLATION (Crime Against Society) offense (NIBRS Code 35A) or DRUG EQUIPMENT VIOLATION (Crime Against Society) offense (NIBRS Code 35B) should receive one of the following **four** error messages, as appropriate: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84007"] -%} -0 | {{error.mandatory["4s7"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84107"] -%} -1 | {{error.mandatory["4s7"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84207"] -%} -2 | {{error.mandatory["4s7"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84307"] -%} -3 | {{error.mandatory["4s7"]}} | {{error.err_no}} | {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | -------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84007"] -%} | | | | +| 0 | {{error.mandatory["4s7"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84107"] -%} | | | | +| 1 | {{error.mandatory["4s7"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84207"] -%} | | | | +| 2 | {{error.mandatory["4s7"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84307"] -%} | | | | +| 3 | {{error.mandatory["4s7"]}} | {{error.err_no}} | {{ error.err_message }} | -___ +--- Incidents submitted with a DRUG/NARCOTIC VIOLATION (Crime Against Society) offense (NIBRS Code 35A) should receive the following **three** error messages: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84407"] -%} -0 | {{error.mandatory["4s7"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84507"] -%} -1 | {{error.mandatory["4s7"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84607"] -%} -2 | {{error.mandatory["4s7"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84707"] -%} -3 | {{error.mandatory["4s7"]}} | {{error.err_no}} | {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | -------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84407"] -%} | | | | +| 0 | {{error.mandatory["4s7"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84507"] -%} | | | | +| 1 | {{error.mandatory["4s7"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84607"] -%} | | | | +| 2 | {{error.mandatory["4s7"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84707"] -%} | | | | +| 3 | {{error.mandatory["4s7"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ +---
### Subsection 08: EXTORTION/BLACKMAIL (210) -___ +--- #### Requirements: Incidents submitted with a EXTORTION/BLACKMAIL (Crime Against Property) offense (NIBRS Code 210) should receive the following **five** error messages: -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84008"] -%} -0 | {{error.mandatory["4s8"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84108"] -%} -1 | {{error.mandatory["4s8"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84208"] -%} -2 | {{error.mandatory["4s8"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84308"] -%} -3 | {{error.mandatory["4s8"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84408"] -%} -4 | {{error.mandatory["4s8"]}} | {{error.err_no}} | {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | -------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84008"] -%} | | | | +| 0 | {{error.mandatory["4s8"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84108"] -%} | | | | +| 1 | {{error.mandatory["4s8"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84208"] -%} | | | | +| 2 | {{error.mandatory["4s8"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84308"] -%} | | | | +| 3 | {{error.mandatory["4s8"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84408"] -%} | | | | +| 4 | {{error.mandatory["4s8"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ +--- ### Subsection 09: FRAUD OFFENSES (26A-E) -___ +--- #### Requirements: Incidents submitted with FRAUD OFFENSES (Crimes Against Property) (NIBRS Codes 26A-E) should receive the following **three** error messages: -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84009"] -%} -0 | {{error.mandatory["4s9"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84109"] -%} -1 | {{error.mandatory["4s9"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84209"] -%} -2 | {{error.mandatory["4s9"]}} | {{error.err_no}} | {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | -------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84009"] -%} | | | | +| 0 | {{error.mandatory["4s9"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84109"] -%} | | | | +| 1 | {{error.mandatory["4s9"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84209"] -%} | | | | +| 2 | {{error.mandatory["4s9"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ +---
### Subsection 10: GAMBLING OFFENSES (39A-D) -___ +--- #### Requirements: Incidents submitted with GAMBLING OFFENSES (Crimes Against Society) (NIBRS Codes 39A-D) should receive one of the following two error messages, as appropriate: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84010"] -%} -0 | {{error.mandatory["4s10"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84110"] -%} -1 | {{error.mandatory["4s10"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84210"] -%} -2 | {{error.mandatory["4s10"]}} | {{error.err_no}} | {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | --------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84010"] -%} | | | | +| 0 | {{error.mandatory["4s10"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84110"] -%} | | | | +| 1 | {{error.mandatory["4s10"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84210"] -%} | | | | +| 2 | {{error.mandatory["4s10"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ - +--- ### Subsection 11: HOMICIDE OFFENSES (09A, 09B or 09C) -___ +--- #### Requirements: Incidents submitted with HOMICIDE OFFENSES (Crimes Against Persons) (NIBRS Codes 09A, 09B and 09C) should receive one of the following **five** error messages, as appropriate: -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84011"] -%} -0 | {{error.mandatory["4s11"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84111"] -%} -1 | {{error.mandatory["4s11"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84211"] -%} -2 | {{error.mandatory["4s11"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84311"] -%} -3 | {{error.mandatory["4s11"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84411"] -%} -4 | {{error.mandatory["4s11"]}} | {{error.err_no}} | {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | --------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84011"] -%} | | | | +| 0 | {{error.mandatory["4s11"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84111"] -%} | | | | +| 1 | {{error.mandatory["4s11"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84211"] -%} | | | | +| 2 | {{error.mandatory["4s11"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84311"] -%} | | | | +| 3 | {{error.mandatory["4s11"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84411"] -%} | | | | +| 4 | {{error.mandatory["4s11"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ +---
### Subsection 12: KIDNAPPING/ABDUCTION (100) -___ +--- #### Requirements: Incidents submitted with KIDNAPPING/ABDUCTION (Crimes Against Person) (NIBRS Code 100) should receive one of the following **eight** error messages, as appropriate: -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84012"] -%} -0 | {{error.mandatory["4s12"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84112"] -%} -1 | {{error.mandatory["4s12"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84212"] -%} -2 | {{error.mandatory["4s12"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84312"] -%} -3 | {{error.mandatory["4s12"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84412"] -%} -4 | {{error.mandatory["4s12"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84512"] -%} -5 | {{error.mandatory["4s12"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84612"] -%} -6 | {{error.mandatory["4s12"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84712"] -%} -7 | {{error.mandatory["4s12"]}} | {{error.err_no}} | {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | --------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84012"] -%} | | | | +| 0 | {{error.mandatory["4s12"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84112"] -%} | | | | +| 1 | {{error.mandatory["4s12"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84212"] -%} | | | | +| 2 | {{error.mandatory["4s12"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84312"] -%} | | | | +| 3 | {{error.mandatory["4s12"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84412"] -%} | | | | +| 4 | {{error.mandatory["4s12"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84512"] -%} | | | | +| 5 | {{error.mandatory["4s12"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84612"] -%} | | | | +| 6 | {{error.mandatory["4s12"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84712"] -%} | | | | +| 7 | {{error.mandatory["4s12"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ - +--- ### Subsection 13: LARCENY/THEFT OFFENSES (23A-H) -___ +--- #### Requirements: Incidents submitted with LARCENY/THEFT OFFENSES (NIBRS Codes 23A-H) or EMBEZZLEMENT (NIBRS Code 270) offenses (both Crimes Against Property) should receive the following **three** error messages, as appropriate: -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84013"] -%} -0 | {{error.mandatory["4s13"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84113"] -%} -1 | {{error.mandatory["4s13"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84213"] -%} -2 | {{error.mandatory["4s13"]}} | {{error.err_no}} | {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | --------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84013"] -%} | | | | +| 0 | {{error.mandatory["4s13"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84113"] -%} | | | | +| 1 | {{error.mandatory["4s13"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84213"] -%} | | | | +| 2 | {{error.mandatory["4s13"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ +---
### Subsection 14: MOTOR VEHICLE THEFT (240) -___ +--- #### Requirements: Incidents submitted with MOTOR VEHICLE THEFT (Crimes Against Property) (NIBRS Code 240) should receive one of the following **five** error messages, as appropriate: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84014"] -%} -0 | {{error.mandatory["4s14"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84114"] -%} -1 | {{error.mandatory["4s14"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84214"] -%} -2 | {{error.mandatory["4s14"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84314"] -%} -3 | {{error.mandatory["4s14"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84414"] -%} -4 | {{error.mandatory["4s14"]}} | {{error.err_no}} | {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | --------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84014"] -%} | | | | +| 0 | {{error.mandatory["4s14"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84114"] -%} | | | | +| 1 | {{error.mandatory["4s14"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84214"] -%} | | | | +| 2 | {{error.mandatory["4s14"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84314"] -%} | | | | +| 3 | {{error.mandatory["4s14"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84414"] -%} | | | | +| 4 | {{error.mandatory["4s14"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ +--- ### Subsection 15: PORNOGRAPHY/OBSCENE MATERIAL OFFENSES (370) -___ +--- #### Requirements: Incidents submitted with PORNOGRAPHY/OBSCENE MATERIAL OFFENSES (Crimes Against Society) (NIBRS Code 370) should receive the following error message, as appropriate: -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84015"] -%} -0 | {{error.mandatory["4s15"]}} | {{error.err_no}} | {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | --------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84015"] -%} | | | | +| 0 | {{error.mandatory["4s15"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ +--- ### Subsection 16: PROSTITUTION OFFENSES (40A, 40B) -___ +--- #### Requirements: Incidents submitted with PROSTITUTION OFFENSES (Crimes Against Society) (NIBRS Codes 40A and 40B) should receive the following error message, as appropriate: -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84016"] -%} -0 | {{error.mandatory["4s16"]}} | {{error.err_no}} | {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | --------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84016"] -%} | | | | +| 0 | {{error.mandatory["4s16"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ +---
### Subsection 17: ROBBERY OFFENSES (120) -___ +--- #### Requirements: Incidents submitted with ROBBERY OFFENSES (Crimes Against Property) (NIBRS Code 120) should receive one of the following **six** error messages: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84017"] -%} -0 | {{error.mandatory["4s17"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84117"] -%} -1 | {{error.mandatory["4s17"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84217"] -%} -2 | {{error.mandatory["4s17"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84317"] -%} -3 | {{error.mandatory["4s17"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84417"] -%} -4 | {{error.mandatory["4s17"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84517"] -%} -5 | {{error.mandatory["4s17"]}} | {{error.err_no}} | {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | --------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84017"] -%} | | | | +| 0 | {{error.mandatory["4s17"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84117"] -%} | | | | +| 1 | {{error.mandatory["4s17"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84217"] -%} | | | | +| 2 | {{error.mandatory["4s17"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84317"] -%} | | | | +| 3 | {{error.mandatory["4s17"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84417"] -%} | | | | +| 4 | {{error.mandatory["4s17"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84517"] -%} | | | | +| 5 | {{error.mandatory["4s17"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ - +--- ### Subsection 18: SEX OFFENSES – FORCIBLE (11A-D) -___ +--- #### Requirements: Incidents submitted with SEX OFFENSES - FORCIBLE (Crimes Against Persons) (NIBRS Codes 11A-D) should receive the following **two** error messages, as appropriate: -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84018"] -%} -0 | {{error.mandatory["4s18"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84118"] -%} -1 | {{error.mandatory["4s18"]}} | {{error.err_no}} | {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | --------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84018"] -%} | | | | +| 0 | {{error.mandatory["4s18"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84118"] -%} | | | | +| 1 | {{error.mandatory["4s18"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ - +--- ### Subsection 19: SEX OFFENSES – NON-FORCIBLE (36A-36B) -___ +--- #### Requirements: Incidents submitted with SEX OFFENSES – NON-FORCIBLE (Crimes Against Persons) (NIBRS Codes 36A or 36B) should receive the following two error messages, as appropriate: -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84019"] -%} -0 | {{error.mandatory["4s19"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84119"] -%} -1 | {{error.mandatory["4s19"]}} | {{error.err_no}} | {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | --------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84019"] -%} | | | | +| 0 | {{error.mandatory["4s19"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84119"] -%} | | | | +| 1 | {{error.mandatory["4s19"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ +---
### Subsection 20: STOLEN PROPERTY OFFENSES (280) -___ +--- #### Requirements: Incidents submitted with STOLEN PROPERTY OFFENSES (Crimes Against Property) (NIBRS Code 280) should receive one of the **four** following error messages, as appropriate: -___ +--- -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84020"] -%} -0 | {{error.mandatory["4s20"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84120"] -%} -1 | {{error.mandatory["4s20"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84220"] -%} -2 | {{error.mandatory["4s20"]}} | {{error.err_no}} | {{ error.err_message }} -{% assign error = site.data.error["84320"] -%} -3 | {{error.mandatory["4s20"]}} | {{error.err_no}} | {{ error.err_message }} +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | --------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84020"] -%} | | | | +| 0 | {{error.mandatory["4s20"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84120"] -%} | | | | +| 1 | {{error.mandatory["4s20"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84220"] -%} | | | | +| 2 | {{error.mandatory["4s20"]}} | {{error.err_no}} | {{ error.err_message }} | +| {% assign error = site.data.error["84320"] -%} | | | | +| 3 | {{error.mandatory["4s20"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ - +--- ### Subsection 21: WEAPONS LAW VIOLATIONS (520) -___ +--- #### Requirements: -___ - -Requirement | Requirement Description | Error Number | Error Message -:-----------:|-------------------------|:------------:|---------- -{% assign error = site.data.error["84021"] -%} -0 | {{error.mandatory["4s21"]}} | {{error.err_no}} | {{ error.err_message }} +--- +| Requirement | Requirement Description | Error Number | Error Message | +| :--------------------------------------------: | --------------------------- | :--------------: | ----------------------- | +| {% assign error = site.data.error["84021"] -%} | | | | +| 0 | {{error.mandatory["4s21"]}} | {{error.err_no}} | {{ error.err_message }} |
-___ - - - +--- diff --git a/models.md b/models.md index 0b22a34..d4ddd6a 100644 --- a/models.md +++ b/models.md @@ -3,55 +3,58 @@ title: Data Model Specifications layout: default permalink: /models --- - # Data Model Specifications + This page contains the specifications on how to use the data models found on our github pages: + * LIBRS Models - [https://github.com/teisdbr/LibrsDataModels](https://github.com/teisdbr/LibrsDataModels) * Contains the models used for our JSON Validator, as well as the NIBRS-Based model, which includes a NIBRS Report plus the other things that LIBRS cares about (vendors need to create the constructors between the two). * NIBRS Models - [https://github.com/teisdbr/NibrsDataModels](https://github.com/teisdbr/LibrsDataModels) - * Contains the NIBRS IEPD Report as C# Objects. + * Contains the NIBRS IEPD Report as C# Objects. # LIBRS Data Models + These models are meant to be a simplification of the existing Flat File format, but still meant to be compatible with it. For instance, in some places entire segments have been removed and rolled into other ones (EG: Segment 51 - Victim Injury is gone, and instead injuryType is just a property of Victim now).
## Quick Start -To get down to it, the easiest way to start incorporating the LIBRS JSON models would be to convert existing Flat Files to JSON Format, and compare the inputs and outputs. You can do this with the ValidateFFtoJSON Endpoint. See below for details. You can also view more in-depth information on the Swagger Page for the API: [https://json.librs.org:5000/swagger/index.html](https://json.librs.org:5000/swagger/index.html) ***Note:*** It's been brought to our attention that Swagger will remove the New Line characters from the request, which will cause the FFToJson and ValidateFFToJson requests to fail. The recommended workaround is to use Postman. +To get down to it, the easiest way to start incorporating the LIBRS JSON models would be to convert existing Flat Files to JSON Format, and compare the inputs and outputs. You can do this with the ValidateFFtoJSON Endpoint. See below for details. You can also view more in-depth information on the Swagger Page for the API: [https://json.librs.org:5000/swagger/index.html](https://json.librs.org:5000/swagger/index.html) ***Note:*** It's been brought to our attention that Swagger will remove the New Line characters from the request, which will cause the FFToJson and ValidateFFToJson requests to fail. The recommended workaround is to use Postman. ### API Endpoints Currently the JSON Validator is hosted at [https://json.librs.org:5000](https://json.librs.org:5000). -| Endpoint | Body Requirement | Description | -| --------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ | -| /api/jsonvalidate | An RVO (Root Validation Object) containing an array of LIBRS Incidents to be processed. Body should be formatted as application/json. No authentication/authorization is required for validation. | This is the API Endpoint that will take one an RVO with any number of JSON-formatted LIBRS Incidents, and return the validation plus the original object as an extended RVO. Can be used to both validate and submit data. | -| /api/fftojson | A LIBRS Flat File (Whole thing, Header to Footer). Can contain as many incidents as desired. Body should be formatted as text/plain. No authentication/authorization is required for use. | This Endpoint will take an existing LIBRS Flat File, and convert it to an RVO. This is useful when first getting started so you can see how the old Flat File segments have been converted into Objects. This endpoint does not store any data, and cannot be used for monthly submissions. | -| /api/validatefftojson | A LIBRS Flat File (Whole thing, Header to Footer). Can contain as many incidents as desired. Body should be formatted as text/plain. No authentication/authorization is required for use. | Similar to FFtoJSON, this endpoint will also validate the converted JSON File, returning both the converted RVO and validations of the Incident(s) to the User. | +| Endpoint | Body Requirement | Description | +| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| /api/jsonvalidate | An RVO (Root Validation Object) containing an array of LIBRS Incidents to be processed. Body should be formatted as application/json. No authentication/authorization is required for validation. | This is the API Endpoint that will take one an RVO with any number of JSON-formatted LIBRS Incidents, and return the validation plus the original object as an extended RVO. Can be used to both validate and submit data. | +| /api/fftojson | A LIBRS Flat File (Whole thing, Header to Footer). Can contain as many incidents as desired. Body should be formatted as text/plain. No authentication/authorization is required for use. | This Endpoint will take an existing LIBRS Flat File, and convert it to an RVO. This is useful when first getting started so you can see how the old Flat File segments have been converted into Objects. This endpoint does not store any data, and cannot be used for monthly submissions. | +| /api/validatefftojson | A LIBRS Flat File (Whole thing, Header to Footer). Can contain as many incidents as desired. Body should be formatted as text/plain. No authentication/authorization is required for use. | Similar to FFtoJSON, this endpoint will also validate the converted JSON File, returning both the converted RVO and validations of the Incident(s) to the User. |
-Note: As of 10/2021, the JSONValidate Endpoint has been set to validation-only mode. When sufficient testing with vendors has been performed, we'll enable it to also allow for data to be directly submitted through that endpoint. +Note: As of 10/2021, the JSONValidate Endpoint has been set to validation-only mode. When sufficient testing with vendors has been performed, we'll enable it to also allow for data to be directly submitted through that endpoint.
## Root Validation Object + This is the primary object that is used in the JSON Validator. It contains the following properties/objects: -| Property Name | Data Type | Description | Required | -| -------------------------------------- | ----------------------- | ------------------------------------------------------------ | --------------------------------------- | -| Spec | String | LIBRS Spec version that the file follows (currently 2.5) | Yes | -| Ori | String | ORI of the Submitting Agency | Yes | -| ReportYear | Integer | 4-Digit Reporting Period Year | Yes | -| ReportMonth | Integer | Reporting Period Month | Yes | -| AgencyName | String | Descriptive Name of the Agency | No (Legacy DE - Not used in validation) | -| SoftwareID | String | Name of the RMS Generating the Data | Yes | -| SoftwareVersion | String | Version of the RMS Generating the Data | Yes | -| ForSubmission | Boolean | Boolean that tells us if you're just validating the data in the file, or if you want to actually submit it to us. | No (Assumed False if missing or NULL) | -| ZeroReport | Boolean | Boolean that tells us there's no data for this Agency for the specified Reporting Period and Year | No (Assumed False if missing or NULL) | -| [IncidentList](#librs-incident-object) | List of Librs Incidents | The actual Incident Data in the form of a List of the LibrsIncident object. | Yes | - -___ +| Property Name | Data Type | Description | Required | +| ----------------------------------- | ----------------------- | ----------------------------------------------------------------------------------------------------------------- | --------------------------------------- | +| Spec | String | LIBRS Spec version that the file follows (currently 2.5) | Yes | +| Ori | String | ORI of the Submitting Agency | Yes | +| ReportYear | Integer | 4-Digit Reporting Period Year | Yes | +| ReportMonth | Integer | Reporting Period Month | Yes | +| AgencyName | String | Descriptive Name of the Agency | No (Legacy DE - Not used in validation) | +| SoftwareID | String | Name of the RMS Generating the Data | Yes | +| SoftwareVersion | String | Version of the RMS Generating the Data | Yes | +| ForSubmission | Boolean | Boolean that tells us if you're just validating the data in the file, or if you want to actually submit it to us. | No (Assumed False if missing or NULL) | +| ZeroReport | Boolean | Boolean that tells us there's no data for this Agency for the specified Reporting Period and Year | No (Assumed False if missing or NULL) | +| [IncidentList](#librs-incident-object) | List of Librs Incidents | The actual Incident Data in the form of a List of the LibrsIncident object. | Yes | + +---
@@ -59,7 +62,7 @@ ___ Before we get too far into things, here's a quick example of the entire RVO (Root Validation Object): -``` json +```json { "spec": "2.5", "ori": "LA0320100", @@ -161,53 +164,51 @@ Before we get too far into things, here's a quick example of the entire RVO (Roo } ``` -___ +---
## [Librs Incident Object](#librs-incident-object) -The LibrsIncident object is the object that will be populated for each Incident that is being submitted. You'll notice that not all Flat File Segments are represented by child objects. This is because we have been working on simplifying the objects where we can. For instance, Segment 41 - Offender Using/Gaming is gone, and instead represented by a property in the Offender Object. +The LibrsIncident object is the object that will be populated for each Incident that is being submitted. You'll notice that not all Flat File Segments are represented by child objects. This is because we have been working on simplifying the objects where we can. For instance, Segment 41 - Offender Using/Gaming is gone, and instead represented by a property in the Offender Object. -***THIS IS SUBJECT TO CHANGE*** - Don't hold this as gospel. We will probably make more changes to this to make things simpler, like rolling in the Arrestee Statute Segment into the Arrestee, as well. +***THIS IS SUBJECT TO CHANGE*** - Don't hold this as gospel. We will probably make more changes to this to make things simpler, like rolling in the Arrestee Statute Segment into the Arrestee, as well. Basically, the only things that are required are what make it an Incident - Admin, Offense, and a Victim. And we also need to know the Incident Number and if it's an insertion or a deletion, so Action Type and Incident Number are also needed. Everything else can be left out of the JSON Object if it's not relevant (EG: Property Segment 30 for an Aggravated Assault). -| Property Name | Data Type | Description | Required | -| ------------------------------------------- | ------------------------------- | ------------------------------------------------------------ | ---------------------------------- | -| ActionType | String | Action Type for this Incident (Insert, Delete, etc...) | Yes | -| IncidentNumber | String | Incident Number of this Incident | Yes | -| [Admin](#admin-object) | Admin Object | Admin Segment (10) represented as a C# Object | Yes | -| [Offense](#offense-object) | List of Offense Objects | List of Offense Segments (20) represented as a C# Object | Yes | -| [PropertySeg](#property-object) | PropertySeg Object | Property Segment (30) represented as a C# Object | No | -| [PropDesc](#property-description-object) | List of PropDesc Objects | List of Property Description Segments (31) represented as a C# Object | No | +| Property Name | Data Type | Description | Required | +| ---------------------------------------- | ------------------------------- | ------------------------------------------------------------------------------ | ---------------------------------- | +| ActionType | String | Action Type for this Incident (Insert, Delete, etc...) | Yes | +| IncidentNumber | String | Incident Number of this Incident | Yes | +| [Admin](#admin-object) | Admin Object | Admin Segment (10) represented as a C# Object | Yes | +| [Offense](#offense-object) | List of Offense Objects | List of Offense Segments (20) represented as a C# Object | Yes | +| [PropertySeg](#property-object) | PropertySeg Object | Property Segment (30) represented as a C# Object | No | +| [PropDesc](#property-description-object) | List of PropDesc Objects | List of Property Description Segments (31) represented as a C# Object | No | | [PropertyOffense](#property-offense-object) | List of PropertyOffense Objects | List of Property/Offense Relationship Segments (33) represented as a C# Object | No | -| [Offender](#offender-object) | List of Offender Objects | List of Offender Segments (40) represented as a C# Object | No | -| [Victim](#victim-object) | List of Victim Objects | List of Victim Segments (50) represented as a C# Object | Yes | -| [Arrestee](#arrestee-object) | List of Arrestee Objects | List of Arrestee Segments (60) represented as a C# Object | No | -| [Errors](#errors-object) | List of Error Objects | List of LIBRS Errors represented as a C# Object | No (Returned back in API Response) | -| [Warnings](warnings-object) | List of Warning Objects | List of LIBRS Warnings represented as a C# Object | No (Returned back in API Response) | +| [Offender](#offender-object) | List of Offender Objects | List of Offender Segments (40) represented as a C# Object | No | +| [Victim](#victim-object) | List of Victim Objects | List of Victim Segments (50) represented as a C# Object | Yes | +| [Arrestee](#arrestee-object) | List of Arrestee Objects | List of Arrestee Segments (60) represented as a C# Object | No | +| [Errors](#errors-object) | List of Error Objects | List of LIBRS Errors represented as a C# Object | No (Returned back in API Response) | +| [Warnings](warnings-object) | List of Warning Objects | List of LIBRS Warnings represented as a C# Object | No (Returned back in API Response) |
-___ +---
### [Admin Object](#admin-object) -This is a C# Object that represents the existing Administrative Segment (10) from the Flat File. Some properties have been pulled out into the Root Validation Object (RVO) and thus don't need to be repeated here or in other segments. +This is a C# Object that represents the existing Administrative Segment (10) from the Flat File. Some properties have been pulled out into the Root Validation Object (RVO) and thus don't need to be repeated here or in other segments. -| Property Name | Data Type | Description | Required | -| -------------------- | --------- | ------------------------------------------------------------ | --------------------------------------------------------- | -| Location | String | 12-Character String of the Incident Location Type (DE 9) | No (Defaults to blank spaces) | -| StationID | String | 6-Character String of the Agency's Station ID (DE L54) | No (Defaults to blank spaces) | -| IncidentDate | DateTime | **UTC** Formatted Datetime of the Incident (DE 3) | Yes | -| IsReportingDate | Boolean | Boolean that replaces the R Modifier in DE 3 | No (Defaults False) | +| Property Name | Data Type | Description | Required | +| -------------------- | --------- | --------------------------------------------------------------------------------------- | --------------------------------------------------------- | +| Location | String | 12-Character String of the Incident Location Type (DE 9) | No (Defaults to blank spaces) | +| StationID | String | 6-Character String of the Agency's Station ID (DE L54) | No (Defaults to blank spaces) | +| IncidentDate | DateTime | **UTC** Formatted Datetime of the Incident (DE 3) | Yes | +| IsReportingDate | Boolean | Boolean that replaces the R Modifier in DE 3 | No (Defaults False) | | ClearedExceptionally | String | 1-Character String to represent the Exceptional Clearance Status of the Incident (DE 4) | No (Defaults to "N" for None) | -| ExcpClearDate | DateTime | UTC Formatted Datetime of the Exceptional Clearance Date (DE 5) | If ClearedExceptionally is not N, then Yes. Otherwise No. | - - +| ExcpClearDate | DateTime | UTC Formatted Datetime of the Exceptional Clearance Date (DE 5) | If ClearedExceptionally is not N, then Yes. Otherwise No. | **Example** @@ -222,29 +223,27 @@ This is a C# Object that represents the existing Administrative Segment (10) fro } ``` -___ +---
### [Offense Object](#offense-object) -This is a C# Object that represents the existing Offense Segment (20) from the Flat File. You can include as many as required in the form of an array of these objects. - -| Property Name | Data Type | Description | Required | -| ------------------------- | --------------- | ------------------------------------------------------------ | ------------------------------------------------------------ | -| OffenseSequenceNum | Integer | Number to Uniquely Identify the Offense (DE L6) | Yes | -| AttemptedCompleted | String | 1-Digit Character (A for Attempted, or C for Completed) that depicts if the offense was Attempted or fully committed (Completed) (DE 7) | Yes | -| OffConnecttoVic | Integer | Number that links the Offense to a single Victim via the Victim's Sequence Number (DE 24) | Yes | -| LocationType | Integer | Number that describes the Location in which the Offense took place (DE 9) | No | -| Premises | Integer | Number that describes the Number of Premises an Offender Entered (DE 10) | Yes if the Offense is Burglary and Location Type is 14 or 19, otherwise, no | -| MethodOfEntry | String | 1-Digit Character (F for Force, or N for No Force) that describes how the Offender entered a location in case of a Burglary. (DE 11) | Yes if the Offense is Burglary, otherwise, no | -| CriminalActivity | List of Strings | List (up to three) 1-Digit Characters to represent three types of Criminal Activity/Gang Information involved in an Offense (DE 12) | Yes | -| [Weapons](#weapon-object) | List of Weapons | List of the [Weapons Object](#weapon-object), which contains a property for the weapon type, if it was an automatic firearm, if a firearm was stolen, and if a firearm was discharged in committing the offense (New DE) | No (Defaults to Empty List) | -| CargoTheft | Boolean | Boolean value to indicate whether or not an Offense involved cargo theft. If any are true, the Incident-Level DE for the NIBRS Report will also reflect True, but for Louisiana we want to know about the individual Offense. | No (Defaults to False) | -| AgencyAssignedNibrs | String | 3-Digit String of the NIBRS Code of the Offense at hand. (DE N6) | Yes | -| LrsNumber | String | Up to 12-Digits of Characters to represent the Louisiana Revised Statute (LRS) Code of the Offense at hand (DE 6) | Yes | - - +This is a C# Object that represents the existing Offense Segment (20) from the Flat File. You can include as many as required in the form of an array of these objects. + +| Property Name | Data Type | Description | Required | +| ---------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- | +| OffenseSequenceNum | Integer | Number to Uniquely Identify the Offense (DE L6) | Yes | +| AttemptedCompleted | String | 1-Digit Character (A for Attempted, or C for Completed) that depicts if the offense was Attempted or fully committed (Completed) (DE 7) | Yes | +| OffConnecttoVic | Integer | Number that links the Offense to a single Victim via the Victim's Sequence Number (DE 24) | Yes | +| LocationType | Integer | Number that describes the Location in which the Offense took place (DE 9) | No | +| Premises | Integer | Number that describes the Number of Premises an Offender Entered (DE 10) | Yes if the Offense is Burglary and Location Type is 14 or 19, otherwise, no | +| MethodOfEntry | String | 1-Digit Character (F for Force, or N for No Force) that describes how the Offender entered a location in case of a Burglary. (DE 11) | Yes if the Offense is Burglary, otherwise, no | +| CriminalActivity | List of Strings | List (up to three) 1-Digit Characters to represent three types of Criminal Activity/Gang Information involved in an Offense (DE 12) | Yes | +| [Weapons](#weapon-object) | List of Weapons | List of the[Weapons Object](#weapon-object), which contains a property for the weapon type, if it was an automatic firearm, if a firearm was stolen, and if a firearm was discharged in committing the offense (New DE) | No (Defaults to Empty List) | +| CargoTheft | Boolean | Boolean value to indicate whether or not an Offense involved cargo theft. If any are true, the Incident-Level DE for the NIBRS Report will also reflect True, but for Louisiana we want to know about the individual Offense. | No (Defaults to False) | +| AgencyAssignedNibrs | String | 3-Digit String of the NIBRS Code of the Offense at hand. (DE N6) | Yes | +| LrsNumber | String | Up to 12-Digits of Characters to represent the Louisiana Revised Statute (LRS) Code of the Offense at hand (DE 6) | Yes | **Example** @@ -294,7 +293,7 @@ This is a C# Object that represents the existing Offense Segment (20) from the F ] ``` -___ +---
@@ -302,15 +301,13 @@ ___ This is a C# Object that represents the existing Property Segment (30) from the Flat File. This Object is optional if you have no information to give us (EG: The only offense is an Aggravated Assault and has nothing to do with stolen vehicles). If you don't include it, we fill in a blank object automatically, so the number of stolen and recovered vehicles will be the same as if they were left as blank spaces in the Flat File. -This may go away in the future and be tallied based on the Property Descriptions that are given to us, since all it contains is the number of stolen and recovered vehicles. +This may go away in the future and be tallied based on the Property Descriptions that are given to us, since all it contains is the number of stolen and recovered vehicles. -| Property Name | Data Type | Description | Required | -| ---------------------- | --------- | ------------------------------------------------------------ | -------- | +| Property Name | Data Type | Description | Required | +| ---------------------- | --------- | -------------------------------------------------------------------------------- | -------- | | NumOfStolenVehicles | Integer | Number to define the number of vehicles that were stolen in an Incident. (DE 18) | No | | NumOfRecoveredVehicles | Integer | Number to define the number of vehicles that were stolen in an Incident. (DE 19) | No | - - **Example** ```json @@ -320,26 +317,24 @@ This may go away in the future and be tallied based on the Property Descriptions } ``` -___ +---
### [Property Description Object](#property-description-object) -This is a C# Object that represents the existing Property Description Segment (31) from the Flat File. You can include as many as you like as an array of this object. +This is a C# Object that represents the existing Property Description Segment (31) from the Flat File. You can include as many as you like as an array of this object. -| Property Name | Data Type | Description | Required | -| ------------------- | --------- | ------------------------------------------------------------ | ----------------------------- | -| PropertySeqNum | Integer | Number to uniquely identify the Property that's being described (DE P1) | Yes | -| PropertyLossType | Integer | Number to describe the Loss Type of the Property that is being Described. (DE 14) | Yes | -| PropertyDescription | Integer | Numbered Code that's used to describe what the actual property is (DE 15) | Yes | -| PropertyValue | Integer | Number that's used to identify the value of the Property that's being described (DE 16) | No | -| DateRecovered | Datetime | **UTC** Datetime of when the Property was Recovered (DE 17) | No | +| Property Name | Data Type | Description | Required | +| ------------------- | --------- | ------------------------------------------------------------------------------------------------------------- | ----------------------------- | +| PropertySeqNum | Integer | Number to uniquely identify the Property that's being described (DE P1) | Yes | +| PropertyLossType | Integer | Number to describe the Loss Type of the Property that is being Described. (DE 14) | Yes | +| PropertyDescription | Integer | Numbered Code that's used to describe what the actual property is (DE 15) | Yes | +| PropertyValue | Integer | Number that's used to identify the value of the Property that's being described (DE 16) | No | +| DateRecovered | Datetime | **UTC** Datetime of when the Property was Recovered (DE 17) | No | | SuspectedDrugType | String | 2-Digit String that is used to Identify the kind of drug the Property is if its Description is "Drug" (DE 20) | No (Defaults to blank spaces) | -| EstimatedDrugQty | Decimal | Decimal Number to represent the quantity of a drug based on the selected Measurement Type (DE 21) | No | -| TypeDrugMeas | String | 2-Digit String of the shortcode for the measurement type (DE 22) | No (Defaults to blank spaces) | - - +| EstimatedDrugQty | Decimal | Decimal Number to represent the quantity of a drug based on the selected Measurement Type (DE 21) | No | +| TypeDrugMeas | String | 2-Digit String of the shortcode for the measurement type (DE 22) | No (Defaults to blank spaces) | **Example** @@ -368,7 +363,7 @@ This is a C# Object that represents the existing Property Description Segment (3 ] ``` -___ +---
@@ -376,13 +371,11 @@ ___ This is a C# Object that represents the existing Property Offense Relationship Segment (33) from the Flat File. You can include as many as you like as an array of this object. It's just a simple pair of Property Sequence Numbers and Offense Numbers so we can accurately link together the Properties to their associated Offense(s). -| Property Name | Data Type | Description | Required | -| ---------------------- | --------- | ------------------------------------------------------------ | -------- | -| PropertySequenceNumber | Integer | Number to identify the Property we want to relate to an Offense (DE P1R) | Yes | +| Property Name | Data Type | Description | Required | +| ---------------------- | --------- | ---------------------------------------------------------------------------- | -------- | +| PropertySequenceNumber | Integer | Number to identify the Property we want to relate to an Offense (DE P1R) | Yes | | OffenseSequenceNumber | Integer | Number to uniquely identify the Offense that the Property goes with (DE L6R) | Yes | - - **Example** ```json @@ -398,28 +391,26 @@ This is a C# Object that represents the existing Property Offense Relationship S ] ``` -___ +---
### [Offender Object](#offender-object) -This is a C# Object that represents the existing Offender Segment (40) from the Flat File. You can include as many as you like as an array of this object. It also wraps the Offender Using Segment (41) into it, so that Segment/Object doesn't exist. - -| Property Name | Data Type | Description | Required | -| -------------- | --------------- | ------------------------------------------------------------ | -------- | -| OffenderSeqNum | String | Number to uniquely identify the Offender that's being specified (Currently Left Padded with Zeros, but will probably become just an Integer in the future) (DE 36) | Yes | -| Age | Integer | Number to represent the Offender's Age | Yes | -| EstimatedAge | Boolean | True/False value to tell us if the Age is an Estimate (replaces the "E" Modifier from the Flat File) | No | -| Dob | DateTime | **UTC** Datetime of the Offender's Birthdate | No | -| Sex | String | 1-Digit Character to represent the biological sex of the Offender M, F, or U | Yes | -| Race | String | 1-Digit Character to represent the race of the Offender | Yes | -| Gender | String | 3-Digit Character String to represent the Gender Identity of the Offender. Note, we don't actually have any requirements for this right now, but it is a thing. | No | -| BiasMotivation | Integer | Number to represent the Bias/Motivation Type | Yes | -| Ethnicity | String | 1-Digit Character to represent the Ethnicity of the Offender | Yes | -| UsingGaming | List of Strings | List of 1-Digit Strings to represent the Using/Gaming Motivation Types of the Offender | Yes | - - +This is a C# Object that represents the existing Offender Segment (40) from the Flat File. You can include as many as you like as an array of this object. It also wraps the Offender Using Segment (41) into it, so that Segment/Object doesn't exist. + +| Property Name | Data Type | Description | Required | +| -------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | +| OffenderSeqNum | String | Number to uniquely identify the Offender that's being specified (Currently Left Padded with Zeros, but will probably become just an Integer in the future) (DE 36) | Yes | +| Age | Integer | Number to represent the Offender’s Age. 1-99 for Age in years. If it is impossible to determine even an Estimated Age of the Offender, then enter Unknown (‘0’). If the Offender’s Age is NOT KNOWN, estimate the Offender’s Age. If a range is given for the Offender’s Age, enter the median (average) age of the range (rounded down). Estimated Age should be set to True if the age is estimated.Number to represent the Offender's Ag | Yes | +| EstimatedAge | Boolean | True/False value to tell us if the Age is an Estimate (replaces the "E" Modifier from the Flat File) | No | +| Dob | DateTime | **UTC** Datetime of the Offender's Birthdate | No | +| Sex | String | 1-Digit Character to represent the biological sex of the Offender M, F, or U | Yes | +| Race | String | 1-Digit Character to represent the race of the Offender | Yes | +| Gender | String | 3-Digit Character String to represent the Gender Identity of the Offender. Note, we don't actually have any requirements for this right now, but it is a thing. | No | +| BiasMotivation | Integer | Number to represent the Bias/Motivation Type | Yes | +| Ethnicity | String | 1-Digit Character to represent the Ethnicity of the Offender | Yes | +| UsingGaming | List of Strings | List of 1-Digit Strings to represent the Using/Gaming Motivation Types of the Offender | Yes | **Example** @@ -442,40 +433,34 @@ This is a C# Object that represents the existing Offender Segment (40) from the ] ``` - - -___ +---
### [Victim Object](#victim-object) -This is a C# Object that represents the existing Offender Segment (40) from the Flat File. You can include as many as you like as an array of this object. Please note that it also includes the Victim Injury Segment (51) and the Victim/Offender Relationship (52) in it, so those are no longer separate Segments/Objects to be reported. - - - -| Property Name | Data Type | Description | Required | -| --------------------------- | ---------------------- | ------------------------------------------------------------ | -------------------------------------- | -| VictimSeqNum | Integer | Number to uniquely identify the Victim that's being specified (DE 36) | Yes | -| VictimType | String | 1-Digit Character to represent the Type of Victim being described | Yes | -| Age | Integer | String to represent the Victim's Age | Yes | -| EstimatedAge | Boolean | True/False value to tell us if the age of the Victim is an Estimate (replaces the E Modifier from Flat File) | No | -| Dob | DateTime | **UTC** Datetime of the Victim's Birthdate | No | -| Sex | String | 1-Digit Character to represent the Biological Sex of the Victim - M, F, or U | Yes | -| Race | String | 1-Digit Character to represent the Race of the Victim | Yes | -| Gender | String | 3-Digit Character String to represent the Gender Identity of the Victim. Note, we don't actually have any requirements for this right now, but it is a thing. | No | -| Ethnicity | String | 1-Digit Character to represent the Ethnicity of the Victim | Yes | -| ResidentStatus | String | 1-Digit Character to represent the Permanent Resident/Citizenship status of the Victim. | No | -| AggravatedAssault | List of Integers | List of up to two Numbers to describe the Aggravated Assault Circumstances, Negligent Manslaughter Circumstances, or Justifiable Homicide Circumstances (Dependent on the NIBRS Code of the Offense the Victim is associated with). | 13A, 09A, 09B, & 09C | -| AdditionalHomicide | String | 1-Digit Character to further describe the circumstances surrounding an 09C - Justifiable Homicide. | If Offense related to Victim is 09C | +This is a C# Object that represents the existing Offender Segment (40) from the Flat File. You can include as many as you like as an array of this object. Please note that it also includes the Victim Injury Segment (51) and the Victim/Offender Relationship (52) in it, so those are no longer separate Segments/Objects to be reported. + +| Property Name | Data Type | Description | Required | +| --------------------------- | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------- | +| VictimSeqNum | Integer | Number to uniquely identify the Victim that's being specified (DE 36) | Yes | +| VictimType | String | 1-Digit Character to represent the Type of Victim being described | Yes | +| Age | String | String to represent the Victim’s Age. 0-99, NN, NB, or BB is allowed. Use 0 for Unknown victims. NN for NeoNatal, NB for Newborn, and BB for Baby.String to represent the Victim's Ag | Yes | +| EstimatedAge | Boolean | True/False value to tell us if the age of the Victim is an Estimate (replaces the E Modifier from Flat File) | No | +| Dob | DateTime | **UTC** Datetime of the Victim's Birthdate | No | +| Sex | String | 1-Digit Character to represent the Biological Sex of the Victim - M, F, or U | Yes | +| Race | String | 1-Digit Character to represent the Race of the Victim | Yes | +| Gender | String | 3-Digit Character String to represent the Gender Identity of the Victim. Note, we don't actually have any requirements for this right now, but it is a thing. | No | +| Ethnicity | String | 1-Digit Character to represent the Ethnicity of the Victim | Yes | +| ResidentStatus | String | 1-Digit Character to represent the Permanent Resident/Citizenship status of the Victim. | No | +| AggravatedAssault | List of Integers | List of up to two Numbers to describe the Aggravated Assault Circumstances, Negligent Manslaughter Circumstances, or Justifiable Homicide Circumstances (Dependent on the NIBRS Code of the Offense the Victim is associated with). | 13A, 09A, 09B, & 09C | +| AdditionalHomicide | String | 1-Digit Character to further describe the circumstances surrounding an 09C - Justifiable Homicide. | If Offense related to Victim is 09C | | PrecipitatingOffense | String | 3-Digit NIBRS Code of the Offense that the Victim was committing when an 09C - Justifiable Homicide occurred. Note that the Victim of an 09C is the Offender of another Offense. This offense may or may not be reported alongside the 09C, so this DE is intended to capture that in case it isn't. | If Offense related to Victim is 09C | -| OfficerActivityCircumstance | Integer | Number to describe the actions/activities an Officer was performing when they became the Victim of an Offense. | If Victim is Type "L" | -| OfficerAssignmentType | String | 1-Digit Character to describe the role the Officer that was the Victim of an Offense was performing/a part of when the Offense occurred. | If Victim is Type "L" | -| OfficerOri | String | 9-Digit String of the Victim Officer's ORI Number | If Victim is Type "L" | -| InjuryType | String | 1-Digit Character to represent the Injury Type of the Victim | For Crimes Against Person | -| RelatedOffenders | List of VicOff Objects | Object that contains the Victim Sequence Number, Offender Sequence Number, and their relationship. This will get revised to only be the Offender Number and Relationship. | For Crimes Against Person and Property | - - +| OfficerActivityCircumstance | Integer | Number to describe the actions/activities an Officer was performing when they became the Victim of an Offense. | If Victim is Type "L" | +| OfficerAssignmentType | String | 1-Digit Character to describe the role the Officer that was the Victim of an Offense was performing/a part of when the Offense occurred. | If Victim is Type "L" | +| OfficerOri | String | 9-Digit String of the Victim Officer's ORI Number | If Victim is Type "L" | +| InjuryType | String | 1-Digit Character to represent the Injury Type of the Victim | For Crimes Against Person | +| RelatedOffenders | List of VicOff Objects | Object that contains the Victim Sequence Number, Offender Sequence Number, and their relationship. This will get revised to only be the Offender Number and Relationship. | For Crimes Against Person and Property | **Example** @@ -484,7 +469,7 @@ This is a C# Object that represents the existing Offender Segment (40) from the { "victimSeqNum": 1, "victimType": "I", - "age": 33, + "age": "33", "estimatedAge": false, "dob": null, "sex": "F", @@ -511,7 +496,7 @@ This is a C# Object that represents the existing Offender Segment (40) from the } ``` -___ +---
@@ -519,29 +504,26 @@ ___ This is a C# Object that represents the existing Arrestee Segment (60) from the Flat File. You can include as many as you like as an array of this object. - - -| Property Name | Data Type | Description | Required | -| ------------------------- | ------------------ | ------------------------------------------------------------ | ---------------------------- | -| ArrestSeqNum | Integer | Number to uniquely identify the Arrestee that's being specified (DE 36) | Yes | -| ArrestNumber | String | 12-Digit Alpha/Numeric String of Characters that uniquely identifies the Arrest in the Agency's RMS | Yes | -| ArrTransactionNumber | String | 15-Digit Alpha/Numeric String of Characters that uniquely Identifies the Arrestee in AFIS (DE L55) | Yes | -| ArresteeName | String | 20-Digit Character String of the Arrestee's Name. Should be in the format of (Last)(Suffix),(First)(Middle) | No | -| ArrestDate | DateTime | **UTC** Datetime of the Arrest | Yes | -| ArrestType | String | 1-Digit Character to describe the nature of how the Arrest was Initiated - O, S, or T. | Yes | -| MultipleArresteeIndicator | String | 1-Digit Character that indicates if this Arrest should be counted towards the number of *people* arrested by an Agency. Sometimes an Offender will appear multiple times in the same Incident, or across multiple Incidents. Their arrest for one of these Offenses will subsequently "clear" the others, but since they were only physically arrested one time, the MAI should be used to denote that the Arrest record shouldn't affect the number of *people* the agency has arrested, only the number of Offenses cleared by arrest. | Yes | -| Age | Integer | Number to represent the Arrestee's Age. | Yes | -| Dob | DateTime | **UTC** Datetime of the Arrestee's Birthdate | No | -| Sex | String | 1-Digit Character to represent the Biological Sex of the Arrestee - M, F, or U | Yes | -| Race | String | 1-Digit Character to represent the Race of the Arrestee | Yes | -| Gender | String | 3-Digit Character String to represent the Gender Identity of the Arrestee. Note, we don't actually have any requirements for this right now, but it is a thing. | No | -| Ethnicity | String | 1-Digit Character to represent the Ethnicity of the Arrestee | Yes | -| ResidentStatus | String | 1-Digit Character to represent the Permanent Resident/Citizenship status of the Arrestee. | No | -| DispositionUnder17 | String | 1-Digit Character used to describe how an Arrestee 17 years of age or younger was handled by the Agency. | If Arrestee is 17 or younger | -| ArrestArmed | List of Weapon | List of [Weapon Objects](#weapon-object) (Same as in the Offense Object) that were found on the Arrestee's person at the time of Arrest. | Yes | -| ArrestStatute | List of ArrStatute | List of the [Arrestee Statute Objects](#arrestee-statute-object) associated with the Arrestee | Yes | - - +| Property Name | Data Type | Description | Required | +| ------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------- | +| ArrestSeqNum | Integer | Number to uniquely identify the Arrestee that's being specified (DE 36) | Yes | +| ArrestNumber | String | 12-Digit Alpha/Numeric String of Characters that uniquely identifies the Arrest in the Agency's RMS | Yes | +| ArrTransactionNumber | String | 15-Digit Alpha/Numeric String of Characters that uniquely Identifies the Arrestee in AFIS (DE L55) | Yes | +| ArresteeName | String | 20-Digit Character String of the Arrestee's Name. Should be in the format of (Last)(Suffix),(First)(Middle) | No | +| ArrestDate | DateTime | **UTC** Datetime of the Arrest | Yes | +| ArrestType | String | 1-Digit Character to describe the nature of how the Arrest was Initiated - O, S, or T. | Yes | +| MultipleArresteeIndicator | String | 1-Digit Character that indicates if this Arrest should be counted towards the number of*people* arrested by an Agency. Sometimes an Offender will appear multiple times in the same Incident, or across multiple Incidents. Their arrest for one of these Offenses will subsequently "clear" the others, but since they were only physically arrested one time, the MAI should be used to denote that the Arrest record shouldn't affect the number of *people* the agency has arrested, only the number of Offenses cleared by arrest. | Yes | +| Age | Integer | 1-99 for Age in years. If it is impossible to determine even an Estimated Age of the Arrestee, then enter Unknown (‘0’). If the Arrestee’s Age is NOT KNOWN, estimate the Arrestee Age. If a range is given for the Arrestee’s Age, enter the median (average) age of the range (rounded down). Estimated Age should be set to True if the age is estimated | Yes | +| EstimatedAge | Boolean | True/False value to tell us if the age of the Victim is an Estimate (replaces the E Modifier from Flat File) | No | +| DobDob | DateTime | **UTC** Datetime of the Arrestee's Birthdate | No | +| Sex | String | 1-Digit Character to represent the Biological Sex of the Arrestee - M, F, or U | Yes | +| Race | String | 1-Digit Character to represent the Race of the Arrestee | Yes | +| Gender | String | 3-Digit Character String to represent the Gender Identity of the Arrestee. Note, we don't actually have any requirements for this right now, but it is a thing. | No | +| Ethnicity | String | 1-Digit Character to represent the Ethnicity of the Arrestee | Yes | +| ResidentStatus | String | 1-Digit Character to represent the Permanent Resident/Citizenship status of the Arrestee. | No | +| DispositionUnder18 | String | Options in this field are as follows: D - Handled Within Department and Released. J - Referred to Juvenile Court or Probation Department W - Referred to Welfare Agency P - Referred to Other Police Agency A - Referred to Criminal or Adult Court The Federal UCR program considers juveniles as under 18 years of age regardless of state law. The LIBRS program will stay aligned with the FBI even though the Juvenile Age definition has changed. If the arrestee is 17 and considered an adult in Louisiana, please use A – Referred to Criminal or Adult Court. | If Arrestee is 17 or younger | +| ArrestArmed | List of Weapon | List of[Weapon Objects](#weapon-object) (Same as in the Offense Object) that were found on the Arrestee's person at the time of Arrest. | Yes | +| ArrestStatute | List of ArrStatute | List of the[Arrestee Statute Objects](#arrestee-statute-object) associated with the Arrestee | Yes | **Example** @@ -556,13 +538,14 @@ This is a C# Object that represents the existing Arrestee Segment (60) from the "arrestType": "O", "multipleArresteeIndicator": "N", "age": 37, + "estimatedAge": false, "dob": "1980-01-31T00:00:00Z", "sex": "M", "gender": " ", "race": "W", "ethnicity": "U", "residentStatus": "U", - "dispositionUnder17": " " + "dispositionUnder18": " " "arrestArmed": [{ "weaponForce": "40", @@ -584,28 +567,26 @@ This is a C# Object that represents the existing Arrestee Segment (60) from the ] ``` -___ +---
### [Errors Object](#errors-object) -The Errors Object is equivalent to the Error Details that are provided in the Flat File's Error Detail Report. We provide them back here so that the JSON Validator's API can be called within the RMS, and errors can be directly returned to the User. +The Errors Object is equivalent to the Error Details that are provided in the Flat File's Error Detail Report. We provide them back here so that the JSON Validator's API can be called within the RMS, and errors can be directly returned to the User. -This is a Read-Only object, you won't be sending this along with your data, only getting it back. +This is a Read-Only object, you won't be sending this along with your data, only getting it back. -| Property Name | Data Type | Description | -| -------------- | --------- | ------------------------------------------------------------ | -| ErrorCode | Integer | The Error Code of the Error (Typically a 5-Digit Number) | -| ErrorMsg | String | The text of the Error Code describing what's wrong | -| Contents | String | The particular data that was submitted that the validation had an issue with | -| DataElem | String | The particular data elements that the validation had an issue with | -| IncidentNumber | String | The Incident Number that the validation had an issue with | +| Property Name | Data Type | Description | +| -------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| ErrorCode | Integer | The Error Code of the Error (Typically a 5-Digit Number) | +| ErrorMsg | String | The text of the Error Code describing what's wrong | +| Contents | String | The particular data that was submitted that the validation had an issue with | +| DataElem | String | The particular data elements that the validation had an issue with | +| IncidentNumber | String | The Incident Number that the validation had an issue with | | SegmentNumber | String | Legacy, but the equivalent of the Segment Number as it refers to the JSON Object that the validation error came from (Will get updated to just say what the name of the object was, but for now it spits out something like 20 if it doesn't like and Offense) | - - -___ +---
@@ -613,22 +594,16 @@ ___ The Warnings Object is basically the same thing as the Errors Object, but just for warnings. Makes it easy to keep the actual Errors that are preventing the Incident from being accepted separate from just Warnings about it. -This is a Read-Only object, you won't be sending this along with your data, only getting it back. +This is a Read-Only object, you won't be sending this along with your data, only getting it back. -| Property Name | Data Type | Description | -| ------------- | --------- | ------------------------------------------------------------ | -| ErrorCode | Integer | The Warning Code of the Warning (Typically a 5-Digit Number) | -| ErrorMsg | String | The text of the Warning Code describing what's wrong | +| Property Name | Data Type | Description | +| ------------- | --------- | ---------------------------------------------------------------------------- | +| ErrorCode | Integer | The Warning Code of the Warning (Typically a 5-Digit Number) | +| ErrorMsg | String | The text of the Warning Code describing what's wrong | | Contents | String | The particular data that was submitted that the validation had an issue with | -| DataElem | String | The particular data elements that the validation had an issue with | - - - -___ - - - +| DataElem | String | The particular data elements that the validation had an issue with | +---
@@ -636,7 +611,7 @@ ___ The following Objects are used within the other objects that make up an Incident. : -___ +---
@@ -644,15 +619,11 @@ ___ This is a C# Object that represents the existing Arrestee Statute Segment (62) from the Flat File. This will end up getting rolled into the Arrestee Object, but for now it is separate. - - -| Property Name | Data Type | Description | Required | -| ------------------- | --------- | ------------------------------------------------------------ | -------- | +| Property Name | Data Type | Description | Required | +| ------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | | ArrestConToOffense | String | 15-Character String that combines the Offense Sequence Number with the Incident Number EG XXXYY-YYYYYY-YY, where XXX is the Offense Sequence Number and YY-Y... is the Incident Number | Yes | -| AgencyAssignedNibrs | String | 3-Digit NIBRS Code of the Offense that the Arrestee was Arrested for. | Yes | -| LrsNumber | String | 12-Digit LRS Code (Louisiana Revised Statute Code) that the Arrestee was Arrested for. | | - - +| AgencyAssignedNibrs | String | 3-Digit NIBRS Code of the Offense that the Arrestee was Arrested for. | Yes | +| LrsNumber | String | 12-Digit LRS Code (Louisiana Revised Statute Code) that the Arrestee was Arrested for. | | **Example** @@ -671,23 +642,21 @@ This is a C# Object that represents the existing Arrestee Statute Segment (62) f ] ``` -___ +---
### [Weapon Object](#weapon-object) -This is an object that replaces the Type of Weapon/Force Data Element from the Flat File. +This is an object that replaces the Type of Weapon/Force Data Element from the Flat File. -| Property Name | Data Type | Description | Required | -| ----------------- | --------- | ------------------------------------------------------------ | ------------------- | -| WeaponForce | Integer | Number that represents the Type of Weapon Force being described | Yes | -| Automatic | Boolean | True/False value that describes if the Weapon was an Automatic Weapon or not (only relevant for Firearms) | No (Defaults False) | -| StolenFirearm | Boolean | True/False value that describes if a Firearm was Stolen (only relevant for Firearms) | No (Defaults False) | +| Property Name | Data Type | Description | Required | +| ----------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | +| WeaponForce | Integer | Number that represents the Type of Weapon Force being described | Yes | +| Automatic | Boolean | True/False value that describes if the Weapon was an Automatic Weapon or not (only relevant for Firearms) | No (Defaults False) | +| StolenFirearm | Boolean | True/False value that describes if a Firearm was Stolen (only relevant for Firearms) | No (Defaults False) | | DischargedFirearm | Boolean | True/False value that describes if a Firearm was Discharged in the course of an Offense being committed (only relevant for Firearms) | No (Defaults False) | - - **Example:** ```json @@ -700,28 +669,23 @@ This is an object that replaces the Type of Weapon/Force Data Element from the F }] ``` - - -___ +---
- - ## Legacy LIBRS Values -In order to maintain compatibility with the existing codebase, we had to bring forward some legacy data elements. When submitting data to us, you ***do not need to include any of these*** - these are here for us behind the scenes because we're using the same library you are. +In order to maintain compatibility with the existing codebase, we had to bring forward some legacy data elements. When submitting data to us, you ***do not need to include any of these*** - these are here for us behind the scenes because we're using the same library you are. Another way to look at it is this is all the stuff you had to repeat on every single segment, despite that 99% of it never changed. Cutting fluff. -| Property Name | Data Type | Description | Required | -| ----------------- | --------- | ------------------------------------------------------------ | -------- | -| EntireLineSegment | String | Entire Legacy Flat File line (Segment) that was read in | No | +| Property Name | Data Type | Description | Required | +| ----------------- | --------- | --------------------------------------------------------------------------------- | -------- | +| EntireLineSegment | String | Entire Legacy Flat File line (Segment) that was read in | No | | SegmentDescriptor | String | First two digits of the Flat File Segment to tell us what it was (10, 20, etc...) | No | -| ActionType | String | Action Type that the Segment was trying to perform | No | -| ORINumber | String | ORI of the Submitting Agency | No | -| IncidentNumber | String | Incident Number the Segment is associated with | No | -| ExpansionBuffer | String | Blank Space left for future expansion | No | -| SegmentEnd | String | ZZ at the end of the data | No | -| Padding | String | Blank Spaces to make the line 150 Characters long. | No | - +| ActionType | String | Action Type that the Segment was trying to perform | No | +| ORINumber | String | ORI of the Submitting Agency | No | +| IncidentNumber | String | Incident Number the Segment is associated with | No | +| ExpansionBuffer | String | Blank Space left for future expansion | No | +| SegmentEnd | String | ZZ at the end of the data | No | +| Padding | String | Blank Spaces to make the line 150 Characters long. | No |