<expression> := <Purpose_Name>
<expression> := <Purpose_Name>(<Match_level>)
<expression> := (not<expression>)
<expression> := (<expression> or <expression>)
<expression> := (<expression> and <expression>)
<expression> := (<expression>)

Address
Contact
Division
Fields
Household
Individual
Organization
Person_Name
Resident
Wide_Contact
Geocode
Filter1,Filter2,... Filter9

Typical
Conservative
Loose

If one of the adjusted limits is greater than 100, the limit is set to 100.
If one of the adjusted limits is less than 0, the limit is set to 0.
If the adjusted accept limit is less than the reject limit, the accept limit is set to the reject limit.
If the accept match adjustment is 101, the accept limit is set to 101. As a result, SSA-NAME3 does not accept any record, and SSA-NAME3 either rejects a record or marks it as undecided.
For example, if
MATCH_LEVEL=Loose+101-10
, the accept limit is set to 101.
If a match call returns a score of 100, SSA-NAME3 marks the record as undecided.
If a match call returns a score that is less than 100 and less than the reject limit, SSA-NAME3 rejects the record. If the score is less than 100 but greater than or equal to the reject limit, SSA-NAME3 marks the record as undecided.

matchlevel+/-nn

Adjusts the accept and reject limits by using the same specified number. For example:

MATCH_LEVEL=Typical+20

If the predefined accept limit is 79 and reject limit is 50, the adjusted accept limit is 99 and reject limit is 70.

matchlevel+/-nn+/-nn

Adjusts the accept and reject limits by using the specified numbers. For example:

MATCH_LEVEL=Typical-40+40

If the predefined accept limit is 79 and reject limit is 50, the calculated accept limit is 39, which is less than the reject limit of 90. The adjusted accept limit is set to 90, and the reject limit remains at 90.

Date

The

Date

field accepts the

Date_Format

option. The

MATCH_OPTIONS

control uses the following format for the

Date_Format

option :

MATCH_OPTIONS=DATE:Date_Format=<DDMMYY>|<MMDDYY>|<YYMMDD>

The values are not case sensitive.

Geocode

The

Geocode

field accepts the

FORMAT

and

RADIUS

options. The

MATCH_OPTIONS

control uses the following format for the

FORMAT

and

RADIUS

options:

MATCH_OPTIONS=GEOCODE:FORMAT=1,GEOCODE:RADIUS=10000

The

FORMAT

option indicates the order of the latitude and longitude coordinates that you specify.

If

GEOCODE:FORMAT=1

, SSA-NAME3 considers the geographic coordinates in the following order:

*Geocode*<Longitude> <Latitude>***

If

GEOCODE:FORMAT=0

, SSA-NAME3 considers the geographic coordinates in the following order:

*Geocode*<Latitude> <Longitude>***

The default value is 0.

The

RADIUS

option indicates the search radius to generate keys according to the latitude and longitude coordinates that you specify. The default value is 1000 m, and the default unit is meter.

Use the following guidelines when you specify the geocode radius:

SSA-NAME3 considers the radius to be in meters even if you specify any other unit.
SSA-NAME3 ignores the decimal values and uses the whole number as the radius. For example, if you specify the radius as 850.8, SSA-NAME3 considers the radius as 850.

SSA-NAME3 ignores any incorrect or unrecognised options in the

MATCH_OPTIONS

control and proceeds with matching, which might result in unexpected scores.

Address, Organization Name, Person Name

When the Search or File field contains one token, this match option uses the field with more tokens for matching. This

MATCH_OPTIONS

control uses the following format:

MATCH_OPTIONS=(<field>:M)

where field can be Address_Part1, Address_Part2, Organization_Name, and Person_Name.

Example:

MATCH_LEVEL=Conservative-20 PURPOSE=Person_Name MATCH_OPTIONS=(Person_Name:M)
*Person_Name*James***
*Person_Name*James Andrews***

With

