Feature request: Explicit confirmation before experiment is started

[smathot]

For some worker types, the link expires after it has been started. In my experience, users do this all the time. You can tell them very clearly to not click the link unless they actually want to launch the experiment, but many of them do it anyway.

Would it be possible to have an explicit confirmation button that users need to click before the experiment is launched? I'm aware of the preview functionality, and I suspect that it can be made to work with OSWeb, but it strikes me as an unnecessarily complicated way to avoid the simple issue of users clicking on the link.

[kristian-lange]

Hmm, that sounds feasible.

1. worker uses study link
2. if link is legit, JATOS shows page with confirmation button
3. only when clicked JATOS starts study

In the prefs we could have an option to show or not to show this confirmation button.
Let us think about it.

[kristian-lange]

@smathot, we thought about it again and would propose a slightly different approach. We would change the preview feature.

Right now a study with preview is set up during link creation. For OpenSesame/OSWeb this has the problem that you can't set it up via export/import of a study. The checkbox has to be checked by the user of JATOS and they might not be aware of it.

We propose an additional setting in the study properties. Those you can write from OSWeb (you do already). This field could be something like a boolean 'isPreviewAllowed'. Although this means that you would need an additional JATOS component, additionally to the OSWeb one. This component would contain the confirmation button you are looking for and could potentially contain other stuff like introduction or consent.

The advantage is that you can determine this confirmation page completely by yourself (layout, text etc.) - the disadvantage is that you have to define an additional JATOS component (although this should be a one time thing).

[smathot]

This would be acceptable. It strikes me as a bit more complicated then necessary, but if you feel that this is the best route then we can certainly build this into OpenSesame.

[kristian-lange]

It is versatile. You (and others) could define their own layout and wording, using their own language of this confirmation page.

…

On Thu, Apr 18, 2019, 15:49 Sebastiaan Mathot ***@***.***> wrote: This would be acceptable. It strikes me as a bit more complicated then necessary, but if you feel that this is the best route then we can certainly build this into OpenSesame. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#164 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB6V4BVFNEBSNBS5EZEJAKTPRB36PANCNFSM4HFRFV2Q> .

[kristian-lange]

@smathot Are you still interested in this feature? I would implement this the next then.

[kristian-lange]

Feature is part of 3.7.1