Hi Becky,
I'm not sure this will be the solution for all the features you need, but it might be:
Since JATOS v.3.5.1 participants have the possibility of uploading arbitrary files (like videos) using jatos.uploadResultFile (
https://www.jatos.org/Submit-and-upload-data-to-the-server.html). I'm not sure if you know this but your description of the problem, where participants upload videos to the JATOS server outside of JATOS makes me think you might not. Now you can do it all within JATOS.
These uploaded files are available only within a single study run, so they are available for the participant who uploaded them only.
So, if you need participants to access the files only at a later session, this is what I would do:
- Say you have a study with components 1,2,3. Component 1 is the gatekeeper. If it's a new participant, they will be directed to component 2 where they do the task, upload the study, etc.
- At the end of component 2, do not use any of the jatos.endStudy or jatos.startNextComponent functions. Instead, simply display a message telling participants that 'they can now close the tab'. This will keep the study unfinished, and participants will be able to come back to it later. Set a flag in the batch session data where you have the subjectID and a value that tells your JS whether the video was uploaded.
- Have the experimenter check the video from the GUI. Once they approve it, they can edit the batch session data and change a flag that tells your code that the video was approved.
- Now participants can use the same link to start the study from component 1. Your code will read the flag in the batch session data (corresponding to the subjectID's entry) that the video was approved, and redirect participants to component 3. Participants can now see the video, and at the end, finish the study.
I *think* this does all you need, but might have missed something.
Hope it helps!
Best
Elisa