Propose a first catalog

[Nelly-Barret]

Following #27 , we have to propose a first version of the catalog and see how this fits with current catalogs. Then, hospitals could take this first version as an example and complete the catalogue with what they want to expose and how.

[Nelly-Barret]

Considerations for the catalog:

• show "metadata", e.g., dataset schema, number of NaN value, min max - this is not privacy-risky
• show aggregated data (only for some columns, any hospitals can decide to share or not), e.g., age, etc - this is privacy-risky
• do NOT share the daiganosis values (-> simply say that we are working on intellectual diability, etc).

The catalogue will be used to help each center to build queries (to be sent to the centers by the trains) by showing what is in each center.

[Nelly-Barret]

https://github.com/Nelly-Barret/BETTER-fairificator/issues/61

[Nelly-Barret]

The catalogue has to be buil on the MongoDB integrated databases:

• The "schema" page = SELECT * FROM Examination
• The "general" page = stats about the integrated files (not done yet)
• The "business" page = Analysis class
• The "aggregated" page = aggregates

[Nelly-Barret]

https://rp3.mockplus.com/editor/WLnOOktXQ/QpdwGDCHIS

[Nelly-Barret]

Page schema metadata

The schema page should be computed based on the consolidated database at the hospital. To get this table, we can query the table of Examination instances and also the Analysis class which will report numbers such as empty cells, N/A cells, etc

What about diseases, genomics, images? We can maybe do:

• a panel for "clinical data",
• one for the diseases (+their mappings, etc),
• one for a "kind of" genomic metadata (like the header in the VCF?),
• one for the images (resolution, frame, date of scan, ...?)

Page "structured querying"

Compose "structured" queries by selecting:

• a table
• possibly, an attribute
• possibly, a pair (operator, value) Possibility to ask for several columns and/or join several tables

What about the querying of several centers, e.g., centers in UC1?

Page "concept-based querying"

Compose "concept-based" queries by selecting:

• a concept
• possibly, an attribute
• possibly, a pair (operator, value) Possibility to ask for several columns and/or join several tables

This will take care of joining the tables Examination and ExaminationRecord to get only ExaminationRecords that record ages. This is simpler for users than the page "Structured querying", but it will be a bit "more complex" to implement.