Matchcode Optimization:Alphas: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
==Alphas== | ==Alphas== | ||
===Specifics=== | ===Specifics=== | ||
Only alphabetic characters will be compared. | :Only alphabetic characters will be compared. | ||
===Summary=== | ===Summary=== | ||
This algorithm will remove all characters that are not in the English alphabet and compares strings based on this criteria. | :This algorithm will remove all characters that are not in the English alphabet and compares strings based on this criteria. | ||
===Returns=== | ===Returns=== | ||
Returns a match is all alphabetic characters match exactly. | :Returns a match is all alphabetic characters match exactly. | ||
===Example Matchcode Component=== | ===Example Matchcode Component=== | ||
| Line 20: | Line 20: | ||
|AdditionalRows= | |AdditionalRows= | ||
{{EDTRow|White|Johnson|Jhnsn|Unique}} | {{EDTRow|White|Johnson|Jhnsn|Unique}} | ||
{{EDTRow| | {{EDTRow|White|Lynda|Dylan|Unique}} | ||
{{EDTRow|Green|Apco Oil Lube 170|Apco Oil Lube 342|Match}} | {{EDTRow|Green|Apco Oil Lube 170|Apco Oil Lube 342|Match}} | ||
{{EDTRow| | {{EDTRow|White|Thomas|Tom|Unique}} | ||
}} | }} | ||
| Line 34: | Line 34: | ||
===Recommended Usage=== | ===Recommended Usage=== | ||
Hybrid Deduper, where a single incoming record can quickly be evaluated independently against each record in an existing large master database. | :Hybrid Deduper, where a single incoming record can quickly be evaluated independently against each record in an existing large master database. | ||
Databases created via real-time data entry where audio likeness errors are introduced. | :Databases created via real-time data entry where audio likeness errors are introduced. | ||
Databases of US and English language origin. | :Databases of US and English language origin. | ||
===Not Recommended For=== | ===Not Recommended For=== | ||
Gather/scatter, survivorship, or record consolidation of sensitive data. | :Gather/scatter, survivorship, or record consolidation of sensitive data. | ||
Quantifiable data or records with proprietary keywords not associated in our knowledgebase tables. | Quantifiable data or records with proprietary keywords not associated in our knowledgebase tables. | ||
===Do Not Use With=== | ===Do Not Use With=== | ||
UTF-8 data. This algorithm was ported to MatchUp with the assumption that a character equals one byte, and therefore results may not be accurate if the data contains multi-byte characters. | :UTF-8 data. This algorithm was ported to MatchUp with the assumption that a character equals one byte, and therefore results may not be accurate if the data contains multi-byte characters. | ||
[[Category:MatchUp Hub]] | [[Category:MatchUp Hub]] | ||
[[Category:Matchcode Optimization]] | [[Category:Matchcode Optimization]] | ||
Revision as of 22:35, 26 September 2018
Alphas
Specifics
- Only alphabetic characters will be compared.
Summary
- This algorithm will remove all characters that are not in the English alphabet and compares strings based on this criteria.
Returns
- Returns a match is all alphabetic characters match exactly.
Example Matchcode Component
Example Data
STRING1 STRING2 RESULT Johnson Jhnsn Unique Lynda Dylan Unique Apco Oil Lube 170 Apco Oil Lube 342 Match Thomas Tom Unique
| Performance | |||||
|---|---|---|---|---|---|
| Slower | Faster | ||||
| Matches | |||||
| More Matches | Greater Accuracy | ||||
Recommended Usage
- Hybrid Deduper, where a single incoming record can quickly be evaluated independently against each record in an existing large master database.
- Databases created via real-time data entry where audio likeness errors are introduced.
- Databases of US and English language origin.
Not Recommended For
- Gather/scatter, survivorship, or record consolidation of sensitive data.
Quantifiable data or records with proprietary keywords not associated in our knowledgebase tables.
Do Not Use With
- UTF-8 data. This algorithm was ported to MatchUp with the assumption that a character equals one byte, and therefore results may not be accurate if the data contains multi-byte characters.