<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE codeBook 
SYSTEM "http://www.ddialliance.org/sites/default/files/Version2-1.dtd">

<codeBook version="1.2.2" ID="ICPSR03026">
	<docDscr>
		<citation>
			<titlStmt>
				<titl>Metadata record for Evaluating a Lethality Scale for the Seattle Police Department Domestic Violence Unit, 1995-1997</titl>
			</titlStmt>
			<prodStmt>
				<producer abbr="ICPSR">
					<ExtLink URI="http://www.icpsr.umich.edu/images/icpsr-logo.gif" title="ICPSR Logo" role="image" /> 
					Inter-university Consortium for Political and Social Research
					<ExtLink URI="http://www.icpsr.umich.edu/ICPSR/" title="URL of ICPSR Web Site" />
				</producer>
				<copyright>
					ICPSR metadata records are licensed under a Creative Commons Attribution-Noncommercial 3.0 United States License <ExtLink URI="http://creativecommons.org/licenses/by-nc/3.0/us/" title="Link to full text of license" />.
				</copyright>
			</prodStmt>
			<verStmt>
				
				<version date="2013-06-20">2013-06-20</version>
			</verStmt>
			
			
				<holdings URI="http://www.icpsr.umich.edu/icpsrweb/ICPSR/ddi2/studies/3026"></holdings>
			
		</citation>
	</docDscr>
	<stdyDscr>
       <citation>
           <titlStmt>
             <titl>Evaluating a Lethality Scale for the Seattle Police Department Domestic Violence Unit, 1995-1997</titl>
 				
             <IDNo agency="ICPSR">3026</IDNo>
             <IDNo agency="CrossRef">10.3886/ICPSR03026.v1</IDNo>
           </titlStmt>
           <rspStmt>
    	
			<AuthEnty affiliation="University of Washington. Harborview Injury Prevention and Research Center">Wolf, Marsha E.</AuthEnty>
    	
			<AuthEnty affiliation="University of Washington. Harborview Injury Prevention and Research Center">Stoner, Julie</AuthEnty>
    	
			<AuthEnty affiliation="University of Washington. Harborview Injury Prevention and Research Center">Kernic, Mary A.</AuthEnty>
    	
			<AuthEnty affiliation="University of Washington. Harborview Injury Prevention and Research Center">Holt, Victoria L.</AuthEnty>
    	
			<AuthEnty affiliation="University of Washington. Harborview Injury Prevention and Research Center">Critchlow, Cathy</AuthEnty>
    	
           </rspStmt>
           <prodStmt>
				
    				
    					<fundAg>United States Department of Justice. Office of Justice Programs. National Institute of Justice</fundAg>
    				
				

    	
    		<grantNo agency="United States Department of Justice. Office of Justice Programs. National Institute of Justice">95-IJ-CX-0097</grantNo>
    	

           </prodStmt>
           <distStmt>
             <distrbtr abbr="ICPSR" affiliation="Institute for Social Research, University of Michigan" URI="http://www.icpsr.umich.edu/ICPSR/">
               <ExtLink URI="http://www.icpsr.umich.edu/images/icpsr-logo.gif" title="Logo" />
               Inter-university Consortium for Political and Social Research
               <ExtLink URI="http://www.icpsr.umich.edu/ICPSR/" title="URL" />
             </distrbtr>
             <distDate date="2001-12-21">2001-12-21</distDate>
           </distStmt>


    	
           <verStmt>
           
             <version date="2012-08-22">2012-08-22</version> 
             
             <notes>2012-08-22 A Restricted Data Use Agreement form was added to the documentation files that can be downloaded from the study home page.</notes>
           </verStmt>
    	


           <biblCit>Wolf, Marsha E., Julie Stoner, Mary A. Kernic, Victoria L. Holt, and Cathy Critchlow. Evaluating a Lethality Scale for the Seattle Police Department Domestic Violence Unit, 1995-1997. ICPSR03026-v1. Ann Arbor, MI: Inter-university Consortium for Political and Social Research [distributor], 2012-08-22. doi:10.3886/ICPSR03026.v1</biblCit>

				<holdings URI="http://dx.doi.org/10.3886/ICPSR03026.v1"></holdings>


        </citation>
      <stdyInfo>
           <subject>
		
      		<keyword vocab="thesaurus">crime prediction</keyword>
      	
      		<keyword vocab="thesaurus">criminal histories</keyword>
      	
      		<keyword vocab="thesaurus">domestic violence</keyword>
      	
      		<keyword vocab="thesaurus">felony offenses</keyword>
      	
      		<keyword vocab="thesaurus">misdemeanor offenses</keyword>
      	
      		<keyword vocab="thesaurus">program evaluation</keyword>
      	
      		<keyword vocab="thesaurus">risk assessment</keyword>
      	
		
      		<topcClas source="archive" vocab="ICPSR subject classifications">ICPSR.XVII.E</topcClas>
      	
      		<topcClas source="archive" vocab="NACJD subject classifications">NACJD.XIII</topcClas>
      	
      		<topcClas source="archive" vocab="NACJD subject classifications">NACJD.VII</topcClas>
      	
           </subject>
          <abstract>The specific aim of this project was to evaluate the
