💻Core Data Model
What is a data model?
Understanding CoreModels' data modeling methodology begins with a solid grasp of what a data model is and how our product helps you build a Core Data Model. This page outlines our approach to creating a unified schema for your entire ecosystem.
What is a Data Model?
A Data Model is an abstract framework that organizes data entities within a system, outlining their properties and interconnections. The concept exists in many fields:
In SQL, it refers to the collection of tables, columns, views and their relations that define how the data is stored in a certain database.
In Programming, it's the equivalent of a design diagram of all the classes and their connections.
In a web page, it's the underlying structure of a website (header, footer, navigation, forms, and other visual components).
In CoreModels, all of these ideas can be represented through nodes (types, elements, taxonomies, etc..) and their interconnected relations.
These nodes exist within a defined space. You can think of the space as the technical term used in CoreModels to refer to a schema of a single system.
We recommend using a different space for each data model in your ecosystem.
The CoreModels Methodology
CoreModels helps you build a Core Data Model, which is a unified, inclusive structure that documents and links entities from various data models of different systems, standards, or teams. This approach:
Standardizes Workflows: By defining a single, shared model, you ensure consistency across different projects and teams.
Bridges Silos: It connects disparate data sources, breaking down the barriers between systems and making all your data visible in one place.
Ensures Governance: A central model simplifies data quality management and provides a single location for governance rules.
The Role of Spaces
A Space is the technical term used in CoreModels to refer to a single schema. In business terms, you can think of a Space as a container for a specific project's data, such as a "Product Catalog Schema" or a "User Profiles Schema."
A single project can be composed of multiple Spaces, each representing a different schema. These Spaces are interconnected, allowing you to link data between them.
Building a Core Data Model
In CoreModels, you build a Core Data Model by linking multiple Spaces together. This approach allows you to break down a complex system into smaller, manageable schemas while still maintaining a single, unified view of your entire data. The way you organize your Spaces depends on the complexity and scale of your project.
Example 1: One Space per System
For a business with multiple distinct systems, a single Space can be used to contain the schema for each system. For example, a company might have a separate Space for their ERP System, a Space for their CRM, and a Space for their main E-commerce project. This works well when each system's schema is of a manageable size.
Example 2: Multiple Spaces for a Single Project
For very large or complex projects, it is more effective to use multiple Spaces for a single project. The schema for each major module can be given its own Space. For example, a complete e-commerce project might contain a Product Space, a Customer Space, and an Orders Space. By creating relations between these individual schemas, you build a comprehensive Core Data Model for the entire business.
This flexibility allows you to organize your schemas at the level that best suits your team and the complexity of your project.
Your Next Step: Let's get started by Building your first Schema (Part 1)
If you already have your schema available in JSON-LD or JSON Schema, you can follow the guides for importing those schemas, JSON-LD
Last updated