Databases allow you to define a structure bound by a set of attributes. In general, all assets do not necessarily have the same attributes. For example, a boiler does not have the same characteristics as an engine or even as an anomaly;
Once created, databases allow :
- To ensure consistency in the structure of your data.
- To facilitate the search via filters.
- To restrict access to your users via consultation rights.
It is possible to manage sub-databases. The sub-database will inherit attributes from the parent database.
Be careful not to confuse this with the parent / child equipment relationship which allows you to prioritize your data
- Go to the Database tab on the platform.
- Create a New database, "Construction sites"
- In the Attributes tab, create attributes of different types :
- For example :
- Site number (Number)
- Site address (Text)
- MOE (Text)
- Companies present (multiple choice)
- For example :
On the Data tab of your new database, create a new asset.
Name it"test site"
- You can now see that you are asked to fill in the different attributes for your "test site". These attributes will be requested for all the asset present in the Construction sites database
We are now going to create a sub-database.
- Go to the Database tab.
- Create a New database, "Engines"
- Create the attributes:
- Engine brand (Text)
- Engine model (Text)
- Oil level (Number)
- Condition of cables (choice A / B = Good / Bad)
- General condition (Multiple choice: Good / Average / Bad)
- Create a new resource within this database and name it Engine 1
- Create a New database, "Asynchronous Motors";
- Choose as "Parent database" the "Engines" database.
In the "Structure" tab of our new database, we can see that the attributes of the "Engines" database are already present and that we can complete them by adding other attributes.
You can now practice how to connect your forms to databases.