Profiler Object:Result Codes

From Melissa Data Wiki
Jump to navigation Jump to search

← Profiler Object Reference

Profiler Object Interface Navigation
Object Information
Enumeration Listing and Parsing
Column Specification
Initiate Profiling
Data Input
Table-Based Statistics
Column-Based Statistics
Column-Based String Statistics
Column-Based Numeric Statistics
Column-Based Date/Time Statistics
Column-Based Name Statistics
Column-Based State/Province Statistics
Column-Based Zip/Postal Code Statistics
Column-Based Country Statistics
Column-Based Email Statistics
Column-Based Phone Statistics
Frequency Iterators
Column-Based Value Frequency Table Iteration
Column-Based Value Length Frequency Table Iteration
Column-Based Value Pattern Table Iteration
Column-Based Value Date/Time Table Iteration
Column-Based Value SoundEx Table Iteration
Column-Based Word Table Iteration
Column-Based Word Length Table Iteration
Result Codes
Profiler Object Result Codes
Result Codes

Result Code Use

Result codes are retrieved by the GetResults function. These codes will be available right after calling AddRecord(). You can evaluate these result codes as you enter the data, allowing you to do incremental profiling.

Melissa Data's products use a result code system to indicate data quality; the status and any errors. These result codes are four-character codes (two letters followed by two numbers), delimited by commas. Unlike other Melissa Data products, result codes in the Profiler Object are Column Specific. Currently, there are close to 50 possible results codes for Profiler Object alone.


An example returned result code string:

QS17, QS40

Instead of looking at multiple properties and methods to determine status, you can look at the output of the results parameter.

From this output you can determine that the column is:

Code Short Description Long Description
QS17 Trailing Spaces Value contains trailing spaces.
QS40 5-digit ZIP/Postal Code Zip/Postal Code value has 5-digit ZIP with no Plus 4.

Be sure to reference Profiler Object Result Codes for a list of Melissa Data's result codes.

Understanding the Code

To fully understand result codes, you need to know them. Knowing what codes are possible and what they indicate will be key in building an effective application. It is useful to know all the codes, but this does not necessarily mean you will use them all. Just because you have a toolbox, doesn't mean you will also try to use a screwdriver along with a hammer on a nail.

Results Codes Will Change. Code for It

Melissa Data is always innovating and adding new information and enrichments. You will not be able to know exactly what new codes may be introduced in the future, but we can still account for them. Always use the string.Contains() or an equivalent function when detecting for codes, so reordering and future additions will not affect your current code. Also, have all records that do not pass your filter become a “bad” record. This allows for future codes to be added without records being lost if you don't specifically filter for them.