| ... |
... |
@@ -1,5 +1,5 @@ |
| 1 |
1 |
{{collapsible title="What does ~"openMINDS~" stand for?"}} |
| 2 |
|
-"openMINDS" stands for **o**pen **M**etadata **I**nitiative for **N**euroscience **D**ata **S**tructures. Within this initiative various metadata models are developed and integrated. These metadata models can be used as architectural building blocks in graph databases. |
|
2 |
+**openMINDS** stands for **o**pen **M**etadata **I**nitiative for **N**euroscience **D**ata **S**tructures. Within this initiative various metadata models are developed and integrated. These metadata models can be used as architectural building blocks in graph databases in order to register and describe heterogeneous neuroscience data structures. |
| 3 |
3 |
{{/collapsible}} |
| 4 |
4 |
|
| 5 |
5 |
{{collapsible title="What is a metadata schema in comparison to a metadata model?"}} |
| ... |
... |
@@ -9,3 +9,5 @@ |
| 9 |
9 |
{{collapsible title="Why are the openMINDS metadata models distributed over sevaral GitHub repositories?"}} |
| 10 |
10 |
Each openMINDS metadata model covers a certain detail level or aspect around the description of neuroscience data structures. For example, the openMINDS_core metadata model is comprised of schemas that can be used to describe the general origin, location and content of neuroscience research products, while the openMINDS_SANDS metadata model contains schemas describing the anatomical locations and relation of neuroscience data. In order to facilitate the maintenance of the existing and the development of new metadata models, it was decided to keep them in different GitHubs governed by respective expert groups. Nonetheless, all openMINDS metadata models are interconnected and accessible as git submodules in a central openMINDS GitHub repository. |
| 11 |
11 |
{{/collapsible}} |
|
12 |
+ |
|
13 |
+ |
