Changes for page Application details

Last modified by lzehl on 2021/10/13 13:11

From version 7.1
edited by lzehl
on 2021/02/24 11:58
Change comment: There is no comment for this version
To version 1.1
edited by lzehl
on 2021/02/18 16:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,34 +1,0 @@
1 -(% class="box infomessage" %)
2 -(((
3 -(% style="text-align: justify;" %)
4 -The metadata representation (instance) of each openMINDS metadata schema has to be provided as JSON-LD. For a graph database and correspondingly designed metadata models, a full metadata description of a research product includes multiple, interlinked metadata instances representing various schemas.
5 -
6 -(% style="text-align: justify;" %)
7 -[[JSON-LD>>https://json-ld.org/]] is a powerful, lightweight Linked Data format, ideal for storing such collections of interlinked metadata instances of a graph database (e.g., the EBRAINS Knowledge Graph).
8 -
9 -(% style="text-align: justify;" %)
10 -Please find below, a general description of a typical JSON-LD as used in the EBRAINS Knowledge Graph and the different approaches in place for writing a metadata description for your research product in form of an openMINDS conform JSON-LD metadata collection.
11 -)))
12 -
13 -=== JSON-LD - the openMINDS serialization format ===
14 -
15 -(% style="text-align: justify;" %)
16 -As stated above, openMINDS supports JSON-LD as serialization format for the metadata representations (instances) of its schemas. In the following we will briefly explain the JSON-LD syntax essential for writing a correct openMINDS instance.
17 -
18 -(% style="text-align: justify;" %)
19 -Let us first start with the example of an openMINDS core schema that is not linked to any other openMINDS schema: the ##ContactInformation##. According to its schema template (cf. its HTML), the only required property for a contact information instance is ##"email"##. Nonetheless, every valid JSON-LD needs two more properties: ##@type## and ##@id##.
20 -
21 -=== The openMINDS Python API ===
22 -
23 -(% style="text-align: justify;" %)
24 -For users with at least some programming experience, one possible way to write openMINDS conform JSON-LDs is to use the openMINDS Python API.
25 -
26 -=== The openMINDS spreadsheet templates ===
27 -
28 -(% style="text-align: justify;" %)
29 -For users with no programming experience, it is possible to provide at least openMINDS conform metadata by using the openMINDS spreadsheet templates.
30 -
31 -=== The Knowledge Graph Editor ===
32 -
33 -(% style="text-align: justify;" %)
34 -For curators of the EBRAINS Share Data service, it is possible to register openMINDS conform metadata into the EBRAINS Knowledge Graph database by using the Knowledge Graph Editor.
Public

openMINDS