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. ... ... @@ -13,172 +13,58 @@ 13 13 === openMINDS core === 14 14 15 15 (% style="text-align: justify;" %) 16 -The openMINDS core metadata model contains schemas that can beusedto describe the general origin, resource location, and content of research products in the field of neuroscience. Currently( Feb 2021)this metadata model comprises37usableschemas,groupedintofive classes: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): 17 17 18 -{{container layoutStyle="columns"}} 19 -((( 20 -(% class="small" %) 21 -**ACTORS** 22 -Affiliation 23 -ContactInformation 24 -Contribution 25 -Organization 26 -Person 27 -(% class="small" %) 28 -**DATA** 29 -ContentType 30 -Copyright 31 -FileBundle 32 -FileInstance 33 -FileRepository 34 -Hash 35 -License 36 -))) 37 -((( 38 -(% class="small" %) 39 -**MISCELLANEOUS** 40 -DigitalIdentifier 41 -DigitalIdentifierSchema 42 -Funding 43 -QuantitativeValue 44 -QuantitativeValueRange 45 -(% class="small" %) 46 -**PRODUCTS** 47 -Dataset 48 -DatasetVersion 49 -MetaDataModel 50 -MetaDataModelVersion 51 -Model 52 -ModelVersion 53 -Project 54 -Software 55 -SoftwareVersion 56 -))) 57 -((( 58 -(% class="small" %) 59 -**RESEARCH** 60 -ParameterSetting 61 -Protocol 62 -ProtocolExecution 63 -Subject 64 -SubjectGroup 65 -SubjectGroupState 66 -SubjectState 67 -TissueSample 68 -TissueSampleCollection 69 -TissueSampleCollectionState 70 -TissueSampleState 71 -))) 72 -{{/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}} 73 73 74 74 (% class="wikigeneratedid" style="text-align: justify;" %) 75 - In caseof EBRAINS, metadatarepresentations(instances) of the schemas ContentType, License, andDigitalIdentifierSchema arecentrallydefined andmaintainedon a separateGitHubtoguaranteemoreconsistencyacrossthe databaseinstancesofthe Knowledge Graph(cf.sectionopenMINDSinstances).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. 76 76 77 77 (% class="wikigeneratedid" style="text-align: justify;" %) 78 -For details ,contributingorreviewingexamplesplease checkoutas wellthe correspondingGitHub repository: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]]. 79 79 80 -(% class="wikigeneratedid" %) 81 -[[https:~~/~~/github.com/HumanBrainProject/openMINDS_core>>https://github.com/HumanBrainProject/openMINDS_core||rel=" noopener noreferrer" target="_blank"]] 82 - 83 83 === openMINDS SANDS === 84 84 85 85 (% style="text-align: justify;" %) 86 -The openMINDS SANDS (**S**patial **A**nchoring for **N**euroscience **D**ata **S**tructures) metadata model contains schemas that can beusedto capture the anatomical location of neuroscience data as well as to identify and highlight commonly used reference brain atlases and coordinate spaces. Currently(Feb 2021)this metadata model comprises12metadata schemas: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): 87 87 88 -{{container layoutStyle="columns"}} 89 -((( 90 -(% class="small" %) 91 -AnatomicalEntity 92 -AnatomicalEntityRelation 93 -Annotation 94 -AtlasTerminology 95 -))) 96 -((( 97 -(% class="small" %) 98 -BrainAtlas 99 -BrainAtlasVersion 100 -CoordinatePoint 101 -CoordinateSpace 102 -))) 103 -((( 104 -(% class="small" %) 105 -Electrode 106 -ElectrodeArray 107 -ElectrodeContact 108 -Image 109 -))) 110 -{{/container}} 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}} 111 111 112 112 (% class="wikigeneratedid" style="text-align: justify;" %) 113 -For details ,contributingorreviewingexamplesplease checkoutas wellthecorrespondingGitHub repository: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]]. 114 114 115 -(% class="wikigeneratedid" %) 116 -[[https:~~/~~/github.com/HumanBrainProject/openMINDS_SANDS>>https://github.com/HumanBrainProject/openMINDS_SANDS]] 40 +=== openMINDS controlledTerms === 117 117 118 -=== openMINDS controlledTerms - schemas === 119 - 120 120 (% style="text-align: justify;" %) 121 -The openMINDS controlledTerms metadata model contains schemas that ensure consistent registration of well-defined terms, including linkages to existing ontological terms where applicable. Currently (Feb 2021)this metadata model comprises38nearlyidenticalschemas: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): 122 122 123 -{{container layoutStyle="columns"}} 124 -((( 125 -(% class="small" %) 126 -AgeCategory 127 -AnatomicalAxesOrientation 128 -BehavioralTask 129 -BiologicalSex 130 -CellType 131 -ContributionType 132 -CriteriaQualityType 133 -DatasetType 134 -Disease 135 -DiseaseModel 136 -EthicsAssessment 137 -FileBundleGrouping 138 -FileUsageRole 139 -))) 140 -((( 141 -(% class="small" %) 142 -Genotype 143 -Language 144 -Laterality 145 -MetaDataModelType 146 -Modality 147 -ModelAbstractionLevel 148 -ModelScope 149 -OperatingDevice 150 -OperatingSystem 151 -Organ 152 -Phenotype 153 -PreparationType 154 -ProductAccessibility 155 -))) 156 -((( 157 -(% class="small" %) 158 -ProgrammingLanguage 159 -QualitativeOverlap 160 -SoftwareApplicationCategory 161 -SoftwareFeature 162 -Species 163 -Strain 164 -Technique 165 -TermSuggestion 166 -Terminology 167 -TissueSampleType 168 -TypeOfUncertainty 169 -UnitOfMeasurement 170 -))) 171 -{{/container}} 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}} 172 172 173 173 (% style="text-align: justify;" %) 174 -Except for TermSuggestion, the openMINDS controlledTerms metadata schemas differ only in their type which defines the name oftheterminology the correspondingly controlled termsare registeredto (cf. openMINDS controlledTerms - terminologies). Comparedo these schemas,the TermSuggestion has one additionalproperty ("terminology") where users canstate to which terminology thenewsuggested(notyet controlled)termbelongsto.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. 175 175 176 -(% class="wikigeneratedid" style="text-align: justify;" %)177 -For details,contributingor reviewing examples please checkout aswell thecorrespondingGitHubrepository: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. 178 178 179 -(% class="wikigeneratedid" %)180 - [[https:~~/~~/github.com/HumanBrainProject/openMINDS_controlledTerms>>https://github.com/HumanBrainProject/openMINDS_controlledTerms]]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. 181 181 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 + 182 182 === openMINDS instances === 183 183 184 -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 +(% style="text-align: justify;" %) 67 +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>>mailto: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). 68 + 69 +(% style="text-align: justify;" %) 70 +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.