Skip to main content
Version: v2.4.1

The Lifecycle of a reVISit Study

A reVISit study will go through multiple stages over its lifetime. It'll first start as a local study that is iteratively refined until the study is fully built, it will then be deployed and tested, it will be sent out to participants for data to be collected, and finally the study will be disseminated to reviewers.

Revisit Modes​

To assist study designers with each stage of this process, we expose 3 application state switches:

ReVISit modes

  1. Data Collection- This enables/disables data collection which is useful when making modifications to the study when you don't want to add data to the database. This also disables sequence assignments, which means viewing the study will not affect your latin square balance.
  2. Development Mode - This enables the study browser in the study interface. This is great for moving around your study during development, and great for reviewers that might want to inspect the stimuli you gave to participants.
  3. Share Data and Make Analytics Interface Public - This makes the study visible to un-authenticated users in the analytics platform. This is great for sharing your results with reviewers and the wider public. We suggest that when this mode is turned on, you also disable data collection so that your data is not tainted by people reviewing your study.

Local Development​

In local development, it's likely that you want to collect sample data, try multiple sequences, navigate through the study, and see the collected data. To this end, you will likely want to:

  • Enable data collection
  • Enable development mode
  • Make the analytics interface publicly accessible

Testing a Production Deployment​

Just as in local development, when testing your study on the production deployment, you should:

  • Enable data collection
  • Enable development mode
  • Make the analytics interface publicly accessible

Collecting Participant Data​

When you start collecting participant data, you will want to:

  • Clear out the testing data from your database using the snapshots interface
  • Enable data collection
  • Disable development mode
  • Make the analytics interface not publicly accessible

Disseminating to Reviewers​

When disseminating your study to reviewers and the wider public, you should:

  • Make a snapshot of your data using the snapshots interface. Snapshots create a copy of your data to protect against any issues, but allows the wider public to see your collected data.
  • Disable data collection
  • Enable development mode
  • Make the analytics interface publicly accessible

If you are submitting to a venue that requires anonymization, such as ACM SIGCHI, consider creating a second deployment. If your primary deployment is on GitHub, consider adding a secondary one on such as Netlify or Vercel. For more information about deploying to other websites, see deploying to a static website.