ONE Desktop
ONE Desktop is a developer tool for the Ataccama ONE platform. Thanks to this integrated development environment (IDE) built on top of Eclipse, you can create advanced DQ and master data management solutions based on Ataccama products.
Installation prerequisites
ONE Desktop can be locally installed on systems running Linux, MacOS, or Windows.
The main requirement for installation is that Java 11 JRE or newer is present.
If used together with ONE, ONE Desktop requires access to Metadata Management Module (MMM), Data Processing Module (DPM), and the Keycloak server. These are used to authenticate ONE Desktop users and allow them to interact with data sources.
How ONE Desktop is used?
There are two main domains that ONE Desktop is used for, data quality (DQ) and master data management (MDM).
Data quality
With ONE Desktop, you can create complex DQ rules as it offers advanced configuration options compared to what is available out-of-the-box in ONE. In this case, rules are built out of smaller units called steps or, in case when multiple steps are configured to serve as a single step, components. Each step, or component, has a clearly defined task, such as reading a data source, validating a particular record or a part of it, storing the processing results, and so on.
The tool comes with a number of preconfigured steps (that is, low level building blocks) and a selection of components (more complex, high level building blocks) that can, for example, verify postal codes and other country-specific data.
Typically, new components have to be built for each organization, depending on the customer needs. Custom components can be stored and shared with the rest of the organization the same way the default components are.
Before a rule is promoted to the production environment, you can test it in a staging or development environment using a data source defined within ONE or a local source. This ensures the rule works as intended and is ready to be applied to your data.
Master data management
Similarly to how DQ rules are handled in ONE Desktop, the MDM process includes configuring a set of rules to help determine what data should constitute a master data record.
For example, a single customer record could have different input streams, such as the sales team, the data provided by the customer online, the data coming from the legal team. All these sources need to be weighed in order to build a master data record for this customer.
Using steps and components in ONE Desktop, you can build a multilayer pipeline where each part of a data record is given a confidence score. The score is then used to determine whether the information should be rejected as likely incorrect or used to update the master data record.
Once a rule is finished, you can test it on sample or actual data in a development environment before promoting the final version to the production environment.
Was this page useful?