|
jbfleming
|
|
|
Group: Forum Members
Posts: 46,
Visits: 75
|
1) In our experiment, there are two tasks that have an <openended> entry box. The instructions are to "spend a few minutes" thinking and writing something in the box. We don't want to strictly force them to sit at that page for too long or they may wander away and not complete the experiment. But we would like to make it impossible to proceed for, say, 30 or 60 seconds, in the hopes of enforcing not just flying through that page. Is that possible?
2) At the end of the experiment, we debrief the participant and offer a chance for them to withdraw their data from the study. The simple form this takes now is to have them enter "DELETE MY DATA" or something in a textbox. The idea is, we will manually find cases where that was entered and manually delete that data. Can we delete that data on the Inquisit-hosted copy of the data or only after we download it? And of course, if there were any way to automate this, that would be great--I could not determine that there was.
3) Users coming to this experiment URL will have already completed an eligibility screening separately and been randomized into an experimental condition. But they won't have completed the informed consent process. How do most people handle that? Doing it within the Inquisit experiment seems clumsy. Can we do it with a page hosted by Inquisit somehow, like the launch page?
Getting closer to putting this online...!
Thanks! John
|
|
|
|
|
Dave
|
|
|
Group: Administrators
Posts: 13K,
Visits: 108K
|
#1: Yes. You can do that via /isvalidresponse.
<openended myopenended> [...] / isvalidresponse = [openended.myopenended.latency >= 30000] </openended>
#2: No, there is no automated way to do this -- you need to go down the manual deletion route.
#3: Well, you could use the launch page -- if a given person doesn't consent, she/he should never hit the "Start" button. Otherwise you can do it within the script. Run a <trial> at the beginning that asks for consent and if people decline quit the script based on the response in that trial via the script.abort() function.
|
|
|
|
|
jbfleming
|
|
|
Group: Forum Members
Posts: 46,
Visits: 75
|
The isvalidresponse worked for the pause, thanks!
Regarding informed consent, we have a form that needs to be displayed and agreed to. It could be displayed as part of the experiment but that seems kind of awkward to me for some reason. especially since that will have required them to download a plug-in only to then not consent and not proceed. I'll keep thinking about it.
|
|
|
|
|
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?
|
|
|
|
|
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
|
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
|
> 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
|
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
|
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
|
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!
|
|
|
|