Graph Data Transformers
Use any data to build your graph database
Use any source for your graph database
Within your toolkit you can select as many or as few Graph.Build Transformers as you need, depending on the package you select.
Each Transformer specialises in a type of data source ranging from SQL to flat files like CSV or XML. These can, of course, be easily changed through time whilst maintaining the graph model you have created making this a single toolkit, independent of input, for building and maintaining your graph databases.
In addition to this, the Graph.Build CDC capability means that you only need to update your data in one place.
Simple Deployment
Cloud or In-House
- Individual containers for each Transformer
- Cloud deployment supported through AWS
- On-Premise deployment supported through Docker
- Deployment support available
Flexible Configuration
For complex transformations
- Visual Configuration Using Graph.Build Studio
- Option to use RML and R2RML mapping files
- Configure multiple mappings from one source
- Create bespoke functions
Time series data supported as standard
Every time a Transformer ingests some data, it adds provenance information. This means that you have a full record of data over time, allowing you to see what the state of the data was at any moment in time.
If you have experience with Knowledge Graphs, you may already have worked with the PROV-O model. This is the model we use to record Provenance information.
Choosing your Transformers
You can change and update the transformers through time as your requirements change. For proof of concept you might decide to use just a single tranfromer - regardless, selecting the right one is easy. The descriptions below show the file compatibility types for each one. Just select the data transformer that suits your graph model.
Input File Compatibility
Document Transformer
Tags documents to data using AI
Structured File Transformer
Easily Ingest Structured Files
SQL Transformer
JDBC Connection
RESTful Transformer
Fetch from any RESTful endpoint
Why Graph.Build Transformers?
"Having experienced the challenges of knowledge graph projects for many years, one key recurring one was getting data into the database. We wanted to allow data scientists to take sources quickly from multiple source types through configuration rather than software development."