MatchUp Object (Global)

Important Announcements

None

General Information

Release Frequency: Quarterly

Release Date: Monday of the last full work week of the month.

Next Release Date: January 27, 2025

• Important Notice
• Known Issues
• MatchUp Object:Converting Versions
• MatchUp Object:Best Practices
• MatchUp Object Quick Start Guide
• MatchUp Object Result Codes
• Support contact information: tech@melissa.com or 1-800-MELISSA (1-800-635-4772)

Build History

2024.Q4

Released on: October 23, 2024

MatchUp Object version 5169

Added

• None

Changed

• Database changes
  • Updated datafiles

Deprecated

• None

Removed

• None

Fixed

• None

Security

• None

2024.Q3

Released on: July 22, 2024

MatchUp Object version 5168

Added

• None

Changed

• None

Deprecated

• None

Removed

• None

Fixed

• None

Security

• None

2024.Q2

Released on: April 22, 2024

MatchUp Object version 5168

Added

• None

Changed

• Database changes
  • Updated datafiles

Deprecated

• None

Removed

• None

Fixed

• None

Security

• None

2024.Q1

Released on: January 22, 2024

MatchUp Object version 5167

Added

• None

Changed

• Database changes
  • Updated datafiles

Deprecated

• None

Removed

• None

Fixed

• MatchUp editor crash bug fix

Security

• None

2023.Q4

Released on: October 25, 2023

MatchUp Object version 5166

Added

• None

Changed

• Database changes

  • Updated - mdMatchup.sac

• Interface changes

  • mdMatchUp.cs renamed to mdMatchup_cSharpCode.cs

Deprecated

• None

Removed

• None

Fixed

• None

Security

• None

2023.Q3

Released on: July 25, 2023

MatchUp Object version 5159

Added

• None

Changed

• Library changes

  • This update will require a new library - mdGlobalParse.dll - to reside alongside mdMatchUp.dll in windows, and mdGlobalParse.so - to reside alongside mdMatchUp.so in linux.

• Database changes

  • Previously required mdGlobal* datafiles are now rolled up into a single file - mdMatchup.sac
  • mdMatchup.dat has been updated
  • icudt52l.dat is once again required

• Interface changes

  • We've changed our wrapper building process to make usage easier to build, maintain, and support. The following wrappers should be version\agnostic - eliminating minor version updates of languages from causing libraries to crash

  • Python: mdMatchup_pythoncode.py is the new wrapper which can be directly dropped into your python executable directory. Additional wrapper source code has been removed and the need to re-compile the wrapper has been eliminated.

  • Java : mdMatchUpJavaWrapper.cpp is now mdMatchupJavaWrapper.cpp

  • .NET : mdMatchup.cs has been updated to fix compatibility issues with various net framework versions.

  • Based on the current landscape of programming language, we are supporting CSharp (.NET Core), Java, C++ and Python. Perl, Ruby and PHP-windows have been removed.

Deprecated

• None

Removed

• mdGlobalAddr.* data files

Fixed

• None

Security

• None

2022.Q2

Released on: April 25, 2022

MatchUp Object version 5131

Added

• None

Changed

• gcc41 linux library is now compiled with gcc48
• Updated Global datafiles (Global MatchUp)

Deprecated

• None

Removed

• None

Fixed

• None

Security

• None

2022.Q1

Released on: January 24, 2022

MatchUp Object Version 5118

Added

• None

Changed

• Updated Global datafiles (Global MatchUp)

Deprecated

• None

Removed

• None

Fixed

• Fixed large file sorting issue in linux.

Security

• None

2021.Q4

Released on: October 25, 2021

MatchUp Object Version 5112

Maintenance build.

Added

• None

Changed

• Updated Global datafiles (Global MatchUp)

Deprecated

• None

Removed

• None

Fixed

• None

Security

• None

2021.Q3

Released on: August 03, 2021

MatchUp Object Version 5109

Added

• Countries added to Full Support Status: LU, PT. (Global MatchUp)

Changed

• Updated datafiles (Domestic MatchUp) for address pattern fix
• Updated Global datafiles. (Global MatchUp)
• Linux .sh scripts still require dos2unix.

Deprecated

• None

Removed

• None

Fixed

• None