MATCH_OPTIONS=(Person_Name:M),

*Person_Name*James Andrews***

is considered for matching.

Exact matching. Returns 100% score only if the search data values match with the file data values.
Fuzzy matching. Returns 0 to 100% score based on how close the search data and file data values match.
Inexact matching. Returns 100% score if the search data values do not match with the file data values.
Range matching. Returns 100% score if the search data and file data values are within the specified range.

PURPOSE=Person_Name SEARCH=Person_Name(Exact),0,16 FILE=Person_Name,0,16
. The expression returns 100% score only if the search data value exactly matches with the file data value.
PURPOSE=Fields SEARCH=Person_Name(2;5;Exact),0,16 FILE=Person_Name(2;Exact),0,16
. The expression creates an extended field for the
Person_Name
field named
Person_Name(2)
and sets the weight for the extended field to 5. The search data value returns 100% score if the search data value exactly matches with the file data value.
PURPOSE=Person_Name SEARCH=Person_Name(0;5;Exact),0,16 FILE=Person_Name,0,16
. The expression sets the weight of the
Person_Name
field to 5 without creating any extended field. The search data value returns 100% score if the search data value exactly matches with the file data value.
PURPOSE=Person_Name SEARCH=Person_Name(1;Exact),0,16 FILE=Person_Name(1;Exact),0,16
. The expression creates an extended field for the
Person_Name
field named
Person_Name(1)
. The extended field uses the weight of the
Person_Name
field. The search data value returns 100% score if the search data value exactly matches with the file data value.
PURPOSE=Fields SEARCH=Date,0,8 FILE=Date(Exact:Z),0,8
. The expression returns 100% score if the file data value is 0.

Field Name
. Name of the SSA-NAME3 field.
Field ID
. Number that you want to assign to the extended field. If you want to extend a key field, use any number as the
Field ID
value. If you do not want to extend a key field, use 0 as the
Field ID
value. If you extend a key field in the search data, extend the corresponding key field in the file data.
Algorithm Name
. Name of the supported algorithm that performs the fuzzy matching.
Use one of the following values:
Levenshtein
. Scores the records based on the minimum number of single-character edits required to change one word into the other.
Dice
. Scores the records based on the Dice's coefficient.
JaroWinkler
. Scores the records based on the minimum number of single-character transpositions required to change one word into the other.
Upper Score Limit/Lower Score Limit
. Minimum score required for the records to be considered as matches or unique records.
If a score is more than the upper score limit, the records are considered as a match. If a score is less than the lower score limit, the records are considered as unique records. If a score is between the upper and lower score limits, the records are considered as undecided matches. Default is 0.

SEARCH=Attribute1(1;Levenshtein:79;60) FILE=Attribute1(1;Levenshtein:79;60)
. The expression extends the Attribute1 field and uses the Levenshtein algorithm to perform fuzzy matching.
SEARCH=Attribute1(0;JaroWinkler) FILE=Attribute1(0;JaroWinkler)
. The expression does not extend the Attribute1 field and uses the JaroWinkler algorithm to perform fuzzy matching.

PURPOSE=Person_Name SEARCH=Person_Name(!Exact),0,16 FILE=Person_Name,0,16
. The expression returns 100% score if the search data value does not match with the file data value.
PURPOSE=Fields SEARCH=Person_Name(1;5;!Exact),0,16 FILE=Person_Name(1;!Exact),0,16
. The expression creates an extended field for the
Person_Name
field named
Person_Name(1)
and sets the weight for the extended field to 5. The search data value returns 100% score if the search data value does not match with the file data value.
PURPOSE=Person_Name SEARCH=Person_Name(0;5;!Exact),0,16 FILE=Person_Name,0,16
. The expression sets the weight of the
Person_Name
field to 5 without creating any extended field. The search data value returns 100% score if the search data value does not match with the file data value.
PURPOSE=Fields SEARCH=Person_Name(3;!Exact),0,16 FILE=Person_Name(3;!Exact),0,16
. The expression creates an extended field for the
Person_Name
field named
Person_Name(3)
, and the extended field uses the weight of the
Person_Name
field. The search data value returns 100% score if the search data value does not match with the file data value.
PURPOSE=Fields SEARCH=Date,0,8 FILE=Date(!Exact:ZB),0,8
. The expression returns 100% score if the file data value is not 0 or null.

PURPOSE=<Purpose Name> SEARCH=<Field Name>[(<Field ID>;<Weight>;Range:<Negative Limit>;<Positive Limit>)],<Offset>,<Length> FILE=<Field Name>[(<Field ID>;<Weight>;Range:<Negative Limit>;<Positive Limit>)],<Offset>,<Length>
If you want to extend a key field, use any number as the
Field ID
value. If you do not want to extend any key field, use 0 as the
Field ID
value. If you extend a key field in the search or file data, you must extend the corresponding key field in the search or file data.
For example, the
PURPOSE=Person_Name SEARCH=Person_Name,0,16,Attribute1(1;5;Range:20;10),16,2 FILE=Person_Name,0,16,Attribute1(1;Range),16,2
expression creates an extended field for the
Attribute1
field named
Attribute1(1)
and sets the weight for the extended field to 5. If the
Attribute1(1)
value in the search data is 100, the range for the search data is 100-20 to 100+10, which is 80 to 110. The range matching returns 100% score if the
Attribute1(1)
value in the file data is within the search data range.
If both the positive and negative limits are the same, you can specify the range in the
(Range:<Limit>)
format. For example,
(Range:20)
equals
(Range:20;20).
PURPOSE=<Purpose Name> SEARCH=<Field Name>[(<Field ID>;<Weight>;Range:%<Negative Limit>;<Positive Limit>)],<Offset>,<Length> SEARCH=<Field Name>[(<Field ID>;<Weight>;Range:%<Negative Limit>;<Positive Limit>)],<Offset>,<Length>
If you want to extend a key field, use any number as the
Field ID
value. If you do not want to extend any key field, use 0 as the
Field ID
value. If you extend a key field in the search or file data, you must extend the corresponding key field in the search or file data.
For example, the
PURPOSE=Person_Name SEARCH=Person_Name,0,16,Attribute1,16,2 FILE=Person_Name,0,16,Attribute1(Range:%10;20),16,2
expression indicates that if the
Attribute1
value in the file data is 100, the range for the file data is 100-10% of the
Attribute1
value to 100+20% of the
Attribute1
value, which is 90 to 120. The range matching returns 100% score if the
Attribute1
value in the search data is within the file data range.
If both the positive and negative limits are the same, you can specify the range in the
(Range:%<Limit>)
format. For example,
(Range:%20)
equals
(Range:%20;20).
PURPOSE=<Purpose Name> SEARCH=<Field Name>[(Range:F|S)],<Offset>,<Length> FILE=<Field Name>[(Range:F|S]),<Offset>,<Length>
The value F indicates to use the file data to create the range, and the value S indicates to use the search data to create the range.
For example, the
PURPOSE=Fields SEARCH=Date(Range:F),0,4 FILE=Date(Range:F),0,4,Date(Range:F),4,4
expression indicates that if the file data is 50008000, the range for the search data is 5000 to 8000. The range matching returns 100% score if the
Date
value in the search data is within the file data range.

