MatchUp Object:Incremental Interface - Revision history

Admin at 20:45, 28 July 2015

2015-07-28T20:45:17Z

← Older revision		Revision as of 20:45, 28 July 2015
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]]

Admin at 19:05, 28 July 2015

2015-07-28T19:05:56Z

← Older revision		Revision as of 19:05, 28 July 2015
Line 4:		Line 4:

	==Overview==		==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:
			#The program processes a record and sends the specific information (ZIP/PC, Name, Address, etc) to MatchUp Object.
			#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.
			#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 [[MatchUp Object:Incremental:Match Key#AddRecord\|AddRecord]] function as one, speeding up processing of large lists.


	[[Category:MatchUp Object]]		[[Category:MatchUp Object]]

Admin: Created page with "{{MatchUpObjectIncrementalNav}} {{CustomTOC}} ==Overview== Category:MatchUp Object"

2015-07-21T17:48:38Z

Created page with "{{MatchUpObjectIncrementalNav}} {{CustomTOC}} ==Overview== Category:MatchUp Object"

New page

{{MatchUpObjectIncrementalNav}}

{{CustomTOC}}

==Overview==

[[Category:MatchUp Object]]