Security

• None

2020.Q2

Released on: April 17, 2020

MatchUp Object Version 5083

Added

• None

Changed

• Updated Global datafiles. (Global MatchUp)

Deprecated

• None

Removed

• None

Fixed

• Fixed Keybuilding issue for Numerics only Fuzzy Algorithm

Security

• None

2020.Q1

Released on: January 17, 2020

MatchUp Object Version 5070

Added

• None

Changed

• Updated Global datafiles. (Global MatchUp)

Deprecated

• Deprecated linux/gcc34 library distribution and support

Removed

• None

Fixed

• Fixed Critical Global Keybuilding issue for Vietnam (unsupported) and France

Security

• None

2019.Q3

Released on: August 16, 2019

MatchUp Object Version 5060

Maintenance Build

Added

• None

Changed

• None

Deprecated

• None

Removed

• None

Fixed

• None

Security

• None

2019.Q2

Released on: May 17, 2019

MatchUp Object Version 5058

Maintenance Build

Added

• None

Changed

• None

Deprecated

• None

Removed

• None

Fixed

• None

Security

• None

2019.Q1

Released on: January 18, 2019

MatchUp Object Version 5058

Maintenance Build

Added

• None

Changed

• None

Deprecated

• None

Removed

• None

Fixed

• None

Security

• None

2018.Q4

Released on: October 17, 2018

MatchUp Object Version 5046

Added

• Countries added to Full Support Status: CZ, LI, ZA. (Global MatchUp)
• Added/Edited recommendations in documentation regarding advanced matchcode

Changed

• Improved CityStateZip splitting for non-standardized Canadian records.
• Improved support for viewing Matchcode Keys with extended characters.

Deprecated

• None

Removed

• None

Fixed

• None

Security

• None

2018.Q3

Released on: August 17, 2018

MatchUp Object Version 5046

Maintenance Build

Added

• None

Changed

• None

Deprecated

• None

Removed

• None

Fixed

• None

Security

• None

2018.Q2

Released on: April 13, 2018

MatchUp Object Version 5028

Maintenance Build

Added

• None

Changed

• None

Deprecated

• None

Removed

• None

Fixed

• None

Security

• None

2018.Q1

Released on: February 16, 2018

MatchUp Object Version 5023

Added

• Global Address Matching: LT, FI, PL, FR, SG added to full support status

Changed

• None

Deprecated

• None

Removed

• None

Fixed

• None

Security

• None

2017.Q4

Released on: November 17, 2017

MatchUp Object Version 5015

Added

• Global Address Matching: LT, FI, PL, FR, SG added to full support status

Changed

• Improved (Rural) Route processing
• Speed Optimizations
• Improved Territory support for UK Crown dependencies (Guernsey, Isle of Man, Jersey)

Deprecated

• None

Removed

• None

Fixed

• None

Security

• None

2017.Q3

Released on: September 15, 2017

MatchUp Object Version 5009

Added

• Countries added to Full Support Status: HR, IS, NO (Global)

Changed

• Country support for US Territories: AS, FM, GU, PW, MH, MP ,PR, VI (Domestic and Global)
• No new methods or properties.

Deprecated

• None

Removed

• None

Fixed

• None

Security

• None

2017.Q2

Released on: March 17, 2017

MatchUp Object Version 2929

Added

• SetEncoding() and SetMaximumCharacterSize() added to SQL-CLR installed functions

Changed

• MatchUp Object and Global MatchUp Object have been separated into two distinct products
• New Matchcode Component: Post Box - differences in functionality made a distinct Global component necessary.
• Legacy Global Matchcodes with PO Box will now appear as Post Box

Deprecated

• None

Removed

• Domestic matchcodes have been removed from the Global matchcode list

Fixed

• Global Address Matching: MX, DK, NZ, IE, SE added to full support status

Security

• None

2016.Q2

Released on: April 15, 2016

MatchUp Object Version 2768

Added

• Global Address Matching: CL, NL added to full support status

Changed

• None

Deprecated

• None

Removed

• Domestic matchcodes have been removed from the Global matchcode list

Fixed

• Multi-Thread bug fixed
• Minor bug fixes

Security

• None

2016.Q2

Released on: March 18, 2016

