Changes for page Application details

Last modified by lzehl on 2021/10/13 13:11

From version 47.1
edited by lzehl
on 2021/06/24 11:07
Change comment: There is no comment for this version
To version 49.1
edited by lzehl
on 2021/06/30 12:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -71,7 +71,7 @@
71 71  {{/code}}
72 72  
73 73  (% style="text-align: justify;" %)
74 -Note that we do not use all properties defined for the schema (cf. the [[Person HTML>>https://humanbrainproject.github.io/openMINDS/core/schemas/v3/actors/person.html||rel="noopener noreferrer" target="_blank"]]), but that we only used the required property **##"givenName"##** and two optional properties **##"familyName"##** and **##"ContactInformation"##**. Please also note, that a person is allowed to link to multiple contact information instances, hence it expects a list of dictionaries, instead of a single dictionary (which would be valid if only a single link is expected).
74 +Note that we do not use all properties defined for the schema (cf. the [[Person HTML>>https://humanbrainproject.github.io/openMINDS/core/schemas/v3/actors/person.html||rel="noopener noreferrer" target="_blank"]]), but that we only used the required property **##"givenName"##** and two optional properties **##"familyName"##** and **##"contactInformation"##**. This means, optional properties, if not known, do not have to be defined in the respective JSON-LD, but they could also be listed with a **##null##** value. Please note in addition, that values for properties which expect an array should always be provided as such (cf. property **##"contactInformation"##**), even if only one item is defined.
75 75  
76 76  (% style="text-align: justify;" %)
77 77  You learned now how a valid JSON-LD for an openMINDS metadata instance looks like and how linkages between openMINDS instances are defined. In the following sections you will learn about the different tools that support you to create your own openMINDS JSON-LD metadata collection.
... ... @@ -149,7 +149,7 @@
149 149  (1) Input masks for all openMINDS metadata schemas. New metadata instances can be easily created through an intuitive input mask that validates the user entries already against the respective openMINDS schema.
150 150  
151 151  (% style="text-align: justify;" %)
152 -(2) Drop down menus for existing metadata instances. In accordance with the openMINDS metadata models, registered metadata instances can be linked with each other. Establishing these linkages is facilitated by drop down menus for selecting existing and fitting instances in dedicated properties of each input mask.
152 +(2) Facilitation of correct linkages between metadata instances. In accordance with the openMINDS metadata models, registered metadata instances can be linked with each other. Establishing these linkages is facilitated by jumping via dedicated properties to new input masks of matching schema types.
153 153  
154 154  (% style="text-align: justify;" %)
155 -(3)
155 +(3) Drop down menus for existing metadata instances. Establishing linkages between instances in accordance with the openMINDS metadata models is further facilitated by providing drop down menus for the dedicated properties for selecting existing instances of matching schema types.
Public

openMINDS