BREAKING CHANGE: Update data paths

[RobertGemmaJr]

• This changes the directory to which data is saved - any matlab scripts that labs may be using to parse the data will need to be updated

Folder Structure

The big change here is how we're nesting the folders. The file follows the following structure:

/data/mode/studyID/participantID/start_date.json

• mode: development or production
• studyID: The ID of the study the participant logged in as
• participantID: The ID of the participant on the studyID the participant logged in as

That structure is nested inside userData while the participant is running through the experiment and then is copied into an output folder (Desktop/getName) when the participant finishes the experiment.

1. data is used to separate the output data from the experiment from any other data that may be included. I don't really have anything in mind but have noticed Honeycomb users tend to have other information (matlab scripts, papers, etc) in the folder. I like data as a better delineator here rather than jumping straight into studyID
2. mode is used to further delineate production data from data that was created during development. Most users have a separate lab computer for the production data so it's not much of a change but is definitely helpful for me. Plus we basically get it for free now that we're using Vite!

User data

I was looking to move the "running" file save to the temp folder but everything I've been reading online points to saving the data in userData like it was. This way the data will stay there permanently.

Note that the really important quirk of userData is the fact that is saves partial run-throughs of the experiment. If a participant begins the experiment but quits the app before completing it (including app errors/crashes) the data will still be saved in userdata it just won't be copied over to the desktop. I think it's best to leave it as userData so that those partial run-throughs will be saved permanently, just hidden away.

Output

Maintains that the data file(s) are created on the desktop at the end of the file. The file is copied from userData. Eventually I'd like for this path to be customizable but that's not a super pressing feature, the lab can change it with a single line of code if the really need

[github-actions]

Visit the preview URL for this PR (updated for commit 5caa0b7):

https://ccv-honeycomb--pr476-ref-paths-2eyroq5u.web.app

_{(expires Thu, 23 May 2024 19:22:15 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 4ace1dcea913a952d2a1af84b94a4421bf36e610}