Difference between revisions of "API:FAQ:Capabilities"

From Melissa Data Wiki
Jump to navigation Jump to search
 
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Custom TOC}}
==[[API:FAQ:Capabilities:Name Standardization|File & Name Standardization]]==
==File & Name Standardization==
*[[API:FAQ:Capabilities:Name Standardization#Input Consolidation|Input Consolidation]]
===Explain in detail how your tool consolidates several different input files with different file formats into single output file format.===
*[[API:FAQ:Capabilities:Name Standardization#Input Parsing|Input Parsing]]
The Melissa Data APIs are essentially blind to the data source – you control the file handling, allowing for the greatest flexibility to access (and process) data in any format or structure. Using native plugins for ETL tools such as SSIS or Pentaho Data Integration, the Data Quality Components allow cleansing of most file formats and outputting the format of choice.
*[[API:FAQ:Capabilities:Name Standardization#Name Record Splitting|Name Record Splitting]]
*[[API:FAQ:Capabilities:Name Standardization#Name Record Splitting and Parsing|Name Record Splitting and Parsing]]
*[[API:FAQ:Capabilities:Name Standardization#Search and Replace Functionality|Search and Replace Functionality]]
*[[API:FAQ:Capabilities:Name Standardization#Inconsistent Name Standardization|Inconsistent Name Standardization]]
*[[API:FAQ:Capabilities:Name Standardization#Free Formatted Data Fields|Free Formatted Data Fields]]
*[[API:FAQ:Capabilities:Name Standardization#Matching Standards and Alternative Spellings/Nicknames|Matching Standards and Alternative Spellings/Nicknames]]




===Explain in detail how your tool parses input names into pre name, first name, middle name, last name and post name and sends the data to individual fields.===
==[[API:FAQ:Capabilities:Address Standardization|Address Standardization (Online/Batch)]]==
When a Full Name or Multiple Names are passed into Name Object it first determines the gender of the first-names from a lookup table and then parses the specific name components as individual output properties using proprietary logic. Name Object will parse names into all the individual components. Incoming data can be in varied formats and patterns (Mr John Smith; Smith, John; Mr J L Smith Sr: etc., as well as dual names (Mr and Mrs John Smith). There are more than 190,00 first and last names from the US Census in the Name Object.
*[[API:FAQ:Capabilities:Address Standardization#Service/DPV/GeoCoding Updates|Service/DPV/GeoCoding Updates]]
*[[API:FAQ:Capabilities:Address Standardization#GeoCoding Data Source and Information Type|GeoCoding Data Source and Information Type]]
*[[API:FAQ:Capabilities:Address Standardization#NCOALink and LACSLink Features and Updates|NCOALink and LACSLink Features and Updates]]
*[[API:FAQ:Capabilities:Address Standardization#Address Scrubbing Online/Batch|Address Scrubbing Online/Batch]]
*[[API:FAQ:Capabilities:Address Standardization#Undeliverable Address Identification/Scrubbing|Undeliverable Address Identification/Scrubbing]]
*[[API:FAQ:Capabilities:Address Standardization#Vanity Address Identification/Scrubbing|Vanity Address Identification/Scrubbing]]
*[[API:FAQ:Capabilities:Address Standardization#Dual Address Lines|Dual Address Lines]]
*[[API:FAQ:Capabilities:Address Standardization#Address Line Swapping|Address Line Swapping]]
*[[API:FAQ:Capabilities:Address Standardization#ZIP Move and eLOT Features|ZIP Move and eLOT Features]]
*[[API:FAQ:Capabilities:Address Standardization#Assigning Latitude, Longitude, Census Track, FIPS Code|Assigning Latitude, Longitude, Census Track, FIPS Code]]
*[[API:FAQ:Capabilities:Address Standardization#Level of GeoCoding Options|Level of GeoCoding Options]]
*[[API:FAQ:Capabilities:Address Standardization#Local Municipal Tax Support|Local Municipal Tax Support]]
*[[API:FAQ:Capabilities:Address Standardization#2010 Census Tract Change Support and Existing Census Tract Maintenance|2010 Census Tract Change Support and Existing Census Tract Maintenance]]
*[[API:FAQ:Capabilities:Address Standardization#Suggestion List Support|Suggestion List Support]]
*[[API:FAQ:Capabilities:Address Standardization#Natural Hazard and Fire Protection Classification Zones for Insurance Purposes|Natural Hazard and Fire Protection Classification Zones for Insurance Purposes]]




===Explain in detail how your tool splits combined names from one record into two separate records.===
==[[API:FAQ:Capabilities:Matching|Matching/Householding/De-duping]]==
Name Object has a built-in list of words that connect names (“and,” “or,” “&,” etc.). It is the presence of these connectors that tell the object that a dual name may exist in the input full name string.
*[[API:FAQ:Capabilities:Matching#Matching Solutions|Matching Solutions]]
*[[API:FAQ:Capabilities:Matching#Suppport for De-duping, Matching Rules, Householding|Suppport for De-duping, Matching Rules, Householding]]
*[[API:FAQ:Capabilities:Matching#Matching Criteria for Householding|Matching Criteria for Householding]]
*[[API:FAQ:Capabilities:Matching#Household IDs and Unique Customer Records|Household IDs and Unique Customer Records]]




===If a file contains a name field with a “Mr. and Mrs. Tom Jones,” explain how your tool splits these into two separate records (e.g. One record for Mr. Tom Jones and a second record for Mrs. Tom Jones).===
==[[API:FAQ:Capabilities:Architecture|Architecture]]==
The respective parsed names would be split into these properties, one set per name.
*[[API:FAQ:Capabilities:Architecture#Logical and Physical Architecture Design|Logical and Physical Architecture Design]]
*[[API:FAQ:Capabilities:Architecture#Application Language Support|Application Language Support]]
*[[API:FAQ:Capabilities:Architecture#3rd Party Software Requirements|3rd Party Software Requirements]]
*[[API:FAQ:Capabilities:Architecture#Required Application Platforms|Required Application Platforms]]
*[[API:FAQ:Capabilities:Architecture#Required/Supported DBMS Platforms|Required/Supported DBMS Platforms]]
*[[API:FAQ:Capabilities:Architecture#Required/Supported Operating Systems|Required/Supported Operating Systems]]


Results for name ‘Mr. and Mrs. Tom Jones’:
{|
|-
|Prefix: Mr.
|Prefix2: Mrs.
|-
|First Name: Tom
|First Name2: Tom
|-
|Middle Name:
|Middle Name2:
|-
|Last Name: Jones
|Last Name2: Jones
|-
|Suffix:
|Suffix2:
|-
|Gender: M
|Gender2: F
|}


==[[API:FAQ:Capabilities:Integration|Integration]]==
*[[API:FAQ:Capabilities:Integration#Integration API's and Messaging Protocols|Integration API's and Messaging Protocols]]
*[[API:FAQ:Capabilities:Integration#Functionality|Functionality]]


==[[API:FAQ:Capabilities:Configuration|Configuration]]==
*[[API:FAQ:Capabilities:Configuration#Configuration of Business Rules for Matching|Configuration of Business Rules for Matching]]
*[[API:FAQ:Capabilities:Configuration#Required Development Tools|Required Development Tools]]




[[Category:API]]
[[Category:API]]
[[Category:FAQ]]
[[Category:Data Quality Suite]]
[[Category:Data Quality Suite]]
[[Category:Reference]]
[[Category:Reference]]

Latest revision as of 21:42, 12 June 2014

File & Name Standardization


Address Standardization (Online/Batch)


Matching/Householding/De-duping


Architecture


Integration


Configuration

Retrieved from "http://wiki.melissadata.com/index.php?title=API:FAQ:Capabilities&oldid=3953"