Dave
|
|
Group: Administrators
Posts: 13K,
Visits: 108K
|
There'll be a separate data file for every participant on the server -- you simply delete the ones you don't want / aren't allowed to keep.
|
|
|
jbfleming
|
|
Group: Forum Members
Posts: 46,
Visits: 75
|
So theoretically, if we were under obligation to delete a subject's data, we could download the data from Inquisit, delete their data from our copy, and delete the files on Inquisit server (and new data will go in a new file that starts empty again)?
I don't think we're going to encounter this situation often, or at all, we just need to be able to comply if it comes up.
|
|
|
Dave
|
|
Group: Administrators
Posts: 13K,
Visits: 108K
|
You can't *edit* data files on the server, but you sure can delete them.
|
|
|
jbfleming
|
|
Group: Forum Members
Posts: 46,
Visits: 75
|
They won't be able to screen in using the same IP, so if the same IP shows up more than once in actual data, they are cheating somehow by re-using the URL.
I understand that may exclude some people from screening in for the reason you state, but that is okay with us for now.
Another question: The data that is stored on the Inquisit server, are we able to edit that? Or only download it and edit it locally? We are giving participants the option to withdraw their data from the study, and ideally we'd want to delete their data within a few days if they request that. Thanks!
|
|
|
Dave
|
|
Group: Administrators
Posts: 13K,
Visits: 108K
|
You'll have to have participant tracking enabled in your web experiment's settings -- that tracking data includes public IP and you can use that to filter. Note, though, that many people may be behind a NAT -- i.e., share the same public IP with many others -- and thus I'm not sure you really want to toss out data sets based on IP only.
|
|
|
jbfleming
|
|
Group: Forum Members
Posts: 46,
Visits: 75
|
OK - but we will have the IP address recorded, correct? So, we could throw out data from duplicate IPs?
|
|
|
Dave
|
|
Group: Administrators
Posts: 13K,
Visits: 108K
|
> How do we prevent someone who has already screened in and has the URL to the Inquisit launch page, from going through the study more than once from a single IP?
I can think of no way to do this, I'm afraid.
|
|
|
jbfleming
|
|
Group: Forum Members
Posts: 46,
Visits: 75
|
So, we've decided to add our consent form to our eligibility process on a separately hosted web page. It's straightforward what it will do: ask screening questions, determine eligibility, get informed consent, assign group number, give a link to the Inquisit-hosted launch page with the assigned group # in the URL, etc. One of our eligibility requirements is that we don't want people to be able to do the study more than once from a single IP address (keeping in mind all of the reasons that doesn't guarantee we won't have repeat users and that it will possibly exclude some valid people because of shared computers, NAT, etc.).
We can do that on our end in the screener fairly easily. How do we prevent someone who has already screened in and has the URL to the Inquisit launch page, from going through the study more than once from a single IP?
|
|
|
Dave
|
|
Group: Administrators
Posts: 13K,
Visits: 108K
|
For /errormessage to work, /correctresponse (or /iscorrectresponse) must be defined.
Edited to add: Example
<block myblock> / trials = [1=myopenended] </block>
<openended myopenended> / validresponse = (anyresponse) / correctresponse = (anyresponse) / iscorrectresponse = [openended.myopenended.latency >= 10000] / response = correct / errormessage = (errmsg, 500) </openended>
<text errmsg> / items = ("Please take a little more time to respond...") / position = (50%, 75%) </text>
|
|
|
jbfleming
|
|
Group: Forum Members
Posts: 46,
Visits: 75
|
I'm trying to use /errormessage to display a message if the user tries to advance past the openended question with the isvalidresponse set up to only allow moving on after 30 seconds. It doesn't seem to be doing anything. Should this be possible?
|
|
|