Enhance HEDDA.IO with various Reference Data Services to clean up and enrich your data domains.

Especially if you want to extend your existing data with additional knowledge and information, simple domains often cannot help. With Reference Data Services you have the possibility to validate data against external data sources or to enrich it with other data.

Using the global settings of HEDDA.IO, you can register Reference Data Service company-wide. Once you have registered RDS, you can later assign them to a composite domain within your knowledge base.

HEDDA.IO is delivered by default with 4 reference data services that you can select when deploying using the Azure Market Place:
  • Google libphonenumber Validation
  • Email Validation
  • Credit Card Validation
  • Azure Maps Geocoding
We also add more and more Reference Data Services which you can deploy to your existing HEDDA.IO installation.

 

Further Reference Data Services as well as some programming examples will be provided as open source projects on GitHub, so that you can easily extend HEDDA.IO with your own solutions.

To configure and add a Reference Data Service, navigate to “Settings” in the HEDDA.IO ribbon, add a new RDS and provide the required URL and API-Key in the opening window. Additionally, it is necessary to link a Composite Domain with the RDS.

To do so, navigate to the RDS button in the “Build & Manage” group and provide the Knowledge Base and the Composite Domain the RDS should belong to.

Step by Step Configuration of an RDS

In the Azure Portal, go into the Resource Group you deployed HEDDA.IO to and select the RDS App Service you intend to configurate. In this example we will use the Credit Card Validator.

Copy the URL of the App Service…

and go back to the HEDDA.IO ribbon in Excel to “Settings”.

Add a new RDS, enter a name and the URL of the App Service.

The RDS “Azure Maps Geocoding” – and possibly also further RDS in the future – require the input of a corresponding API-Key.

This API key is not provided via the HEDDA.IO App Service or the HEDDA.IO RDS. The API key is usually provided to you by the provider of the RDS or the resource used. For our example Azure Maps RDS which you can create directly during deployment, you can find the API Key (Primary Key) for example in the Azure Maps Service generated at the same time.

Next switch to “RDS” in the HEDDA.IO ribbon…

and add a Composite Domain to the previously created RDS.

Now you have to configure the RDS.

By doing so you will link the Domains of the Composite Domain to an input column of the RDS.

The configuration of the RDS is now complete.