Search results

Page title matches

• MatchUp Object:Read/Write Deduping
  ...ach record, along with additional deduplication information, from the Read/Write deduper. Read/Write deduping consists of the following steps:
  4 KB (693 words) - 18:43, 25 November 2014

Page text matches

• MatchUp Object:Deduping Methods
  ==[[MatchUp Object:Incremental Deduping|Incremental Deduping]]== ==[[MatchUp Object:Read/Write Deduping|Read/Write Deduping]]==
  872 bytes (123 words) - 18:45, 25 November 2014
• MatchUp Object:Read-Write:Processing
  ...no longer add more records to the key file with the [[MatchUp Object:Read-Write:Match Key#WriteRecord|WriteRecord]] function. ...#WriteRecord|WriteRecord]] function and passes them through the Read-Write deduping logic to determine which are unique, which have duplicates, and which are d
  711 bytes (92 words) - 23:44, 27 July 2015
• MatchUp Object:Basics
  ;[[MatchUp Object:Incremental Deduping|Incremental Deduping]] ;[[MatchUp Object:Read/Write Deduping|Read/Write Deduping]]
  1 KB (197 words) - 18:44, 25 November 2014
• MatchUp Object:Read-Write Interface
  ...ach record, along with additional deduplication information, from the Read/Write interface. Read/Write deduping consists of the following steps:
  2 KB (391 words) - 16:26, 24 July 2015
• MatchUp Object:Interfaces
  ===[[MatchUp Object:Read-Write Interface|Read-Write Interface]]=== The Read-Write Interface checks an entire list of records against itself, flagging unique
  2 KB (336 words) - 22:52, 21 July 2015
• MatchUp Object:Read/Write Deduping
  ...ach record, along with additional deduplication information, from the Read/Write deduper. Read/Write deduping consists of the following steps:
  4 KB (693 words) - 18:43, 25 November 2014
• MatchUp Object:Read-Write:Mapping
  ...match keys for the database records, the application must supply the Read-Write interface with information about what sort of data it will be handling. ...fields, especially if the application may be required to perform multiple deduping operations in a single session.
  3 KB (385 words) - 20:26, 5 August 2015
• MatchUp Object:Hybrid Interface
  ...own. It is up to the developer to maintain a list of match keys to use for deduping operations. This increases the flexibility of the Hybrid interface but at t The main advantage of Hybrid deduping is that it allows the developer to build smaller lists of match keys on the
  2 KB (388 words) - 17:24, 29 July 2015
• MatchUp Object:Read-Write:Order of Operations
  These are the basic steps of a typical implementation of the Read-Write Interface. #Initialize the Read-Write Interface.
  8 KB (1,272 words) - 18:43, 16 December 2016
• MatchUp Object:Hybrid Deduping
  ...own. It is up to the developer to maintain a list of match keys to use for deduping operations. This increases the flexibility of the Hybrid deduper but at the The main advantage of Hybrid deduping is that it allows the developer to build smaller lists of match keys on the
  4 KB (684 words) - 18:43, 25 November 2014
• MatchUp Object:Incremental Deduping
  ...existing customer. At any time, a calling program can pass the incremental deduping engine the contents of a record; the engine will then report as to whether Incremental deduping consists of the following steps:
  4 KB (602 words) - 18:43, 25 November 2014
• MatchUp Object:Read-Write:Initialization
  The following functions prepare the Read/Write interface for use and link it to its ...string value containing the path to the folder containing the MatchUp Read-Write data files. It must be called before calling the [[#InitializeDataFiles|Ini
  11 KB (1,478 words) - 21:47, 19 December 2016
• MatchUp Object:FAQ:Feature Comparison
  ==Deduping Engines== |Read-Write (batch, or full database(s))
  6 KB (740 words) - 17:54, 16 December 2016
• MatchUp Object:Hybrid:Order of Operations
  ...Hybrid interface requires the developer to maintain a list of keys for the deduping operation. In this example, the keys are stored in a text file generated on Each record is read from the database, converted to a match key and written to the text file.
  7 KB (1,116 words) - 21:57, 8 March 2019
• MatchUp Object:Incremental:Order of Operations
  #Read the record from the data source. #Write new records to the key file.
  9 KB (1,347 words) - 21:45, 19 December 2016
• MatchUp Object:Component Combinations
  ...or usage. In some cases, processing will be faster if the traditional Read-Write engine is selected because of First Component properties. These are:
  3 KB (485 words) - 22:48, 22 July 2015
• MatchUp Object:Matchcode Mapping
  All three of the MatchUp Object deduping interfaces (Incremental, Read/Write and Hybrid) have an AddMapping function. This is used to create mappings fo
  7 KB (1,039 words) - 18:06, 23 November 2015
• FAQ:MatchUp Software
  ..., and many more specific instructions on how to read input data and how to write the output data - all which may be unique to this setup. ...matchcode, extracted from each record and is used to compare records when deduping.
  15 KB (2,607 words) - 17:14, 25 September 2017
• MatchUp Object:FAQ
  ...pplication. Also, when using the wrappers in the Interfaces folder, please read the readmes for each wrapper you are using as they may contain changes to t :Yes, if custom development or real time deduping isn’t what you need, MatchUp is also available in a Windows standalone ve
  28 KB (4,493 words) - 00:45, 26 March 2022
• MatchUp Hub:Environment
  ...base, it produces a matchkey for each record, sorts the keys for efficient deduping, and for some distributions, such as the ETL solutions, must keep track of ...on to a fast, local drive with plenty of writable disk space and full read write permissions.
  9 KB (1,361 words) - 17:35, 22 February 2019

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)