Difference between revisions of "MatchUp Object"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{ProductInfoWidget | {{ProductInfoWidget | ||
|Logo=MD_MatchUp_256_v3.png | |||
|ProductName=MatchUp Object | |ProductName=MatchUp Object | ||
|ReleaseDate=July 2012 | |ReleaseDate=July 2012 | ||
Revision as of 22:27, 20 August 2012
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.
Support
FAQ
Tutorials
Downloads
Documentation
Current Build
Build 2009
Released July 2012
- Important
- Please update to this version (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