usefulness of the Seattle Police Department's (SPD) Lethality Scale in
identifying misdemeanor cases that might be high risk for escalating
violence and subsequent felony incidents. Data provide information on
11,972 unique couples with incidents occurring between January 1,
1995, and December 31, 1997, involving intimate couples in which the
suspect was at least 18 years old and the victim was at least 16,
with no age restriction for cases referred to the juvenile
division. The researchers reformatted the Domestic Violence Unit's
(DVU) database to reflect a three-year history of violence between
unique couple members. Only intimate couples were considered, meaning
suspects and victims who were married, divorced, had a child in
common, or were dating. The Lethality Scale was derived from the data
in the DVU database. It was composed of six incident characteristic
components (offense score, weapon score, location score, injury score,
personal score, and incident/other score) with varying values that
contributed to an overall score. The Total Lethality Score was the sum
of the values from these six components. The lethality score referred
to an individual only and did not reflect information about other
people involved in the incident. To interpret the score, the DVU
specified a period of time--for example, six months--and computed
lethality score values for every person involved in an incident during
this period. Information on individuals with a Total Lethality Score
over a certain cut-off was printed and reviewed by a detective. Data
are provided for up to 25 incidents per unique couple. Incident
variables in the dataset provide information on number of persons
involved in the incident, time and weekday of the incident, beat,
precinct, census tract, and place where the incident occurred, type of
primary and secondary offenses, if a warrant was served, charges
brought, final disposition, weapon type used, arrests made, court
order information, if evidence was collected, if statements or photos
were taken by the DVU, and sergeant action. Dates were converted to
time intervals and provide the number of days between the incident
date and the date the file was sent to the prosecutor, the date
charges were brought, and the date the case was officially
closed. Time intervals were also calculated for days between each
incident for that couple. Personal information on the two persons in a
couple includes age, gender, injuries and treatment, relationship and
cohabitation status of the individuals, pregnancy status of each
individual, alcohol and drug use at the time of the incident, and role
of the individual in the incident (victim, suspect,
victim/suspect). Lethality scale scores are included as well as the
number of incidents in which the unique couple was involved in 1995
and 1996, and 1989 median household income for the census tract.</abstract>
 			
           <abstract>The majority of domestic violence incidents
 involve misdemeanor cases, but Seattle Police Department (SPD)
 detectives were routinely assigned to follow only felony
 incidents. Since assigning detective follow-up for all misdemeanor
 cases was not practical, the SPD created the Lethality Scale to
 screen misdemeanor domestic violence incidents for assignment to
 detectives for follow-up. The specific aim of this project was to
 evaluate the usefulness of the Seattle Police Department's (SPD)
 Lethality Scale in identifying misdemeanor cases that might be high
 risk for escalating violence and subsequent felony
 incidents. However, it should be noted that the term "Lethality
 Scale" is a misnomer since the scale did not cover only lethal
