Skip to content
Marco B edited this page Feb 16, 2016 · 7 revisions

Welcome to the Distiller-CORE library wiki!

Getting and building Distiller

If you need a guide on how to download and build the Distiller, please check How to build Distiller. For experienced users, it should be enough to know that Distiller is a Java 8, Maven-based project, so you can use your favorite IDE to clone this repository and you should be able to build Distiller without any hassle.

Using Distiller

If you need a guide on how to use Distiller, please check the Tutorial page.

Contributions

Distiller is an open project and every contribution is welcome.

To contribute to the project please check the Development Guidelines, but first of all read this page to understand our goals.

#Our philosophy

Distiller as a framework has two goals: the first and more practical is to provide a friendly prototyping environment to the developer interested in building knowledge extraction and text mining applications, the second and more ambitious is to rethink knowledge extraction as a domain, standardizing terminology and providing an open source implementation of state of the art algorithms as well as a set of adapters to popular systems. ##Text processing done quickly Distiller provides a quick way to build applications that process natural language text and extract various kinds of knowledge, such as keywords, entities, sentiment, or anything else that could be relevant to the extents of your applications. Do not mistake our notion of "quick" because we refer strictly to development time: building an application with Distiller should be a matter of few hours at worst, but do not expect highly optimized code. Optimization is not a priority to us, since the main focus is and always will be ease of use. ##Text processing done right On the other hand Distiller aims at providing a unified view on the text processing domain. Such view is the result of several years of extensive review of scientific literature and research experience of our team. Everything accepted in the main branch of the project is backed by solid knowledge, good practices, and discussion among the core developers.