Changes for page Metadata models and schemas
Last modified by lzehl on 2021/07/02 17:06
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Metadata models &schemas1 +Metadata models and schemas - Parent
-
... ... @@ -1,1 +1,1 @@ 1 -Collabs.openminds.o penMINDS core.WebHome1 +Collabs.openminds.Documentation.WebHome - 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 - Please find theHTML description for all schemas ofeach openMINDSmetadatamodel inrespondingsub-pages.Ashortoverview foreachopenMINDSmetadata modelcan befound below.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. ... ... @@ -12,76 +12,57 @@ 12 12 13 13 === openMINDS core === 14 14 15 -The openMINDS core metadata model contains schemas that can be used to describe the general origin, resource location, and content of research products in the field of neuroscience. Currently this metadata model comprises 37 usable schemas, grouped into five classes: 15 +(% style="text-align: justify;" %) 16 +The openMINDS core metadata model contains schemas that you can use to describe the general origin, resource location, and content of your research products in the field of neuroscience. Currently this metadata model comprises the following schemas (default: latest stable version): 16 16 17 -{{container layoutStyle="columns"}} 18 -((( 19 -(% class="small" %) 20 -ACTORS 21 -Affiliation 22 -ContactInformation 23 -Contribution 24 -Organization 25 -Person 26 -))) 27 -((( 28 -(% class="small" %) 29 -DATA 30 -ContentType 31 -Copyright 32 -FileBundle 33 -FileInstance 34 -FileRepository 35 -Hash 36 -License 37 -))) 38 -((( 39 -(% class="small" %) 40 -MISCELLANEOUS 41 -DigitalIdentifier 42 -DigitalIdentifierSchema 43 -Funding 44 -QuantitativeValue 45 -QuantitativeValueRange 46 -))) 47 -((( 48 -(% class="small" %) 49 -PRODUCTS 50 -Dataset 51 -DatasetVersion 52 -MetaDataModel 53 -MetaDataModelVersion 54 -Model 55 -ModelVersion 56 -Project 57 -Software 58 -SoftwareVersion 59 -))) 60 -((( 61 -(% class="small" %) 62 -RESEARCH 63 -ParameterSetting 64 -Protocol 65 -ProtocolExecution 66 -Subject 67 -SubjectGroup 68 -SubjectGroupState 69 -SubjectState 70 -TissueSample 71 -TissueSampleCollection 72 -TissueSampleCollectionState 73 -TissueSampleState 74 -))) 75 -{{/container}} 18 +(% style="text-align: right;" %) 19 +(% class="small" style="color:#7f8c8d" %)Select a version and click on a schema to discover its full HTML description. 20 +{{html}}<iframe id="coreFrame" src="https://humanbrainproject.github.io/openMINDS/v2.0.0/core.html" width="100%" style="border:0; height: 35em"/>{{/html}} 76 76 22 +(% class="wikigeneratedid" style="text-align: justify;" %) 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 + 25 +(% class="wikigeneratedid" style="text-align: justify;" %) 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]]. 27 + 77 77 === openMINDS SANDS === 78 78 79 -xxx 30 +(% style="text-align: justify;" %) 31 +The openMINDS SANDS (**S**patial **A**nchoring for **N**euroscience **D**ata **S**tructures) metadata model contains schemas that you can use to capture the anatomical location of your neuroscience data as well as to identify and highlight commonly used reference brain atlases and coordinate spaces. Currently this metadata model comprises the following schemas (default: latest stable version): 80 80 33 +(% style="text-align: right;" %) 34 +(% class="small" style="color:#7f8c8d" %)Select a version and click on a schema to discover its full HTML description. 35 +{{html}}<iframe src="https://humanbrainproject.github.io/openMINDS/v2.0.0/SANDS.html" width="100%" style="border:0; height: 20em"/>{{/html}} 36 + 37 +(% class="wikigeneratedid" style="text-align: justify;" %) 38 +For further details or to review schemas of an older version of this metadata model, please check out the [[openMINDS SANDS GitHub repository>>https://github.com/HumanBrainProject/openMINDS_SANDS]]. 39 + 81 81 === openMINDS controlledTerms === 82 82 83 -xxx 42 +(% style="text-align: justify;" %) 43 +The openMINDS controlledTerms metadata model contains schemas that ensure consistent registration of well-defined terms, including linkages to existing ontological terms where applicable. Currently this metadata model comprises the following schemas (default: latest stable version): 84 84 45 +(% style="text-align: right;" %) 46 +(% class="small" style="color:#7f8c8d" %)Select a version and click on a schema to discover its full HTML description. 47 +{{html}}<iframe src="https://humanbrainproject.github.io/openMINDS/v2.0.0/controlledTerms.html" width="100%" style="border:0; height: 25em"/>{{/html}} 48 + 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 + 52 +(% style="text-align: justify;" %) 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 + 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;" %) 59 +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 + 85 85 === openMINDS instances === 86 86 87 -xxx 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.