JATOS/JATOS v3.7.6

JATOS v3.7.6

on GitHub

If you update a JATOS server from version < 3.7.1

Warning 1: Do not update your JATOS while studies are running. Wait for them until they are finished and then update. Updating while studies are running will break those study runs and result data will probably be lost.

Warning 2: If you are using study links with preview (the ones with ?pre in the URL) - they won't trigger a preview anymore (although they will still work and start the study run). The preview setting moved to the Study Properties.

Info 1: If you are using Nginx with JATOS you might have to change the location directive for Websockets to "/(jatos/testWebSocket|publix/[a-z0-9-]+/(group/join|batch/open))".

Info 2: The update procedure might take longer than usual depending on the number of workers you currently have stored in your JATOS. The time that the update will take is difficult to estimate but to give an example in one instance 65.000 workers took around 90 minutes to update. You can follow the progress in JATOS' log in logs/application.log.

Try out the new version on cortex.jatos.org.

Changes in 3.7.6

• Bug fix - Result data not shown in GUI in some cases when using the default embedded H2 database (#272)

Changes in 3.7.5

Info: Depending on your database size the JATOS update procedure can take a couple minutes since some database rows have to be updated. You can check the progress in JATOS log logs/application.log.

• Download of results - fix some issues (e.g. not working in Firefox) by abandoning StreamSaver.js and use browser-fs-access instead
• Database performance - Optimize queries (a problem with large databases)
• GUI / study page - Fix display on wide screens (#261)
• GUI security - Add Content Security Policy (CSP) headers with nonce for all <scripts>
• Migrate from Google Sign-In to Google Identity (only if enabled - Google Identity is off by default)
• Migrate from Scala 2.11 to 2.13 and sbt 0.13 to 1.3
• Docker: use eclipse-temurin:11-jre-ubi9-minimal instead of openjdk:11-jre
• jatos.js - add jatos.startComponentByTitle (starts the component by specifying its title)

Changes in 3.7.4

• Introducing Superuser:
  • Next to Admin a user can now be Superuser: Superusers can access all studies as if they are a member of this study. This includes accessing/deleting result data and changing/deleting the study.
  • Since this new user role is pretty powerful it is turned off by default and can be turned on in the production.conf.
• Admins can now edit users' name and email
• Users got a new field 'email'
• Fix 'Allow preview' bug
• Fix General Single Worker problem
• Fix exporting result data for JATOS used with an URL base path
• GUI / Administration / User Manager - Fix sorting in column 'Studies'
• GUI / Administration / Study Admin - make study assets size, result data size, result file size calculation configurable in production.conf
• Check for duplicate Component UUIDs while importing a study
• Bump dependencies
• Multi-arch Docker images: provide arm64 and amd64 (#256)

Changes in 3.7.3

• Better LDAP support
  • Allow multiple base DNs
  • Optionally specify an LDAP admin user for user searching
• Remove webpack bundling for jatos.js

Changes in 3.7.2

• Fix "TypeError: cannot use 'in' operator ..." in Firefox with some OSWeb studies
• Add more logging during update for one-time generation of study links
• Add "Your result upload files path" to local home screen

Changes in 3.7.1

Introducing Study Links and Study Codes

• Easier to handle links for participants:
  hand out e.g. https://my.jatos.server/publix/q75bwQyqyi8
  instead of https://my.jatos.server/publix/1/start?batchId=1&personalSingleWorkerId=123
• Old links will be automatically converted to the new link style
• No more link tampering from workers (study code is a 11 digit random string and can't be guessed)
• There are two variants of Study Links:
  1. Open Directly - This link opens the study directly without redirecting to the Study Entry page.
  2. Confirm First - This link first opens the Study Entry page where the participant has to confirm the study start (useful if links are distributed via social media or emails).
• Worker & Batch Manager page is now the Study Links page
• QR codes can be used instead of study links
• Easier to use: copy-to-clipboard buttons for links etc.
• Extra Study Links pop-up for Personal type workers: lets you easily create and manage study Personal study links
• Study Code can be used in Study Entry page
• Study preview moved to Study Properties (the links with the ?pre don't work anymore)

Study Entry page

• See it in action:
  1. https://cortex.jatos.org/publix/run with study code RdzFey2Xd0T
  2. https://cortex.jatos.org/publix/run?code=RdzFey2Xd0T
• Two uses:
  1. Confirmation for worker (e.g. worker accidentally clicks on links without actually intending to run the study)
  2. Enter study code: Possibility to hand out study codes instead of study links
• Message is customizable in Study Properties

Misc

• New documentation build with Docusaurus
• jatos.js build with webpack -> minified code, less requests, faster loads
• Administration page: show total numbers of studies, study results, and workers
• Fixed #229
• Added #191

Previous releases: github.com/JATOS/JATOS/releases

Which variant do I need?

• If you have Java (version 8 or 11) already installed (all OS): jatos.zip
• No Java installed: Choose according to your OS between
  • jatos_win_java.zip
  • jatos_mac_java.zip (if you have problems install your own Java with brew)
  • jatos_linux_java.zip
• If you prefer Docker: hub.docker.com/r/jatos/jatos