Osweb JATOS results have dates with one month difference

kolfers

Hi all,

One of our researchers noticed that there was a discrepancy in the dates recorded in their results file.

All of the date_* columns have values that are one month off (earlier) than the datetime (which is the correct date). E.g. for datetime: "Thu Sep 07 2023 22:16:28 GMT+0200 (Central European Summer Time)", the date_startdate column in the converted file would say 07-08-23. This occurred for all dates present (and for all months) in the file.

In the unconverted file, I found similar values under "startdate" (without the "date_" part). So I'm guessing it's not a conversion problem. But that leaves me wondering what went wrong. As this is data from many participants, I guess the problem can't really be on their end.

For context, the versioning was:

• OSWeb version of the task was: 1.4.11
• Jatos: 3.7.3
• Converted with version 1.4.13.1

Kind regards,

Kerwin

sebastiaan

Hi @kolfers ,

Thanks for reporting this. I'm moving this to the JATOS category, because it sounds like this all happening on the JATOS side of things (not in OSWeb). @kri does this sound familiar?

— Sebastiaan

elisa

Hi, Kristian will be able to reply better. To me though, this does sound like an OSWeb problem. @kolfers can you check the date on the server for those result files?

I don't know where OSWeb collects the date and time from, but if it's from JATOS, you should also see that month error appearing on the metadata.

Elisa

sebastiaan

@elisa Yes, I think you're right actually. It appears to be in the context data that OSWeb sets. (See issue.)

sebastiaan

This was due to JavaScript using zero-based month notation, such that January is month 0. This should be fixed in OSWeb 2.0.2, which will be released through the automatic updater.

kolfers

Hi Sebastiaan and Elisa,

Thank you for the responses, glad to know we weren't going crazy, and that it will be fixed in the new version!

Kind regards!

Kerwin