You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/explanations/curator_data_model.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ Here is the Patient described above represented as a CSV data model:
22
22
| Gender ||
23
23
| Name ||
24
24
25
-
The end goal is to create a JSON schema that can be used in Curator. A JSON Schema consists of only one data type and their attributes. Converting the above data model to JSON Schema results in:
25
+
The end goal is to create a JSON Schema that can be used in Curator. A JSON Schema consists of only one data type and their attributes. Converting the above data model to JSON Schema results in:
26
26
27
27
```json
28
28
{
@@ -196,11 +196,11 @@ The format of this attribute. See [format](https://json-schema.org/understanding
@@ -317,7 +317,7 @@ If you have an existing data model using any of the following validation rules,
317
317
318
318
The `DependsOn` and `Valid Values` columns can be used together to flexibly define conditional logic for determining the relevant attributes for a data type.
319
319
320
-
In this example we have the `Patient` data type. In this case the`Patient` can be diagnosed as healthy or with cancer. For Patients with cancer we also want to collect info about their cancer type, and any cancers in their family history.
320
+
In this example we have the `Patient` data type. The`Patient` can be diagnosed as healthy or with cancer. For Patients with cancer we also want to collect info about their cancer type, and any cancers in their family history.
321
321
322
322
Data Model:
323
323
@@ -381,7 +381,7 @@ As a result of the above data model, in the JSON Schema:
0 commit comments