In dickoa/robotoolbox: Client for the 'KoboToolbox' API

knitr::opts_chunk$set(
  collapse = TRUE,
  message = FALSE,
  warning = FALSE,
  echo = TRUE,
  comment = "#>"
)

KoboToolbox audit logging feature records all activities related to a specific form submission in a log file. This log file can include things like when the form was opened, when individual questions were answered, when the form was saved, and when it was finally submitted. This feature provides a detailed record of the timing and sequence of events associated with each form submission.

This feature is particularly beneficial for several reasons:

• Data Quality Control: Audit logs can help data managers in verifying that data collection activities are happening as planned. For example, if a survey is supposed to take 20 minutes on average and you see many instances of it being completed in 2 minutes, that could be a sign of rushed or careless data entry.

• Troubleshooting: If issues with data collection arise, the audit logs can provide clues as to what might be going wrong. For example, if a particular question is often being skipped or answered incorrectly, that could suggest a problem with the question wording or placement.

• Security and Accountability: If data are altered or deleted, audit logs can provide a trail of what happened and who was involved. This can be important for maintaining the integrity of the data and holding individuals accountable for their actions.

• Workflow Management: Managers can better comprehend the duration of different parts of the data collection process and seek ways to increase efficiency by reviewing the timestamps in the audit logs.

Audit logging data

The following form provides a simplified example to demonstrate how audit logs can be read using robotoolbox.

library(robotoolbox)
library(dplyr)

l <- asset_list

• Survey questions

| type | name | label | parameters | |:-----------|:-----------|:------------------------|:---------------------------------------------------------------------------| | start | start | | | | end | end | | | | username | username | | | | audit | audit | | identify-user=true location-priority=balanced location-min-interval=60 location-max-age=120 track-changes=true track-changes-reasons=on-form-edit | | text | Q1 | Q1. What is your name? | | | integer | Q2 | Q2. How old are you? | |

We have four metadata questions: start, end, username and audit. You need to have the audit metadata question enable to use this feature. We also have two questions: Q1 and Q2.

Loading the project

The above form was uploaded to the server. It's the only project named Audit multi params, and can be selected from the list of assets asset_list (using kobo_asset_list).

library(robotoolbox)
library(dplyr)
asset_list <- kobo_asset_list()
uid <- filter(asset_list, name == "Audit multi params") |>
  pull(uid)
asset <- kobo_asset(uid)
asset

asset <- asset_audit
asset

Extracting the audit data

In order to get the audit logging, we need to use the kobo_audit function.

df <- kobo_audit(asset)
glimpse(df)

df <- data_audit
glimpse(df)

The columns in the audit logging data include:

• _id : This columns generated by robotoolbox, allows you to map the _id of the submissions in kobo_data.

• event: This column records the action that took place. The different event types include form start, form exit, question, group questions, end screen, and device or metadata audit.

• node: This column records the name of the question or group related to the event.

• name: This column is appended by robotoolbox to match the name of the question in the audit and the data from kobo_data.

• start_int: This column records the timestamp when the event started in integer timestamp.

• end_int: This column records the timestamp when the event ended in integer timestamp.

• start: This column records the timestamp when the event started in date time format (POSIXct).

• end: This column records the timestamp when the event ended in date time format (POSIXct).

• latitude: This column records the latitude of the device when the event occurred.

• longitude: This column records the longitude of the device when the event occurred.

• accuracy: This column records the GPS accuracy of the location data.

• old-value: This column records the previous value of the question before it was changed in this event.

• new-value: This column records the new value of the question after it was changed in this event.

• user: This column records the username of the data collector.

• change-reason: This column records the reason before they save changes to a form.

The structure of the output depends on the audit logging parameters you set in your form. For instance, if you set the parameter track-changes=true, the columns old-value and new-value become available. latitude, longitude and accuracy are associated to the parameter location-priority. The user column is available when you use the identify-user=true parameter. Using the parameter track-changes-reasons=on-form-edit prevents editing of filled-out forms without providing a reason. These reasons are recored in the change-reason column. You can learn how to use audit logging in the documentation of KoboToolbox and ODK.

• ODK's guide on audit logging: https://docs.getodk.org/form-audit-log/
• KoboToolbox's guide on audit logging: https://support.kobotoolbox.org/audit_logging.html

dickoa/robotoolbox documentation built on July 12, 2024, 1:55 p.m.