Difference between revisions of "MatchUp Object:Incremental Interface"

From Melissa Data Wiki
Jump to navigation Jump to search
 
Line 20: Line 20:
  
 
==Transaction-Based Processing==
 
==Transaction-Based Processing==
The Incremental interface of MatchUp Object features the option of using transaction-based operations on the historical database. This enables an application to process multiple calls to the [[MatchUp Object:Incremental:Match Key#AddRecord|AddRecord]] function as one, speeding up processing of large lists.
+
The Incremental interface of MatchUp Object features the option of using transaction-based operations on the historical database. This enables an application to process multiple calls to the [[MatchUp Object:Incremental:Key File#AddRecord|AddRecord]] function as one, speeding up processing of large lists.
  
  
 
[[Category:MatchUp Object]]
 
[[Category:MatchUp Object]]

Latest revision as of 20:45, 28 July 2015

← MatchUp Object Reference

MatchUp Object Incremental Interface Navigation
Overview
Order of Operations
Functions
Initialization
Mapping
Match Key
Comparison
Key File
Transaction



Overview

The Incremental interface is usually used for real-time data entry validation. For example, a call center data-entry system where an operator would like to determine whether or not the caller is an existing customer. At any time, a calling program can pass the Incremental interface the contents of a record; the interface will then report as to whether or not this record is a dupe, and if so, which record or records it matches.

Incremental deduping consists of the following steps:

  1. The program processes a record and sends the specific information (ZIP/PC, Name, Address, etc) to MatchUp Object.
  2. Based on previous records sent to the API, it reports whether or not the record from the first step matches any of these previous records.
  3. Optionally, the application can tell MatchUp Object to add this record to its database for consideration in future comparisons.

The Historical Database

The Incremental interface relies heavily on a historical database that it maintains.

The lifetime of this database is as long as necessary (seconds, days, even years). This database is constructed and maintained by MatchUp Object, so it can determine whether or not an incoming record matches other records fairly quickly.

Multi-User/Multi-Thread Considerations

The Incremental interface is unique in that multiple users or multiple processes can access the same historical database simultaneously. The API maintains a locking system to ensure that competing processes don't collide. In order for two processes to work in this fashion, the initialization function for each process must specify the same historical database (a.k.a. “key file”).

Transaction-Based Processing

The Incremental interface of MatchUp Object features the option of using transaction-based operations on the historical database. This enables an application to process multiple calls to the AddRecord function as one, speeding up processing of large lists.