MatchUp Object:FAQ:Feature Comparison: Difference between revisions

From Melissa Data Wiki
Jump to navigation Jump to search
Newer edit →
Created page with "{{CustomTOC}} ==Licenses== {|class="alternate01" cellspacing="0" !MatchUp Object V3 !MatchUp Object V2 !style="border-right:0px;"|Legacy (DTAPI) |- |Uses new License class for..."
 
No edit summary
Line 58: Line 58:
|
|
|-
|-
|Redesigned in a more linear fashion for ease of usage. Repetitive edit controls have been removed
|Redesigned in a more linear fashion for ease of usage.
Repetitive edit controls have been removed
|
|
|
|
Line 148: Line 149:
|
|
;New Interface
;New Interface
MatchcodeList – easier to develop dynamic
*MatchcodeList
Applications for selecting a matchcode
:Easier to develop dynamic Applications for selecting a matchcode
SetPathToMatchUpFiles  
*SetPathToMatchUpFiles  
InitializeDataFiles
*InitializeDataFiles
GetInitializeErrorString
*GetInitializeErrorString
GetMatchcodeCount  
*GetMatchcodeCount  
GetMatchcodeName  
*GetMatchcodeName  
|
|
|
|

Revision as of 00:38, 26 July 2013


Licenses

MatchUp Object V3 MatchUp Object V2 Legacy (DTAPI)
Uses new License class for easy integration With other Melissa Data products. Can be set as ENV variable Uses old style license – deprecated. Can not be set with a Melissa Data ENV Uses old style license – deprecated. Can not be set with a Melissa Data ENV


Deduping Engines

MatchUp Object V3 MatchUp Object V2 Legacy (DTAPI)
Read-Write (batch, or full database(s)) Read-Write (batch, or full database(s)) Read-Write (batch, or full database(s))
Incremental (real-time deduping) Incremental (real-time deduping) Incremental (real-time deduping)
Hybrid (more developer flexible)
  • Cluster selection
  • Key storage
 Hybrid (more developer flexible)
  • Cluster selection
  • Key storage
 Hybrid (more developer flexible)
  • Cluster selection
  • Key storage
Intersecting Deduper
  • First component in all combinations no longer required
  • No restrictions on first component
 first component restrictions first component restrictions


Matchcode Editor

MatchUp Object V3 MatchUp Object V2 Legacy (DTAPI)
Completely redesigned Matchcode Editor Older interface - deprecated Older interface – deprecated
Expanded descriptions for more intuitive understanding
Redesigned in a more linear fashion for ease of usage.

Repetitive edit controls have been removed

Fuzzy
  • Exact
  • Phonetex
  • Sounex
  • Containment
  • Frequency
  • Fast Near
  • Accurate Near
  • Frequency Near
  • Vowels
  • Consonants
  • Alphas
  • Numerics
Fuzzy
  • Exact
  • Phonetex
  • Sounex
  • Containment
  • Frequency
  • Fast Near
  • Accurate Near
  • Frequency Near
  • Vowels
  • Consonants
  • Alphas
  • Numerics
Fuzzy
  • Exact
  • Phonetex
  • Sounex
  • Containment
  • Frequency
  • Fast Near
  • Vowels
  • Consonants
  • Alphas
  • Numerics
New Fuzzy Algorithms
  • N-Gram
  • Jaro Distance
  • Jaro-Winkler Distance
  • Longest Common Substring
  • Jaccard Index
  • Dices Coefficient
  • Overlap Coefficient
  • Needleman-Wunsch
  • Smith-Waterman-Gotoh
  • MD Keyboard
Integrated into SSIS component

No need to shell out of SSIS to file system


Matchcode Component Types

MatchUp Object V3 MatchUp Object V2 Legacy (DTAPI)
Existing 33 Component types + New:
  • Date (days)
  • Numeric (integer unit)
  • Proximity (miles)
 Existing 33 Component types Existing 33 Component types


Expanded Interfaces and Methods

MatchUp Object V3 MatchUp Object V2 Legacy (DTAPI)
New Interface
  • MatchcodeList
Easier to develop dynamic Applications for selecting a matchcode
  • SetPathToMatchUpFiles
  • InitializeDataFiles
  • GetInitializeErrorString
  • GetMatchcodeCount
  • GetMatchcodeName
New Methods

GetResults – conforms to other Melissa Data products for easy integration

  • GetNearDbl (component)
  • SetNearDbl (component)
  • GetDescription (matchcode)
  • SetDescription (matchcode)
  • GetNGram (matchcode)
  • SetNGram (matchcode)
  • RenameMatchcode
  • DeleteMatchcode
 GetStatusCode and GetCombinations have been deprecated GetStatusCode and GetCombinations have been deprecated


Distributed Libraries

MatchUp Object V3 MatchUp Object V2 Legacy (DTAPI)
  • 32-bit windows dll, COM
  • 64-bit windows dll, COM
  • 32-bit *nix .so
  • 64-bit *nix .so
  • Interface wrappers – multiple languages,
  • Conform to other Melissa Data products for
  • Easy integration
  • SSIS Component (rapid development)
  • 32-bit windows dll, COM
  • 64-bit windows dll, COM
  • 32-bit *nix .so
  • 64-bit *nix .so
  • 32-bit windows dll
SQL specific
  • Single library required
  • 32-bit User Defined Fuctions
  • 32-bit Extended Stored Procedures
  • 64-bit User Defined Fuctions
  • 64-bit Extended Stored Procedures
  • CLR interface functions
  • Triggers
SQL specific
  • Single library required
  • 32-bit UDFs and _xps
  • 64-bit UDFs and _xps
SQL specific
  • Separate libraries needed to be maintained
  • 32-bit UDFs and _xps


Data Files

MatchUp Object V3 MatchUp Object V2 Legacy (DTAPI)
mdMatchUp.dat

Existing data files have been rolled into a single data file

mdMatchUp.cfg

Editable override for .dat file allows for streamlined data file updates

mdMatchUp.dat

Existing data files have been rolled into a single data file

mdMatchUp.cfg

Editable override for .dat file allows for streamlined data file updates

*.dbf
Automatic install of data files to User location Preventing UAC issues


Help

MatchUp Object V3 MatchUp Object V2 Legacy (DTAPI)
.pdf .pdf *.chm
Direct links to WebHelp – allowing for up to date documentation
Retrieved from "http://wiki.melissadata.com/index.php?title=MatchUp_Object:FAQ:Feature_Comparison&oldid=2212"