3. Data Modeling (Logical + Physical)
Description
Section titled “Description”Defines how data entities are structured and related from business modeling to physical implementation in Airtable.
Logical Data Model
Section titled “Logical Data Model”Represents business concepts independently of tooling (e.g., Customer, Contract, Invoice, Campaign, Project).
Physical Data Model
Section titled “Physical Data Model”Implements entities in Airtable using:
- Tables
- Fields
- Field Types
- Relationships
- Lookups / Rollups
- Computed Fields
Best Practices
Section titled “Best Practices”- Use snake_case for table and field names.
- Keep relationship direction controlled.
- Minimize lookup chains.
- Avoid circular dependencies.
- Use explicit primary keys.
Recommended Deliverables
Section titled “Recommended Deliverables”- Logical Data Model Diagram
- Physical Airtable Schema
- DBML Documentation
- Relationship Diagram (ERD)
- Field Dictionary