Onto-ns expects entity in the "wrong" format

[sygout]

Some DLite entites are defined with an array of dimensions and an array of properties. onto-ns seems to expect that to be a dictionnary of dimensions or properties.

Test:

• not working: http://onto-ns.com/meta/1.0/OPTIMADEStructure
• working: http://onto-ns.com/meta/1.0/OPTIMADEStructureSpecies

As it is, the problem is solved by converting the array to dictionnaries. It would be better if it can handle the array case.

[CasperWA]

Could you please give a reference to the array data model? What do to the arrays look like?

[sygout]

The references are the two examples of entities stored in the Atlas MongoDB as mentioned in the issue. I removed the one I created that were not working.

[sygout]

You can also have a look here https://gitlab.sintef.no/team40/demonstrators/mylittledemo-datamodel/-/tree/main/tests/data) and see the difference between premod_simple_ version 0.1 and 0.2

[CasperWA]

Ah, I meant more an example of the array data models, not the dict data models, which already exists. I'll take a look in GitLab links - cheers 👍

[CasperWA]

Hmm. Starting to implement this I was thinking: The models currently used in the service are only meant for the "returned" entities, i.e., not to validate the created entities.
Why not instead ensure the old SOFT5-style data models are converted to SOFT7-style models upon upload or on-the-fly between finding them in the backend and serving them?