ResolveX Data Profiling and Onboarding¶
Read a source as it is, then work out the rules that would check it and the mapping that would load it.
Data Profiling and Onboarding is the episodic half of the platform. It runs when a source is onboarded or has changed, not on every record: it measures, it proposes, and it waits for a person. What it produces is versioned and then used by the products that run continuously.
What it hands on¶
| to | what |
|---|---|
| Data Quality Management | a profiling report: the measurements its rules are derived from |
| Data Integration Management | an approved mapping, at a revision a feed pins |
| Master Data Management | nothing directly. The mapping describes how to reach it |
One gate¶
Profiling has no gate, deliberately: a measurement is either right or wrong, and a person clicking "approve" on it changes nothing.
A mapping is a proposal about meaning (this column is that attribute), and that is worth a person. It is the one decision this product asks for.
Where to start¶
- What Data Profiling and Onboarding is: the shape of a run.
- Your first profile: profile a source and read what came back.
- How a source becomes the model: where a mapping comes from.