spacer spacer spacer
JRSA's IBR Resource Center
Return to Main Page
Background and Status of Incident-Based Reporting and NIBRS
State Profiles
Using Incident-Based and NIBRS Data
References and Related Sites
Available Syntax and Sample Data Files
line divider
IBRRC Fact Sheet
Contribute Information
Site Map
Justice Research and Statistics Association (JRSA) Home
 
Notice of Federal Funding and Federal Disclaimer
 

Data Quality Check 5

5. Ensure that victim variables are reported where required and are correct when reported but not required.

Click here to download SPSS code
Download sample data

For those offenses for which a victim injury, an offender number to be related, or a victim-offender relationship is required, is one reported on the victim segment? The following code creates the variables necessary to perform the data quality check and creates several crosstabulation tables. When using this code, be sure to insert the path and the filename of the data file to be used. If you need any assistance working with the syntax provided, please contact us.

For nine offenses against persons -- kidnapping/abduction, forcible rape, forcible sodomy, sexual assault with an object, forcible fondling, robbery, aggravated assault, simple assault, extortion/blackmail -- the FBI coding rules require the reporting of the type of victim injury on the victim data segment. For all crimes against persons and robberies, the offender number to be related and the victim-offender relationship variables on the victim data segment are required. In addition to the nine offenses listed above, the following offenses are included in the latter requirement: murder and nonnegligent manslaughter, negligent homicide, justifiable homicide, intimidation, incest, and statutory rape. The coding rules for these data fields are listed in the FBI's Data Collection Guidelines and are incorporated into this quality control example. To illustrate how an agency can self-test, one month's data from one of the NIBRS certified localities reporting to the FBI in 1999 was modified. This example relies upon single agency data sets.

Selecting the Records for Analysis

To examine victim injury coding, you must first retrieve the victim data segment file and create a new variable called INJCHECK, initially set at zero. For each victim offense variable (V_OFF1 through 10) in the victim segment records, if the victim type (V_TYPE) is individual or "I" and the victim offense (V_OFF) is one of the nine that require the reporting of victim injury, then the new variable INJCHECK is assigned a value of 1.

GET FILE = 'Directory:\Path\Agency Data.sav'.
COMPUTE injcheck = 0.
DO REPEAT voff = v_off1 to v_off10.
IF (v_type = 'I' and
  (voff = '100' or
  voff = '11A' or
  voff = '11B' or
  voff = '11C' or
  voff = '11D' or
  voff = '120' or
  voff = '13A' or
  voff = '13B' or
  voff = '210')) injcheck = 1.
END REPEAT.

To check for the presence of victim-offender relationship codes and offender number to be related, the first step is to create a new variable (OVRCHECK) to identify the records for which these variables are required. OVRCHECK is initially set at zero. Then, for each victim offense variable (V_OFF1 through 10), if the victim type (V_TYPE) is individual and the victim offense (V_OFF) is one which requires a victim-offender relationship, then the new variable OVRCHECK is assigned a value of 1. The FBI coding rules require a victim-offender relationship (OVR) be assigned to each offender number to be related in the victim data segment.

COMPUTE ovrcheck = 0.
DO REPEAT voff = v_off1 to v_off10.
IF (v_type = 'I' and
  (voff = '09A' or
  voff = '09B' or
  voff = '09C' or
  voff = '100' or
  voff = '11A' or
  voff = '11B' or
  voff = '11C' or
  voff = '120' or
  voff = '13A' or
  voff = '13B' or
  voff = '13C' or
  voff = '36A' or
  voff = '36B')) ovrcheck = 1.
END REPEAT.

Defining Value Labels for Required Variables

Next, the valid value labels for victim injury and victim/offender relationship are assigned.

VALUE LABELS
v_inj1 to v_inj10
    'N' 'None'
    'B' 'Apparent Broken Bones'
    'I' 'Possible Internal Injury'
    'L' 'Severe Laceration'
    'M' 'Apparent Minor Injury'
    'O' 'Other Major Injury'
    'T' 'Loss of Teeth'
    'U' 'Unconsciousness'/

