Differences

This shows you the differences between two versions of the page.

--- en:survey:unique-respondents [10.07.2018 11:27] – [Exclude multiple participation] mindset-geburt
+++ en:survey:unique-respondents [10.07.2018 21:22] – [Data clearing] admin
@@ Line 1: / Line 1: @@
-====== Exclude Multiple Participation ======
+====== Prevent Multiple Submissions by the Same Respondent ======
 Theoretically, in the standard setting an online questionnaire can be completed by anyone as often as desired. In scientific surveys it is usually not very attractive for the participant to answer an extensive questionnaire several times. However, the situation might be different if the survey contains a vote or if there is an incentive for filling in the form.
-Multiple participation can be restricted by [[:en:create:access|Access Restrictions]].
+**Note:** To restrict who may access the questionnaire at all, use [[:en:create:access]]. This is also where "serial" and "mailing" restrictions are set.
 ===== Individual participation keys =====
@@ Line 41: / Line 41: @@
 IP is the Internet Protocol. Every computer with internet needs an IP address that is transmitted to a server when a request is made. The server's response (e.g., an HTML website) is sent back to this IP address.
-SoSci Survey allows to record IP addresses. However, the IP address is considered as personal data in German jurisdiction. Therefore, the data record must be treated in accordance with the strict provisions of the BDSG (Federal Data Protection Act) if IP addresses are recorded. Also because participants can no longer be assured of complete anonymity. Therefore, the recording of IP addresses must be actively activated by the project manager in the[[privacy|Privacy Settings]].
+SoSci Survey allows to record IP addresses. However, the IP address is considered as personal data in German jurisdiction. Therefore, the data record must be treated in accordance with the strict provisions of the BDSG (Federal Data Protection Act) if IP addresses are recorded. Also because participants can no longer be assured of complete anonymity. Therefore, the recording of IP addresses must be actively activated by the project manager in the [[privacy|Privacy Settings]].
 For the following reasons IP addresses are of little help for the control of multiple subscribers:
@@ Line 65: / Line 65: @@
 If multiple entries are expected in competitions data cleansing might help. It is very unlikely that a participant will fill out the same questionnaire several times with the same motivation. It is much more likely that they complete the questionnaire as quickly as possible.
-If one excludes "rusher" in the course of data cleansing one should already have identified most multiple participants. This could e.g., be done by identifying questionnaires that were answered extraordinarily quickly, as well as cases with more than 20% missing answers (cf. variable [[:en:results:variables#interview-fortschritt|MISSREL]]). See [[https://www.researchgate.net/publication/258997762|Leiner (2014)]]for more information on data cleansing.
+If one excludes "rusher" in the course of data cleansing one should already have identified most multiple participants. This could e.g., be done by identifying questionnaires that were answered extraordinarily quickly, as well as cases with more than 20% missing answers (variable [[:en:results:variables#interview-progress|MISSREL]]). See [[https://www.researchgate.net/publication/258997762|Leiner (2014)]] for more information on data cleansing.
-If you collect the contact data for the competition separately from the other data ([[:de:create:questions:contact|Collect Contact Data Separately]]) you have to make sure that fast participants cannot register by using the PHP function ''[[:en:create:functions:casetime|caseTime()]]''.
+If you collect the contact data for the competition separately from the other data ([[:de:create:questions:contact|Collect Contact Data Separately]]) you have to make sure that fast participants cannot register by using the PHP function ''[[:en:create:functions:casetime]]''.