Export result: no WorkerID or ResultID Jatos 3.5.1/Osweb 1.3.7
Hello everyone,
I have an installation of Jatos 3.5.1.
With an experiment with OS 3.2.8 (Osweb 1.3.3) is working fine but now and then I lose some trials. (If the participant answer/respond very fast)
I update to OS 3.3 with Osweb 1.3.7 but now I have the problem that I don't have the WorkerID or ResultID in the Exported Result from Jatos. (I use one General Single Worker)
Do I have to flag/set something in Jatos?
Another thing is that I have a lot of DATA_RETRIEVED/RESULTDATA_POSTED, does that mean that some participant press the link and do not complete the task?
Thanks,
Paolo
Comments
Hi Paolo,
yes, updating OSWeb and JATOS should fix the problem with the lost trials.
I update to OS 3.3 with Osweb 1.3.7 but now I have the problem that I don't have the WorkerID or ResultID in the Exported Result from Jatos. (I use one General Single Worker)
Those IDs were added by OSWeb to the result data and maybe they don't do this in the new version anymore (I actually don't know). But you can export those IDs and other meta data with the 'Export Metadata' button in JATOS results page (http://www.jatos.org/Manage-Results.html#export-metadata-jatos-version--331). The only problem left is to align the meta data with your result data, but since they have the same ordering it's doable.
Another thing is that I have a lot of DATA_RETRIEVED/RESULTDATA_POSTED, does that mean that some participant press the link and do not complete the task?
DATA_RETRIEVED and RESULTDATA_POSTED are two states a component (one element of a JATOS study) can have. DATA_RETRIEVED means the component just started and RESULTDATA_POSTED means that some result data were posted. The last state of a successful component is FINISHED. That you have a lot of DATA_RETRIEVED/RESULTDATA_POSTED means that you participants didn't finish your study until the end. This can have many reasons. Often participants just don't finish a study (e.g. got bored). But it's also possible there is a bug in your study and your participants just are not able to continue. Then, sometimes sending of result data just takes to much time (especially if the participant has a slow internet connection) and they close the tab in the browser. It's difficult to say what causes your DATA_RETRIEVED/RESULTDATA_POSTED.
Best,
Kristian
Hi Kristian!
Thank you so much for your reply! It's very clear!
For the first problem, I'll start to export the metadata and pair it with the results.
I will check the experiment again to see if there are problems in some cases.
Best,
Paolo
I added this to my inline_Js:
and I added workerIdaMano to the logger, is working.