SoSci Survey stores activities in the survey project in two logs:
The management log is retained even after a survey project has been archived.
If the event is triggered by a user, the user name and the IP address used by the user are stored in addition to the timestamp. For some events, additional information is stored. For example, the data download stores a hash value of the transmitted file, so that the authenticity of the data can be proven later on.
The following events are recorded in the management log:
| Code | Description |
|---|---|
p.create | Registration of the survey project |
p.archive | Archiving of the survey project |
p.clear | Deletion of the project-related database entries |
p.delete | Deletion of the survey project |
p.folder | Change of the project URL |
p.period | Change of the survey period |
p.agreement | Conclusion of a project-related agreement (in particular a DPA) |
p.timezone | Change of the time zone in the Project Settings |
data.down | Download of the collected data |
data.drop | Deletion of the collected data |
data.drop.sc | Configuration of an automatic deletion of data |
case.drop | Deletion of a single case from the collected data |
case.edit | Creation of a link under Collected Data → Restart an Interview Case |
rc.add | Adding one or more address entries to the List of Contacts |
rc.rm | Deletion of one or more address entries |
rc.mod | Editing an address entry |
rc.lock | Blocking of an address entry by the person concerned (up to SoSci Survey version 3.8.00) |
auth.grant | Sharing the survey project with a user account (Shared Access to Projects) |
auth.change | Change of a project share |
auth.revoke | Deletion of a project share |
auth.grant.ack | Acceptance of a project share by the other user |
auth.owner | Change of the project manager |
dso.assign | Assignment of a user account for privacy approvals |
dso.remove | Removal of the user account for privacy approvals |
The extended documentation may contain collected data and is deleted when a survey project is archived.
In the Project Settings, in the tab Privacy, specify which events shall be recorded. You can select the following categories:
| Category | Setting |
|---|---|
| General | (These events are always recorded) |
| Records | Log creation of records and eventual deletion of empty records |
| Changes | Log changes to the data (responses in the questionnaire) |
| Entries | Log any data collected in the questionnaire |
| Comprehensive | Log POST/GET raw data for all requests |
The following events can be recorded.
| Code | Description | Category |
|---|---|---|
case.delete | Deletion of a case from the dataset | Records |
case.leave | A person leaves the interview via “cancel and delete collected data” | Records |
data.reset | Deletion of the collected data | Records |
case.create | Start of an interview | Records |
data.store | Storing the response to a question in the dataset | Entries |
data.change | The response to a question was changed | Changes |
request | Data transmission from the browser to the server incl. all transmitted information | Comprehensive |
address.lock | Blocking or deletion of an address entry by the recipient | General |
data.anonymize.auto | Scheduled anonymization of one or more records | General |
data.delete.auto | Scheduled deletion of one or more records | General |
ds.php.request | Creation of an approval request for PHP code | General |
ds.php.approve | Approval of PHP code as part of a privacy approval | General |
ds.identify.request | Manual approval request for the de-pseudonymization of an address entry | General |
ds.identity.auto | Automated approval request for the de-pseudonymization of an address entry | General |
ds.identify.grant | Approval of the de-pseudonymization of an address entry | General |
ds.identitiy.view | Viewing the identity of an otherwise pseudonymous address entry | General |