Summary

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

Details

Page properties

Content

...	...	@@ -4,7 +4,7 @@
4	4	The openMINDS metadata models all consist of modular connectable metadata schemas. Each schema can be referenced by it's type and defines properties (including their expected value) for a set of related metadata.
5	5
6	6	(% style="text-align: justify;" %)
7		-A short overview for each openMINDS metadata model can be found below, including links to full HTML descriptions for all schemas across all versions. Note that for schemas, openMINDS provides also a library of selected controlled instances. The available controlled instances are listed in the HTML view for the respective schema.
	7	+A short overview for each openMINDS metadata model can be found below, including links to full HTML descriptions for all schemas across all versions. Note that for some schemas, openMINDS provides also a library of controlled instances. The available controlled instances are listed in the HTML view for the respective schema.
8	8
9	9	(% style="text-align: justify;" %)
10	10	Note that all metadata models are licensed under the MIT license.
...	...	@@ -20,7 +20,7 @@
20	20	{{html}}<iframe id="coreFrame" src="https://humanbrainproject.github.io/openMINDS/v2.0.0/core.html" width="100%" style="border:0; height: 35em"/>{{/html}}
21	21
22	22	(% class="wikigeneratedid" style="text-align: justify;" %)
23		-In case of EBRAINS, metadata representations (instances) of a few selected schemas (**##ContentType##**, **##License, Protocol##**) are centrally defined and maintained in a library on a separate [[openMINDS instances GitHub>>https://github.com/HumanBrainProject/openMINDS_instances/||rel="noopener noreferrer" target="_blank"]] to guarantee more consistency across the database instances of the EBRAINS Knowledge Graph. Feel free to explore these instances and to use them also outside of the EBRAINS Knowledge Graph.
	23	+For the schemas **##ContentType##**, **##License##**, and **##Protocol##**, openMINDS provides a library of controlled instances that were defined and reviewed by corresponding experts of the openMINDS development team (cf. also below). In particular within EBRAINS, the usage of these controlled instances increase the level of data integration inside the EBRAINS Knowledge Graph. Feel free to explore these instances (in the HTML view or on the GitHub) and make use them, inside or outside of EBRAINS.
24	24
25	25	(% class="wikigeneratedid" style="text-align: justify;" %)
26	26	For further details or to review schemas of an older version of this metadata model, please check out the [[openMINDS core GitHub repository>>https://github.com/HumanBrainProject/openMINDS_core]].
...	...	@@ -46,11 +46,23 @@
46	46	(% class="small" style="color:#7f8c8d" %)Select a version and click on a schema to discover its full HTML description.
47	47	{{html}}<iframe src="https://humanbrainproject.github.io/openMINDS/v2.0.0/controlledTerms.html" width="100%" style="border:0; height: 25em"/>{{/html}}
48	48
49		-(% class="wikigeneratedid" style="text-align: justify;" %)
50		-Except for **##TermSuggestion##**, the openMINDS controlledTerms metadata schemas differ only in their schema type which defines the terminology to which correspondingly created metadata representations (instances) belong to. In order to guarantee more consistency across the database instances of the EBRAINS Knowledge Graph, instances for all controlled terms (except **##TermSuggestion##**) are centrally defined and maintained in a library on a separate [[openMINDS instances GitHub>>https://github.com/HumanBrainProject/openMINDS_instances/||rel="noopener noreferrer" target="_blank"]]. Feel free to explore these instances and to use them also outside of the EBRAINS Knowledge Graph.
	49	+(% style="text-align: justify;" %)
	50	+Except for **##TermSuggestion##**, the openMINDS controlledTerms metadata schemas differ only in their schema type which defines the terminology to which the correspondingly created metadata representations (instances) belong to.
51	51
52	52	(% style="text-align: justify;" %)
53		-We expect the list of controlled terms (schema as well as instances) to grow based on your feedback. For instances within the EBRAINS Knowledge Graph that are entries for the property ##"studyTarget"##, you can provide this feedback directly through the schema **##TermSuggestion##**. For all other instances (e.g., of type **##Technique##** or **##BehavioralTask##**) or if you work independent of the EBRAINS Knowledge Graph, please provide your feedback through the [[openMINDS instances GitHub Issue Tracker>>https://github.com/HumanBrainProject/openMINDS_instances/issues||rel="noopener noreferrer" target="_blank"]]. The openMINDS development team reviews all your feedback regularly, in order to integrate all community-driven suggestions into the openMINDS_controlledTerms and openMINDS_instances (where applicable). In addition, your term suggestions will be evaluated as possible extensions for the SciGraph ontologies, powered by the FAIR Data Informatics (FDI) Lab - SciCrunch Infrastrucutre and the INCF Knowledge Space team.
	53	+For all controlled terms schemas (except **##TermSuggestion##**), openMINDS provides a library of controlled instances that were defined and reviewed by corresponding experts of the openMINDS development team (cf. also below). In particular within EBRAINS, the usage of these controlled instances increase the level of data integration inside the EBRAINS Knowledge Graph. Feel free to explore these instances (in the HTML view or on the GitHub) and make use them, inside or outside of EBRAINS.
54	54
55		-(% class="wikigeneratedid" style="text-align: justify;" %)
	55	+(% style="text-align: justify;" %)
	56	+The **##TermSuggestion##** schema was introduced to facilitate community-driven requests for new controlled terms and respective instances for the properties **##"studyOption"##** and **##"studyTarget"##** (which needs are particularly difficult to predict). Correspondingly suggested metadata instances will be frequently evaluated and integrated as proper controlled instances on the GitHub repository be the openMINDS development team.
	57	+
	58	+(% style="text-align: justify;" %)
56	56	For further details or to review schemas of an older version of this metadata model, please check out the [[openMINDS controlledTerms GitHub repository>>https://github.com/HumanBrainProject/openMINDS_controlledTerms]].
	60	+
	61	+=== openMINDS instances ===
	62	+
	63	+(% style="text-align: justify;" %)
	64	+For selected schemas, openMINDS provides a library of controlled instances that were defined and reviewed by corresponding experts of the openMINDS development team (cf. above). These instances are stored on the GitHub repository of the metadata model the respective schema belongs to. In particular within EBRAINS, the usage of these controlled instances increase the level of data integration inside the EBRAINS Knowledge Graph. Feel free to explore these instances (in the HTML view or on the GitHub) and make use them, inside or outside of EBRAINS.
	65	+
	66	+The libraries of these controlled instances will grow based on your feedback. If you miss an instance or terminology, feel free to make a corresponding request via our support email (openminds@ebrains.eu) or raise an issue on the respective GitHub repository. Within EBRAINS, new controlled terms and respective instances for the properties **##"studyOption"##** and **##"studyTarget"##** (which needs are particularly difficult to predict) can also be made by filling out a **##TermSuggestion##** (cf. above).
	67	+
	68	+All your request are reviewed regularly by the openMINDS development team, in order to integrate all community-driven suggestions (where applicable). In addition, your suggestions will be evaluated as possible extensions for the SciGraph ontologies, powered by the FAIR Data Informatics (FDI) Lab - SciCrunch Infrastrucutre and the INCF Knowledge Space team.