The Date Transposition Match comparison determines whether or not two date values match if the day and month are switched (transposed). This allows the matching of records where it is known that the same date may be entered into a system in different formats. For example, if an application has not been properly internationalized, a user from the UK might enter the date 1st August 1970 as "01/08/1970", but a user from the USA might enter the same date as "08/01/1970".
Use the Date Transposition Match comparison in conjunction with other comparisons to find possible matches where the dates may have been entered inconsistently. For example, when matching people using Surname, Post Code and Date of Birth identifiers, you might wish to treat a person with the same Surname and Post code, and a Date of Birth that is the same when the day and month are transposed, as a possible match. Such a person would not match a rule that demanded a full match on Date of Birth (using a Date Match comparison).
This comparison does not support the use of result bands.
|
Option |
Type |
Purpose |
Default Value |
|
Match No Data pairs? |
Yes/No |
This option determines the result of a comparison when it compares two No Data (Null, or containing only whitespace characters) values for an identifier. If set to No, the comparison will give a 'no data' result when comparing a No Data value against another No Data value. If set to Yes, the comparison will give a full match (TRUE) when comparing a No Data value against another No Data value. A 'no data' result will only be returned if a No Data value is compared against a populated value. |
No |
|
Ignore year? |
Yes/No |
Ignore year allows the year part of the date to be ignored when matching. If set to Yes, the year will be ignored when matching. For example, "11/01/1901" will match "01/11/1875" (as the day and month are transposed). If set to No, the year will be used when matching. For example, "11/01/1975" will match "01/11/1975", but "11/01/1901" and "01/11/1875" will not match. |
No |
|
Ignore century? |
Yes/No |
Ignore century allows the century part of the date to be ignored when matching. Note that the Ignore century option will only apply if Ignore year = No. If Ignore year = Yes, the entire year part of the date is always ignored. If set to Yes, the century will be ignored when matching. For example, "11/01/1901" will match "01/11/2001" (but "11/01/1975" will not match "01/11/1874") If set to No, the century will be used when matching. For example, "11/01/2001" will match "01/11/2001", but "11/01/1901" and "01/11/2001" will not match. |
No |
|
Time zone |
Time Zone |
Sets the time zone to use when comparing the two date/time values. |
Director Time Zone |
Example configuration
In this example, the Date Transposition Match comparison is used on a Date of Birth identifier to match people where the date and month of Birth have been transposed. The following options are specified:
Match No Data pairs? = No
Ignore year? = No
Ignore century? = Yes
Time zone = Director Time Zone
Example results
With the above configuration, the following table illustrates some comparison results:
|
Value A |
Value B |
Comparison result |
|
11/01/1960 |
01/11/1960 |
TRUE (match) |
|
11/01/1945 |
01/11/1845 |
TRUE (match) |
|
11/01/1945 |
01/11/1946 |
FALSE (no match) |
|
05/08/1960 |
08/06/1960 |
FALSE (no match) |
|
05/08/1960 |
05/08/1960 |
FALSE (no match) |
|
05/08/1945 |
05/08/1845 |
FALSE (no match) |
Oracle ® Enterprise Data Quality Help version 9.0
Copyright ©
2006,2011 Oracle and/or its affiliates. All rights reserved.