MatchUp Object Version 2768

Added

• Added Numeric & Date as members of the datatype list when creating global matchcode.
• Global Addr Matching: AT, AU, UK, CA, CH added to full support status

Changed

• Changed 'Global Address' matchcode: premise number now set to 'Both blank'

Deprecated

• None

Removed

• Domestic matchcodes have been removed from the Global matchcode list

Fixed

• Minor bug fixes. ie Company mc component start at Word(#)

Security

• None

2015.Q3

Released on: August 14, 2015

MatchUp Object Version 2628

• Object Compatibility Summary
  • Melissa Data has upgraded our windows compiler from Visual Studio 2008 to Visual Studio 2012. This means that the C++ 2012 Redistributable is required to be able to run the objects. This redistributable is installed by the setup. However, if you are manually copying over the libraries, you must first install the redistributable. You can find it in the extras/redist directory on the disc.

Added

• Added Fuzzy Algorithms

  • UTF-8 Near - It counts the number typos, ie character substitutions, differs from others in that it will account for character storage sizes due to different encoding.

• MatchUp is Going Global!

  • This version marks the beginning of integration of Global matching capabilities.
  • If you currently process UK data, or use a matchcode with UK components, do NOT update to this version! Global UK processing will be added next release.
  • Supported Global Countries: Germany

• New Matchcode Components

  • Postal Code - (Zip &/ plus 4) Complete postal code for a particular delivery point.
  • Premises Number - (Street Number) Alphanumeric indicator within premises field.
  • Double Dependent Locality - Smallest population center data element
  • Dependent Locality - (Urbanization) Smaller population center data element. Dependent on Locality.
  • Sub Administrative Area - (County) Smallest geographic data element.
  • Sub National Area - Arbitrary administrative region below that of the sovereign state.
  • Locality - (City) Most common population center data element.
  • Administrative Area - (State) Most common geographic data element.
  • Thoroughfare Leading Type - Leading thoroughfare type indicator within the Thoroughfare field.
  • Thoroughfare Pre-Directional - (Street Pre Direction) Prefix directional contained within the Thoroughfare field.
  • Thoroughfare Name - (Street Name) Name indicator within the Thoroughfare field
  • Thoroughfare Trailing Type - (Street Suffix) Trailing thoroughfare type indicator within the Thoroughfare field.
  • Thoroughfare Post-Directional - (Street Post Direction) Postfix directional contained within the Thoroughfare field.
  • Dependent Thoroughfare Pre-Directional - Prefix directional contained within the Dependent Thoroughfare field.
  • Dependent Thoroughfare Leading Type - Leading thoroughfare type indicator within the Dependent Thoroughfare field.
  • Dependent Thoroughfare Name - Name indicator within the Dependent Thoroughfare field
  • Dependent Thoroughfare Trailing Type - Trailing thoroughfare type indicator within the Dependent Thoroughfare field.
  • Dependent Thoroughfare Post-Directional - Postfix directional contained within the Dependent Thoroughfare field.

Changed

• Matchcode Editor

  • When creating a new matchcode, the Matchcode Editor will now prompt you to specify the type of matchcode you want to create - a domestic or global matchcode. This will cause matchup to dynamically populate the list of available matchcode component types, ensuring that you do not create a matchcode with global components that does not call our global address parsing engine.
  • When constructing a global matchcode, you must include a Country component, so the address parser knows how to parse the address - given the wide variety of international address patterns which differs from country to country.

• Interface Changes

  • New Methods
    • SetEncoding() - allows the user to define the input file encoded format and what the resultant format of the built keys will be.
    • SetMaximumCharacterSize() - accommodates UTF-8 input data. Since a single UTF-8 character can be up to 4 bytes long, the storage of the matchcode keys may need to be altered to accommodate this maximum size.

• Functionality Changes

  • GetMappingItemCount - With the addition of International Address processing, GetMappingItemCount will now return ((# of non-address mappings) + 8) instead of ((# of non-address mappings) + 3). AddMapping now allows 8 address lines instead of three, although you still are only required to call one AddMapping(ADDRESS) and one AddField(Address-data).

Deprecated

• None

Removed

• We have removed the following platforms AIX, HXUX and Solaris.
• We have removed all 32-bit libaries and respective source code.
• We have removed the 32-bit and 64-bit COM Objects.

Installing this version will not remove these legacy folders and files.

Fixed

• None

Security

• None

2015.Q2

Released on: April 17, 2015

MatchUp Object Version 2544

Added

• None

Changed

• None

Deprecated

• None

Removed

• None

Fixed

• Fixed a buffer overrun in the AddMapping method.

Security

• None

2014.Q3

Released on: September 12, 2014

MatchUp Object Version 2419

Added

• None

Changed

• Windows Libraries

  • Melissa Data has upgraded our windows compiler from Visual Studio 2008 to Visual Studio 2012. This means that the C++ 2012 Redistributable is required to be able to run the objects.

  • This redistributable is installed by the setup. However, if you are manually copying over the libraries, you must first install the redistributable. You can find it in the extras/redist directory on the disc.

• Interface Changes

  • NONE

Deprecated

• None

Removed

• None

Fixed

• Fixed a buffer overrun in the AddMapping method.

Security

• None

2014.Q2

Released on: July 18, 2014

MatchUp Object Version 2395

Added

• None

Changed

• Functionality Changes

  • Improved Highway and County pattern recognition.
  • Improved hyphenated last names (spaces around the hyphen).

  • Improved address pattern recognition for uncommon dual street suffix addresses.

  • eMail domain recognition now handles updated domains with or withour TLD (may require added entries to mdMatchUp.cfg).

    • Issues with Components with 'Short Empty:Both' and 'Fuzzy:Containment' resolved.

• Interface Changes

  • NONE

Deprecated

• None

Removed

• None

Fixed

• Jaro and Jaro-Winkler crash on certain 'component size/string size' ratio fixed.

Security

• None

2013.Q1

Released on: April 12, 2013

MatchUp Object Version 2154

Added

• None

Changed

• Interface Changes
  • SetReserved("UserInfoSize",""), users can use to override default userinfo size of 1024 bytes per record. Smaller numbers like "32" greatly reduce disk space requirements and processing times.

Deprecated

• None

Removed

• None

Fixed

• Fixed an issue when temporary sort files grew over 4GB (shown in very large processes)

Security

• None

2012.Q2

Released on: July 13, 2012

MatchUp Object Version 2009

Added

• 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.

Changed

• Environment

  • MatchUp now uses the new Melissa Data License Key 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 Key.
  • MatchUp will also check for a valid License Key in the MD_LICENSE(Environment) variable. This allows you to modify the License Key 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

  • 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

• 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

Deprecated

• GetStatusCode and GetCombinations have been deprecated as GetResults gives the user a single output property to retrieve this information.

Removed

• 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

Fixed

• Fixed an issue when temporary sort files grew over 4GB (shown in very large processes)

Security

• None

2009.Q3.1

Released on: August 13, 2009

MatchUp Object Version 1459

Added

• The MatchUp Object disc now includes all supported platforms:Linux, Windows, and Solaris, and AIX.
• The MatchcodeComponentType enums now have 'Comp' appended at the end of each label.
• The MatchcodeMappingType enumeration was named to MatchcodeMappingTarget. MatchcodeMappingTarget enums all have 'Type' appended at the end of each label.

Changed

• The SetUserInfo and GetUserInfo functions now work with 'const char ' data types rather than a 'void ' for all platforms/languages.
• Moved the enums into their own file mdMatchupEnums.h to make the Object more compatible with our other objects. In doing this, some enumerations were changed (see below).
• The ProgramStatus enum NoError has been renamed to ErrorNone.

Deprecated

• None

Removed

• Removed Set/GetSizeUserInfo functions, as there was no need for them anymore. The maximum size for the UserInfo string is 1024 bytes.

Fixed

• None

Security

• None

2009.Q3

Released on: July 16, 2009

MatchUp Object Version 1451

Added

• Initial public release
  • Multi Platform, new version, new interface, incompatible with legacy MatchUP API. Please refer to product page for details.

Changed

• None

Deprecated

• MatchUp API, DoubleTake API

Removed

• None

Fixed

• None

Security

• None

Past Announcements

Solaris 32/64 Bit GCC Deprecation Notice - April 01, 2015

Deprecation notice details can be found here.