Saving Pyschopy Task CSVs in external storage such as Google Drive/Onedrive

Greetings, everybody!

Our laboratory has developed a psychopy task that we would like to share with other research labs. By providing them with the online task URL, they can ask their own participants to easily access and participate in the task. However, the challenge we face is that when someone uses our Psychopy task URL, the resulting CSV files are currently stored in our GitLab repository. This means that we have to manually share the CSVs with each lab that uses our task :frowning:

I am curious if anyone knows of a solution that would enable others to use our task URL while allowing them to store their participants’ CSV responses in their preferred storage locations, such as OneDrive, Google Cloud, or other platforms. The main constraint is that we want to avoid requiring them to create their own GitLab repository for this purpose.

If you have any suggestions or solutions, please share them with us. Your input would be greatly appreciated! Thank you.

One ways I can think of to allow other labs to access their data would either be to add one person from each lab to your repository. They would all be able to access all of the data but if the participant ids started with a different letter for each lab it would be fairly easy to separate them.

The other way would be for each lab to fork your repository and then run the experiment from their fork. Why do you want to avoid this? They wouldn’t need to install PsychoPy, but would need a Pavlovia account and pay for credits or have a Pavlovia licence - so perhaps that is the reason.

Thank you so much for your comments!

  1. I considered the initial solution you proposed as well. However, we don’t want to grant access to other laboratory members to view CSV files belonging to participants of others.

  2. That sounds feasible! However, one concern is that if we make any updates, all the labs using our task would also need to update their repositories accordingly. While some might argue that updating a repository is straightforward, our goal is to find the easiest possible solution so that numerous labs can effortlessly incorporate our task.

I truly appreciate your suggestions!