Enhance HEDDA.IO with various Reference Data Services to clean up and enrich your data domains.
When you want to extend your existing data with additional knowledge and information, simple domains are often of no help. With Reference Data Services you have the possibility to validate your data against external data sources or to enrich it with additional data.
Using the global settings of HEDDA.IO, you can register the 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 comes with 4 reference data services by default:
- Google libphonenumber Validation
- Email Validation
- Credit Card Validation
- Azure Maps Geocoding
We are working on adding more Reference Data Services (RDS) which you can deploy to your existing HEDDA.IO installation.
Further RDS 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 RDS, 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, you will be required to link a Composite Domain with the RDS.
To do so, navigate to the “Manage RDS” button in the “Build & Manage” group menu and select the Knowledge Base and the Composite Domain the RDS should be applied to.
A step by step configuration guide of an RDS
On the Azure Portal page, find and click on the Resource Group you deployed HEDDA.IO to, then select the Reference Data Services (RDS) App Service you need to configure. In this example we are going to use the Credit Card Validator.
Once you’re on the Credit Card RDS App Service Overview page, copy the URL of the App Service, which you can find in the top-right corner.
Now, go back to the HEDDA.IO ribbon in Excel, and click on “Settings”.
Add a new RDS by clicking on the small “Add” button, then enter a name and the URL of the App Service in the corresponding boxes.
The RDS “Azure Maps Geocoding”, and possibly other RDS in the future, require the input of a corresponding API-Key.
The required API key is not provided via the HEDDA.IO App Service or nor the HEDDA.IO RDS. The API key is usually provided to you by the provider of the RDS or the resource used. For In our example, for the Azure Maps RDS, which you can create directly during deployment, the API Key (Primary Key) can be found in the Azure Maps Service, which is generated during the deployment.
Please note, that this might differ for future RDS, HEDDA.IO will support later on.
Next, click the “RDS” button in the HEDDA.IO ribbon in Excel…
And add a Composite Domain to the previously created RDS.
Now, all that is left is for you is 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.