Identity Resolution
- Identity Resolution 10.2 HotFix 1
- All Products
ALGORITHM-DEFINITION UNCONTROLLED NAME=PERSON * ****** AUTHORISED=N3AUUSP CLEANING=N3CN FORMATTING=N3FTEN STABILIZATION=N3STEN1 CHARSET=N3CS EDITLIST=N3ELUSP FREQUENCY-TABLE=N3TBUSP SCALER-TABLE=N3SCUSP (optional) NAME-LENGTH=50 ALTERNATE-KEYS=Y NAME-FORMAT=R KEY-FORMAT=15 * ....+....1....+....2....+....3 CLEANING-OPTIONS=NN * ....+....1....+....2....+....3 FORMATTING-OPTIONS=SWNNNNNNNNN * ....+....1....+....2....+....3 STABILIZATION-OPTIONS= * ....+....1....+....2....+....3 SSA-NAME3-OPTIONS=NCNNNNNNNNNNNNNNNNNNNN8NANN KEYS-STACK-SIZE=20 WORDS-STACK-SIZE=8 SEARCH-TABLE-SIZE=21 REPORT-SIZE=2000 ALGORITHM-DEFINITION
GENERATING NOT-GENERATING (or NON-GENERATING) UNCONTROLLED
Option | Gen | Auth | Lnk | You are – | You may generate |
|---|---|---|---|---|---|
GENERATING | Yes | Yes | No | Designing a new Algorithm – this may require several passes through the Generation process. While this is being done the Algorithm is not fit for general use, for this reason it cannot be linked into an application. | Everything except the User Service Group |
NOT-GENERATING | No | No | Yes | Ready to apply a new Algorithm – the Generation and Authorization is OK. You now wish to link the Algorithm with your application and lock the Generation process so the modules cannot be changed. | Only the User Service Group |
UNCONTROLLED | Yes | Yes | Yes | Living dangerously – This option is used as a shorthand method of allowing all steps to be taken. However, you have no protection against your production files being overwritten by a careless invocation of Generation. | Everything |
Opt | Description |
|---|---|
15 | Option 15 produces keys which cause common names to be more selective than uncommon names. This is the default method. Uncommon words are stabilized, de-voweled and truncated while common words are only stabilized. Uncommon words can thus sustain greater variations in the tail end of the word than common words and common names achieve a greater selectivity than if treated the same as uncommon. |
17 | This option causes common and uncommon names to be encoded in keys in the same manner. This will reduce the overall selectivity of the keys. This method causes both common and uncommon words to be stabilized, devoweled and truncated (in the same way that uncommon words are treated using KEY-FORMAT=15 ). The benefit of this is that the effects of misspellings or variations in common names is then the same as in uncommon names. The cost is reduced selectivity on common names (that is, more variations of common names will reduce to the same key resulting in more records being selected in a search). This has fairly specific application and is not recommended for general use. |