outcomes.</abstract>
           
 			
           <abstract>Data provide information on 11,972 unique couples
 with incidents occurring between January 1, 1995, and December 31,
 1997, involving intimate couples in which the suspect was at least 18
 years old and the victim was at least 16, with no age restriction for
 cases referred to the juvenile division. The researchers reformatted
 the Domestic Violence Unit's (DVU) database to reflect a three-year
 history of violence between unique couple members. Only intimate
 couples were considered, meaning suspects and victims who were
 married, divorced, had a child in common, or were dating. An
 individual's role as suspect or victim could change from incident to
 incident, meaning in one incident the individual could be a victim and
 in the next incident, the individual could be a suspect. A "strange
 couple" designation was given for incidents without a clearly defined
 victim and a clearly defined suspect. The Lethality Scale was derived
 from the data in the DVU database. It was composed of six incident
 characteristic components (offense score, weapon score, location
 score, injury score, personal score, and incident/other score) with
 varying values that contributed to an overall score. The Total
 Lethality Score was the sum of the values from these six
 components. The lethality score referred to an individual only and did
 not reflect information about other people involved in the
 incident. To interpret the score, the DVU specified a period of
 time--for example, six months--and computed lethality score values for
 every person involved in an incident during this period. An
 individual's Total Six Month Lethality Score was the sum of the Total
 Lethality Scores for every individual involved in an incident over the
 period of six months. Information on individuals with a Total Six
 Month Lethality Score over a certain cut-off was printed and reviewed
 by a detective. The researchers simulated the DVU's approach using two
 years of DVU data from the database to evaluate the predictive ability
of the Lethality Scale.</abstract>
           
 			
          <abstract>Data are provided for up to 25 incidents per unique
 couple. Incident variables in the dataset provide information on
 number of persons involved in the incident, time and weekday of the
 incident, beat, precinct, census tract, and place where the incident
 occurred, type of primary and secondary offenses, if a warrant was
 served, charges brought, final disposition, weapon type used, arrests
 made, court order information, if evidence was collected, if
 statements or photos were taken by the DVU, and sergeant action. Dates
 were converted to time intervals and provide the number of days
 between the incident date and the date the file was sent to the
 prosecutor, the date charges were brought, and the date the case was
 officially closed. Time intervals were also calculated for days
 between each incident for that couple. Personal information on the two
 persons in a couple includes age, gender, injuries and treatment,
 relationship and cohabitation status of the individuals, pregnancy
 status of each individual, alcohol and drug use at the time of the
 incident, and role of the individual in the incident (victim, suspect,
 victim/suspect). Lethality scale scores are included as well as the
 number of incidents in which the unique couple was involved in 1995
and 1996, and 1989 median household income for the census tract.</abstract>
          
           <sumDscr>
           
		
		
				
      		<timePrd event="start" date="1995-01-01" cycle="P1">1995-01-01</timePrd>
      		<timePrd event="end" date="1997-12-31" cycle="P1">1997-12-31</timePrd>
			
			
      		
      		
      	
		
 		
				
      		<collDate event="start" date="1995" cycle="P1">1995</collDate>
      		<collDate event="end" date="1997" cycle="P1">1997</collDate>
			
			
      		
      	
    	
    		<geogCover>Seattle</geogCover>
    	
    		<geogCover>United States</geogCover>
    	
    		<geogCover>Washington</geogCover>
    	
    	
    	
    		<anlyUnit>Unique couples</anlyUnit>
    	
	    	
	    		<universe>All reported misdemeanor domestic violence incidents in
Seattle from 1995-1997.</universe>
	    	
	    	
	    		<dataKind>administrative records data</dataKind>
	    	
           </sumDscr>
       </stdyInfo>
       <method>
           <dataColl>




             <sources>
             
    		<dataSrc>Seattle Police Department Domestic Violence Unit database</dataSrc>
    	
             </sources>
             
    	

		<cleanOps><p>ICPSR data undergo a confidentiality review and are altered when necessary to limit the risk of 
	disclosure. ICPSR also routinely creates ready-to-go data files along with setups in the major 
	statistical software formats as well as standard codebooks to accompany the data. In addition to 
	these procedures, ICPSR performed the following processing steps for this data collection:</p><list type="bulleted">
	<itm>Standardized missing values.</itm><itm>Checked for undocumented or out-of-range codes.</itm>
	</list>
	</cleanOps>
	
           </dataColl>

           <notes>These data are from Subproject 3 of the grant. The
