Changes between Version 8 and Version 9 of UserGuidelines/Import/UpdateDetection

Timestamp:

09/13/12 10:17:35 (12 years ago)

Author:

Dominic König

Comment:

--

UserGuidelines/Import/UpdateDetection

@@ -52 +52 @@
   - mobile phone number: match +1, mismatch -1, missing from either record 0 points
 
-  '''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 retain a manageable set of rules how data sources would have to indicate updates, and adapt the data sources to them.
+  '''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 retain a manageable set of rules how data sources would have to indicate updates, and adapt the data sources to them.
 
 Examples:
@@ -70 +70 @@
 The highest ranking match will be used to identify the record to update. Out of multiple matches with the same rank, the oldest record will be used.
    - ''tbw''
+   - ''tbw''