Cleaner
Cleaner helps you standardize values in a File so the dataset is easier to review, report on, export, or use in another WebHammers Tool.
Use Cleaner when the data is present, but the values are inconsistent. Common examples include extra spaces, different placeholder values, inconsistent wording, or values that need a consistent date or number format.
Cleaner is designed for repeatable cleanup. You create a Configuration, choose the Fields it should affect, define the Rules, save the Configuration, and then use it in a Run.
What Cleaner is for
Cleaner is a good fit when you need to make values more consistent across a dataset, such as:
- trimming extra spaces at the start or end of text
- replacing inconsistent placeholder values with blanks
- finding a known text value and replacing it with a preferred value
- standardizing dates, whole numbers, or decimal numbers into a consistent format
- preparing a dataset so later validation, matching, reporting, or export work is easier to review
What Cleaner is not for
Cleaner is not the best starting point for every data issue.
Use another WebHammers Tool when your primary goal is to:
- keep or exclude Records based on conditions
- compare one File to another
- join or split datasets
- mask or obfuscate sensitive data
- detect duplicate Records as the main task
If your goal is "make these values more consistent," Cleaner is usually the right place to start.
Typical Cleaner workflow
A common workflow looks like this:
- Confirm the File has an Import Config that describes the Fields Cleaner can use.
- Create or edit a Cleaner Configuration.
- Choose the Import configuration or Import Config shown on the screen.
- Add Cleaning Rules and choose the Fields each Rule should affect.
- Save the Configuration as a draft, or publish it when it is ready for use.
- Run Cleaner with an input File.
- Review the Run completion details, Job Summary, and cleaned output File.
Screen overview
Cleaner includes these main areas:
| Area | What you do there |
|---|---|
| Cleaner Configurations | Create, edit, run, and view history for saved Cleaner Configurations. |
| Create Cleaner Config | Set up a new Configuration, choose source data, define Cleaning Rules, and save the first draft. |
| Edit Cleaner Config | Update the Configuration name, source Import Config, Rules, description, and publication status. |
| Run Cleaner | Name the Run, choose the input File, start the Run, watch progress, and download output when available. |
| Cleaner Job History | Review recent Cleaner Runs, including status, imported Records, exported Records, problems, and cells changed. |
| Cleaner Job Summary | Review one Run in more detail and download the cleaned File. |
Before you begin
Before building a Configuration, be clear about the outcome you want.
Ask yourself:
- Which Fields are causing the problem?
- What should the cleaned values look like?
- Which values should change, and which values should stay as they are?
- Will the cleaned output be used for reporting, import, matching, validation, or handoff?
- Does the selected Import Config include the Fields your Rules need?
That clarity helps you create a Configuration that is easier to test and safer to reuse.
What makes a good Cleaner Configuration
The best Cleaner Configurations are narrow, intentional, and easy to understand later.
A strong Configuration usually has these characteristics:
- it solves one clear business problem
- it targets known Fields
- it uses a small number of deliberate Rules
- it can be reviewed using representative Records
- it is named clearly enough that another user can understand its purpose
Data handling note
WebHammers jobs run on your machine. Your data stays on your machine during Tool processing. WebHammers servers store Configurations so they can be reused, shared, and managed. A Configuration may include information such as the Field names from your data files.