Sections in the Article
This article gives an overview of inRiver's Elastic Data Model and explains how it is used when implementing your inRiver PIM solution.
About inRiver's Elastic Data Model
All implementations of inRiver are based on an elastic data model. The data model is created based on the requirements of each individual customer.
inRiver's Elastic Data Model is the most fundamental concept of an inRiver installation. A new project always starts with an analysis of the customer's product information requirements.
A data model is basically an organization of data elements grouped into entities. Relationships are then defined between various entities, as illustrated below.
Building an Elastic Data Model
An elastic data model should be built to enable an efficient enrichment process for your product information.
inRiver's Elastic Data Model is set up and managed in the Model module in Control Center. There are also web-based and client-based tools to create and maintain enrichment data.
A data model is typically not created or maintained directly by the customer, but rather by the solution partner who is responsible for implementation. Our partners have the experience and expertise to create an effective data model.
Once the data model has been finalized, other implementation activities can be performed in the project. These include integrations, data imports, print configurations, input and output channels, etc.
Benefits of Using inRiver's Elastic Data Model
The flexibility of inRiver's Elastic Data Model to organize data in a customer-specific fashion greatly simplifies the enrichment process for PIM users. inRiver provides a flexible modeling framework, making it possible to create an individual model that supports specific solutions without unnecessary overhead, as illustrated below.
In comparison, a system with a fixed data model can provide a variety of features, but it cannot adapt when a customer needs a feature that their model cannot support.