The premier Open Source Data Quality solution.
Powered by Neopost and Human Inference
The main application modules are:
- api - The public API of DataCleaner. Mostly interfaces and annotations that you should use to build your own extensions.
- testware - Useful classes for unit testing of DataCleaner and extension code.
- engine
- core - The core engine piece which allows execution of jobs and components as per the API.
- xml-config - Contains utilities for reading and writing job files and configuration files of DataCleaner.
- env - Different/alternative environments that DataCleaner can run in, for instance Apache Spark or webapp-cluster
- components
- ... - many sub modules containing built-in as well as additional components/extensions to use with DataCleaner.
- standard-components - a container-project that dependends on all components that are normally bundled in DataCleaner community edition.
- desktop
- api - The public API for the DataCleaner desktop application.
- ui - The Swing-based user interface for desktop users
- monitor
- api - the API classes and interfaces of DataCleaner monitor
- services - web services and controllers of DataCleaner monitor
- widgets - reusable widgets and UI work, based on GWT
- ui - the actual web user interface, based primarily on GWT and JSF
- documentation - end-user reference documentation, published on https://datacleaner.org/docs
In the root of the project you can find 'Formatter-[IDE].xml' files which enable you to import the code formatting rules of the project into your IDE.
There's a public build of DataCleaner that can be found on Travis CI:
https://travis-ci.org/datacleaner/DataCleaner
Please visit the main DataCleaner website https://datacleaner.org for downloads, news, forums etc.
Reference Documentation for users is available at https://datacleaner.org/docs - GitHub wiki and issues are used for developers and technical aspects only.
Licensed under the Lesser General Public License, see http://www.gnu.org/licenses/lgpl.txt