Changes between Version 16 and Version 17 of BluePrintDeduplication


Ignore:
Timestamp:
05/07/12 04:19:41 (9 years ago)
Author:
Michael Howden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrintDeduplication

    v16 v17  
    1010  * For specific resources different processes could be used to identify duplicates (See below)
    1111[[Image(http://wiki.sahanafoundation.org/lib/exe/fetch.php/foundation:gsoc_kohli:import:indentify_duplicates.jpg)]]
    12  1. Merging Duplicate Records 
     12(different resources should be on different tables)
     13 1. Display & Merge Duplicate Records 
    1314[[Image(http://wiki.sahanafoundation.org/lib/exe/fetch.php/foundation:gsoc_kohli:import:resolve_duplicates.jpg )]]
    14 See also:
    15   - [wiki:BluePrintRecordMerger Record Merger]
     15 * See also:  [wiki:BluePrintRecordMerger Record Merger]
     16 * For some records it could be important to display virtual fields to show that they are not duplicates (eg a person'a email/phone/address)
    1617 1. Replace Reference to the record with has been merged (must work with offline instances over sync too)
    1718
     
    1920
    2021Update: Some of the above part has been merged into sahana code.
     22
     23== User Stories ==
     241. Admin checks list of items to find out if any of them are duplicates. This list will show a list of item pairs which are similar.
     251. The Admin will select one pair of items which they believe are duplicates. They will be able to open this pair of items, editing both of them, with buttons to be able to copy field values from one record to another, then choosing which one to use.
     261. When you merge the record, all references to the record which got merged will be re-directed into the record it got merged into.
    2127
    2228== Different Processes Identifying Duplicate Records ==
     
    4248
    4349=== People ===
    44 
    4550  1. Person de-duplicator is available under pr/people_duplicate and it picks the duplicate person records from table pr_person based on the following conditions:
    4651    * If soundex of firstname in record1 == soundex of firstname in record2  OR Match% between record 1 & record 2 > 50
     
    5055  1. Clicking on submit will save that record and delete the other one
    5156  1. References to the delete record will be removed and updated with the saved record's Id
    52 
    5357
    5458=== Ideas ===