Table of Contents

Search

  1. Preface
  2. Introduction
  3. Program Design
  4. SSA-NAME3 Functions
  5. Language Specific Guidelines
  6. Controls
  7. Advanced Controls
  8. Address Standardization
  9. ASM Workbench

SSA-NAME3 API Reference Guide

SSA-NAME3 API Reference Guide

Retrieving Address Fields

Retrieving Address Fields

After parsing or validation, individual address fields are available for collection as part of a "suggestion". Suggestion 0 always holds the parsed fields. Suggestions numbered 1 and above hold the validated address fields.
Individual fields are retrieved one by one using
ssan3_addr_get_field_idx
by nominating the suggestion index and field index. As some fields may be missing, only those fields that have a non-zero length (as determined by calling
ssan3_addr_parse
or
ssan3_addr_get_field_info
) should be retrieved.
After validation, a field may be retrieved with
ssan3_addr_get_field
. This API is similar to
ssan3_addr_get_field_idx
but returns two extra codes that describe how the particular field matched the validation data (
val_status
) and whether or not it was changed by the validation process (
val_mods
). Refer below table for
val_status
and
val_mods
for ASM using AddressDoctor v4:
val_status
Meaning
0
Empty
1
Not found
2
Not Checked (no reference data or no chance of success)
3
Matched with errors
4
Matched without errors
val_mods
Meaning
0
Empty
1
Not checked
2
Not checked but standardized
3
Checked and corrected (changed or inserted)
4
Validated, but changed (synonyms, old names)
5
Validated, but standardized
6
Validated and unchanged
Refer below table for
val_status
and
val_mods
for ASM using AddressDoctor v5:
val_status
Meaning
0
Empty
1
Not found
2
Not checked (no reference data)
3
Wrong - Set by validation only
4
Match with errors in this element
5
Match with changes
6
Match without errors
val_mods
Meaning
0
Empty
1
Not validated and not changed
2
Not validated bus standardized
3
Validated but not changed due to invalid input
4
Validated but not changed due to lack of reference data
5
Validated but not changed due to multiple matches
6
Validated and changed by eliminating the input value
7
Validated and changed due to correction based on reference data
8
Validated and changed by adding value based on reference data
9
Validated, not changed, but delivery status not clear
12
Validated, verified but changed due to outdated name
13
Validated, verified but changed from exonym to official name
14
Validated, verified but changed due to standardization based on casing or language
15
Validated, verified and not changed due to perfect match

0 COMMENTS

We’d like to hear from you!