User Guide

10.2 HotFix 1
- 10.5 HotFix 2
- 10.5 HotFix 1
- 10.5
- 10.2
- 10.1
- 10.0 HotFix 1
- 10.0

Back Next

Score Logic

Score Logic is defined in the

Clustering-Definition

. It specifies how the DCE Search Server will select records to be returned from the set of candidates. Score-logic facilities are provided by SSA-NAME3 Population Rules.

The score logic has four possible steps:


KEY-SCORE-LOGIC
KEY-PRE-SCORE-LOGIC
PRE-SCORE-LOGIC
SCORE-LOGIC

At least one score-logic step must be defined.

KEY-PRE-SCORE-LOGIC

is used to define an optional "light weight" scoring scheme that is processed before the

KEY-SCORE-LOGIC

. Its purpose is to make a fast and inexpensive decision as to whether or not the more costly

KEY-SCORE-LOGIC

should be called to process the current record.

KEY-SCORE-LOGIC

is used to define a scoring scheme to score

KEY-DATA

. Refer to the

Key Data/Key-Score-Logic

section for details.

PRE-SCORE-LOGIC

is used to define an optional "light weight" scoring scheme that is processed before the

SCORE-LOGIC

. Its purpose is to make a fast and inexpensive decision as to whether or not the more costly

SCORE-LOGIC

should be called to process the current record.

All the

SCORE-LOGIC

keywords share the following syntax:

SCORE-LOGIC = <type>,<parm-list>

where

<type>: This is SSA (currently only SSA Score-Logic is supported).

<parm-list>: This is a comma-separated list of parameters.

Parameter list:


System(system)
Population(population)
Controls(controls)
Matching-Fields(field-list)

where

system

Defines the System Name of the Population Rules.

population

Defines the population name. The population chosen will depend on the data being processed.

controls

Defines the controls to be used for the Score-Logic. Controls should specify the desired

PURPOSE

and

MATCH_LEVEL

For more details on the Controls, refer to the

SSA-NAME3 API REFERENCE GUIDE

under the

ssa_match

heading within the Controls section.

Matching-Fields

Holds the list of fields and their data type used by the matching routine.

field-list

This is a comma-separated list of the form

field_name:data_type

where

field_name

This is the name of a field in the IDT.

data_type: This is the data type that this field represents, as defined in the Population Rules.

The

field_list

defines which IDT fields will be used for matching and the type of data they represent. Matching will use repeat logic when two or more fields of the same

data_type

are specified. A run-time error will occur if a

data_type

defined as mandatory for the

PURPOSE

has not been specified in the

field_list

. Optional

data_types

may be omitted.

For example,


SCORE-LOGIC=SSA,
            System(system), Population(population),
            Controls ("PURPOSE=purpose_name MATCH_LEVEL=Loose"),
            Matching-Fields("fieldname:Person_Name",
                            "field_date:Date",
                            "field_sex:Attribute1",
                            "field_postal_area:Postal_Area")

Rename Saved Search

Table of Contents

User Guide

User Guide

Score Logic

Score Logic