JATOS Import study features
Hello,
What would be the recommended way to update the assets of my study. For example: I work locally, finish my main development, then export from my local jatos and then import in my server. That works fine.
But for small changes, let's say, a couple of words in an html file, I am left with either ftp to re-upload my file (so I need sftp access to the server) or delete and re-import my whole experiment. That implies re-starting from scratch in the server.
Are there any other options to accomplish this?
Thanks!!
Alex
Comments
Hi Alex,
You don't need to SFTP into the server - it's much easier: You can use JATOS' UI to just overwrite a study. The procedure is simple:
1) Change your study on your local JATOS (edit your HTML or change whatever asset files you have there)
2) Export the study locally and import it in your server JATOS (with the normal import button)
3) You will be told that this study already exists and whether you want to overwrite it. You can even choose (in the advanced options) if you only want to overwrite the assets (all files) and/or the properties (everything in Study Properties / Component Properties, e.g. JSON Input Data). Click okay and you are done.
Result data or result files will stay untouched this way. So if you have a study running with some result data gathered and you just want to update an HTML file, you are on the safe side.
Another way, for how to deal with ever changing input data, is to put it into the JSON Input field that is part of every Study Properties and Component Properties (red box in the image).
Here you can put whatever you want in JSON format and you will be able to access it in your JavaScript via jatos.studyJsonInput or jatos.component.JsonInput. And since it is in JATOS UI you can update it on-the-fly (even while the study is running). But I have to admit this feature of JATOS is not well documented in our docs :/.
Best,
Kristian
Thanks for the response Kristian! That is how I actually end up doing it.
Regarding the JSON input field. Yess! A bit more documentation on that would be awesome.
Alex