Data model overview
The data model describes how information is organized in Minyu.
It defines what kinds of things exist in the system, what information is stored about them, and how they are connected.
For example, you might store people, rooms, bookings, or equipment.
This structure is important because Minyu uses it for much more than storing data.
The same structure also controls forms, rules, search, permissions, and integrations.
What the structure defines
The data structure describes:
- what types of records can exist
- what information can be stored about them
- how different records are connected
It focuses on structure and consistency, not on business processes or workflows.
Tables
Tables represent the different types of things you manage.
Examples might include:
- people
- rooms
- bookings
- equipment
Each row in a table represents one real-world item.
For example, one row in the Person table represents one person.
Tables act as the container where information and connections are defined.
Columns
Columns describe the information stored about each item.
For example, a Person table might contain columns such as:
- name
- phone number
- email address
Columns define what type of information can be stored and whether it is required.
Relations
Relations connect rows in different tables.
For example:
- a booking may be linked to a person
- a room may be linked to a building
Relations allow information to be reused instead of duplicated.
They also allow the system to navigate between related data.
System-managed fields
In addition to the columns you define, Minyu automatically adds some internal fields to every table.
These fields handle things like:
- unique row identification
- tracking when data was created or changed
- internal references needed for relations
These fields are managed by the system to ensure reliable behavior.
How the structure is used
Once the structure is defined, Minyu uses it throughout the system.
For example, it automatically powers:
- forms for entering data
- lists and search
- rules and validations
- scheduling and time-based logic
- APIs and integrations
Because everything is based on the same structure, changes to the model automatically affect the rest of the system.
Related resources
Related concepts