Common Data Model
Mapping APIs with similar data models to a common data model is a critical process that allows for standardized access to data across diverse systems.
We start with analyzing and understanding the data models of each API, identifying the structure, fields, and data types they employ.
Our common data model (CDM) is designed to be generic enough to accommodate data from all the APIs it is meant to integrate, but also detailed enough to capture the necessary information without loss. It consists of standard fields that are common across the individual APIs’ data models.
Semantic Mapping
Each field in the individual API data models is linked to a corresponding field in the CDM. This process requires a deep understanding of the data each API handles to ensure that the mapping is accurate and meaningful. For instance, a field named ‘User’ in one API might correspond to ‘Client’ in another, and both would be mapped to a ‘Customer’ field in the CDM.
Standardized Data Access
Boss Insights translates data between the individual APIs and the CDM in real time using the mappings to convert incoming data from each API into the common data model, and vice versa. This allows applications to interact with the CDM instead of individual APIs, providing a standardized method of accessing data.
Continuous Enhancement
Boss Insights maintains and updates the mappings and the CDM as APIs are updated or when new APIs are introduced. This involves adjusting the mappings or extending the CDM to accommodate new fields or data structures. When new fields are added we sunset old fields so that changes are made in a backward-compatible way and you can build on a solid foundation.
Please visit our Common Data Model documentation for more information.