ovr1 to ovr10
'SE' 'Victim was Spouse'
'CS' 'Victim was Common-law Spouse'
'PA' 'Victim was Parent'
'SB' 'Victim was Sibling'
'CH' 'Victim was Child'
'GP' 'Victim was Grandparent'
'GC' 'Victim was Grandchild'
'IL' 'Victim was In-law'
'SP' 'Victim was Stepparent'
'SC' 'Victim was Stepchild'
'SS' 'Victim was Stepsibling'
'OF' 'Victim was Other Family Member'
'VO' 'Victim was Offender'
'AQ' 'Victim was Acquaintance'
'FR' 'Victim was Friend'
'NE' 'Victim was Neighbor'
'BE' 'Victim was Babysitter'
'BG' 'Victim was Boyfriend/Girlfriend'
'CF' 'Victim was Child of Boyfriend/Girlfriend'
'HR' 'Victim was Homosexual Relationship'
'XS' 'Victim was Ex-Spouse'
'EE' 'Victim was Employee'
'ER' 'Victim was Employer'
'OK' 'Victim was Otherwise Known'
'RU' 'Relationship Unknown'
'ST' 'Victim was Stranger'.

Generating the Lists and Tables

A CROSSTABS will show the joint distribution of victim injury by injury check. The existing variable V_INJ1 is the first of up to five victim injury variables. The new variable INJCHECK acts as a flag indicating that at least one of the target offenses was coded for a victim. If one of the target offenses was coded, then a victim injury should also be coded.

CROSSTABS
  /TABLES = v_inj1 BY injcheck
  /FORMAT = AVALUE TABLES
  /CELLS = COUNT .

Similar in concept to the new variable INJCHECK, OVRCHECK acts a s a flag for records that should include values for victim-offender relationship and offender number to be related. The CROSSTABS command below will generate two joint distribution tables. The first will show the first victim-offender relationship variable (OVR1) by the variable OVRCHECK. This table allows one to determine whether victim segment records that are supposed to have victim-offender relationship data (1) contain data and (2) contain valid relationship codes. The second table will show the first related offender number variable (OFNSEQ1) by the variable OVRCHECK, which allows one to verify that each victim record that requires an offender number to be related actually contains a valid value in the first occurrence of that variable (OFNSEQ1).

CROSSTABS
  /TABLES = ovr1 ofnseq1 BY ovrcheck
  /MISSING = INCLUDE
  /FORMAT = AVALUE TABLES
  /CELLS = COUNT .

To identify any records that are missing either the victim-offender relationship code (OVR1) or the related offender number (OFNSEQ1), a TEMPORARY / SELECT IF is performed. The LIST will show the originating agency identifier (ORI), incident number (INC_NUM), victim type (V_TYPE), and the first UCR offense code (V_OFF1) for any records for which the offender number to be related or victim-offender relationship are missing.

TEMPORARY.
SELECT IF (ovrcheck = 1 and (ovr1 = ' ' or sysmis(ofnseq1))).
LIST ori inc_num v_type v_off1 ofnseq1 ovr1.

As an alternative, the list above could also show the second offender number to be related (OFNSEQ2) and victim-offender relationship (OVR2). This would allow a check to see whether records that required but were missing a value in OFNSEQ1 and OVR1 might be coded with the correct values in the placeholders of the second occurrences of these variables rather than the first.

Reviewing the Lists and Tables

The first cross-tabulation table shows that at least one victim injury was reported in the first variable for victim injury (V_INJ1) if at least one of the offenses reported required the recording of a victim injury. A visual scan of the victim injury codes of V_INJ1 also shows that valid values were used for the 56 injuries reported. Further, the table shows that no victim injuries were reported in the first victim injury variable (V_INJ1) for victim offenses that did not require such reporting.

The second table shows that 56 records contain an offender to be related number, leaving one without (see victim-offender relationship table, below, with an total of 57).

The next cross-tabulation table shows that 1 of 57 victim segment records that should have had a victim-offender relationship recorded did not have a value in variable OVR1. A visual scan of the relationships in column 1 indicates that for the 56 records for which a relationship was defined, a valid value was used (there are no codes other than the ones with valid labels, below).

The corresponding list below shows the incident number for a record missing both the offender number to be related (ONFSEQ1) and victim-offender relationship (OVR1) variables. Because the same record shows a blank for the offender number to be related and the victim-offender relationship, it is possible that not enough information was available for coding. If so, then the offender number to be related should have been coded as "00". Comparing the offender sequence number on the offender segment will determine whether "00" is the appropriated code because the two values should match. Regardless, values for offender number to be related and for victim-offender relationship are required. Blank is not an allowable value for either variable.

As noted above, the list contains are the originating agency identifier, incident number, victim type, offender number to be related -- first occurrence, and victim-offender relationship -- first occurrence. The record can now be researched and corrected.

LIST

ORI        INC_NUM   V_TYPE   V_OFF1 OFNSEQ1  OVR1

XXYS248WU  123400477 I       13B     .        .

Number of cases read: 1 Number of cases listed: 1