MatchUp Web Service:FAQ - Revision history

Admin at 20:12, 7 April 2017

2017-04-07T20:12:08Z

← Older revision		Revision as of 20:12, 7 April 2017
Line 36:		Line 36:
	;How long will Melissa Data store my data? How long do I have to retrieve the Results from a submitted job?		;How long will Melissa Data store my data? How long do I have to retrieve the Results from a submitted job?

	Our current policy for data storage life for customers using the MatchUp Web Service is monitored and manually determined by Melissa Database Administrators. Currently, life of transmitted data is set to 1 week. This means that when a SubmitJob request returns a JobID, you have 1 week to submit records and retrieve your output results. After this time your data will be destroyed ~~upon retrieval or~~ one week after the job was created.		Our current policy for data storage life for customers using the MatchUp Web Service is monitored and manually determined by Melissa Database Administrators. Currently, life of transmitted data is set to 1 week. This means that when a SubmitJob request returns a JobID, you have 1 week to submit records and retrieve your output results. After this time your data will be destroyed one week after the job was created.


	[[Category:FAQ]]		[[Category:FAQ]]
	[[Category:MatchUp Web Service]]		[[Category:MatchUp Web Service]]

Admin at 18:30, 7 April 2017

2017-04-07T18:30:30Z

← Older revision		Revision as of 18:30, 7 April 2017
Line 36:		Line 36:
	;How long will Melissa Data store my data? How long do I have to retrieve the Results from a submitted job?		;How long will Melissa Data store my data? How long do I have to retrieve the Results from a submitted job?

	Our current policy for data storage life for customers using the MatchUp Web Service is monitored and manually determined by Melissa Database Administrators. Currently, life of transmitted data is set to 1 week. This means that when a ~~job~~ returns ~~the status code that the job is completed~~, you have 1 week to retrieve your output results. ~~Your~~ data will be destroyed upon retrieval		Our current policy for data storage life for customers using the MatchUp Web Service is monitored and manually determined by Melissa Database Administrators. Currently, life of transmitted data is set to 1 week. This means that when a SubmitJob request returns a JobID, you have 1 week to submit records and retrieve your output results. After this time your data will be destroyed upon retrieval or one week after the job was created.
	or after ~~I week if not retrieved~~.


	[[Category:FAQ]]		[[Category:FAQ]]
	[[Category:MatchUp Web Service]]		[[Category:MatchUp Web Service]]

Admin at 18:11, 7 April 2017

2017-04-07T18:11:50Z

