|
|
| (97 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| {{ProductInfoWidget | | __NOTOC__ |
| |Logo=MD_MatchUp_256_v3.png | | {{ProductV2 |
| |ProductName=MatchUp Object
| | |ProductImage=[[File:TILE_API_MatchUpObject.png|link=]] |
| |ReleaseDate=July 2012
| | |ProductBody= |
| |CurrentBuild=2009
| | MatchUp® Object is an extremely fast and powerful programmer's tool that can be integrated into custom applications to eliminate duplicate records. |
| |SupportedPlatform=Microsoft Windows, Linux, Solaris SPARC, HP-UX, AIX
| | <br> |
| |SupportedLanguage=Visual Basic, C++, C | | This API is available for the following platforms: Windows®, Linux®, AIX and can be used with any programming language such as C#, Java, Python, C/C++. |
| |BodyText= | | <br> |
| }}
| | <br>Enterprise-Level and Performance Considerations: |
| {{CustomTOC}}
| | *[[MatchUp Hub]] |
| | | [[File:Request-free-demo.png|link=https://www.melissa.com/request-demo?product=wiki+matchup+object]] |
| MatchUp Object is an extremely fast and powerful programmer's tool that can be integrated into custom applications to eliminate duplicate records. Because merge/purge and data quality initiatives go hand in hand, the powerful features of this tool fulfill the needs of many companies. Reducing printing costs, increasing response rates, maintaining an efficient database, and achieving better quality data are just some of the many benefits of the merge/purge process.
| | |CurrentBody= |
| | | <h3>Current Build</h3> |
| ==Support== | | *[https://releasenotes.melissa.com/on-premise-api/matchup-object-global/ Build History] |
| *[[Best Practices]] | | <h3>Notices</h3> |
| | *[[MatchUp Object:Important|<span style="color:red; font-weight:bold;">Important Notice</span>]] |
| *[[Issues:MatchUp Object|Known Issues]] | | *[[Issues:MatchUp Object|Known Issues]] |
| | | *[[MatchUp Object:Converting Versions|Converting to V3]] |
| ===FAQ=== | | *[[Solaris 32/64 Bit GCC Deprecation Notice]] |
| *[[FAQ:API|API Related]] | | |EssentialsBody= |
| *[[FAQ:MatchUp Object|MatchUp Object]] | | <h3>Basics</h3> |
| | | *[[MatchUp Object:Basics|What can MatchUp Do?]] |
| <!--===Results Codes===--> | | *[[API:Best Practices|General API Best Practices]] |
| ==Tutorials==
| | *[[MatchUp Object:Best Practices|MatchUp Object Best Practices]] |
| *[http://www.melissadata.com/multimedia/videos/MatchUp-Demo-Video.wmv MatchUp Demo Video] | | *[[MatchUp Object:Matchcode Components|Matchcode Components]] |
| | | *[[MatchUp Object:Matchcode Mapping|Matchcode Mapping]] |
| ==Downloads==
| | *[[MatchUp Object:Deduping Methods|Deduping Methods]] |
| | | *[[MatchUp Object:Global Processing|Global Processing]] |
| ===Documentation=== | | *[[Data Coverage by Country|Data Coverage by Country]] |
| | <h3>FAQ</h3> |
| | *[[API:FAQ|API Related]] |
| | *[[API:FAQ:Capabilities|API Capabilities]] |
| | *[[MatchUp Object:FAQ|MatchUp Object]] |
| | *[[MatchUp Object:FAQ:Feature Comparison|MatchUp Feature Comparison]] |
| | *[[API:FAQ:Supported Platforms#MatchUp Object|Supported Platforms]] |
| | <h3>Tutorials</h3> |
| | *[https://www.youtube.com/watch?v=4erXP2V-wY0 MatchUp Demo Video] |
| | <h3>Advanced Concepts</h3> |
| | *[[MatchUp Object:Matchcode Combinations|Matchcode Combinations]] |
| | *[[MatchUp Object:Blank Field Matching|Blank Field Matching]] |
| | *[[MatchUp Object:Optimizing Matchcodes|Optimizing Matchcodes]] |
| | *[[MatchUp Object:Advanced Algorithms|Information on Advanced Algorithms]] |
| | <h3>[[Service Samples|Service Sample]]</h3> |
| | *[https://www.melissa.com/data-deduplication Try the service] |
| | |ReferenceBody= |
| | <h3>Documentation</h3> |
| *[[Media:DQT_API_MatchUp_QSG.pdf|MatchUp Object Quick Start Guide]] | | *[[Media:DQT_API_MatchUp_QSG.pdf|MatchUp Object Quick Start Guide]] |
| *[[Media:DQT_API_MatchUp_RG.pdf|MatchUp Object Reference Guide]] | | *[[MatchUp Object:Reference|MatchUp Object Online Reference]] |
| *[[Media:DQT_API_FactSheet.pdf|API Capabilities]] | | *[[MatchUp Object:Config Example|MatchUp Object mdMatchUp.cfg Example]] |
| | | *[[MatchUp Object:SQL-CLR:Basics|MatchUp Object SQL-CLR Online Reference]] |
| <!--===Sample Code===-->
| | <h3>Result Codes</h3> |
| ==Current Build==
| | *[[Result Code Details#MatchUp Object|MatchUp Object Result Codes]] |
| ===Build 2009===
| | <h3>Sample Code</h3> |
| ''Released July 2012''
| | *All sample code may be found on the [https://docs.melissa.com/on-premise-api/matchup-object-global/matchup-object-global-quickstart.html#sample-code Melissa Documentation] website. |
| | | }} |
| ;Important
| |
| *Please update to this version [http://www.melissadata.com/free-trials/matchup-merge-purge-duplicates.htm (Build 2009)] | |
| | |
| ;Environment
| |
| :MatchUp now uses the new Melissa Data license format and ENV variable name.
| |
| :Please call a sales representative at 1-800-MELISSA ext. 3 (1-800-635-4772 x3) for a valid license string. | |
| :MatchUp will also check for a valid license in the MD_LICENSE(Environment) variable. This allows you to modify the license without recompiling the project | |
| :The default installation path for the MatchUp data files is now "c:\ProgramData\Melissa DATA\MatchUP\" for newer operating systems. Please check your 'Common App Data' directory for older OSs, for example: it may be "c:\Documents and Settings\All Users\Application Data\Melissa DATA\MatchUP".
| |
| | |
| ;Matchcode Editor
| |
| :The Matchcode Editor has been redesigned. Existing matchcodes can still be read/edited/used for backwards compatibility. The new Matchcode Editor allows us to provide a common interface with the MatchUp SSIS component
| |
| | |
| ;Functionality Changes
| |
| :Removal of certain matchcode restrictions that were required in existing version. This allows users to use an Intersecting matching logic - meaning you can create matchcodes without a common first component, making it more flexible
| |
| :SQL Server Interface: There is now a set of CLR-based procedures. A seperate installer script is provided as an alternative to the _xp and UDF methods of interfacing the MatchUp library.
| |
| | |
| ;Interface Changes
| |
| :Naming conventions for Interface Wrappers have been changed/updated to use the same naming convention as other Melissa Data Objects
| |
| | |
| :;Added Matchcode Component types:
| |
| :*Date (days)
| |
| :*Numeric (integer unit)
| |
| :*Proximity (miles)
| |
| | |
| :These new types allow you to specify, as a component property, a range for which a match will be possible if the records being compared fall within the set range. There are also new Enumerations, Mapping Targets and Matchcode Mappings for these new component types.
| |
| | |
| :;Added addition 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
| |
| :*Double Metaphone
| |
| | |
| :;New Interface
| |
| :*mdMUMatchcodeList - allows the user to list available matchcodes
| |
| :*SetPathToMatchUpFiles()
| |
| :*InitializeDataFiles()
| |
| :*GetInitializeErrorString()
| |
| :*GetMatchcodeCount() - retrieves number of matchcodes.
| |
| :*GetMatchcodeName() - retrieves name of matchcode at specified position.
| |
| | |
| :;New Methods
| |
| :*GetResults() - retrieves matching result codes.
| |
| :*GetNearDbl() - retrieves Near setting (supercedes GetNear()).
| |
| :*SetNearDbl() - sets Near setting (supercedes SetNear()).
| |
| :*GetDescription() - retrieves a matchcodes user-specified description.
| |
| :*SetDescription() - sets a matchcodes user-specified description.
| |
| :*GetNGram() - retrieves a matchcodes n-gram setting.
| |
| :*SetNGram() - sets a matchcodes n-gram setting.
| |
| :*RenameMatchcode() - change a matchcode’s name.
| |
| :*DeleteMatchcode() - delete a matchcode.
| |
| | |
| :;Deprecated
| |
| :*GetStatusCode and GetCombinations have been deprecated as GetResults gives the user a single output property to retrieve this information.
| |
| | |
| ;Sample Code
| |
| :Previous examples have been changed, with GetStatusCode and GetCombintions being replaced by GetResults to reflect usage in retrieving ouput properties
| |
| :Hybrid examples have been added to most samples and interfaces
| |
| | |
| ===Build History===
| |
| *[[Build History:MatchUp Object|Build History]]
| |
|
| |
|
|
| |
|
| [[Category:API]] | | [[Category:API]] |
| [[Category:MatchUp Object]] | | [[Category:MatchUp Object]] |
