For example, the API allows you to enter (or copy/paste) a full name, including titulation, salutation, initials and more - and get these items parsed and placed into corresponding fields on a detailed contact form. It will even automatically detect what the gender of the contact is, and apply this in gender fields. We have similar data entry aids for address input, email input, phone numbers and contact duplicate checking.
Take a look at the video below, which demonstrate most of the features:
Now this is quite exciting functionality, but this is also a technical blog, so I'll talk a bit about the technology involved.
A few optional features may require some local add-on deployment. In particular, deduplication requires us to know the contact data to use as the source for detecting if a new contact is a duplicate. Here we have two options: On-premise installation of the deduplication engine or hooking up with our cloud-based deduplication engine, which can be configured to sync with your datastores.
All in all I am quite enthusiastic about the FTR solution and the technology behind the solution. I also think that our FTR API is an example of a lightweight approach to implementing Data Quality, which complements DataCleaner very well. Both tools are extremely useful for ensuring a high level of data quality, and both tools are very intuitive and flexible in the way you can deploy them.
By now most of you've probably heard that Java 7 is out and there's a lot of discussions about new features, the loop optimization bug and general adoption.
But one of the things in Java 7 which has escaped most people attention (I think) is the new javadoc style.
Check it out:
And see it live - we've just published an updated API documentation for MetaModel.
(Ensuring correct syntax)
(Checking a single unit of code)
|Validating data profiling?|
(Running all tests periodically)
|Data Quality monitoring?|
(Maintaining records of all code issues)
|Static code analysis|
(a la FindBugs)
|Explorative data profiling?|
(Changing code without breaking functionality)
|ETL with applied DQ rules?|