Difference between revisions of "API:FAQ:Capabilities"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
==File & Name Standardization== | ==[[FAQ:API Capabilities:Name Standardization|File & Name Standardization]]== | ||
*Input Consolidation | |||
*Input Parsing | |||
*Name Record Splitting | |||
*Name Record Splitting and Parsing | |||
*Search and Replace Functionality | |||
*Inconsistent Name Standardization | |||
*Free Formatted Data Fields | |||
*Matching Standards and Alternative Spellings/Nicknames | |||
=== | ==[[FAQ:API Capabilities:Address Standardization|Address Standardization (Online/Batch)]]== | ||
*Service/DPV/GeoCoding Updates | |||
*GeoCoding Data Source and Information Type | |||
*NCOALink and LACSLink Features and Updates | |||
*Address Scrubbing Online/Batch | |||
*Undeliverable Address Identification/Scrubbing | |||
*Vanity Address Identification/Scrubbing | |||
*Dual Address Lines | |||
*Address Line Swapping | |||
*ZIP Move and eLOT Features | |||
*Assigning Latitude, Longitude, Census Track, FIPS Code | |||
*Level of GeoCoding Options | |||
*Local Municipal Tax Support | |||
*2010 Census Tract Change Support and Existing Census Tract Maintenance | |||
*Suggestion List Support | |||
*Natural Hazard and Fire Protection Classification Zones for Insurance Purposes. | |||
== | ==[[FAQ:API Capabilities:Matching|Matching/Householding/De-duping]]== | ||
*Matching Solutions | |||
*Suppport for De-duping, Matching Rules, Householding | |||
*Matching Criteria for Householding | |||
*Household IDs and Unique Customer Records | |||
=== | ==[[FAQ:API Capabilities:Architecture|Architecture]]== | ||
*Logical and Physical Architecture Design | |||
*Application Language Support | |||
*3rd Party Software Requirements | |||
*Required Application Platforms | |||
*Required/Supported DBMS Platforms | |||
*Required/Supported Operating Systems | |||
==[[FAQ:API Capabilities:Integration|Integration]]== | |||
*Integration API's | |||
*Messaging Protocols | |||
*Functionality | |||
==[[FAQ:API Capabilities:Configuration|Configuration]]== | |||
== | *[[FAQ:API Capabilities:Configuration#1|Configuration of Business Rules for Matching]] | ||
*Required Development Tools | |||
Revision as of 19:02, 31 July 2013
File & Name Standardization
- Input Consolidation
- Input Parsing
- Name Record Splitting
- Name Record Splitting and Parsing
- Search and Replace Functionality
- Inconsistent Name Standardization
- Free Formatted Data Fields
- Matching Standards and Alternative Spellings/Nicknames
Address Standardization (Online/Batch)
- Service/DPV/GeoCoding Updates
- GeoCoding Data Source and Information Type
- NCOALink and LACSLink Features and Updates
- Address Scrubbing Online/Batch
- Undeliverable Address Identification/Scrubbing
- Vanity Address Identification/Scrubbing
- Dual Address Lines
- Address Line Swapping
- ZIP Move and eLOT Features
- Assigning Latitude, Longitude, Census Track, FIPS Code
- Level of GeoCoding Options
- Local Municipal Tax Support
- 2010 Census Tract Change Support and Existing Census Tract Maintenance
- Suggestion List Support
- Natural Hazard and Fire Protection Classification Zones for Insurance Purposes.
Matching/Householding/De-duping
- Matching Solutions
- Suppport for De-duping, Matching Rules, Householding
- Matching Criteria for Householding
- Household IDs and Unique Customer Records
Architecture
- Logical and Physical Architecture Design
- Application Language Support
- 3rd Party Software Requirements
- Required Application Platforms
- Required/Supported DBMS Platforms
- Required/Supported Operating Systems
Integration
- Integration API's
- Messaging Protocols
- Functionality
Configuration
- Configuration of Business Rules for Matching
- Required Development Tools