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 andschemas1 +Metadata models & schemas - Parent
-
... ... @@ -1,1 +1,1 @@ 1 -Collabs.openminds. Documentation.WebHome1 +Collabs.openminds.openMINDS core.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 - A short overview for each openMINDSmetadata model can befound below,includinglinkstofullHTML descriptionsfor all schemasacross all versions. Note thatforsomeschemas,openMINDSprovidesalsoalibraryof controlled instances.Theavailablecontrolledtancesarelistedin theHTMLview fortherespectiveschema.7 +Please find the HTML description for all schemas of each openMINDS metadata model in the corresponding sub-pages. A short overview for each openMINDS metadata model can be found below. 8 8 9 9 (% style="text-align: justify;" %) 10 10 Note that all metadata models are licensed under the MIT license. ... ... @@ -13,75 +13,151 @@ 13 13 === openMINDS core === 14 14 15 15 (% style="text-align: justify;" %) 16 -The openMINDS core metadata model contains schemas that youcan use to describe the general origin, resource location, and content ofyourresearch products in the field of neuroscience. Currently this metadata model comprisesthefollowingschemas(default:lateststableversion):16 +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 ( Feb 2021) this metadata model comprises 37 usable schemas, grouped into five classes: 17 17 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}} 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}} 21 21 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 - 28 28 === openMINDS SANDS === 29 29 30 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 youcan use to capture the anatomical location ofyourneuroscience data as well as to identify and highlight commonly used reference brain atlases and coordinate spaces. Currently this metadata model comprisesthefollowing schemas (default: lateststableversion):77 +The openMINDS SANDS (**S**patial **A**nchoring for **N**euroscience **D**ata **S**tructures) metadata model contains schemas that can be used to 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 comprises 12 metadata schemas: 32 32 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}} 79 +{{container layoutStyle="columns"}} 80 +((( 81 +(% class="small" %) 82 +AnatomicalEntity 83 +AnatomicalEntityRelation 84 +Annotation 85 +AtlasTerminology 86 +))) 87 +((( 88 +(% class="small" %) 89 +BrainAtlas 90 +BrainAtlasVersion 91 +CoordinatePoint 92 +CoordinateSpace 93 +))) 94 +((( 95 +(% class="small" %) 96 +Electrode 97 +ElectrodeArray 98 +ElectrodeContact 99 +Image 100 +))) 101 +{{/container}} 36 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]]. 103 +=== openMINDS controlledTerms - schemas === 39 39 40 -=== openMINDS controlledTerms === 41 - 42 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 thefollowing schemas(default:latest stableversion):106 +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 comprises 38 nearly identical schemas: 44 44 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}} 108 +{{container layoutStyle="columns"}} 109 +((( 110 +(% class="small" %) 111 +AgeCategory 112 +AnatomicalAxesOrientation 113 +BehavioralTask 114 +BiologicalSex 115 +CellType 116 +ContributionType 117 +CriteriaQualityType 118 +DatasetType 119 +Disease 120 +DiseaseModel 121 +EthicsAssessment 122 +FileBundleGrouping 123 +FileUsageRole 124 +))) 125 +((( 126 +(% class="small" %) 127 +Genotype 128 +Language 129 +Laterality 130 +MetaDataModelType 131 +Modality 132 +ModelAbstractionLevel 133 +ModelScope 134 +OperatingDevice 135 +OperatingSystem 136 +Organ 137 +Phenotype 138 +PreparationType 139 +ProductAccessibility 140 +))) 141 +((( 142 +(% class="small" %) 143 +ProgrammingLanguage 144 +QualitativeOverlap 145 +SoftwareApplicationCategory 146 +SoftwareFeature 147 +Species 148 +Strain 149 +Technique 150 +TermSuggestion 151 +Terminology 152 +TissueSampleType 153 +TypeOfUncertainty 154 +UnitOfMeasurement 155 +))) 156 +{{/container}} 48 48 49 49 (% style="text-align: justify;" %) 50 -Except for **##TermSuggestion##**, the openMINDS controlledTerms metadata schemas differ only in theirschematype which defines the terminology to which the correspondingly createdmetadata representations (instances) belong to.159 +Except for TermSuggestion, the openMINDS controlledTerms metadata schemas differ only in their type which defines the name of the terminology the correspondingly controlled terms are registered to (cf. openMINDS controlledTerms - terminologies). Compared to these schemas, the TermSuggestion has one additional property ("terminology") where users can state to which terminology the new suggested (not yet controlled) term belongs to. 51 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 - 61 -=== openMINDS computation === 62 - 63 -(% style="text-align: justify;" %) 64 -The openMINDS computation metadata model contains schemas that you can use to capture the provenance of simulations, data analysis and visualizations. Currently this metadata model comprises the following schemas (default: dev): 65 - 66 -(% style="text-align: right;" %) 67 -(% class="small" style="color:#7f8c8d" %)Select a version and click on a schema to discover its full HTML description. 68 -{{html}}<iframe src="https://humanbrainproject.github.io/openMINDS/v3/computation.html" width="100%" style="border:0; height: 20em"/>{{/html}} 69 - 70 -(% class="wikigeneratedid" style="text-align: justify;" %) 71 -For further details or to review schemas of an older version of this metadata model, please check out the [[openMINDS computation GitHub repository>>https://github.com/HumanBrainProject/openMINDS_computation]]. 72 - 73 -=== openMINDS ephys === 74 - 75 -(% style="text-align: justify;" %) 76 -(% style="color:#7f8c8d" %)(//**coming soon**//) 77 - 78 78 === openMINDS instances === 79 79 80 -(% style="text-align: justify;" %) 81 -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. 82 - 83 -(% style="text-align: justify;" %) 84 -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). 85 - 86 -(% style="text-align: justify;" %) 87 -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. 163 +xxx