MatchUp Object:Deduping Methods: Difference between revisions
Jump to navigation
Jump to search
Created page with "<!--__FORCETOC__--> {{CustomTOC}} MatchUp offers three methods of operation: ===Incremental Deduping=== This operation is usually used for real-time data-entry validati..." |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[MatchUp Object|← MatchUp Object]] | |||
{{CustomTOC}} | {{CustomTOC}} | ||
MatchUp offers three methods of operation: | MatchUp offers three methods of operation: | ||
==[[MatchUp Object:Incremental Deduping|Incremental Deduping]]== | |||
This operation 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. | This operation 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. | ||
==[[MatchUp Object:Read/Write Deduping|Read/Write Deduping]]== | |||
This operation is usually used for processing full lists, much in the same what that MatchUp for Windows does. | This operation is usually used for processing full lists, much in the same what that MatchUp for Windows does. | ||
==[[MatchUp Object:Hybrid Deduping|Hybrid Deduping]]== | |||
This operation is a cross between incremental deduping and read/write Deduping. The API is responsible for none of the data storage, which makes it appealing for some DBMS-oriented applications (using SQL Server, DB/2, Oracle, etc.). | This operation is a cross between incremental deduping and read/write Deduping. The API is responsible for none of the data storage, which makes it appealing for some DBMS-oriented applications (using SQL Server, DB/2, Oracle, etc.). | ||
[[Category:MatchUp Object]] | [[Category:MatchUp Object]] | ||
Latest revision as of 18:45, 25 November 2014
MatchUp offers three methods of operation:
Incremental Deduping
This operation 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.
Read/Write Deduping
This operation is usually used for processing full lists, much in the same what that MatchUp for Windows does.
Hybrid Deduping
This operation is a cross between incremental deduping and read/write Deduping. The API is responsible for none of the data storage, which makes it appealing for some DBMS-oriented applications (using SQL Server, DB/2, Oracle, etc.).