evaluation concluded that the scale, with all the scoring and weighting,
reflected recidivism only and could not be modified to be a better
predictive tool.</notes>


          <anlyInfo>

               <respRate>
               
    		Not applicable.
    	
    	</respRate>
    	

               <dataAppr>None.</dataAppr>
              
          </anlyInfo>
       </method>
       <dataAccs>
           <setAvail media="online">
			
			
             <accsPlac URI="http://dx.doi.org/10.3886/ICPSR03026.v1">Ann Arbor, Mi.: Inter-university Consortium for Political and Social Research</accsPlac>
			
            </setAvail>
           <useStmt>
                <specPerm>Additional special permissions, where applicable, are described in the restrictions
                field.</specPerm>
                
                <restrctn>The data are restricted from general dissemination. Users interested in obtaining these data must complete a Restricted Data Use Agreement form and specify the reasons for the request. A copy of the Restricted Data Use Agreement form can be requested by calling 800-999-0960. Researchers can also download this form as a Portable Document Format (PDF) file from the download page associated with this dataset. Completed forms should be returned to: Director, National Archive of Criminal Justice Data, Inter-university Consortium for Political and Social Research, Institute for Social Research, P.O. Box 1248, University of Michigan, Ann Arbor, MI 48106-1248, or by fax: 734-647-8200.</restrctn>
                
 <conditions>
 	





