Changes between Version 11 and Version 12 of UserGuidelines/Import/UpdateDetection


Ignore:
Timestamp:
09/13/12 10:20:34 (9 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UserGuidelines/Import/UpdateDetection

    v11 v12  
    3030Person records are primarily identified by:
    3131
    32   - an exact match of first name and last name (if both are present in the import item), or
    33   - alternatively, an exact match of the initials (if present in the import item)
     32  - an exact match of '''first name''' and '''last name''' (if both are present in the import item), or
     33  - alternatively, an exact match of the '''initials''' (if present in the import item)
    3434
    3535If any matching records can be found, they will be ranked by:
     
    4646These criteria are weighted by a schema to satisfy a wide range of cases:
    4747
    48   - first name: match +2, mismatch -2, missing from either record 0 points
    49   - last name: match +2, mismatch -2, missing from either record 0 points
    50   - date of birth: match +3, mismatch -2, missing from either record 0 points
    51   - email address: match +2, mismatch -5, missing from import item -2 if initials present or -3 if no email in the database or otherwise -4 points, missing from the database 0 points
    52   - initials: match +4, mismatch -1, missing from either record 0 points
    53   - mobile phone number: match +1, mismatch -1, missing from either record 0 points
     48  - '''first name''': match +2, mismatch -2, missing from either record 0 points
     49  - '''last name''': match +2, mismatch -2, missing from either record 0 points
     50  - '''date of birth''': match +3, mismatch -2, missing from either record 0 points
     51  - '''email address''': match +2, mismatch -5, missing from import item -2 if initials present or -3 if no email in the database or otherwise -4 points, missing from the database 0 points
     52  - '''initials''': match +4, mismatch -1, missing from either record 0 points
     53  - '''mobile phone number''': match +1, mismatch -1, missing from either record 0 points
    5454
    5555  '''DEVELOPERS note:''' ''the exact schema needed for a deployment depends on the typical quality of the import data, which may vary. The more consistent and detailed the import items are, the safer the schema works. It is possible (and maybe necessary) to adjust these weights to particular situations by using a set of unit test cases like in {{{!PersonDeduplicateTests}}} in {{{modules/unit_tests/eden/pr.py}}}. However, it should not be expected that this schema can reliably detect any possible edge-case - as per its purpose it is much more important to maintain a manageable set of rules how data sources would have to indicate updates, and adapt the data sources to them.''