Logical View Report Generation Template - DOC
Document Sample


New Hampshire
Criminal Justice Information System
Data Dictionary Report
February 15, 2002
NH - CJIS Data Dictionary Version 1.0
This document is not to be distributed without explicit authorization from
New Hampshire - Department of Safety
Prepared By:
KPMG Consulting, Inc.
99 High Street
Boston, MA 02110
This project was supported by Grant No. 2000-DB-MU-0033 and Grant No. 2001-DB-BX-0033 awarded by the Bureau of Justice
Assistance, Office of Justice Programs, U.S. Department of Justice. Points of view in this document are those of the author a nd do not
necessarily represent the official position or policies of the U.S. Department of Justice.
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Table of Contents
Overview.........................................................................................................................................................4
Our Approach ....................................................................................................................................................................... 4
Why XML? ............................................................................................................................................................................. 5
What is an Object Model and how do you read it?.......................................................................................................... 7
Inheritance ........................................................................................................................................................................ 7
Association........................................................................................................................................................................ 8
Aggregation....................................................................................................................................................................... 8
Cardinality ......................................................................................................................................................................... 9
Elements and Attributes — Naming Conventions................................................................................... 11
Elements ......................................................................................................................................................................... 11
Attributes ......................................................................................................................................................................... 11
The CJIS Object Model .............................................................................................................................. 12
CJIS Package ................................................................................................................................................................. 12
Personal Information Package ....................................................................................................................................... 12
Contact Information Package ......................................................................................................................................... 12
The Class Diagrams, Element and Attribute Definitions .............................................................................................. 13
CJIS Details................................................................................................................................................. 15
Class Diagram: CJIS Details .......................................................................................................................................... 15
Charge ............................................................................................................................................................................ 15
ChargeType .................................................................................................................................................................... 15
Incident............................................................................................................................................................................ 17
Counts ............................................................................................................................................................................. 17
Document ........................................................................................................................................................................ 17
Offense............................................................................................................................................................................ 18
Role ................................................................................................................................................................................. 18
Bail .................................................................................................................................................................................. 19
Dockets ........................................................................................................................................................................... 19
Personal Information Details .................................................................................................................... 20
Class Diagram: Personal Information Details ................................................................................................................ 20
Relationship .................................................................................................................................................................... 21
StateAgency.................................................................................................................................................................... 21
state................................................................................................................................................................................. 21
Party ................................................................................................................................................................................ 21
Name ............................................................................................................................................................................... 21
Demographics ................................................................................................................................................................. 22
Employer ......................................................................................................................................................................... 24
IDDocument .................................................................................................................................................................... 24
PersonalIdentification ..................................................................................................................................................... 24
Vehicle ............................................................................................................................................................................ 24
IdentifyingMarks.............................................................................................................................................................. 25
StateType ........................................................................................................................................................................ 25
MarkLocation .................................................................................................................................................................. 26
Contact Information Details ...................................................................................................................... 27
Class Diagram: Contact Information Details.................................................................................................................. 27
ContactInformation ......................................................................................................................................................... 28
Address ........................................................................................................................................................................... 29
Email ............................................................................................................................................................................... 29
Phone .............................................................................................................................................................................. 29
Types Details .............................................................................................................................................. 30
Class Diagram: Types Details ........................................................................................................................................ 30
AgencyType .................................................................................................................................................................... 30
ContactInformationType ................................................................................................................................................. 30
DocumentType ............................................................................................................................................................... 31
EmployerType ................................................................................................................................................................. 31
EmploymentType ............................................................................................................................................................ 32
EyeColorType ................................................................................................................................................................. 32
GenderType .................................................................................................................................................................... 33
HairColorType ................................................................................................................................................................. 33
IdentificationType............................................................................................................................................................ 33
Page 2 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
MaritalStatusType ........................................................................................................................................................... 34
NameType ...................................................................................................................................................................... 34
PartyType ........................................................................................................................................................................ 35
PhoneType...................................................................................................................................................................... 35
RaceType ........................................................................................................................................................................ 36
RoleType ......................................................................................................................................................................... 36
SkinToneType ................................................................................................................................................................. 36
Enumerations Details ................................................................................................................................. 38
Class Diagram: Enumerations Details ........................................................................................................................... 38
AgencyTypeEnum .......................................................................................................................................................... 38
ChargeEnum ................................................................................................................................................................... 39
ComplaintTypeEnum ...................................................................................................................................................... 39
ContactTypeEnum .......................................................................................................................................................... 39
DocTypeEnum ................................................................................................................................................................ 40
DocumentTypeEnum ...................................................................................................................................................... 40
EmployerTypeEnum ....................................................................................................................................................... 40
EmploymentTypeEnum .................................................................................................................................................. 40
EyeColorEnum ................................................................................................................................................................ 40
GenderEnum................................................................................................................................................................... 41
HairColorEnum ............................................................................................................................................................... 41
IdentificationTypeEnum .................................................................................................................................................. 43
MaritalStatusEnum ......................................................................................................................................................... 43
NameTypeEnum ............................................................................................................................................................. 43
PartyTypeEnum .............................................................................................................................................................. 44
PhoneTypeEnum ............................................................................................................................................................ 44
RaceEnum ...................................................................................................................................................................... 44
RelationshipTypeEnum .................................................................................................................................................. 46
RoleTypeEnum ............................................................................................................................................................... 46
SkinToneEnum ............................................................................................................................................................... 46
StateEnum ...................................................................................................................................................................... 47
TimeTypeEnum .............................................................................................................................................................. 73
YesNoEnum .................................................................................................................................................................... 73
Utility Details .............................................................................................................................................. 74
Class Diagram: Utility Details ......................................................................................................................................... 74
ActionDateTime .............................................................................................................................................................. 74
Page 3 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Overview
The State of New Hampshire has recognized the importance of sharing criminal justice
information among a community of authorized users from a variety of justice agencies,
government branches, and interested parties-- including law enforcement, the courts, and local
and state jail and prison systems, attorneys, and, in some cases, the public.
In 1995, the Criminal Justice Information System Master Plan for the State of New Hampshire
was developed. This report articulated a vision and approach for achieving the CJIS. Subsequent
to that report, additional information related to the CJIS was developed by Justiceworks and is
outlined in their Benchmarks and Blueprints report.
In the fall of 2001, the State of New Hampshire issued a Request for Proposal (RFP) for CJIS
Logical Design Services. KPMG Consulting was awarded this competitive bid and the CJIS
Logical Design project was initiated late November 2001.
Our Approach
As a first step, a repository of all the documents that are currently being used by the various
participants who represent the CJIS community was created. These documents were analyzed to
extract the list of data elements captured on these documents. This list was compared with the
OJP (Office of Justice Programs) published ‗Justice and Public Safety – XML Data Element
Definitions, and the NCIC published code list manual. Special attention was paid to capturing the
existing elements and any other elements that might become relevant in the future, given the ever-
changing public safety environment.
The next step was to organize this information into and object model (An explanation of object
models is included in this guide.). The stated deliverable for this effort is a data model that will
help define the interfaces to all the legacy systems that will eventually become part of the CJIS
environment. However, an object model allows us:
to communicate the desired structure and behavior of the system.
to visualize and control the system‘s architecture.
to better understand the system and expose opportunities for simplification and reuse.
to manage risk.
The object model can be enhanced and leveraged to model the application flow and component
development. The model can easily be transformed into an XML Schema specification that could
potentially be used to represent the messaging interfaces. And last but not the least, the object
model also allows us to generate the data model which will become the final deliverable.
Page 4 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Why XML?
The eXtensible Markup Language (XML) is an initiative proposed by the World Wide Web
Consortium (W3C) as an alternative to HTML, which currently dominates Web publishing.
Complementary to HTML, XML can be implemented for information publishing and data-
intensive applications alike. Unlike HTML, XML is a meta-language — i.e., it allows users to
create their own markup languages or vocabularies relevant to their particular business needs.
HTML is a standard set of tags that are defined to present web pages in a web browser when a
user requests a page. Any tag that is not defined as part of the HTML specification is not
recognized by the browser and may be displayed as standard text. Web pages displayed in HTML
can be static — generic informational literature — or dynamic — generated from information that
is in some way related to the user or is customized based on the user‘s preferences. Information in
dynamic web pages can come from databases or even from other web sites; it can be either raw
information as it comes from the data sources, or information that is analyzed, extracted, sorted,
styled, and customized to create a personalized web experience for the end user.
Because XML provides the ability to manipulate data in a much more advanced fashion than
HTML, it has very quickly become the markup language of choice for web developers. Unlike
HTML, XML allows the data to be separated from its presentation. While HTML can be used to
present the information using standard tags, XML gives users the capability to create their own
custom tags to describe the data contained within them.
The following example illustrates the difference between HTML and XML. Here is some HTML
code:
<p><font name = “Arial” size=”3”>Complaint</font></p>
<p><font name = “Arial” size=”1”>Strafford County
Court</font></p>
<p><font name = “Arial” size=”1”>Strafford
County</font></p>
HTML tells us about how this data is going to be displayed.
In XML, the same information might look like this:
<DocumentType>Complaint</DocumentType>
<Court>Strafford County</Court>
<County>Strafford</County>
XML allows content to describe itself through the tags in which the data are enclosed. These tags
can be leveraged to manipulate the data depending on the end user‘s requests or requirements.
Data tagged this way can be presented through different media types (browser, client-server
desktop application, wireless devices etc.) or displayed differently (e.g., as a grid or in a chart, or
hide/display data elements based upon the security role, etc.) on different sites, by changing the
presentation style, without making any changes to the actual data.
Page 5 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
An XML schema is a set of components and rules that represent the business vocabulary of an
industry, a process, or an application. Schemas help define how these rules affect the components
that represent the business, or how these components relate to each other. Any XML document
that is created using these rules and components needs to be compliant with this schema to be a
valid representation of the business vocabulary. Once the schemas are validated and embraced by
a community as the standard mechanism for communicating or exchanging information, they
provide enhanced capabilities for searching, validating, compiling or filtering information
quickly.
Page 6 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
What is an Object Model and how do you read it?
All industries, businesses and user communities are made up of a set of components and rules that
represent their business requirements. The viability of most communities depends upon how these
rules affect the components that represent their requirements, and how these components interact
with each other. An object model is a visual representation of these components and the rules that
govern them. Object models can be very elaborate, to represent the entire community/enterprise;
or they can be very focused, to represent a particular aspect of the community; or they can be
used to model a solution for a specific problem.
Generally speaking, objects can be defined as the components that represent the community; the
rules that govern these components become the relationships that exist between these objects. In
this context, these objects are represented as rectangular boxes (classes) that are divided into two
sections — the top containing the name of the class (identity), and the bottom containing facts
(attributes) that describe this class. This will become clear from the following example.
Diagram 1
In this example, Car is the class, as defined by its position in the top container of its box. There
are traits that define this car; these are called the attributes. In this example, the attributes are
Color, Make, Model, and Year. By supplying values for these attributes, we can uniquely define a
car. Some other classes are CarPart, Owner and Person. By themselves, these classes might not
mean much, or they might describe an object without much relevance as to how this object
interacts with its environment. But if we were somehow able to relate these objects with one
another, they could potentially fit together as a jigsaw puzzle and explain a small portion of the
automobile industry. The diagram that displays these classes and their respective relationships is
referred to as the Class Diagram (Diagram 5 below).
Let's start with a definition of some of the most commonly used relationship types — inheritance,
associations and aggregations.
Inheritance
An inheritance represents a connection between two classes that shows that the subclass
shares the structure and behavior defined in one or more super classes. This allows the super
class to be treated as a generic object that can be used by some other application, or could be
Page 7 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
provided by some other application. The triangular arrow connecting the Owner and Person
means that Owner is the subclass that shares all the attributes of the parent class (Person). So,
Owner now has all the attributes of Person besides the OwnedFromDate and OwnedToDate.
In other words, Owner is derived from Person.
Diagram 2
Association
An association represents a semantic connection between two classes. This bi-directional
relationship is the most commonly used of all relationships. It is represented as a single line
drawn to connect two classes. For example:
Diagram 3
Aggregation
The aggregation relationship is used to show a whole-and-part connection between two
classes, as shown in the following example:
Diagram 4
(Aggregate class) (Part class)
The class at the Car end of the aggregation relationship is sometimes called the Aggregate
class (represented by a diamond at the end of the connecting line). The class at the CarPart
end of the aggregation relationship is the Part class, instances of which are contained or
Page 8 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
owned by the Aggregate object. Use of the aggregation relationship shows that the aggregate
object is physically constructed from, or logically contains, another object.
But, you may say, a car is made up of more than one part. How do you represent this in the
object model? The concept of Cardinality provides the answer.
Cardinality
Cardinality specifies how many instances of one class may be associated with a single
instance of another class. You can indicate cardinality for classes and relationships. An
example in the context of the current example is:
Diagram 5
The following values can be used to represent cardinality:
Value Description Value Description
0 Zero 1 One
0..1 Zero or One 1..* One or More
0..* Zero or More * Unlimited number
In the above example, the value on the Car class side of the relationship is 1, and on the
Owner class side, 0..*. This means that a car may have zero or many owners. This is true in
the real world, as a car has no owner until someone purchases it. On the other hand, it could
have a single owner, or could be jointly owned (e.g., a husband and wife purchasing a car
together).
Page 9 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
In the other instance, there is an aggregation relationship between the Car and the CarPart
classes. Car class is the aggregate class, as described earlier. The value on the Car side is 1
and the value on the CarPart side is 1..*. This means that the Car is made up of at least one
CarPart, and can be made up of from one to an unlimited number of CarParts.
Page 10 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Elements and Attributes — Naming Conventions
The following naming conventions were used when translating the working draft into the object
model and thereby into the schema:
Elements
The first character of all words making up the element name will be in upper case. All other
characters will be in lower case, with no spaces between the words (UpperCamelCase).
Attributes
The first character of the first word of an attribute will be in lower case. The first characters of
all the subsequent words that make up the name will be in upper case. All other characters
will be in lower case, with no spaces between the words (lowerCamelCase).
Page 11 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
The CJIS Object Model
The CJIS Object Model has been logically divided into three major sections. In the object
modeling terminology, these sections are called packages. These packages are merely aides to
better organize the data elements and ease the analysis and understanding of these sections. The
three packages that make up the CJIS Object model are described below:
CJIS Package
This section documents the information about the actual offense committed, the charges, the
disposition information and the documents generated as part of this process.
Personal Information Package
This section describes the personal information about the various actors participating in the
Criminal Justice Process — including the demographic information, identification information,
etc.
Contact Information Package
This section documents contact information about the various actors participating in the
Criminal Justice Process.
Each section in the following documentation is made up of a package name (a name for the
collection of objects that were logically packaged together). Within each package there is a
description of classes that make up that package. Following the definition of any class is a listing
and definition of the attributes that make up that class. If the class is an aggregator of other
classes, they are listed after the attributes listing. Where an enumeration modifies an attribute
(denoted by the suffix ―Enum,‖ e.g., ―GenderTypeEnum‖), refer to the list of Enumerations at the
end of this Dictionary.
Page 12 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
The Class Diagrams, Element and Attribute Definitions
Page 13 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Page 14 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
CJIS Details
This section documents the information about the actual offense committed, the charges, the
disposition information and the documents generated as part of this process.
Class Diagram: CJIS Details
CJIS DETAILS
Address
Vehicle
addressID
vehID buildingName RoleType
vinNumber addressLine1
year addressLine2 ChargeType
make city
model 1..* chargeTypeCode : ChargeEnum
county Role Party
style description
state roleID partyID
color 1 effectiveStartDate : Date
zip
plateNumber 0..* 1 1..* effectiveEndDate : Date
longitude
plateType currentlyActive : YesNoEnum
latitude
issueState
issueCountry Offense Location Offense
issueYear Crime Vehicle 1..* offenseID
comments chargeID
1 1
Incident
ActionDateTime 1 incidentID
actionID docketNumber
day tnNumber
1..* pno 1
month Charge
1 domViolenceIndicator : YesNoEnum 1
year
time complaintType : ComplaintTypeEnum
timeType : TimeType court
dateTime : Date county 0..*
offenseDescription
0..* offenseDetails Counts
rsa
1 complainant
1 department
Dockets
Document
documentType : DocumentTypeEnum
1..*
createdDate
createdBy
approvedDate
approvedTime
approvedBy
issuedBy 1 Bail
issuedDate cashBailIndicator : YesNoEnum
issuedTime cashBailAmt
servicedBy 0..* perRecogIndicator : YesNoEnum
servicedDate perRecogAmt
servicedTime bailConditions : YesNoEnum
comments bailCommAmt
Charge
Aggregations:
Role (Required)
Offense (Required)
Counts (Optional, Multiples Allowed)
ChargeType
Charge Type table.
Page 15 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Elements and Attributes:
chargeTypeCode (Required, ChargeEnum)
Unique code as listed in the enumerations table
description (Required, String)
Description of the code.
effectiveStartDate (Required, Date)
Date this code became effective.
effectiveEndDate (Required, Date)
Date this code will cease to end.
currentlyActive (Required, YesNoEnum)
Indicator to indicate if the code is currently active.
Page 16 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Incident
Elements and Attributes:
incidentID (Required, String)
docketNumber (Required, String)
tnNumber (Required, String)
pno (Required, String)
domViolenceIndicator (Required, YesNoEnum)
complaintType (Required, ComplaintTypeEnum)
court (Required, String)
county (Required, String)
offenseDescription (Required, String)
offenseDetails (Required, String)
rsa (Required, String)
complainant (Required, String)
department (Required, String)
Aggregations:
Address (Required)
Vehicle (Optional, Multiples Allowed)
ActionDateTime (Required, Multiples Allowed)
Document (Required, Multiples Allowed)
Role (Required, Multiples Allowed)
Offense (Required, Multiples Allowed)
Counts
Aggregations:
Dockets (Required)
Document
Elements and Attributes:
documentType (Required, DocumentTypeEnum)
createdDate (Required, String)
createdBy (Required, String)
Page 17 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
approvedDate (Required, String)
approvedTime (Required, String)
approvedBy (Required, String)
issuedBy (Required, String)
issuedDate (Required, String)
issuedTime (Required, String)
servicedBy (Required, String)
servicedDate (Required, String)
servicedTime (Required, String)
comments (Required, String)
Aggregations:
ActionDateTime (Optional, Multiples Allowed)
Bail (Optional, Multiples Allowed)
Offense
Elements and Attributes:
offenseID (Required, String)
chargeID (Required, String)
Role
Elements and Attributes:
roleID (Required, String)
Unique ID - Primary Key.
Page 18 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Bail
Elements and Attributes:
cashBailIndicator (Required, YesNoEnum)
cashBailAmt (Required, String)
perRecogIndicator (Required, YesNoEnum)
perRecogAmt (Required, String)
bailConditions (Required, YesNoEnum)
bailCommAmt (Required, String)
Dockets
Page 19 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Personal Information Details
This section describes the personal information about the various actors participating in the
Criminal Justice Process - including the demographic information, identification information, etc.
Class Diagram: Personal Information Details
PERSONAL INFORMATION DETAILS
AgencyType PartyType DocumentType Vehicle EyeColorType
vehID
vinNumber
year
StateAgency IDDocument SkinToneType
make
agencyID 1 Party docID model
name docDescription style
jurisdiction 0..* partyID docNumber +Eye Color
color
county 1 IssueState plateNumber
issueDate plateType MaritalStatusType
issueCountry issueState
EmployerType
issuedBy issueCountry
expirationDate +Skin Tone
issueYear
0..* RaceType
comments +Marital Status
EmploymentType 0..*
Employer HairColorType
GenderType
employerID +Race
name 1 1
1..* +Hair Color
startDate 0..* +Sex
endDate Name
numberOfHours nameID Demographics
1 prefix
1 demographicID
lastName
1 dob
1 middleName
age
0..* 0..* firstName
1 0..1 height
ContactInformation suffix
weight
fullName
contactInfoID maritalStatusEffDate : Date
ssn
title 1 1
1..*
PersonalIdentification
value +Place of Birth
0..*
0..1
IdentifyingMarks
markID StateType
IdentificationType NameType
markType
markLocation
1
0..*
MarkLocation
locationType
Page 20 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Relationship
Elements and Attributes:
relationshipType (Required, RelationshipTypeEnum)
StateAgency
Elements and Attributes:
agencyID (Required, String)
ORI
name (Required, String)
jurisdiction (Required, String)
county (Required, String)
Aggregations:
Party (Optional, Multiples Allowed)
state
Party
Elements and Attributes:
partyID (Required, String)
Aggregations:
Name (Required, Multiples Allowed)
Role (Required, Multiples Allowed)
Name
Elements and Attributes:
nameID (Required, String)
prefix (Required, String)
lastName (Required, String)
middleName (Required, String)
firstName (Required, String)
suffix (Required, String)
fullName (Required, String)
Can be used to capture the Complete name of the Individual, Business, Agency or
Institution
Page 21 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
ssn (Required, String)
title (Required, String)
Aggregations:
ContactInformation (Optional, Multiples Allowed)
Vehicle (Optional, Multiples Allowed)
IDDocument (Optional, Multiples Allowed)
Demographics (Optional)
Employer (Optional, Multiples Allowed)
PersonalIdentification (Required, Multiples Allowed)
Demographics
Demographics represents all the personal information that could be used to positively identify
the individual.
Elements and Attributes:
demographicID (Required, String)
Unique ID - Primary Key.
dob (Required, String)
According to the NCIC codes, the DOB is expressed as a Gregorian date
(YYYYMMDD): year (YYYY), month (MM), and day (DD).
All records should be entered with a complete DOB, if available. When the complete
date is not available, zeros can be used for an unknown month or day.
age (Required, String)
Age of the individual.
height (Required, String)
According to the NCIC codes, height must be expressed in feet and inches. Fractions
of an inch should be rounded off to the nearest inch.
weight (Required, String)
According to the NCIC codes, weight must be expressed in pounds. Fractions of a
pound should be rounded off to the nearest pound.
maritalStatusEffDate (Required, Date)
This is the effective date of the current marital status of the individual.
Page 22 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Aggregations:
IdentifyingMarks (Optional, Multiples Allowed)
GenderType (Required)
RaceType (Required)
EyeColorType (Required)
HairColorType (Required)
MaritalStatusType (Required)
SkinToneType (Required)
StateType (Optional)
The agregation of state here represents the Place of Birth.
Page 23 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Employer
Elements and Attributes:
employerID (Required, String)
name (Required, String)
startDate (Required, String)
endDate (Required, String)
numberOfHours (Required, String)
Aggregations:
ContactInformation (Optional, Multiples Allowed)
IDDocument
Elements and Attributes:
docID (Required, String)
docDescription (Required, String)
docNumber (Required, String)
IssueState (Required, String)
issueDate (Required, String)
issueCountry (Required, String)
issuedBy (Required, String)
expirationDate (Required, String)
PersonalIdentification
Elements and Attributes:
value (Required, String)
Vehicle
Elements and Attributes:
vehID (Required, String)
vinNumber (Required, String)
year (Required, String)
make (Required, String)
model (Required, String)
style (Required, String)
Page 24 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
color (Required, String)
plateNumber (Required, String)
plateType (Required, String)
issueState (Required, String)
issueCountry (Required, String)
issueYear (Required, String)
comments (Required, String)
IdentifyingMarks
Elements and Attributes:
markID (Required, String)
markType (Required, String)
markLocation (Required, String)
Aggregations:
MarkLocation (Optional, Multiples Allowed)
StateType
State Type table.
Elements and Attributes:
stateTypeCode (Required, StateEnum)
Unique code as listed in the enumerations table
description (Required, String)
Description of the code.
effectiveStartDate (Required, Date)
Date this code became effective.
effectiveEndDate (Required, Date)
Date this code will cease to end.
currentlyActive (Required, YesNoEnum)
Indicator to indicate if the code is currently active.
Page 25 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
MarkLocation
Elements and Attributes:
locationType (Required, String)
Page 26 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Contact Information Details
The Contact Information section documents contact information about the various actors
participating in the Criminal Justice Process.
Class Diagram: Contact Information Details
CONTACT INFORMATION DETAILS
ContactInformation +Contact Information Type
ContactInformationType
contactInfoID 0..1 1
1
1 1
0..*
0..*
Address Phone
addressID phoneID
buildingName 0..* +Phone Type
countryCode PhoneType
addressLine1 areaCode
addressLine2 Email phoneNumber
city emailID extensionPIN
county emailAddress
state
zip
longitude
latitude
Page 27 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
ContactInformation
Elements and Attributes:
contactInfoID (Required, String)
Aggregations:
Address (Optional, Multiples Allowed)
Phone (Optional, Multiples Allowed)
Email (Optional, Multiples Allowed)
ContactInformationType (Required)
This relationship represents what type of contact information is represented in the
Contact Information class.
Page 28 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Address
Elements and Attributes:
addressID (Required, String)
buildingName (Required, String)
addressLine1 (Required, String)
addressLine2 (Required, String)
city (Required, String)
county (Required, String)
state (Required, String)
zip (Required, String)
longitude (Required, String)
latitude (Required, String)
Email
Elements and Attributes:
emailID (Required, String)
emailAddress (Required, String)
Phone
Elements and Attributes:
phoneID (Required, String)
countryCode (Required, String)
areaCode (Required, String)
phoneNumber (Required, String)
extensionPIN (Required, String)
Aggregations:
PhoneType (Required)
This relationship represents what type of phone is represented in the phone class.
Page 29 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Types Details
The Types section contains all the type classes that will hold the domain look-up values.
Class Diagram: Types Details
TYPES DETAILS
ContactInformationType PhoneType
contactTypeCode : ContactTypeEnum phoneTypeCode : PhoneTypeEnum
description description
effectiveStartDate : Date effectiveStartDate : Date
effectiveEndDate : Date effectiveEndDate : Date
currentlyActive : YesNoEnum currentlyActive : YesNoEnum
AgencyType
Agency Type table.
Elements and Attributes:
agencyTypeCode (Required, AgencyTypeEnum)
Unique code as listed in the enumerations table
description (Required, String)
Description of the code.
effectiveStartDate (Required, Date)
Date this code became effective.
effectiveEndDate (Required, Date)
Date this code will cease to end.
currentlyActive (Required, YesNoEnum)
Indicator to indicate if the code is currently active.
ContactInformationType
Contact Information Type table.
Elements and Attributes:
contactTypeCode (Required, ContactTypeEnum)
Unique code as listed in the enumerations table
Page 30 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
description (Required, String)
Description of the code.
effectiveStartDate (Required, Date)
Date this code became effective.
effectiveEndDate (Required, Date)
Date this code will cease to end.
currentlyActive (Required, YesNoEnum)
Indicator to indicate if the code is currently active.
DocumentType
Document Type table.
Elements and Attributes:
documentTypeCode (Required, DocumentTypeEnum)
Unique code as listed in the enumerations table
description (Required, String)
Description of the code.
effectiveStartDate (Required, Date)
Date this code became effective.
effectiveEndDate (Required, Date)
Date this code will cease to end.
currentlyActive (Required, YesNoEnum)
Indicator to indicate if the code is currently active.
EmployerType
Employer Type table.
Elements and Attributes:
employerTypeCode (Required, EmployerTypeEnum)
Unique code as listed in the enumerations table
description (Required, String)
Description of the code.
effectiveStartDate (Required, Date)
Date this code became effective.
Page 31 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
effectiveEndDate (Required, Date)
Date this code will cease to end.
currentlyActive (Required, YesNoEnum)
Indicator to indicate if the code is currently active.
EmploymentType
Employment Type table.
Elements and Attributes:
employmentTypeCode (Required, EmploymentTypeEnum)
Unique code as listed in the enumerations table
description (Required, String)
Description of the code.
effectiveStartDate (Required, Date)
Date this code became effective.
effectiveEndDate (Required, Date)
Date this code will cease to end.
currentlyActive (Required, YesNoEnum)
Indicator to indicate if the code is currently active.
EyeColorType
Eye color Type table.
Elements and Attributes:
eyeTypeCode (Required, EyeColorEnum)
Unique code as listed in the enumerations table
description (Required, String)
Description of the code.
effectiveStartDate (Required, Date)
Date this code became effective.
effectiveEndDate (Required, Date)
Date this code will cease to end.
currentlyActive (Required, YesNoEnum)
Indicator to indicate if the code is currently active.
Page 32 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
GenderType
Gender Type table.
Elements and Attributes:
genderTypeCode (Required, GenderEnum)
Unique code as listed in the enumerations table
description (Required, String)
Description of the code.
effectiveStartDate (Required, Date)
Date this code became effective.
effectiveEndDate (Required, Date)
Date this code will cease to end.
currentlyActive (Required, YesNoEnum)
Indicator to indicate if the code is currently active.
HairColorType
Hair color Type table.
Elements and Attributes:
hairTypeCode (Required, HairColorEnum)
Unique code as listed in the enumerations table
description (Required, String)
Description of the code.
effectiveStartDate (Required, Date)
Date this code became effective.
effectiveEndDate (Required, Date)
Date this code will cease to end.
currentlyActive (Required, YesNoEnum)
Indicator to indicate if the code is currently active.
IdentificationType
Identification Type table.
Elements and Attributes:
identificationTypeCode (Required, IdentificationTypeEnum)
Unique code as listed in the enumerations table
Page 33 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
description (Required, String)
Description of the code.
effectiveStartDate (Required, Date)
Date this code became effective.
effectiveEndDate (Required, Date)
Date this code will cease to end.
currentlyActive (Required, YesNoEnum)
Indicator to indicate if the code is currently active.
MaritalStatusType
Marital Status Type table.
Elements and Attributes:
maritalStatusTypeCode (Required, MaritalStatusEnum)
Unique code as listed in the enumerations table
description (Required, String)
Description of the code.
effectiveStartDate (Required, Date)
Date this code became effective.
effectiveEndDate (Required, Date)
Date this code will cease to end.
currentlyActive (Required, YesNoEnum)
Indicator to indicate if the code is currently active.
NameType
Name Type table.
Elements and Attributes:
nameTypeCode (Required, NameTypeEnum)
Unique code as listed in the enumerations table
description (Required, String)
Description of the code.
effectiveStartDate (Required, Date)
Date this code became effective.
Page 34 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
effectiveEndDate (Required, Date)
Date this code will cease to end.
currentlyActive (Required, YesNoEnum)
Indicator to indicate if the code is currently active.
PartyType
Party Type table.
Elements and Attributes:
partyTypeCode (Required, PartyTypeEnum)
Unique code as listed in the enumerations table
description (Required, String)
Description of the code.
effectiveStartDate (Required, Date)
Date this code became effective.
effectiveEndDate (Required, Date)
Date this code will cease to end.
currentlyActive (Required, YesNoEnum)
Indicator to indicate if the code is currently active.
PhoneType
Phone Type table.
Elements and Attributes:
phoneTypeCode (Required, PhoneTypeEnum)
Unique code as listed in the enumerations table
description (Required, String)
Description of the code.
effectiveStartDate (Required, Date)
Date this code became effective.
effectiveEndDate (Required, Date)
Date this code will cease to end.
currentlyActive (Required, YesNoEnum)
Indicator to indicate if the code is currently active.
Page 35 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
RaceType
Race Type table.
Elements and Attributes:
raceTypeCode (Required, RaceEnum)
Unique code as listed in the enumerations table
description (Required, String)
Description of the code.
effectiveStartDate (Required, Date)
Date this code became effective.
effectiveEndDate (Required, Date)
Date this code will cease to end.
currentlyActive (Required, YesNoEnum)
Indicator to indicate if the code is currently active.
RoleType
Role Type table.
Elements and Attributes:
roleTypeCode (Required, RoleTypeEnum)
Unique code as listed in the enumerations table
description (Required, String)
Description of the code.
effectiveStartDate (Required, Date)
Date this code became effective.
effectiveEndDate (Required, Date)
Date this code will cease to end.
currentlyActive (Required, YesNoEnum)
Indicator to indicate if the code is currently active.
SkinToneType
Skin Tone Type table.
Elements and Attributes:
skinToneTypeCode (Required, SkinToneEnum)
Unique code as listed in the enumerations table
Page 36 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
description (Required, String)
Description of the code.
effectiveStartDate (Required, Date)
Date this code became effective.
effectiveEndDate (Required, Date)
Date this code will cease to end.
currentlyActive (Required, YesNoEnum)
Indicator to indicate if the code is currently active.
Page 37 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Enumerations Details
Listing of all the enumerated values.
Class Diagram: Enumerations Details
ContactTypeEnum EmployerTypeEnum
PhoneTypeEnum
RelationshipTypeEnum
NameTypeEnum YesNoEnum
EmploymentTypeEnum
GenderEnum TimeTypeEnum
MaritalStatusEnum
IdentificationTypeEnum
DocumentTypeEnum
PartyTypeEnum
DocTypeEnum
ComplaintTypeEnum
EyeColorEnum
RaceEnum
SkinToneEnum
HairColorEnum
AgencyTypeEnum
ORI
Page 38 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Enumeration Values:
SupremeCourt
SuperiorCourt
DistrictCourt
StatePolice
SherrifOffice
PoliceDepartment
DepartmentOfCorrection
HouseOfCorrection
StatePrison
ParoleBoard
CostContainmentOffice
ChargeEnum
ComplaintTypeEnum
Enumeration Values:
Violation
ClassAMisdemeanor
ClassBMisdemeanor
Felony
ContactTypeEnum
Listing of the different types of contact information like home, mailing, etc.
Enumeration Values:
Home
Personal contact information.
Business
Business/Office contact information.
Mailing
Mailing contact information.
Page 39 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
DocTypeEnum
Enumeration Values:
DriverLicense
Passport
StateIdentification
SchoolID
DocumentTypeEnum
Enumeration Values:
Complaint
Indictment
Arraingment
Order
BailBond
EmployerTypeEnum
Enumeration Values:
Individual
Business
EmploymentTypeEnum
Enumeration Values:
FullTime
PartTime
Seasonal
EyeColorEnum
Listing of NCIC recommended values for the eye color field.
Enumeration Values:
BLK
Black.
BLU
Blue.
Page 40 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
BRO
Brown.
GRY
Gray.
GRN
Green.
HAZ
Hazel.
MAR
Maroon.
MUL
Multicolored.
PNK
Pink.
XXX
Unknown.
GenderEnum
Listing of NCIC recommended values for the gender field.
Enumeration Values:
M
Male.
F
Female.
U
Unknown.
HairColorEnum
Listing of NCIC recommended values for the hair color field.
Enumeration Values:
BLD
Bald (III records only).
Page 41 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
BLK
Black.
BRO
Brown.
GRY
Gray or Partially Gray.
GRN
Green.
BLN
Blond or Strawberry.
MAR
Maroon.
MUL
Multicolored.
PNK
Pink.
XXX
Unknown.
BLK
Black.
BLU
Blue.
BRO
Brown.
GRY
Gray.
GRN
Green.
HAZ
Hazel.
Page 42 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
MAR
Maroon.
MUL
Multicolored.
PNK
Pink.
XXX
Unknown.
IdentificationTypeEnum
Enumeration Values:
SID
NCIC
OfficerNumber
FBINumber
FIN
Federal Tax ID
SIN
State Tax ID
MaritalStatusEnum
Enumeration Values:
Single
Married
Divorced
Separated
Widowed
Widower
NameTypeEnum
Listing of the different types of names an individual can have.
Page 43 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Enumeration Values:
Real
This is the real name of the person.
Alias
This is the alias or the A.K.A. name of the person.
PartyTypeEnum
Enumeration Values:
Individual
Business
Agency
Institution
PhoneTypeEnum
Listing of the different types of phone numbers that an individual can have.
Enumeration Values:
Phone
Telephone number.
Fax
Fascimile Number.
Mobile
Mobile/Celular telephone number.
Pager
Pager number.
RaceEnum
NCIC recommended values for the race field. Records for Hispanics should be entered with
the race code most clearly representing the individual.
Enumeration Values:
W
White - a person having origins in any of the original peoples of Europe, North
Africa, or Middle East.
B
Black - a person having origins in any of the black racial groups of Africa.
Page 44 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
A
Asian or Pacific Islander - a person having origins in any of the original peoples of
the Far East, Southeast Asia, the Indian sub-continent or the Pacific Islands.
I
American Indian or Alaskan Native - a person having origins in any of the original
peoples of the Americas and maintaining cultural identification through tribal
affiliations or community recognition.
U
Unknown.
Page 45 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
RelationshipTypeEnum
Enumeration Values:
Husband
Wife
Father
Mother
Son
Daughter
BoyFriend
GirlFriend
Other
RoleTypeEnum
Enumeration Values:
Plaintiff
Defendant
Victim
Arresting Officer
Court Clerk
Judge
Justice of Peace
Witness
Complainant
Prosecuting Counsel
Defense Counsel
Probation and parole
SkinToneEnum
Listing of NCIC recommended values for the skin tone field.
Enumeration Values:
ALB
Albino.
Page 46 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
BLK
Black.
DRK
Dark.
DBR
Dark Brown.
FAR
Fair.
LGT
Light.
LBR
Light Brown.
MED
Medium.
MBR
Medium Brown.
OLV
Olive.
RUD
Ruddy.
SAL
Sallow.
YEL
Yellow.
StateEnum
Listing of NCIC recommended values for the State field. This field is used in a number of
places. This is a combination of codes for all the states and provinces in the US and Canada,
and codes for all the other countries. From an implementation standpoint, this list might have
to be segragated to present a different list of States and Countries. However, the codes being
returned from the user interface might have to be programatically reconciled to make them
compliant with this list.
Page 47 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Enumeration Values:
AA
ALBANIA
AB
ALBERTA
AC
AFRICA
AD
ANDORRA
AE
ANGUILLA
AF
AFGHANISTAN
AG
AGUASCALIENTES
AH
ASHMORE,CARTIER IS
AI
ANTIGUA
AJ
ARUBA
AK
ALASKA
AL
ALABAMA
AN
ALGERIA
AO
ANGOLA
AP
ARMENIA
Page 48 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
AQ
AZORES ISLAND
AR
ARKANSAS
AS
AUSTRALIA
AT
ARGENTINA
AU
AUSTRIA
AV
AZERBAIJAN
AY
ANTARCTICA
AZ
ARIZONA
BB
BARBADOS
BC
BRITISH COLUMBIA
BD
BAHAMAS, THE
BE
BAHRAIN/BAHREIN
BF
BASSAS DA INDIA
BG
BELGIUM
BH
BELIZE
Page 49 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
BI
BURUNDI
BJ
BAJA CALIFORNIA SUR
BK
BAKER ISLAND
BL
BANGLADESH
BM
BERMUDA
BN
BHUTAN
BO
BRIT IND OCEAN TERR
BP
BOSNIA, HERCEGOVENA
BQ
BOUVET ISLAND
BR
BURMA
BS
SOLOMON ISLANDS
BT
BOTSWANA
BU
BULGARIA
BV
BOLIVIA
BW
BALEARIC ISLANDS
Page 50 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
BX
BRUNEI
BY
BYELARUS
BZ
BRAZIL
CA
CALIFORNIA
CB
COLOMBIA
CC
CUBA
CD
CANADA
CE
CAMPECHE
CF
CHAD
CG
CAROLINE ISLANDS
CH
CHIHUAHUA
CI
CHIAPAS
CJ
CAMBODIA
CK
CZECHOSLOVAKIA
CL
COLIMA
Page 51 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
CM
CAMEROON
CN
CHINA
CO
COLORADO
CP
CAYMAN ISLANDS
CQ
CHILI
CR
COSTA RICA
CS
CYPRUS, REPUBLIC OF
CT
CONNECTICUT
CU
COAHUILA
CV
CAPE VERDI
CW
CENTRAL AFRICAN REP
CX
CONGO
CY
SRI LANKA
CZ
CANAL ZONE
DB
CLIPPERTON ISLAND
Page 52 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
DC
DISTRICT OF COLUMBIA
DD
COCOS ISLANDS, TERR
DE
DELAWARE
DF
DISTRITO FEDERAL
DG
COMOROS, FED REPUB
DH
BENIN
DI
COOK ISLANDS
DJ
CORAL SEA ISLND TERR
DK
DENMARK
DM
DOMINICA
DN
DJIBOUTI, REPUBLIC
DO
DURANGO
DR
DOMINICAN REPUBLIC
DU
DUCIE ISLANDS
EK
EQUATORIAL GUINEA
Page 53 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
EL
EL SALVADOR
EM
EAST GERMANY
EN
ENGLAND
EO
ETHIOPIA
ER
EUROPA ISLAND
ES
ESTONIA
EU
ECUADOR
EY
EGYPT
EZ
CZECH REPUBLIC
FA
FALKLAND ISLNDS
FD
FINLAND
FG
FRENCH GUIANA
FJ
FIJI
FL
FLORIDA
FN
FRANCE
Page 54 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
FO
FAROE ISLANDS
FP
FRENCH POLYNESIA
FR
FRNCH SO & ANTARCTIC
FS
FED STS OF MICRNESIA
GA
GEORGIA
GB
GABON
GC
GREECE
GE
GERMANY
GF
GUERNSEY, BAILIWICK
GG
GHANA
GI
GUINEA
GJ
GRENADA
GK
GAMBIA
GL
GILBERT, ELLICE IS
GM
GUAM
Page 55 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
GN
GREENLAND
GO
GLORIOSO ISLANDS
GP
GUADELOUPE, DEPT OF
GR
GUERRERO
GS
SO GEORGE,SANDWCH IS
GT
GUATEMALA
GU
GUANAJUATO
GY
GUYANA
GZ
GAZA
HD
HONDURAS
HE
MCDONALD, HEARD ISLD
HI
HAWAII
HK
HONG KONG
HL
HIDALGO
HN
VANUATU, REPUBLIC OF
Page 56 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
HO
HOWLAND ISLAND
HR
CHRISTMAS ISLND TERR
HS
SAINT HELENA
HT
HAITI
HU
HUNGARY
IA
IOWA
IB
ISLE OF MAN
IC
ICELAND
ID
IDAHO
IE
IRELAND
II
INDIA
IL
ILLINOIS
IM
MADEIRA ISLANDS
IN
INDIANA
IO
INDONESIA
Page 57 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
IQ
IRAQ
IR
IRAN
IS
ISRAEL
IT
ITALY
IU
NIUE
IY
COTE D'IVOIRE, REP
JA
JAPAN
JE
JERSEY, BAILIWICK OF
JI
JOHNSTON ATOLL
JL
JALISCO
JM
JAMAICA
JN
JAN MAYEN
JO
JORDAN
JR
JARVIS ISLAND
JU
JUAN DE NOVA ISLAND
Page 58 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
KB
KIRIBATI
KC
CROATIA
KE
KENYA
KH
MANAHIKI ISLAND
KI
KINGMAN REEF
KN
NORTH KOREA
KO
SOUTH KOREA
KR
KOREA
KS
KANSAS
KT
KAZAKHSTAN
KU
KUWAIT
KY
KENTUCKY
KZ
KYRGYZSTAN
LA
LOUISIANA
LB
LIBERIA
Page 59 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
LD
MOLDOVA
LE
LESOTHO
LF
SLOVAKIA
LH
LITHUANIA
LI
LIECHTENSTEIN
LN
LEBANON
LO
SLOVENIA
LS
LAOS
LT
LATVIA
LU
SAINT LUCIA
LX
LUXEMBOURG
LY
LIBYA
MA
MASSACHUSETTS
MB
MANITOBA
MC
MICHOACAN
Page 60 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
MD
MARYLAND
ME
MAINE
MF
MALAWI
MG
MONGOLIA
MH
MARSHALL ISLANDS
MI
MICHIGAN
MJ
MONACO
MK
NORTH MARIANA ISLNDS
ML
MALI
MM
MEXICO (REF ONLY)
MN
MINNESOTA
MO
MISSOURI
MP
MADAGASCAR
MQ
MORROCO
MR
MORELOS
Page 61 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
MS
MISSISSIPPI
MT
MONTANA
MU
MAURITANIA
MV
MALDIVES
MW
MIDWAY ISLANDS
MX
MEXICO
MY
MALTA
MZ
MALAYSIA
NA
NAYARIT
NB
NEBRASKA
NC
NORTH CAROLINA
ND
NORTH DAKOTA
NE
HOLLAND
NF
NEWFOUNDLAND
NG
NIGERIA
Page 62 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
NH
NEW HAMPSHIRE
NI
NORTHERN IRELAND
NJ
NEW JERSEY
NK
NEW BRUNSWICK
NL
NUEVO LEON
NM
NEW MEXICO
NN
NIGER
NO
PAPUA NEW GUINEA
NP
NEPAL
NQ
NEW CALEDONIA, DEP
NR
NAURU
NS
NOVA SCOTIA
NT
NORTHWEST TERR
NU
NICARAGUA
NV
NEVADA
Page 63 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
NW
NORWAY
NX
NETHERLANDS ANTILLES
NY
NEW YORK
NZ
NEW ZEALAND
OA
OAXACA
OC
MACAU
OF
NORFOLK ISLAND, TERR
OH
OHIO
OI
OKINAWA
OK
OKLAHOMA
OM
OMAN
ON
ONTARIO
OR
OREGON
PA
PENNSYLVANIA
PB
PUEBLA
Page 64 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
PC
PITCAIRN ISLAND
PD
PALAU, REPUBLIC OF
PE
PRINCE EDWARD ISLAND
PF
PARACEL ISLANDS
PG
GUINEAU-BISSAU
PI
PHILIPPINES
PK
PAKISTAN
PL
PALMYRA ATOLL
PM
PANAMA
PO
POLAND
PQ
QUEBEC
PR
PUERTO RICO
PS
ST PIERRE, MIGUELON
PT
PORTUGAL
PU
PERU
Page 65 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
PV
PARAGUAY
QA
QATAR
QR
QUINTANA ROO
QU
QUERETARO
RA
RUSSIA
RB
REP OF CONGO,BRZZVLL
RC
PEOPLES REP OF CHINA
RE
REUNION, DEPT OF
RF
RUSSIAN FEDERATION
RG
GIBRALTAR
RI
RHODE ISLAND
RR
MONTSERRAT
RS
WESTERN SAHARA
RU
ROMANIA
RV
VIETNAM,SCLST REP OF
Page 66 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
RW
RWANDA
RY
YEMEN, REPUBLIC OF
SA
SIERRE LEONE
SB
SAUDI ARABIA
SC
SOUTH CAROLINA
SD
SOUTH DAKOTA
SE
SEYCHELLES
SF
SOUTH AFRICA
SG
SENEGAL
SH
SAN MARINO
SI
SINALOA
SJ
NAMIBIA (SW AFRICA)
SL
SAN LUIS POTOSI
SM
SOMALIA
SN
SASKATCHEWAN
Page 67 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
SO
SONORA
SP
SPAIN
SQ
SWEDEN
SR
SINGAPORE
SS
SCOTLAND
ST
PEOPLES DEM REP YEMN
SU
SUDAN
SV
SVALBARD
SW
SWAZILAND
SX
USSR (REF ONLY)
SY
SYRIA
SZ
SWITZERLAND
TA
TAMAULIPAS
TB
TABASCO
TC
UNITED ARAB EMIRATES
Page 68 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
TD
TRUST TERR PCFIC IS
TE
SPRATLY ISLANDS
TF
TUAMOTU ARCHIPELAGO
TG
TONGA
TH
THAILAND
TI
PORTUGESE TIMOR
TJ
TAJIKISTAN
TK
TOKELAU
TL
TLAXCALA
TM
TROMELIN ISLAND
TN
TENNESSEE
TO
TOGO
TP
SAO TOME & PRINCIPE
TQ
TONGAREVA
TR
TURKS, CALCOS ISLNDS
Page 69 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
TS
NEVIS, ST CHRISTOPHR
TT
TRINIDAD
TU
TUNISIA
TV
TAVALU
TW
TAIWAN
TX
TEXAS
TY
TURKEY
TZ
TANZANIA, UNITED REP
UA
UNITED ARAB REP (RO)
UG
UGANDA
UK
UKRAINE
UM
MAURITIUS
UR
TURKMENISTAN
US
US OF AMERICA
UT
UTAH
Page 70 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
UV
BURKINA FASO
UY
URUGUAY
UZ
UZBEKISTAN, REP OF
VA
VIRGINIA
VB
BRITISH VIRGIN ISLND
VC
VERACRUZ
VI
VIRGIN ISLANDS
VL
NAVASSA ISLAND
VM
VIETNAM (REF ONLY)
VN
NO VIETNAM(REF ONLY)
VS
SO VIETNAM(REF ONLY)
VT
VERMONT
VV
ST VINC & GRENADINES
VY
VATICAN CITY
VZ
VENEZUELA
Page 71 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
WA
WASHINGTON
WB
WEST BANK
WF
WALLIS, FUTUNA TERR
WG
WEST GERMANY
WI
WISCONSIN
WK
WAKE ISLAND
WL
WALES
WN
WEST INDIES
WS
WESTERN SAMOA
WV
WEST VIRGINIA
WY
WYOMING
YG
YUGLOSLAVIA
YO
MAYOTTE, TERRITORIAL
YT
YUKON (TERRITORY)
YU
YUCATAN
Page 72 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
ZA
ZACETECAS
ZB
MARTINIQUE
ZC
SURINAM
ZI
CANARY ISLANDS
ZO
MOZAMBIQUE
TimeTypeEnum
Enumeration Values:
AM
AM.
PM
PM.
YesNoEnum
Enumeration Values:
Y
Yes.
N
No.
U
Unknown.
Page 73 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
CJIS Data Dictionar y
S tat e o f N ew Hamp sh ir e 6/22 /2 010 Public Ser vices
Utility Details
The Utility section contains any utilities that will be useful in various places in the CJIS Object
Model.
Class Diagram: Utility Details
UTILITY DETAILS
ActionDateTime
actionID
day
month
year
time
timeType : TimeType
dateTime : Date
ActionDateTime
Elements and Attributes:
actionID (Required, String)
day (Required, String)
month (Required, String)
year (Required, String)
time (Required, String)
timeType (Required, TimeType)
dateTime (Required, Date)
Page 74 of 74
This document is not to be distributed without explicit authorization from New Hampshire - Department of Safety
Related docs
Get documents about "