Search results

• MatchUp Object:Interfaces
  ==Interface Overview== ===[[MatchUp Object:Read-Write Interface|Read-Write Interface]]===
  2 KB (336 words) - 22:52, 21 July 2015
• MatchUp Object:Reference
  [[MatchUp Object|← MatchUp Object]] |Image=[[File:MediumTile_MatchUp.png|link=MatchUp Object]]
  2 KB (238 words) - 21:40, 2 October 2015
• MatchUp Object:Read-Write:Functions
  This is a master list of the functions in the Read-Write deduper interface. ==[[MatchUp Object:Read-Write:Initialization|Initialize the Read-Write Interface]]==
  4 KB (438 words) - 17:07, 6 August 2015
• MatchUp Object:Matchcode:Mapping Information
  ...ype tells you the data type which will be used to match records, while the matchcode mapping tells the API the format of the incoming data. ...rmation from a matchcode and dynamically create the mappings based on that information.
  2 KB (265 words) - 18:39, 29 July 2015
• MatchUp Object:Matchcode:Functions
  This is a master list of the functions in the Matchcode interface. ==[[MatchUp Object:Matchcode:Initialization|Initialize MatchUp Object]]==
  6 KB (746 words) - 21:47, 19 December 2016
• MatchUp Object:Read-Write:Mapping
  ...atabase records, the application must supply the Read-Write interface with information about what sort of data it will be handling. {{ Object Syntax
  3 KB (385 words) - 20:26, 5 August 2015
• MatchUp Object:Incremental:Functions
  This is a master list of the functions in the Incremental deduper interface. ==[[MatchUp Object:Incremental:Initialization|Initialize the Incremental Interface]]==
  5 KB (531 words) - 16:55, 28 October 2015
• MatchUp Object:Read-Write Interface
  ...cord, 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: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:Read-Write:Retrieval
  ...ion cycle through each record processed and return output unique/duplicate information. ...nnot be called until after the application has called the [[MatchUp Object:Read-Write:Processing#Process|Process]] function.
  5 KB (627 words) - 18:39, 7 August 2015
• MatchUp Object:Incremental:Order of Operations
  These are the basic steps of a typical implementation of the Incremental interface. #Initialize the Incremental interface.
  9 KB (1,347 words) - 21:45, 19 December 2016
• MatchUp Object:Hybrid:Order of Operations
  Using the Hybrid interface allows for greater flexibility than the other interfaces, as it gives you m These are the basic steps of a typical implementation of the Hybrid interface.
  7 KB (1,116 words) - 21:57, 8 March 2019
• MatchUp Object:Read-Write:Initialization
  The following functions prepare the Read/Write interface for use and link it to its ...ts a string value containing the path to the folder containing the MatchUp Read-Write data files. It must be called before calling the [[#InitializeDataFil
  11 KB (1,478 words) - 21:47, 19 December 2016
• MatchUp Object:Matchcode:Order of Operations
  ...ated but there are many options that must be considered for matchcodes and matchcode components. These are the basic steps of a typical implementation of the Matchcode interface.
  11 KB (1,507 words) - 21:57, 19 December 2016
• MatchUp Object:Incremental Deduping
  ...and sends the specific information (ZIP/PC, Name, Address, etc) to MatchUp Object. #Optionally, the application can tell MatchUp Object to add this record to its database for consideration in future comparisons.
  4 KB (602 words) - 18:43, 25 November 2014
• Tutorial:Matchcodes
  ...truct a "match key," a simplified string of characters that represents the information within the record, enough to determine if the given records is unique or a ...on on how to use the Matchcode Editor, see the [[Tutorial:Matchcode Editor|Matchcode Editor]] page.
  19 KB (2,967 words) - 23:13, 14 August 2012
• Pentaho/Contact Zone:MatchUp:Matchcodes
  ...between two records. A match found using any one of the combinations in a matchcode is considered a match. Programmers may think in terms of a series of OR con MatchUp allows up to 16 different combinations of components per matchcode.
  19 KB (2,924 words) - 20:49, 11 January 2017
• Pentaho:MatchUp:Matchcodes
  ...between two records. A match found using any one of the combinations in a matchcode is considered a match. Programmers may think in terms of a series of OR con MatchUp allows up to 16 different combinations of components per matchcode.
  19 KB (2,918 words) - 22:06, 15 June 2015
• Contact Zone:MatchUp:Matchcodes
  ...between two records. A match found using any one of the combinations in a matchcode is considered a match. Programmers may think in terms of a series of OR con MatchUp allows up to 16 different combinations of components per matchcode.
  20 KB (3,075 words) - 00:32, 5 January 2017
• MatchUp Object:FAQ
  [[MatchUp Object|← MatchUp Object]] ===What is the MatchUp Object?===
  28 KB (4,493 words) - 00:45, 26 March 2022

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