Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -44,7 +44,7 @@
44	44	where **##XXX##** and **##YYY##** should be replaced with the openMINDS sub-module (e.g., **##core##**) and corresponding schema-name (e.g., **##ContactInformation##**), respectively.
45	45
46	46	(% style="text-align: justify;" %)
47		-In return, the JSON-LD property **##"@id"##** defines the particular metadata instance (node). For this reason, the **##"@id"##** also expects an entry (value) of type string with the format of an IRI. In particular when you plan to submit your metadata collection later to the EBRAINS Knowledge Graph, we recommend you use the following naming convention on your local machine for this identifier:
	47	+In return, the JSON-LD property **##"@id"##** defines the particular metadata instance (i.e., graph database node). For this reason, the **##"@id"##** also expects an entry (value) of type string with the format of an IRI. In particular when you plan to submit your metadata collection later to the EBRAINS Knowledge Graph, we recommend you use the following naming convention on your local machine for this identifier:
48	48
49	49	(% style="text-align: center;" %)
50	50	**##"@id": "http:~/~/localhost/YYY/ZZZ"##**
...	...	@@ -121,7 +121,7 @@
121	121	{{/code}}
122	122
123	123	(% class="wikigeneratedid" %)
124		-To learn in general about the available openMINDS metadata models and schemas including their required or optional metadata properties, please check out the HTML representations of the schemas (cf. [[Metadata models & schemas>>doc:Collabs.openminds.Documentation.Metadata models & schemas.WebHome]]) or the code on the corresponding GitHub.
	124	+To learn in general about the available openMINDS metadata models and schemas including their required or optional metadata properties, please check out the HTML representations of the schemas (cf. [[Metadata models & schemas>>doc:Collabs.openminds.Documentation.Metadata models and schemas.WebHome]]) or the code on the corresponding GitHub.
125	125
126	126	Interactively you can also get an overview of the requirement of a schema and all its properties by using the **##help_##** function of the openMINDS.compiler. Here an example:
127	127
...	...	@@ -129,8 +129,6 @@
129	129	mycollection.help_core_person()
130	130	{{/code}}
131	131
132		-
133		-
134	134	=== The openMINDS spreadsheet templates ===
135	135
136	136	(% style="text-align: justify;" %)
...	...	@@ -139,4 +139,19 @@
139	139	=== The EBRAINS Knowledge Graph Editor ===
140	140
141	141	(% style="text-align: justify;" %)
142		-For curators of the EBRAINS Data & Knowledge service, it is possible to register openMINDS conform metadata into the EBRAINS Knowledge Graph database by using the EBRAINS Knowledge Graph Editor.
	140	+For curators of the EBRAINS Data & Knowledge service and users with an EBRAINS account, it is possible to register openMINDS conform metadata into the EBRAINS Knowledge Graph database by using the EBRAINS Knowledge Graph Editor. This editor not only allows the manual registration of openMINDS conform metadata, but also has many project management related features establishing a controlled and secured environment for curating metadata of submitted research products that should be published via the EBRAINS Knowledge Graph database (including the assignment of an EBRAINS DOI if requested).
	141	+
	142	+(% style="text-align: justify;" %)
	143	+To guarantee the latter, the EBRAINS Data & Knowledge service has its own EBRAINS Knowledge Graph Editor environment which reserves the rights of publicly releasing metadata and assigned EBRAINS DOIs via the EBRAINS Knowledge Graph for the members of the curation team. Nonetheless, users with an EBRAINS account can receive access to a separate EBRAINS Knowledge Graph Editor environment through a private Collab in the EBRAINS Collaboratory. All members of such a private Collab can then manually register openMINDS conform metadata through the EBRAINS Knowledge Graph Editor to a restricted space of the Knowledge Graph database that is not accessible to any user outside of the respective Collab. In order to publicly release these privately registered metadata, an official curation request has to be made through the EBRAINS Data & Knowledge service.
	144	+
	145	+(% style="text-align: justify;" %)
	146	+Independent of the different user environments, the EBRAINS Knowledge Graph Editor has the following features to facilitate the manual registration of openMINDS conform metadata:
	147	+
	148	+(% style="text-align: justify;" %)
	149	+(1) Input masks for all openMINDS metadata schemas. New metadata instances can be easily created through an intuitive input mask that validates the user entries already against the respective openMINDS schema.
	150	+
	151	+(% style="text-align: justify;" %)
	152	+(2) Drop down menus for existing metadata instances. In accordance with the openMINDS metadata models, registered metadata instances can be linked with each other. Establishing these linkages is facilitated by drop down menus for selecting existing and fitting instances in dedicated properties of each input mask.
	153	+
	154	+(% style="text-align: justify;" %)
	155	+(3)