JupyterLab : We are currently experiencing unexpected issues following a recent system update, and as a result, the Lab @ JSC is temporarily unavailable. We apologize for the inconvenience this may cause. In the meantime, we kindly ask users to use the Lab @ Cineca as an alternative.


Last modified by maaike on 2022/07/06 10:10

From version 10.1
edited by maaike
on 2022/07/05 20:20
Change comment: There is no comment for this version
To version 11.1
edited by maaike
on 2022/07/05 20:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,7 +6,7 @@
6 6  
7 7  === Writing Knowledge Graph queries ===
8 8  
9 -A query for the Knowledge Graph is defined declaratively in JSON-LD and always executed against a specific data structure (e.g. a "Dataset version") allowing the graph to be traversed.
9 +A query for the Knowledge Graph is defined declaratively in JSON-LD and is always executed against a specific data structure (e.g. a "Dataset version"), allowing the graph to be traversed.
10 10  
11 11  In the snippet below, we can see that we first define the semantical context for the query with //"@context",// which belongs to the namespace "//https:~/~/schema.hbp.eu/graphQuery/".//
12 12  
... ... @@ -70,10 +70,10 @@
70 70  **Access detailed metadata**
71 71  
72 72  (% class="wikigeneratedid" id="H" %)
73 -The Knowledge Graph Search UI has visualised the basic metadata. In many cases, more metadata is stored in the KG than is readily accessible via the Search UI and we can use this to our advantage when refining our query.
73 +The Knowledge Graph Search UI has visualised the basic metadata. In many cases, more metadata is stored in the KG than is readily accessible via the Search UI. We can use this to our advantage when refining our query.
74 74  
75 75  (% class="wikigeneratedid" %)
76 -For example, we can filter datasets with data from male subjects by making this a required feature in the query.
76 +For example, we can filter datasets with data from male subjects by making this a required feature in the query (set the label of "biologicalSex" to "male).
77 77  
78 78  ==== [[image:QB4.png||alt="Step 4: Access detailed metadata" height="432" width="700"]] ====
79 79