Data Models in Elementrix represent the structure and organization of data within your organization. They define:
Purpose:
Data Model vs Data Product:
Data Model: Structure/Schema definition (the blueprint)
↓
Data Product: Actual data implementation (the building)
Step-by-Step Guide:
Navigate to Data Model Management
Define Model Basics:
Name: Customer Data Model
Description: Standard structure for customer information
Version: 1.0
Domain: Customer Domain
Add Fields:
Example Customer Model:
Field Name | Data Type | Required | Description
-------------------|----------------|----------|---------------------------
customer_id | UUID | Yes | Unique customer identifier
first_name | String(100) | Yes | Customer first name
last_name | String(100) | Yes | Customer last name
email | String(255) | Yes | Primary email address
phone | String(20) | No | Contact phone number
date_of_birth | Date | No | Customer birth date
created_at | Timestamp | Yes | Account creation timestamp
lifetime_value | Decimal(10,2) | No | Customer lifetime value
segment | Enum | Yes | Customer segment tier
Define Relationships (if applicable):
Customer Model
└── Has Many: Orders
└── Has One: Customer Profile
└── Belongs To: Customer Segment
Add Constraints:
- email: Must be unique
- phone: Format validation (E.164)
- lifetime_value: Must be >= 0
- segment: Values [Premium, Standard, Basic]
Set Metadata:
Owner: data-architecture-team@company.com
Stewards: [customer-team@company.com]
Status: DRAFT
Save and Publish:
Editing Existing Models:
View Model Details:
Version Control:
Adding Fields:
Modifying Fields:
Non-Breaking Changes (safe):
Breaking Changes (requires version bump):
Deprecating Fields:
Field: legacy_customer_id
Status: DEPRECATED
Deprecation Date: 2025-12-31
Replacement: customer_id (UUID)
Migration Guide: Use new UUID-based customer_id
Archiving Models: