MatchUp Object:Matchcode:Change Settings: Difference between revisions
Created page with "{{MatchUpObjectMatchcodeInterfaceNav |FunctionsCollapse= }} {{CustomTOC}} The functions in this section set the values for the various settings of a matchcode component obje..." |
No edit summary |
||
Line 10: | Line 10: | ||
This function specifies the type for the current MatchcodeComponent object. | This function specifies the type for the current MatchcodeComponent object. | ||
The only parameter for this function is an enumerated value of the type MatchcodeComponentType. | The only parameter for this function is an enumerated value of the type [[MatchUp Object:Enumerations#MatchcodeComponentType|MatchcodeComponentType]]. | ||
For a list of these enumerations, see [[MatchUp Object:Enumerations#MatchcodeComponentType|Matchcode Component Type Enumerations]]. | For a list of these enumerations, see [[MatchUp Object:Enumerations#MatchcodeComponentType|Matchcode Component Type Enumerations]]. | ||
Line 22: | Line 22: | ||
==SetSize== | ==SetSize== | ||
This function sets how many characters from the source data will be used by the current MatchcodeComponent. | This function sets how many characters from the source data will be used by the current MatchcodeComponent object. | ||
This integer value sets the number of characters that this component will use from the related field from each record. If the field is longer than this value, the data will be truncated. If the field is shorter, it will be padded with spaces. | This integer value sets the number of characters that this component will use from the related field from each record. If the field is longer than this value, the data will be truncated. If the field is shorter, it will be padded with spaces. | ||
Line 54: | Line 54: | ||
The maximum number of words offers further control over the amount of data used by each component. If this function is set to 1, then MatchUp Object will take every character up to, but not including, the first space. | The maximum number of words offers further control over the amount of data used by each component. If this function is set to 1, then MatchUp Object will take every character up to, but not including, the first space. | ||
If the first word is shorter than the value passed to the SetSize function, the data will still be truncated at that character, regardless of the setting from this function. | If the first word is shorter than the value passed to the [[#SetSize|SetSize]] function, the data will still be truncated at that character, regardless of the setting from this function. | ||
{{ Object Syntax | {{ Object Syntax | ||
Line 64: | Line 64: | ||
==SetStart== | ==SetStart== | ||
This function sets the starting point used by the current MatchcodeComponent object | This function sets the starting point used by the current MatchcodeComponent object. It controls where MatchUp Object starts counting when applying the component size and accepts an enumerated value of the type [[MatchUp Object:Enumerations#MatchcodeStart|MatchcodeStart]]. | ||
For a list of these enumerations, see [[MatchUp Object:Enumerations#MatchcodeStart|Matchcode Start Enumerations]]. | |||
If the selected value is either '''StartAtPos''' or '''StartAtWord''', the application will need to call the [[#SetStartPos|SetStartPos]] function. | If the selected value is either '''StartAtPos''' or '''StartAtWord''', the application will need to call the [[#SetStartPos|SetStartPos]] function. | ||
Line 76: | Line 78: | ||
==SetStartPos== | ==SetStartPos== | ||
This function is required if the selection from the [[#SetStart|SetStart]] function is either '''StartAtPos''' or '''StartAtWord'''. | This function is required if the selection from the [[#SetStart|SetStart]] function is either '''StartAtPos''' or '''StartAtWord'''. | ||
This function sets either the character position or the word where MatchUp Object starts counting when adding a field to a match key. | |||
For example, if the value passed to '''SetStartPos''' is 2 and the [[#SetStart|SetStart]] function is set to '''StartAtWord''', MatchUp Object will start at the second word. | For example, if the value passed to '''SetStartPos''' is 2 and the [[#SetStart|SetStart]] function is set to '''StartAtWord''', MatchUp Object will start at the second word. | ||
{{ Object Syntax | {{ Object Syntax | ||
Line 105: | Line 92: | ||
==SetTrim== | ==SetTrim== | ||
This function enables or disables trimming of blank spaces from the beginning or end of field data through an enumerated value of the type MatchcodeTrim. | This function enables or disables trimming of blank spaces from the beginning or end of field data through an enumerated value of the type [[MatchUp Object:Enumerations#MatchcodeTrim|MatchcodeTrim]]. | ||
For a list of these enumerations, see [[MatchUp Object:Enumerations#MatchcodeTrim|Matchcode Trim Enumerations]]. | |||
For most applications, this function will be set to '''AllTrim''', which trims excess blank spaces from both the start and end of a field before adding to a match key. | For most applications, this function will be set to '''AllTrim''', which trims excess blank spaces from both the start and end of a field before adding to a match key. | ||
{{ Object Syntax | {{ Object Syntax | ||
Line 128: | Line 106: | ||
==SetFuzzy== | ==SetFuzzy== | ||
The function selects the matching algorithm used when comparing this MatchcodeComponent. It accepts an enumerated value of the type MatchcodeFuzzy. | The function selects the matching algorithm used when comparing this MatchcodeComponent. It accepts an enumerated value of the type [[MatchUp Object:Enumerations#MatchcodeFuzzy|MatchcodeFuzzy]]. | ||
For a list of these enumerations, see [[MatchUp Object:Enumerations#MatchcodeFuzzy|Matchcode Fuzzy Enumerations]]. | |||
See [[MatchUp Object:Component Properties|Matchcode Component Properties]] for more information on the various matching strategies. | See [[MatchUp Object:Component Properties|Matchcode Component Properties]] for more information on the various matching strategies. | ||
Line 190: | Line 120: | ||
==SetNear== | ==SetNear== | ||
This function sets the degree of precision used when the [[#SetFuzzy|SetFuzzy]] function is set to Fast Near, Accurate Near, or Frequency Near. | This function sets the degree of precision used when the [[#SetFuzzy|SetFuzzy]] function is set to '''Fast Near''', '''Accurate Near''', or '''Frequency Near'''. | ||
The integer value from 1 to 4 sets how many differences are allowed before two keys are no longer considered a match when one of the Near matching strategies is selected with the [[#SetFuzzy|SetFuzzy]] function. | The integer value from 1 to 4 sets how many differences are allowed before two keys are no longer considered a match when one of the Near matching strategies is selected with the [[#SetFuzzy|SetFuzzy]] function. | ||
Line 216: | Line 146: | ||
*DoubleMetaphone algorithm. | *DoubleMetaphone algorithm. | ||
The double value from 100 to 0 sets the minimum threshold percent similarity between two keys which will be considered a match when one of the NearDbl matching strategies is selected with the [[#SetFuzzy|SetFuzzy]] function. | The double value from 100 to 0 sets the minimum threshold percent similarity between two keys which will be considered a match when one of the '''NearDbl''' matching strategies is selected with the [[#SetFuzzy|SetFuzzy]] function. | ||
{{ Object Syntax | {{ Object Syntax | ||
Line 226: | Line 156: | ||
==SetFieldMatch== | ==SetFieldMatch== | ||
This function determines how MatchUp Object handles blank or partial fields when applying a matchcode. It accepts an enumerated value of the type MatchcodeFieldMatch. | This function determines how MatchUp Object handles blank or partial fields when applying a matchcode. It accepts an enumerated value of the type [[MatchUp Object:Enumerations#MatchcodeFieldMatch|MatchcodeFieldMatch]]. | ||
For a list of these enumerations, see [[MatchUp Object:Enumerations#MatchcodeFieldMatch|Matchcode Field Match Enumerations]]. | |||
These selections are not mutually exclusive. In order to select more than one, you will need to use a logical OR operation to combine multiple options and pass that value to the function. | These selections are not mutually exclusive. In order to select more than one, you will need to use a logical OR operation to combine multiple options and pass that value to the function. | ||
Line 256: | Line 176: | ||
==SetCombination== | ==SetCombination== | ||
This function selects which combinations in the current matchcode will use this component. It accepts an enumerated value of the type MatchcodeCombination. | This function selects which combinations in the current matchcode will use this component. It accepts an enumerated value of the type [[MatchUp Object:Enumerations#MatchcodeCombination|MatchcodeCombination]]. | ||
For a list of these enumerations, see [[MatchUp Object:Enumerations#MatchcodeCombinations|Matchcode Combinations Enumerations]]. | |||
These selections are not mutually exclusive. In order to select more than one, you will need to use a logical OR operation to combine multiple options and pass that value to the function. | These selections are not mutually exclusive. In order to select more than one, you will need to use a logical OR operation to combine multiple options and pass that value to the function. | ||
Line 306: | Line 192: | ||
==SetSwap== | ==SetSwap== | ||
This function selects the swap pair or swap pairs to which this MatchcodeComponent object belongs and accepts an enumerated value of the type MatchcodeSwap. | This function selects the swap pair or swap pairs to which this MatchcodeComponent object belongs and accepts an enumerated value of the type [[MatchUp Object:Enumerations#MatchcodeSwap|MatchcodeSwap]]. | ||
For a list of these enumerations, see [[MatchUp Object:Enumerations#MatchcodeSwap|Matchcode Swap Enumerations]]. | |||
These selections are not mutually exclusive. In order to select more than one, you will need to use a logical OR operation to combine multiple options and pass that value to the function. | These selections are not mutually exclusive. In order to select more than one, you will need to use a logical OR operation to combine multiple options and pass that value to the function. |
Revision as of 18:43, 5 August 2015
MatchUp Object Matchcode Interface Navigation | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Overview | |||||||||||
Order of Operations | |||||||||||
Mapping Information | |||||||||||
|
The functions in this section set the values for the various settings of a matchcode component object. They can be used to construct new matchcode components when adding them to a matchcode, or to change the settings of an existing component. Every function in this section requires a variable based on the mdMatchcodeComponent class.
SetComponentType
This function specifies the type for the current MatchcodeComponent object.
The only parameter for this function is an enumerated value of the type MatchcodeComponentType.
For a list of these enumerations, see Matchcode Component Type Enumerations.
Syntax | mdMCC->SetComponentType(MatchcodeComponentType) |
---|---|
C | mdMUMatchcodeComponentSetComponentType(mdMCC,mdMUMatchcodeComponentType) |
.Net | mdMCC.ComponentType = MatchcodeComponentType |
SetSize
This function sets how many characters from the source data will be used by the current MatchcodeComponent object.
This integer value sets the number of characters that this component will use from the related field from each record. If the field is longer than this value, the data will be truncated. If the field is shorter, it will be padded with spaces.
Size is only applied to a piece of data after all other component properties have been considered.
Syntax | mdMCC->SetSize(int) |
---|---|
C | mdMUMatchcodeComponentSetSize(mdMCC, int) |
.Net | mdMCC.Size = integer |
SetLabel
This function assigns a label to the current MatchcodeComponent object.
Not all components accept a label. For example, none of the street address components (Street number, street name and so on) can have a label since they are not used for mapping.
Components that are not assigned a label will return the name of their component type. If a label is passed to a component that cannot use one, the component will ignore it.
Syntax | mdMCC->SetLabel(char) |
---|---|
C | mdMUMatchcodeComponentSetLabel(mdMCC, char) |
.Net | mdMCC.Label = string |
SetWordCount
This function sets the maximum number of words used by the current MatchcodeComponent object.
The maximum number of words offers further control over the amount of data used by each component. If this function is set to 1, then MatchUp Object will take every character up to, but not including, the first space.
If the first word is shorter than the value passed to the SetSize function, the data will still be truncated at that character, regardless of the setting from this function.
Syntax | mdMCC->SetWordCount(int) |
---|---|
C | mdMUMatchcodeComponentSetWordCount(mdMCC, int) |
.Net | mdMCC.WordCount = integer |
SetStart
This function sets the starting point used by the current MatchcodeComponent object. It controls where MatchUp Object starts counting when applying the component size and accepts an enumerated value of the type MatchcodeStart.
For a list of these enumerations, see Matchcode Start Enumerations.
If the selected value is either StartAtPos or StartAtWord, the application will need to call the SetStartPos function.
Syntax | mdMCC->SetStart(MatchcodeStart) |
---|---|
C | mdMUMatchcodeComponentSetStart(mdMCC, mdMUMatchcodeStart) |
.Net | mdMCC.Start = MatchcodeStart |
SetStartPos
This function is required if the selection from the SetStart function is either StartAtPos or StartAtWord.
This function sets either the character position or the word where MatchUp Object starts counting when adding a field to a match key.
For example, if the value passed to SetStartPos is 2 and the SetStart function is set to StartAtWord, MatchUp Object will start at the second word.
Syntax | mdMCC->SetStartPos(int) |
---|---|
C | mdMUMatchcodeComponentSetStartPos(mdMCC, int) |
.Net | mdMCC.StartPos = integer |
SetTrim
This function enables or disables trimming of blank spaces from the beginning or end of field data through an enumerated value of the type MatchcodeTrim.
For a list of these enumerations, see Matchcode Trim Enumerations.
For most applications, this function will be set to AllTrim, which trims excess blank spaces from both the start and end of a field before adding to a match key.
Syntax | mdMCC->SetTrim(MatchcodeTrim) |
---|---|
C | mdMUMatchcodeComponentSetTrim(mdMCC, mdMUMatchcodeTrim) |
.Net | mdMCC.Trim = MatchcodeTrim |
SetFuzzy
The function selects the matching algorithm used when comparing this MatchcodeComponent. It accepts an enumerated value of the type MatchcodeFuzzy.
For a list of these enumerations, see Matchcode Fuzzy Enumerations.
See Matchcode Component Properties for more information on the various matching strategies.
Syntax | mdMCC->SetFuzzy(MatchcodeFuzzy) |
---|---|
C | mdMUMatchcodeComponentSetFuzzy(mdMCC, mdMUMatchcodeFuzzy) |
.Net | mdMCC.Fuzzy = MatchcodeFuzzy |
SetNear
This function sets the degree of precision used when the SetFuzzy function is set to Fast Near, Accurate Near, or Frequency Near.
The integer value from 1 to 4 sets how many differences are allowed before two keys are no longer considered a match when one of the Near matching strategies is selected with the SetFuzzy function.
Syntax | mdMCC->SetNear(int) |
---|---|
C | mdMUMatchcodeComponentSetNear(mdMCC, int) |
.Net | mdMCC.Near = integer |
SetNearDbl
This function sets the minimum percentage of similarity which will return a match between two strings when the SetFuzzy function is set to any of the following:
- Proximity
- N-Gram
- Jaro
- Jaro Winkler
- LCS
- Needleman
- MDKeyboard
- Smith Waterman
- Dice's Coefficient
- Jaccard
- Overlap Coefficient
- DoubleMetaphone algorithm.
The double value from 100 to 0 sets the minimum threshold percent similarity between two keys which will be considered a match when one of the NearDbl matching strategies is selected with the SetFuzzy function.
Syntax | mdMCC->SetNearDbl(double) |
---|---|
C | mdMUMatchcodeComponentSetNearDbl(mdMUMatchcodeComponent, double) |
.Net | mdMCC.NearDbl(double) |
SetFieldMatch
This function determines how MatchUp Object handles blank or partial fields when applying a matchcode. It accepts an enumerated value of the type MatchcodeFieldMatch.
For a list of these enumerations, see Matchcode Field Match Enumerations.
These selections are not mutually exclusive. In order to select more than one, you will need to use a logical OR operation to combine multiple options and pass that value to the function.
Some languages, such as C++, do not easily handle using logical operation on enumerations. In these cases, it may be necessary to cast the enumerated values as integers and then combine them using the OR operation.
When working with the first component of a matchcode, keep in mind the special rules for first components. The first component cannot use Initial Only matching or One Blank Field matching.
For more information, see Blank Field Matching.
Syntax | mdMCC->SetFieldMatch(MatchcodeFieldMatch) |
---|---|
C | mdMUMatchcodeComponentSetFieldMatch(mdMCC, mdMUMatchcodeFieldMatch) |
.Net | mdMCC.FieldMatch = MatchcodeFieldMatch |
SetCombination
This function selects which combinations in the current matchcode will use this component. It accepts an enumerated value of the type MatchcodeCombination.
For a list of these enumerations, see Matchcode Combinations Enumerations.
These selections are not mutually exclusive. In order to select more than one, you will need to use a logical OR operation to combine multiple options and pass that value to the function.
Some languages, such as C++, do not easily handle using logical operation on enumerations. In these cases, it may be necessary to cast the enumerated values as integers and then combine them using the OR operation.
Syntax | mdMCC->SetCombination(MatchcodeCombination) |
---|---|
C | mdMUMatchcodeComponentSetCombination(mdMCC, mdMUMatchcodeCombination) |
.Net | mdMCC.Combination = MatchcodeCombination |
SetSwap
This function selects the swap pair or swap pairs to which this MatchcodeComponent object belongs and accepts an enumerated value of the type MatchcodeSwap.
For a list of these enumerations, see Matchcode Swap Enumerations.
These selections are not mutually exclusive. In order to select more than one, you will need to use a logical OR operation to combine multiple options and pass that value to the function.
Some languages, such as C++, do not easily handle using logical operation on enumerations. In these cases, it may be necessary to cast the enumerated values as integers and then combine them using the OR operation.
Syntax | mdMCC->SetSwap(MatchcodeSwap) |
---|---|
C | mdMUMatchcodeComponentSetSwap(mdMCC, mdMUMatchcodeSwap) |
.Net | mdMCC.Swap = MatchcodeSwap |