Changes for page Technical details

Last modified by lzehl on 2021/07/05 18:57
From version 86.2
edited by lzehl
on 2021/07/05 15:01
Change comment: There is no comment for this version
To version 85.1
edited by lzehl
on 2021/07/05 13:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -124,7 +124,6 @@
124 124   "PROPERTY_NAME": {
125 125   "type": "DATA_TYPE",
126 126   "_instruction": "METADATA_ENTRY_INSTRUCTION"
127 - }
128 128   },
129 129   "required": [
130 130   "PROPERTY_NAME"
... ... @@ -160,61 +160,11 @@
160 160  ==== Data type depending constraints ====
161 161  
162 162  (% style="text-align: justify;" %)
163 -Depending on the expected data **##"type"##** additional constraints can be made for the metadata entry of a respective property. Currently, the openMINDS schema template syntax supports the following data types: **##"string"##**, **##"number"##** (integer or float), ##**"integer"**##, **##"float"##**, **##"boolean"##**, **##"array"##** and **##"object"##**.
162 +Depending on the expected data **##"type"##** additional constraints can be made for the metadata entry of a respective property. Currently, the openMINDS schema template syntax supports the following data types: **##"string"##**, ##**"integer"**##, **##"float"##**, **##"boolean"##**, **##"array"##** and **##"object"##**.
164 164  
165 165  (% style="text-align: justify;" %)
166 -If the expected data **##"type"##** is a **##"string"##** the expected number of characters, the format or a regular expression pattern of the string can be further defined. Here abstract examples for all possible string constraints:
165 +If the expected data **##"type"##** is a **##"string"##** the expected number of characters, the format or a regular expression pattern of the string can be further defined.
167 167  
168 -{{code language="json"}}
169 -{
170 - "properties": {
171 - "stringProperty_noConstraints": {
172 - "type": "string",
173 - "_instruction": "Enter a free text."
174 - },
175 - "stringProperty_lengthConstraints": {
176 - "maxLength": 6,
177 - "minLength": 2,
178 - "type": "string",
179 - "_instruction": "Enter a free text (allowed numbers of characters: 2 - 6)."
180 - },
181 - "stringProperty_formatConstraints": {
182 - "type": "string",
183 - "_formats": [
184 - "email",
185 - "date",
186 - "time",
187 - "date-time",
188 - "iri"
189 - ]
190 - "_instruction": "Enter a string matching one of the given formats."
191 - },
192 - "stringProperty_patternConstraints": {
193 - "pattern": "«regular_expression»"
194 - "type": "string",
195 - "_instruction": "Enter a string matching the given regex pattern (ECMA 262 dialect)."
196 - }
197 - }
198 -}
199 -{{/code}}
200 -
201 -(% class="wikigeneratedid" %)
202 -If the expected data **##"type"##** is an **##"integer"##** or a **##"number"##** (float or integer) the expected range or multiples can be further defined. Here abstract examples for all possible  **##"integer"##** and **##"number"##** constraints:
203 -
204 -{{code language="json"}}
205 -{
206 - "properties": {
207 - "numberProperty_noConstraints": {
208 - "type": "number",
209 - "_instruction": "Enter a number (float or integer)."
210 - }
211 - }
212 -}
213 -{{/code}}
214 -
215 -(% class="wikigeneratedid" %)
216 -If ...
217 -
218 218  === The openMINDS integration pipeline ===
219 219  
220 220  (//**coming soon**//) If you'd like to learn more about the openMINDS integration pipeline, especially if you'd like to contribute to it, please get in touch with us (the openMINDS development team) via the issues on the openMINDS or openMINDS_generator GitHub or the support email: openminds@ebrains.eu
Public

openMINDS