PURPOSE=<Purpose Name> SEARCH=<Date Field Name>[(Range:F|S)],<Offset>,<Length> FILE=<Date Field Name>[(Range:F|S]),<Offset>,<Length>
The value
F
indicates to use the file data to create the range, and the value
S
indicates to use the search data to create the range.
For example, the
PURPOSE=Fields SEARCH=Date(Range:F),0,8 FILE=Date(Range:F),0,8,Date(Range:F),8,8
expression indicates that if the file data is 1999101019991020, the range for the search data is 19991010 to 19991020. The range matching returns 100% score if the Date value in the search data is within the file data range.
PURPOSE=<Purpose Name> SEARCH=<Date Field Name>[(DateRange:<Negative Limit>;<Positive Limit>)],<Offset>,<Length> SEARCH=<Date Field Name>[(DateRange:<Negative Limit>;<Positive Limit>)],<Offset>,<Length>
For example, the
PURPOSE=Fields SEARCH=Date(Range:F),0,8 FILE=Date(DateRange:5;10),8,8
expression indicates that if the
Date
value in the file data is 20150410, the range for the file data is 20150405 to 20150420. The range matching returns 100% score if the
Date
value in the search data is within the file data range.
If both the positive and negative limits are the same, you can specify the range in the
(DateRange:<Limit>)
format. For example,
(DateRange:7)
equals
(DateRange:7;7).
PURPOSE=<Purpose Name> SEARCH=<Date Field Name>[(DateRange:%<Negative Limit>;<Positive Limit>)],<Offset>,<Length> SEARCH=<Date Field Name>[(DateRange:%<Negative Limit>;<Positive Limit>)],<Offset>,<Length>
For example, the
PURPOSE=Fields SEARCH=Date,0,8 FILE=Date(DateRange:%10;20),0,8
expression indicates that if the
Date
value in the file data is 19991010, the range for the file data is 10-10% of the
Date
value to 10+20% of the
Date
value, which is 19991009 to 19991012. The range matching returns 100% score if the
Date
value in the search data is within the file data range.
If both the positive and negative limits are the same, you can specify the range in the
(DateRange:%<Limit>)
format. For example,
(DateRange:%20)
equals
(DateRange:%20;20).

PURPOSE=(Filter<Filter Purpose Number>,...) FILTER_SEARCHVALUES=<Filter Purpose Number>,<List of Flags>,(<List of Values>)|{<Value>,(<List of Values>)} 

PURPOSE=(Filter2 AND Filter3) FILTER_SEARCHVALUES=2,SP,(WILLIAM,BILL),3,FP,{ROBERT,(ROB,ROBBIE)}

Filter Purpose Number

Indicates the Filter purpose number for which you define a list of values.

For example, if you use the Filter5 purpose to specify the search data, use 5 as the Filter purpose number.

(List of Values)|{Value,(List of Values)}

Indicates the list of values to match with the search data, file data, or both. You can specify a list of values, or you can pair a value with a list of values.

For example:

FILTER_SEARCHVALUES=2,SP,(WILLIAM,BILL),3,FP,{ROBERT,(ROB,ROBBIE)}

Use appropriate flags to indicate whether to match the specified values with the search data, file data, or both.

List of Flags

Indicates whether to match the specified values with the search data, file data, or both. You can use multiple flags. For example, FP.

If you specify a list of values, you can use the following flags:

S. Indicates to match the values with the search data.
F. Indicates to match the values with the file data.
B. Indicates to match the values with both the search and file data.
P. Indicates to match the values in the list with the search data, file data, or both based on the length of the values in the list. This flag functions in conjunction with other flags.
For example, specify
FILTER_SEARCHVALUES=2,SP,Rob
as one of the SCORE-LOGIC controls and
*Filter2*Rose***
in the search data. The length of
Rob
is three characters, so the matching considers only the first three characters of the search data. The matching does not return 100% score because
Rob
in the list does not exactly match with the first three characters of the search data, which are
Ros
.

If you pair a value with a list of values, you can use the following flags:

S. Indicates to match the value with the search data and the list of values with the file data.
F. Indicates to match the value with the file data and the list of values with the search data.
P. Indicates to match the values in the list with the search data, the file data, or both based on the length of the values in the list. This flag functions in conjunction with other flags.
For example, the
FILTER_SEARCHVALUES=3,S,{ROBERT,(ROB,ROBBIE)}
control indicates to match
Robert
with the search data and the list of values,
Rob and Robbie
, with the file data.