The Person Full Name Mask
This mask shall generate Full Names that consist of one or more First Names and one Last Name for a single field.
The longest First Name is 11 characters and the longest Last Name is 13 characters. If a receiving column width is shorter than a generated Full Name then the generated Full Name shall be truncated.
Every First and Last Name generated consists of only alphabetic characters. In other words, there are no hyphenated names, and there are no apostrophes.
DataVeil does not preserve any punctuation or special symbols such as the characters ; : , . | / \ The only exception is that the Separator Character shall be included in the masked Full Name if the 'Expect Separator Character...' option is selected and the separator was found in the original value or the original value was NULL.
The default Person Full Name mask is shown below.
Last Name appears at:
This specifies the relative position of the Last Name within the field.
First Position should be selected when the Last Name is expected to appear first. Example: "Smith John"
Last Position should be selected when the Last Name is expected to appear last. Example: "John Smith"
Please see "Why Locating First and Last Names May Be Important To You" below.
If field contains a single name then accept it as a:
This deals with the potential situation that a Full Name field contains only a single name. E.g. "Prince"
First Name specifies that the single name is replaced using a DataVeil-generated First Name.
Last Name specifies that the single name is replaced using a DataVeil-generated Last Name.
Expect Separator Character between Last Name and First Name(s)
If this option is selected then DataVeil shall scan the field for the first occurrence of the Separator Character ("," is the default.)
If the separator character is absent then the handling options are:
Use normal parsing... DataVeil shall attempt to locate the First Name(s) and Last Name as if this 'Expect Separator Character...' option was not selected.
Treat the entire field as a single name The field value shall be considered as either a single First Name or Last Name according to the setting of the 'If field contains a single name...' parameter.
How DataVeil Parses a Field to Locate the First Name(s) and Last Name
A hyphenated name is always regarded as a single name.
A field can contain zero or more First Names.
A field can contain zero or one Last Name.
If a field contains more than two words then DataVeil shall check for prepositions (e.g. "de") and articles (e.g. "le") preceding the Last Name. If prepositions or articles are found then they shall be considered as part of the Last Name. Example "de la Rosa" shall be considered as a single Last Name. DataVeil recognizes the following prepositions and articles: al, bin, binti, da, de, del, della, des, di, du, el, la, le, van, von.
If a field contains exactly two words then prepositions and articles are not considered. Eg. "Van Chow" would be considered as consisting of a First Name and a Last Name, whereas "John James van Huesen" would be considered as consisting of two First Names ("John" and "James") and a Last Name ("van Huesen") assuming that 'Last Name appears at' was configured for 'Last Position'.
If the Separator option is specified then the first occurrence of the separator character shall be assumed to divide the First Name(s) from the Last Name. If multiple words are found at the position of the Last Name (according to the separator and 'Last Name appears at' parameter) then all of those words shall be considered as consisting of a single Last Name.
A field that contains a NULL value shall be replaced with one First Name and one Last Name.
Here are some examples to clarify:
Sample 1 - Default parameters
"Mary" is consistently masked by "Ariana" except:
* on row 5 because "Mary-Jo" is hyphenated and DataVeil considers hyphenated names as distinct individual names. In this case "Mary-Jo" is masked by "Maribeth".
Also note on row 4 that since "Mary Jo" is not hyphenated it was considered as two distinct First Names.
Similarly, the Last Name "Williams" is consistently masked by "Araiza" except:
* on row 2 "Williams" appears as a First Name and is therefore masked as a First Name ("Ronny".)
* on row 3 "Williams-Smith" is hyphenated and is therefore considered as a single Last Name different to "Williams".
Sample 2 - Last Name in First Position, Observe Separator ','
This mask is configured to expect the Last Name at the beginning of the field ('First Position'). As you can see, "Williams" is masked by "Araiza" which is consistent with the previous examples in Sample 1 where Last Name was expected in 'Last Position'.
This mask, however, uses the Separator option. On row 3 the separator is found which means that everything preceding it ("WILLIAMS SMITH") is considered a single Last Name. In this case it is equivalent to a hyphenated name. Therefore "Williams-Smith" on row 4 is also masked by the same Last Name "Kapp" as on row 3.
Also note that if the Separator Character is found (or the field is NULL) then it shall be included in the masked Full Name as in rows 3 and 6. If it is not found then it is omitted.
Why Locating First and Last Names May Be Important To You
You may be wondering 'Does it really matter if First Names get replaced with Last Names and vice-versa?'
The answer is it may be inconsequential, or it may be important if consistency with other Name fields in your database is required.
For example, suppose that you have a Full Name field that contains the value "John Smith" and elsewhere in your database you have a corresponding Last Name field that contains "Smith".
Therefore, if your application is expecting consistency between these fields and if the Full Name is masked with "Peter Jones" then the corresponding Last Name field should also be masked with "Jones".
This consistent masking is only possible if Deterministic mode is used for the masks of both fields (the default) and that the Full Name mask correctly identifies the Last Name in the Full Name field. i.e. If you incorrectly specified the 'Last Name appears at' parameter as 'First Position' then then Last Name would be considered as "John" which would not synchronize with the other field's value of "Smith" which would result in inconsistent masking.
The First Names Tab
This specifies how DataVeil shall generate masked First Names.
Its parameters and operation is the same as for the Person First Name mask.
If Deterministic mode masking (the default) is used then First Names masked by the 'Person First Name' mask and the 'Person Full Name' masks shall be masked consistently. For example "John" will be replaced with the same masked value by both masks.
The Last Names Tab
This specifies how DataVeil shall generate a masked Last Name.
Its parameters and operation is the same as for the Person Last Name mask.
If Deterministic mode masking (the default) is used then Last Names masked by the Person Last Name and the Person Full Name masks shall be masked consistently. For example "Smith" will be replaced with the same masked value by both masks.