Table of Contents

Search

  1. Preface
  2. Introduction
  3. The Design Issues
  4. Standard Population Choices
  5. Parsing, Standardization and Cleaning
  6. Customer Identification Systems
  7. Fraud and Intelligence Systems
  8. Marketing Systems
  9. Simple Search
  10. Summary

Application and Database Design Guide

Application and Database Design Guide

Simple Search Application Design - An Example

Simple Search Application Design - An Example

You can create a simple search application that searches on different fields and different field combinations.
The example assumes the customer is licensed to use the USA population and has a CUSTOMER database table with the following columns:
Name
Datatype
Length
CUSTOMER_ID
NUMBER
10
CUSTOMER_NAME
VARCHAR
32
CUSTOMER_ADDRESS
VARCHAR
32
CUSTOMER _ORG
VARCHAR
32
To provide search capability on customer names, an application may create SSA-NAME3 keys for the data from CUSTOMER_NAME column with the algorithm that builds keys and search ranges for Person Names. Call SSANAME3 and pass
FIELD=Person_Name
in the Controls parameter of the
get_keys
or
get_ranges
calls to invoke the algorithm. The candidates returned by
get_ranges
are scored using
match
to determine the likelihood of their match with the search data. Depending on purpose of search, various out of the box match purposes may be used.
To provide search capability on customer addresses, an application may create SSA-NAME3 keys for the data from
CUSTOMER_ADDRESS
column with the algorithm that builds keys and search ranges for Addresses. Call SSA-NAME3 and pass
FIELD=Address_Part1
in the Controls parameter of the
get_keys
or
get_ranges
calls to invoke the algorithm. The candidates returned by
get_ranges
are score d by
match
using a match purpose designed to work with Address data.
To provide search capability on organization names, an application may create SSA-NAME3 keys for the data from
CUSTOMER_ORG
column with the algorithm that builds keys and search ranges for Organization Names. Call SSA-NAME3 and pass
FIELD=Organization_Name
in the Controls parameter of the
get_keys
or
get_ranges
calls to invoke the algorithm. The candidates returned by
get_ranges
are scored by
match
using a match purpose designed to work with the Company names data.
If the type of data is not known or if the search needs to include results from either of Customer Name, Customer Address or Customer Company, an application may create SSA-NAME3 keys for the data from
CUSTOMER_NAME
column,
CUSTOMER_ADDRESS
column, and
CUSTOMER_ORG
column with the Algorithm that builds Generic keys and search ranges. Call SSA-NAME3 and pass
FIELD=Generic_Field
in the Controls parameter of the
get_keys
or
get_ranges
calls to invoke the algorithm. The candidates returned by
get_ranges
are scored using
match
to determine the likelihood of their match with the search data. You can use the match purpose
Generic
to work with a combination of person names, addresses, and organization names.

0 COMMENTS

We’d like to hear from you!