Closed tomaroberts closed 2 years ago
My understanding of the current database schema: I'm not clear on what the 'Fact' table is for and what the 'signature' field in the 'ProcessTask' is for. I think if we want to group Acquisitions (single DICOM file that is uploaded) into Studies, then we can add another table to the schema linking many acquisitions to a study that are linked to a task being performed by a user.
@sophie22 both good questions!
The Fact table is to store the output of a particular process task applied to a particular acquisition.
The signature attribute of ProcessTask, i think was supposed to be the funciton signature e.g. SNR(file: Dicom) -> float - but i think this is not useful and happy for it to be pruned.
Also can you share what you used to produce the visualisations in your screenshot? :)
Thanks for the explanation. The schema visualisation was created using DBdiagram.io.
Great app shout-out, @sophie22!
I also like the idea of simplifying/normalising the tables to accommodate multiple DICOMs, duplicate file names, etc., e.g.:
Currently, the Acquisitions table only accepts single DICOM Series. If you upload, say, a folder of multiple DICOMs, they are added to the Acquisitions table as separate files. This is incompatible with some of the hazenlib tasks which operate on >1 DICOM Series.
We need to update hazen-web-app so the Acquisitions db can have more than one series per entry, and, alter the front end to reflect this.