Improvements in DataModels and Asset Type
In recent versions of Onesait Platform we have been working on improving both data models and asset types, and in this version 7.0.0-Zelda of the Platform it was not going to be less.
Thus, if in version 6.3.0-Yoshi the menu option where the data models are located was updated from the Administration menu and moved to the Development Tools menu, now, with the reorganisation of the Control Panel menus, the data models and asset types are located in Core > Data Models.
Another improvement is the possibility for users with ‘analyst’ and ‘developer’ roles to add, edit and delete data models. To this end, a field has been added to determine whether the data model is public or private.
The possibility of versioning data models has been added, for which a version field has been added, where the version number of the model will be displayed. The possibility to share data models through applications has also been added.
For reasons of functional necessity, these improvements have also been implemented in version 6.2.1-Xenon.
Public and private models
Until now, the ‘administrator’ roles were the only users in charge of creating, editing and deleting data models. From this version, the possibility has been added for analytical users and developers to create, edit and delete the different data models.
To this end, a new public field has been introduced, in which it will be determined whether a data model can be edited or viewed by the rest of the users. The ‘administrator’ type user will be able to view, update and delete any data model, both public and private. Users with ‘analyst’ and ‘developer’ roles may only edit and view user-created and public data models. They may also delete models, but only their own models.
A data model can be created either publicly or privately. If a data model is created by a user of type ‘administrator’, this field will be public by default, and if a model is created by a user of role “analyst” and ‘developer’, it will be private by default. This field can also be edited when updating the model.
Version control
Previously, when updating a data model, it could only be edited. Now there is the possibility to version it, thanks to the addition of a specific field for this purpose. By default it will comment at version ‘1’, and each time the model is versioned, its version will increase by one unit.
Any data model can be versioned, but the latest existing version of the model will be used as a reference. For example, if you have a data model with 3 versions and you want to version version version ‘1’, when you increment the version it will be version 4, because you have taken as reference the last version of that model. Models can only be versioned by the user who created the model.
Header Image: DataEdo
✍🏻 Author(s)
