Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2000-10-23 : 10:40:11
|
Shashi writes "we have a requirement to automate the process of checking if
a new customer exists in the Denied Party List(DPL). This list is published by the US govt twice a month.
here are the criteria for an automated system:
AUTOMATED NAME SCREENING STANDARDS
1.The name comparison functionality would provide both perfect-match and near-match result options for human assessment and reconciliation. Illustrations of the comparison functionalities or "standards" for such a program would include routines to accommodate:
a) "Soundex-like" comparisons, i.e
..... Bee Corp
..... Vee Co.
.... Mach II Videos
.... Mach 2 Videeos
b) Common spelling errors and transcription errors, character/word transpositions, missing characters, alpha sort misalignment, leading character switch, i.e.
.... Wien Oil Products
.... Wein Oil Produkts
.... Curbscide Chemicals
.... Curbcide Chemicals
.... Postal Industries
.... Bostal Industries
.... Oy Petrova
.... Petrova Oy
c) Truncation or word missing conditions, i.e.
.... Closeup Powders Incorporated
.... Closeup Powders Inc.
.... Bayside Properties (Pte) Ltd
.... Bayside Properties Ltd.
.... CASSETTE Financial Systems Inc.
.... CASSETTE
.... Dr. Herbert Klaus
.... H. Klaus
d) Acronyms, i.e.
.... World Energy Systems Technology Inc
.... WESTI
e) Hierarchical grading, neutralization and editing of common null value terms, standard symbol sets, character spaces, i.e.
.... Clark-Higgins, Inc.
.... Clark Higgins Incorporated
.... Andrew Straat/ Pty. Ltd.
.... Andrewstraat Ltd
.... Parsons***Developers
.... Parsons Developers
2. The program would demonstrate a functionality to "tune" or calibrate the core comparison algorithm to increase or decrease the selection criteria values that determine the existence of an exact or near "name match condition".
3. The program would create a permanent record or audit trail of each screening event that
captured these data elements:
.... Date of screening (day/month/year)
.... Screener/operator identity
.... Reference number of or to the DPL version used
.... Names compared, both the DPL name entry and the entered name
.... Screener/operator decision
5. The program would demonstrate a reports generation feature capable of providing a
history of screening results that displayed, at a minimum, the five data elements reflected in functionality 3. above and permit record search and selection based on at
least three data element criteria: (1) the date of the screening event, (2) the DPL name
or name compared to and (3) the identification of the screener/operator.
6. The program would provide "password-only" access to DPL data administrators and anyone authorized to override “matching” or transaction holds/blocks..
7. The program would demonstrate the capability to execute an automatic "suspend
transaction" condition , i.e. freeze further transaction processing, when a name or
country match specification was deemed to have been satisfied, subject to release
thereafter only by a designated password-authorized supervisor or other non-operator
party.
8. The system would demonstrate the capability for both real time and off line, password
controlled updating of the master DPL list of names and would permanently record all
update transactions for audit verification.
9. The system would demonstrate the capability to "screen" names in both real time, single
transaction, one-to-one comparison and "clean" database modes, using either manual
keystroke input or automated database source input." |
|
|
|
|
|
|
|
Complex string matching algorithm to be implemented in SQL Server