Modeling basics
Modeling describes how information is structured in the system. It defines what kinds of things exist, how they are described, and how they relate to each other.
In Minyu, the model is not only a data description. It is the foundation for rules, views, scheduling, permissions, and integrations. Understanding the model is therefore essential to understanding system behavior.
What a model is
A model is a structured description of a domain.
It identifies the entities that exist in the system and the relationships between them. The model does not describe workflows or actions. It describes what exists and how things are connected.
Once defined, the model becomes the reference point for all evaluation in the system.
Tables, rows, attributes
A table represents a type of entity in the domain. Examples include people, resources, bookings, or documents.
A row represents one specific instance of that entity. Each row has a stable identity that does not change over time.
An attribute is a property of a row. Attributes store values such as text, numbers, dates, or references. Attributes describe an entity but do not define its identity.
Together, tables, rows, and attributes define the structure of information in the system.
Relationships and direction
Relationships describe how rows in different tables are connected.
A relationship has a direction. It defines how one row can reference or reach another. Direction matters because it affects how data is traversed, filtered, and evaluated.
Relationships enable navigation, classification, scheduling logic, and permission checks. They are a core part of the model, not an optional extension.
What makes a good model
A good model reflects how the domain actually works.
It separates distinct concepts into separate tables, uses relationships to express connections, and avoids encoding meaning implicitly in text or overloaded fields.
A clear model reduces the need for complex rules and makes system behavior easier to predict.
Common beginner mistakes
Common modeling mistakes include:
- Combining multiple concepts into a single table.
- Using descriptive text fields to represent relationships.
- Treating attributes as identifiers.
- Modeling workflows instead of structure.
These issues often lead to complex rules, confusing behavior, and fragile integrations. Correcting the model usually simplifies the rest of the system.