<p>Please read the terms of use below. If you agree to them, click on the "I Agree" button to proceed. If you do not agree, you can click on the "I Do Not Agree" button to return to the home page.</p> <p>ICPSR adheres to the principles of the Data Seal of Approval <ExtLink URI="http://www.datasealofapproval.org/"/>, which, in part, require the data consumer to comply with access regulations imposed both by law and by the data repository, and to conform to codes of conduct that are generally accepted in higher education and scientific research for the exchange of knowledge and information. </p> <p>These data are distributed under the following terms of use, which are governed by ICPSR. By continuing past this point to the data retrieval process, you signify your agreement to comply with the requirements stated below:</p> <head n="2">Privacy of RESEARCH SUBJECTS</head> <p>Any intentional identification of a RESEARCH SUBJECT (whether an individual or an organization) or unauthorized disclosure of his or her confidential information violates the PROMISE OF CONFIDENTIALITY given to the providers of the information. Therefore, users of data agree:</p> <list type="bulleted"> <itm><p>To use these datasets solely for research or statistical purposes and not for investigation of specific RESEARCH SUBJECTS, except when identification is authorized in writing by ICPSR (netmail@icpsr.umich.edu <ExtLink URI="mailto:netmail@icpsr.umich.edu"/> )</p></itm> <itm><p>To make no use of the identity of any RESEARCH SUBJECT discovered inadvertently, and to advise ICPSR of any such discovery (netmail@icpsr.umich.edu <ExtLink URI="mailto:netmail@icpsr.umich.edu"/> )</p></itm> </list> <head n="2">Redistribution of Data</head> <p>You agree not to redistribute data or other materials without the written agreement of ICPSR, unless: </p> <list type="ordered"> <itm><p>You serve as the OFFICIAL or DESIGNATED REPRESENTATIVE at an ICPSR MEMBER INSTITUTION and are assisting AUTHORIZED USERS with obtaining data, or</p></itm> <itm><p>You are collaborating with other AUTHORIZED USERS to analyze the data for research or instructional purposes.</p></itm> </list> <p>When sharing data or other materials in these approved ways, you must include all accompanying files with the data, including terms of use. More information on  permission to redistribute data <ExtLink URI="http://www.icpsr.umich.edu/icpsrweb/content/datamanagement/policies/redistribute.html"/> can be found on the ICPSR Web site.</p><head n="2">Citing Data</head> <p>You agree to reference the recommended bibliographic citation in any publication that employs resources provided by ICPSR. Authors of publications based on ICPSR data are required to send citations of their published works to ICPSR for inclusion in a database of related publications (bibliography@icpsr.umich.edu <ExtLink URI="mailto:bibliography@icpsr.umich.edu"/>) .</p> <head n="2">Disclaimer</head> <p>You acknowledge that the original collector of the data, ICPSR, and the relevant funding agency bear no responsibility for use of the data or for interpretations or inferences based upon such uses.</p> <head n="2">Violations</head> <p>If ICPSR determines that the terms of this agreement have been violated, ICPSR will act according to our policy on terms of use violations <ExtLink URI="http://www.icpsr.umich.edu/ICPSR/support/faqs/2008/10/what-are-consequences-of-violating"/>. Sanctions can include:</p> <list type="bulleted"> <itm><p>ICPSR may revoke the existing agreement, demand the return of the data in question, and deny all future access to ICPSR data.</p></itm> <itm><p>The violation may be reported to the Research Integrity Officer, Institutional Review Board, or Human Subjects Review Committee of the user's institution. A range of sanctions are available to institutions including revocation of tenure and termination.</p></itm> <itm><p>If the confidentiality of human subjects has been violated, the case may be reported to the Federal Office for Human Research Protections. This may result in an investigation of the user's institution, which can result in institution-wide sanctions including the suspension of all research grants. </p></itm> <itm><p>A court may award the payment of damages to any individual(s)/organization(s) harmed by the breach of the agreement.</p></itm> </list> <head n="2">Definitions</head> <list type="bulleted"><itm><hi>authorized user</hi> - A faculty member, staff member, or student at a member institution</itm><itm><hi>ICPSR</hi> - Inter-university Consortium for Political and Social Research</itm><itm><hi>member institution</hi> - An institutional member of ICPSR</itm><itm><hi>Official/Designated Representative</hi> - An individual appointed to represent a university's interests in ICPSR. This individual is also charged with providing user support to campus users. </itm><itm><hi>promise of confidentiality</hi> - A promise to a respondent or research participant that the information the respondent provides will not be disseminated without the permission of the respondent; that the fact that the respondent participated in the study will not be disclosed; and that disseminated information will include no linkages to the identity of the respondent. Such a promise encompasses traditional notions of both confidentiality and anonymity. Names and other identifying information regarding respondents, proxies, or other persons on whom the respondent or proxy provides information, are presumed to be confidential.</itm><itm><hi>research subject</hi> - A person or organization observed for purposes of research. Also called a respondent. A respondent is generally a survey respondent or informant, experimental or observational subject, focus group participant, or any other person providing information to a study or on whose behalf a proxy provides information. </itm></list><p>In addition, the National Archive of Criminal Justice Data stipulates the following conditions:</p> <p>Federal law and regulations require that research data collected by the U.S. Department of Justice or by its grantees and contractors may only be used for research or statistical purposes. The applicable laws and regulations may be found in the United States Code, 42 USC Section 3789g(a), the Code of Federal Regulations, 28 CFR 22, and 62 F.R. 35044 (June 27, 1997) (The Federal Confidentiality Order). Accordingly, any intentional identification or disclosure of a person or establishment may violate federal law as well as the assurances of confidentiality given to the providers of the information. Therefore, users of data collected by or with the support from the U.S. Department of Justice and distributed by NACJD or other ICPSR archives must agree to abide by these regulations and understand that ICPSR may report any potential violation to the U.S. Department of Justice.</p>




 
 
 			
                
					<p>AVAILABLE.  This study is freely available to the general public.</p>
                
                  
                
                
                </conditions>
                <disclaimer>The original collector of the data, ICPSR, and the relevant funding agency bear no 
                responsibility for use of the data or for interpretations or inferences based upon such uses.
                </disclaimer>
           </useStmt>
       </dataAccs>
			
     </stdyDscr>
		
 
 
</codeBook>
