Data Masking Components: Names with Gender Dynamic

{TOC}

Names with Gender Dynamic

API Reference, CLR Reference (links)

Purpose

The purpose of the component is to mask full names with the realistic but different data.

Algorithm

Substitution Preserving Referential Integrity

Description

The Masking First Name with Gender Dynamic component expects First Name as an input and produces First Name as an output. The output is “deterministic” – meaning it always provides the same output on the same input and as such helps maintain referential integrity enterprise wide. It also identifies whether the name is Female, Male, or Unisex and maps names according to existing popular name mappings. If however the name is not among those that have component’s mapping, it will map into the unisex name.

API Reference, CLR Reference (links)

Usage Instructions:

1. Configure a source that contains the column with alphabetical and numeric characters. The data in the column may also include any other character that will be treated as a separator.
2. Drag and Drop Names with Gender masking component, connect the source and the generic alpha numeric component with the source's precedence constraint:
3. Now, the precedence constraint (the blue arrow) passes proper meta-data to the Names with Gender component. If you click on constraint, you will see:
4. Now that the metadata for the Names with Gender exists, and values are passed into the data masking component, please open the component editor:
5. In the second tab, there are input columns. Please check-mark only one column, the one that you will be masking with Names with Gender algorithm:
6. This will create an extra column with the prefix “Masked_”.
7. Create a connection manager for the destination and configure source component for the destination. In the connection manager, in the tab “Mappings”, specify that you want newly created Field_Masked to be a field replacing the original value. For that, just click on the available input columns, choose the masked value, and map to the “Available Destination Columns”
8. Now, all the configurations are complete for the valid values. You can run the package with the Names with Gender Data Masking component, and see the results of data masking:

Error Handling

9. If, however, there are invalid values in the package's source, one would need to configure error handling. Invalid values are those that are not conforming to the rules of the entity. To handle invalid values, each data masking component has error handling precedence constraint. One needs to create error destination connection and connect red arrow (error handling constraint) with this destination. As the connection is made, one needs to configure the state of failure: “Fail”,”Ignore” or “Redirect”.
10. It is recommended that one re-directs the output into the error destination, so that later one be able to analyze and process data for quality purposes. The Full Name Info components errors are the only ones not recommended for further processing as it is truly hard to break their format.
11. It is our suggestion that with Names with Gender component one should not process erroneous data without further analysis at all.

Download Example ###**