EasyMorph v2 has been released and it's a major milestone for us:
Starter and Professional versions
From now on EasyMorph comes in two versions: EasyMorph Starter (free) and EasyMorph Professional (paid). The free version is intended for ad hoc data profiling, manipulation, and analysis. It has all the transformations, import options and parameters. Iterations and export capabilities are also available in the free mode but they are somewhat limited. In case you decide to run your projects in an automated mode, or integrate it with 3rd party tools (e.g. schedulers) using the command line mode then it's probably another reason to switch to the paid version which would cost you about $42 per user per month (billed annually). Users of EasyMorph Professional are also provided with technical support by email in business hours. You can read more detailed description of the versions on the pricing page.
Please note that versions 1.x switches to a limited mode in September 2015.
Dealing with data quality
EasyMorph has a number of tools to manage data quality issues:
Monitoring
You can monitor data quality by inserting derived tables at some points of your transformation logic. With the help of filters you can leave only wrong values in these derived tables, so then when the tables are empty it would indicate that no wrong values found. To monitor duplicates you can aggregate data (count) and leave only counts > 1 using filters.
You can also monitor text parsing errors by checking "Show parsing errors" option in Import from text file transformation.
Cleansing
A number of transformations can be useful for cleansing data. For instance, using Lookup and replace you can replace incorrect spellings with correct ones, e.g. replace ‘NY’, ‘N.Y.’, ‘NYC’ with ‘New York’. Another useful transformation is Table-wide replace that can help you clean your data from the same word in every column. For instance remove word 'NULL' that sometimes can be inserted by some databases when exporting into a text file.
Halting execution
Sometimes you might want to stop the transformation process when it's not possible to fix data quality issues in the source data. Starting from version 2 it's possible to stop project execution using Halt on condition transformation. This transformation calculates a condition (expression) for every row in the table and halts if the condition is true for any row. To provide a better insight into the problem the error messages can be customized.
