Notes about Ontopic's approach to Data Integration, Mapping, and Knowledge Graphs
Ontopic has a distinctive approach to data integration, which we would like to share through short and easily readable articles. We kept the number of specific terms to a minimum and created a glossary for the few terms we think are almost unavoidable.
A Quickstart Guide to Ontopic Studio
This guide is for people who want to create a Knowledge Graph containing facts and KPIs from a database. Learn in 15 minutes how to create a Virtual Knowledge Graph (VKG) without writing code from almost any database.
Map column values to classes in your Knowledge Graph without the usual pain
The traditional way of mapping column values to classes when building a Knowledge Graph is annoying. You have to write many SQL queries or break the clear separation between data from the source and the ontology. In this article, we show you how to map a class based on the value in a given column in a single step with Ontopic Studio.
Mapping many-to-many relationships to object properties
Connecting things is undoubtedly the characteristic feature of a Knowledge Graph, and this pattern helps you to build highly connected Knowledge Graphs from database tables.
Mapping database columns to data properties
Mapping table columns to data properties (attributes) in the Knowledge Graph is another fundamental pattern you will use frequently.
Mapping a database table to a class
The pattern presented in this article will likely be your first mapping pattern when building a Knowledge Graph from a relational data source.
Some facts to consider when choosing a Mapping Editor
There is more than one way to map data sources to Knowledge Graphs. We shortly describe the most common ones and advice how to choose which way to go.
Why should you consider mappings when building a Knowledge Graph?
Mapping data sources to the integrated data solution is essential in many data integration projects. We started a series on mapping data with this first article.