How does MegaQC determine the date (x axis) for each report uploaded? about megaqc

[multimeric]

At the point where MegaQC ingests the reports, it chooses either the config_creation_date, or a manually provided date if one was passed in via the CLI or REST API. Then this date gets saved to the DB.

So I'm not sure why this particular issue happened to you. How did you restore the database? Also, can you run an SQL query to look at the data? Something like SELECT report_hash, created_at FROM report LIMIT 50; or apply some kind of date filter like WHERE created_at BETWEEN DATE '2020-02-16' AND DATE '2021-02-16' if you know the time period affected.

[chrispyatt]

Perhaps the long term fix is to force it and supply dates along with the upload then, but I don't understand why I'm seeing different behaviour vs previous deployment.

I guess it's possible that I'm only seeing a subset of the data (for one particular config version) but unclear why that would be, given I know there are multiple 'created_at' values present in the DB.

The DB was backed up using pg_dump and then restored using pg_restore. The megaqc container was then spun up with a config to point it to the restored database (although I do seem to be having connection issues on upload - not sure whether that's due to a container setting or something outside on the new server).

Output of suggested query:

           report_hash            |     created_at
----------------------------------+---------------------
 f4ce4010a9a0007c4a67c3af630bc315 | 2021-10-07 11:45:00
 2d7aaf0ea5ddae123b94719d97e050dd | 2022-04-19 11:10:00
 1deddf31aeaa8246015a234eb1bff550 | 2022-04-12 09:54:00
 285b74798276dc524dbe0f7155ecc21d | 2022-01-19 13:21:00
 3bc94fcedd995b01cd173227b9f5dfae | 2020-05-28 21:18:00
 6c63b8d44b8351a0a0df92cb04e6da8b | 2020-06-01 12:08:00
 5a6aae582000bd4147e870170e908ab5 | 2020-06-28 06:29:00
 8a379e7df88021935f00a3320e78735a | 2020-06-28 06:52:00
 0917e86fb1947590109b02af23067e0e | 2020-06-28 06:57:00

[multimeric]

Perhaps the long term fix is to force it and supply dates along with the upload then

Yes, I would recommend this if you have more precise metadata available to you

I don't understand why I'm seeing different behaviour vs previous deployment.

I don't either, but I think you're most likely right that not all data is being loaded correctly. If you investigate further please let me know what you find.