data requirements |
Individual Level Analysis in NAVCAP requires at least one set of co-event data with the following information:
(1) Unique Individual identifiers: some alpha-numeric code that uniquely identifiers, i.e., each individual has exactly one such code that is associated solely with that individual. (2) Unique Event Identifies: some alpha-numeric code that uniquely identifies the events in which individuals are involved. Often times this is an arrest number, a booking number, or incident number. (3) Date: typically, some date associated with each event or "tie." If you don't have an actual date, don’t worry: you can enter in any date, maybe the date you entered the data. This will not affect the analysis, but is "required" for the program to run. Click here if you would like to see a super basic example. |
data format |
SafetyNET requires one dataset to operate: a comma separated file (.csv) containing three variables: (1) a unique individual identifier (Person ID), (2) a unique event identifier (Event ID), and a date (Arrest Date). The program will not operate without these three pieces of data. Importantly, the dataset must be called “Arrest” in order for the program to identify the proper file. The data need not be for actually arrests: the file just needs to be labeled “Arrest” for identification purposes.
Data must uploaded in a simple .csv format (easily exported from a program like Microsoft Excel or NotePad) and must have a specific set of column headers/names. A list of the required column heading and variable formats can be found here (click here). Perhaps the easiest way to create the necessary "Arrest.csv" format is to copy and paste existing data into a pre-formatted file, like this one (click here). |
additional data |
Three optional files can also be uploaded to SafetyNET that are can be linked with the Arrest file through the use of the Person ID variable:
(1) “Gang” table ~ a csv file containing a unique Person ID for someone in the Arrest file along with the Gang Name of that individual (2) “Victim” table ~ a cvs file containing a unique Person ID for someone in the Arrest file and some information on the type of victimization or injury a person received (e.g., homicide or shooting victim). (3) “POI” table ~ a cvs file containing a unique Person IDs for someone in the Arrest file who is of interest to the user, for example, an individual who is part of a current violence prevention or intervention effort. Again, the easiest way to create these tables is to copy and paste existing data into a pre-formatted files, like these (click here). |
example data |
Perhaps the easiest way to get up and running in SafetyNET is to upload some "example" data and fiddle with the program. If you can get these example datasets to work, you should be able to upload your own data. Use these data files as templates, cutting and pasting your own data in them is one way to go!
|