Changes for page Technical details

Last modified by lzehl on 2021/07/05 18:57

From 85.1 to 84.1 From 89.1 to 88.1

From version 88.1

edited by lzehl
on 2021/07/05 18: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

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -124,7 +124,6 @@
      "PROPERTY_NAME": {
        "type": "DATA_TYPE",
        "_instruction": "METADATA_ENTRY_INSTRUCTION"
--    }
    },
    "required": [
      "PROPERTY_NAME"
@@ -160,98 +160,11 @@
  ==== Data type depending constraints ====
  (% style="text-align: justify;" %)
--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"##**, **##"object"##** or **##"array"##**. Except for **##"boolean"##**, all these data types can have additional constraints. The essential constraints will be summarized in the following (cf. [[JSON-Schema specifications 7.0>>https://json-schema.org/understanding-json-schema/index.html||rel="noopener noreferrer" target="_blank"]] for more).
++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"##**.
  (% style="text-align: justify;" %)
--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:
++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.
--{{code language="json"}}
--{
--  "properties": {
--    "stringProperty_noConstraints": {
--      "type": "string",
--      "_instruction": "Enter a free text."
--    },
--    "stringProperty_lengthConstraints": {
--      "maxLength": 6,
--      "minLength": 2,
--      "type": "string",
--      "_instruction": "Enter a free text (allowed numbers of characters: 2 - 6)."
--    },
--    "stringProperty_formatConstraints": {
--      "type": "string",
--      "_formats": [
--        "email",
--        "date",
--        "time",
--        "date-time",
--        "iri"
--      ]
--      "_instruction": "Enter a string matching one of the given formats."
--    },
--    "stringProperty_patternConstraints": {
--      "pattern": "«regular_expression_ECMA_262_dialect»"
--      "type": "string",
--      "_instruction": "Enter a string matching the given regex pattern."
--    }
--  }
--}
--{{/code}}
--
--(% class="wikigeneratedid" %)
--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 (not that both constraints can be defined for both data types):
--
--{{code language="json"}}
--{
--  "properties": {
--    "integerProperty_noConstraints": {
--      "type": "integer",
--      "_instruction": "Enter an integer."
--    },
--    "integerProperty_rangeConstraints": {
--      "maximum": 50,
--      "minimum": 10,
--      "type": "integer",
--      "_instruction": "Enter an integer equal or between 10 and 50."
--    },
--    "numberProperty_noConstraints": {
--      "type": "number",
--      "_instruction": "Enter a number (float or integer)."
--    },
--    "numberProperty_multipleOfConstraints": {
--      "multipleOf": 10.5,
--      "type": "number",
--      "_instruction": "Enter any number which is a multiple of 10.5."
--    }
--  }
--}
--{{/code}}
--
--(% class="wikigeneratedid" %)
--If the expected data **##"type"##** is an **##"object"##** the expected schema type needs to be defined, as well as if the object is linked or embedded. Note that linked objects can exist by themselves. In contrast embedded objects depend on the existence of their parent schema (if the parent schema is deleted, the embedded objects will be deleted as well). Here abstract examples for all possible  **##"object"##** constraints:
--
--{{code language="json"}}
--{
--  "properties": {
--    "objectProperty_linked": {
--      "_linkedTypes": [
--        "«SCHEMA_TYPE»"
--      ],
--      "_instruction": "Add the link to an instance conform with the given schema types."
--    },
--    "objectProperty_embedded": {
--      "_embeddedTypes": [
--        "«SCHEMA_TYPE»"
--      ],
--      "_instruction": "Enter an instance conform with the given schema types."
--    }
--  }
--}
--{{/code}}
--
--(% class="wikigeneratedid" %)
--If the expected data **##"type"##** is an **##"array"##** the expected data type of the items in the array, as well as the expected length of the array can be further defined. Valid data types for items are **##"string"##**, **##"number"##**, ##**"integer"**##, **##"float"##**, **##"boolean"##**, and/or **##"object"##**. In addition, items can also be defined as n-tuples with expected data types. Here abstract examples for all possible  **##"array"##** constraints:
--
  === The openMINDS integration pipeline ===
  (//**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