To view options related to paradata
collection, select Paradata
from the Options
menu in a data entry or batch edit application.
A paradata event contains information about some aspect of the data collection or editing process. The dropdown list contains three options:
- No: This disables paradata collection.
- Yes: Some Events: This enables paradata collection for some events. You can select the events that you would like to collect by checking or unchecking the checkbox next to the name of each event. You may want to disable some events to reduce the size of the paradata log or if you are concerned about collecting sensitive information.
- Yes: All Events: This enables paradata collection for all events.
The following is a summary of each kind of event that CSPro can collect:
- Data Source: Information about interactions with CSPro data files, including what files were used, what cases were loaded and saved, etc.
- Device State: Details about the data collection device, including indicators about whether GPS, Bluetooth, and Wi-Fi were enabled; what mobile network the device was using; etc.
- External Application: Information about external applications (or CSPro data entry applications) launched from CSPro.
- Field Entry: Details about each field entered, including how long the interviewer spent answering the question, how the program reached that field, etc.
- Field Movement: Information about each field movement, including how the program reached and exited each field.
- Field Validation: Details about CSPro's validation of each entered field, including information on which value set was used and whether or not the field was successfully validated.
- GPS: Information about GPS collection, including the duration to take fresh GPS readings.
- Impute: Details about which items were imputed, including the initial and imputed values.
- Language Change: Information about which language was initially used and records of language changes during the course of data collection.
- Message: Details about any error message triggered during data collection.
- Note: Information about notes left by interviewers (or via logic) during the execution of the program.
- Operator Selection: Details about selections made by the operator as a result of requests coming from functions such as accept or the userbar.
- Property: Information about what CSPro settings were used, or changed, during the program's run.
You can explore these events in more detail using the Paradata Viewer's Table Metadata
For advanced users writing SQL queries on the paradata tables, note that the base "event" table links to each of these event tables, and that some of these events link to other tables with names that end in "_info" or "_instance."
Some of the events listed above can store sensitive information in the paradata log, which is why you can disable the collection of this information while still storing the non-sensitive portions of the event:
- Field values: The Field Validation event can store each value entered into a field. This can be useful if you want to look at the frequency of valid and invalid values, but if you do not want such data stored in the paradata log, you should disable this. The Note event also uses this option to determine if note text should be stored in the paradata log.
- GPS coordinates: The GPS event can store the coordinates of the interviewers. If you do not want this data stored in the paradata log, you should disable the collection of the latitude and longitude coordinates, though other information (altitude, accuracy, etc.) will still be stored.
- Cases loaded via logic loops: This is not an option related to sensitive information, but if your application loops through external data files in logic (using forcase or loadcase), the paradata log will become very large quickly due to a preponderance of Data Source events. You can disable this information if you do not plan to analyze it.
- Initial property values: If this option is enabled, the initial property settings will be stored as Property events in the paradata log when your application begins. This can lead to a large amount of paradata that is potentially not useful. If disabled, only information about changes to properties will be stored.
The default setting is for all of these options to be disabled.
Most events are triggered by some action (e.g., an error message appearing), but two events can occur in the background, even if the interviewer is not doing anything. These background events only occur in data entry applications:
- Device state: Information about the device as described above in the Device State event.
- GPS location: Unless a GPS reading is in progress, the device's GPS unit will be turned on and CSEntry will attempt to take a GPS reading. Once a GPS reading with accuracy 10 meters or less is taken, or once two minutes have elapsed, the GPS unit will be turned off.
The value listed indicates the number of minutes between events occurring, or 0 if the event should be disabled. For example, a value of 30 for GPS location means that CSEntry will attempt to store the GPS coordinates of the interviewer every half hour.