← Older revision		Revision as of 18:11, 7 April 2017
Line 31:		Line 31:

	The service is designed to accurately group records together and reflect how inexact records can fall into the same output group. But since the details of the matching rules are hidden, you can ignore the returned Hit Combination result codes and simply evaluate the initial status code (MS01, MS02 or MS03) to determine if a record is unique, or matched other records. Evaluating the returned Hit Combination result codes will give you a basic idea of the datatypes which resulted in the match. For more details, see [[MatchUp Web Service:Introduction#Matchcode Information\|Matchcode Information]].		The service is designed to accurately group records together and reflect how inexact records can fall into the same output group. But since the details of the matching rules are hidden, you can ignore the returned Hit Combination result codes and simply evaluate the initial status code (MS01, MS02 or MS03) to determine if a record is unique, or matched other records. Evaluating the returned Hit Combination result codes will give you a basic idea of the datatypes which resulted in the match. For more details, see [[MatchUp Web Service:Introduction#Matchcode Information\|Matchcode Information]].


			==Life of Transmitted Data==
			;How long will Melissa Data store my data? How long do I have to retrieve the Results from a submitted job?

			Our current policy for data storage life for customers using the MatchUp Web Service is monitored and manually determined by Melissa Database Administrators. Currently, life of transmitted data is set to 1 week. This means that when a job returns the status code that the job is completed, you have 1 week to retrieve your output results. Your data will be destroyed upon retrieval
			or after I week if not retrieved.


	[[Category:FAQ]]		[[Category:FAQ]]
	[[Category:MatchUp Web Service]]		[[Category:MatchUp Web Service]]

Admin at 16:58, 5 April 2017

2017-04-05T16:58:50Z

← Older revision		Revision as of 16:58, 5 April 2017
Line 30:		Line 30:
	;Why is the Service returning additional Results Codes with additional Matchcode Hit Combinations whose rules are hidden from me?		;Why is the Service returning additional Results Codes with additional Matchcode Hit Combinations whose rules are hidden from me?

	The service is designed to accurately group records together and reflect how inexact records can fall into the same output group. But since the matching rules are hidden, you ~~should~~ ignore the returned Hit Combination result codes and simply evaluate the initial status code (MS01, MS02 or MS03) to determine if a record is unique, or matched other records.		The service is designed to accurately group records together and reflect how inexact records can fall into the same output group. But since the details of the matching rules are hidden, you can ignore the returned Hit Combination result codes and simply evaluate the initial status code (MS01, MS02 or MS03) to determine if a record is unique, or matched other records. Evaluating the returned Hit Combination result codes will give you a basic idea of the datatypes which resulted in the match. For more details, see [[MatchUp Web Service:Introduction#Matchcode Information\|Matchcode Information]].


	[[Category:FAQ]]		[[Category:FAQ]]
	[[Category:MatchUp Web Service]]		[[Category:MatchUp Web Service]]

Admin at 21:13, 3 April 2017

2017-04-03T21:13:56Z

← Older revision		Revision as of 21:13, 3 April 2017
Line 19:		Line 19:

	At this time, the matching strategies available to the service cannot be edited nor can custom matchcodes be created for use. For a list of available matching strategies and respective input fields required to use each matchcode, see the GetMatchcodeList request and response section of the documentation. While we always recommend starting out with basic matching strategies, please reach out to us with your suggestions for matchcode (as well as other features) additions you would like to see.		At this time, the matching strategies available to the service cannot be edited nor can custom matchcodes be created for use. For a list of available matching strategies and respective input fields required to use each matchcode, see the GetMatchcodeList request and response section of the documentation. While we always recommend starting out with basic matching strategies, please reach out to us with your suggestions for matchcode (as well as other features) additions you would like to see.


			==Matchcode Evaluation==
			;What is my Selected MatchCode evaluating, and how?

			Unlike our other MatchUp solutions, the MatchUp Web Service does not give you the flexibility to create or configure your own matching rules. Therefore the details (matchcode settings) are hidden from you. Whereas the matchcodes for the other distributed solutions are by default designed as baseline matching strategies and are 'tight' in their logic, the MatchUp Web Service, in most cases uses additional advanced matchcode options to perform more advanced matching and provide more practical duplicates. For example, 'Address' based matchcodes evaluate records to the 'Suite' level (tighter than other MatchUp solutions), while 'Fuzzy Name' based matchcodes are configured with more advanced options. To see the required fields (necessary datatypes) used for each matchcode, see [[MatchUp Web Service:GetMatchcodeList\|GetMatchcodeList]].


			==Hidden Matchcode Hit Combinations==
			;Why is the Service returning additional Results Codes with additional Matchcode Hit Combinations whose rules are hidden from me?

			The service is designed to accurately group records together and reflect how inexact records can fall into the same output group. But since the matching rules are hidden, you should ignore the returned Hit Combination result codes and simply evaluate the initial status code (MS01, MS02 or MS03) to determine if a record is unique, or matched other records.


	[[Category:FAQ]]		[[Category:FAQ]]
	[[Category:MatchUp Web Service]]		[[Category:MatchUp Web Service]]

Admin at 20:06, 28 March 2017

2017-03-28T20:06:02Z

← Older revision		Revision as of 20:06, 28 March 2017
Line 18:		Line 18:
	;Are available matching strategies flexible? Can I create my own matchcodes?		;Are available matching strategies flexible? Can I create my own matchcodes?

	At this time, the matching strategies available to the service cannot be edited nor can custom matchcodes be created for use. For a list of available matching strategies and respective input fields required to use each matchcode, see the GetMatchcodeList request and response section of the documentation. While we always recommend starting out with basic matching strategies, please reach out to ~~use~~ with your suggestions for matchcode (as well as other features) additions you would like to see.		At this time, the matching strategies available to the service cannot be edited nor can custom matchcodes be created for use. For a list of available matching strategies and respective input fields required to use each matchcode, see the GetMatchcodeList request and response section of the documentation. While we always recommend starting out with basic matching strategies, please reach out to us with your suggestions for matchcode (as well as other features) additions you would like to see.


	[[Category:FAQ]]		[[Category:FAQ]]
	[[Category:MatchUp Web Service]]		[[Category:MatchUp Web Service]]

Admin: Created page with "← MatchUp Web Service {{CustomTOC}} ==Getting Started Process== ;What is the process to get started with using MatchUp Web Service? #Create a Mat..."

2017-03-28T15:25:49Z

Created page with "← MatchUp Web Service {{CustomTOC}} ==Getting Started Process== ;What is the process to get started with using MatchUp Web Service? #Create a Mat..."

New page

[[MatchUp Web Service|← MatchUp Web Service]]
{{CustomTOC}}
==Getting Started Process==
;What is the process to get started with using MatchUp Web Service?

#Create a MatchUp Web Service account with your Melissa Data sales representative. You will be assigned a UserID for your account.
#Once you have a valid MatchUp account, you can use the service endpoints here to create a job, submit records, and retrieve the results.
#Unlike our deduping solutions from Melissa Data, there are no libraries to register or data files to install, making the ‘get started’ process very easy.

==Result Formatting and Properties==
;How are retrieved results formatted? What properties are available?

Like other MatchUp implementations, the service returns an Output Status, Dupe Group, Count, and Matchkey for each record. You can use these properties for proprietary decision making such as linking and consolidating duplicate records, updating a master database, or simply removing duplicate records.

==Matching Strategy Flexibility and Custom Matchcodes==
;Are available matching strategies flexible? Can I create my own matchcodes?

At this time, the matching strategies available to the service cannot be edited nor can custom matchcodes be created for use. For a list of available matching strategies and respective input fields required to use each matchcode, see the GetMatchcodeList request and response section of the documentation. While we always recommend starting out with basic matching strategies, please reach out to use with your suggestions for matchcode (as well as other features) additions you would like to see.

[[Category:FAQ]]
[[Category:MatchUp Web Service]]