CRM_Dedupe_Merger

FIXME: consider creating a common structure with cidRefs() and eidRefs() FIXME: the sub-pages references by the URLs should be loaded dynamically on the merge form instead

Returns the related tables groups for which a contact has any info entered.

Get array tables and fields that reference civicrm_contact.id.

This function calls the merge hook and only exists to wrap the DAO function to support that deprecated call. The entityTypes hook is the recommended way to add tables to this result.

I thought about adding another hook to alter tableReferences but decided it was unclear if there are use cases not covered by entityTables and instead we should wait & see.

Return tables and their fields referencing civicrm_contact.contact_id with entity_id

Return tables using locations.

We treat multi-valued custom sets as "related tables" similar to activities, contributions, etc.

Tables which require custom processing should declare functions to call here.

Doing so will override normal processing.

Return payment related table.

Return payment update Query.

Based on the provided two contact_ids and a set of tables, remove the belongings of the other contact and of their relations.

Based on the provided two contact_ids and a set of tables, move the belongings of the other contact to the main one.

Load all non-empty fields for the contacts

Batch merge a set of contacts based on rule-group and group.

Get the string to join the prevnext cache to the dedupe table.

Get where string for dedupe join.

Update the statistics for the merge set.

Delete information about merges for the given string.

Get merge outcome statistics.

Get merge statistics message.

Merge given set of contacts. Performs core operation.

A function which uses various rules / algorithms for choosing which contact to bias to when there's a conflict (to handle "gotchas"). Plus the safest route to merge.

Compare 2 addresses to see if they are the same.

A function to build an array of information about location blocks that is required when merging location fields

A function to build an array of information required by merge function and the merge UI.

Based on the provided two contact_ids and a set of tables, move the belongings of the other contact to the main one - be it Location / CustomFields or Contact .

. related info. A superset of moveContactBelongings() function.

Get fields in the contact table suitable for merging.

Added for CRM-12695 Based on the contactID provided add/update membership(s) to related contacts

Create activities tracking the merge on affected contacts.

Get Duplicate Pairs based on a rule for a group.

Get the cache key string for the merge action.

Get the metadata for the merge fields.

This is basically the contact metadata, augmented with fields to represent email greeting, postal greeting & addressee.

Get the details of the contact to be merged.

Merge location.

Based on the data in the $locationMigrationInfo merge the locations for 2 contacts.

The data is in the format received from the merge form (which is a fairly confusing format).

It is converted into an array of DAOs which is passed to the alterLocationMergeData hook before saving or deleting the DAOs. A new hook is added to allow these to be altered after they have been calculated and before saving because - the existing format & hook combo is so confusing it is hard for developers to change & inherently fragile - passing to a hook right before save means calculations only have to be done once - the existing pattern of passing dissimilar data to the same (merge) hook with a different 'type' is just ugly.

The use of the new hook is tested, including the fact it is called before contributions are merged, as this is likely to be significant data in merge hooks.

Dedupe a pair of contacts.

Replace the pseudo QFKey with zero if it is present.

Honestly - what DOES this do - hopefully some refactoring will reveal it's purpose.

Update this function formats fields in preparation for them to be submitted to the 'ProfileContactCreate action. This is a lot of code to do this & for - for some fields it fails - e.g Country - per testMergeCustomFields.

Goal is to move all custom field handling into 'move' functions on the various BAO with an underlying DAO function. For custom fields it has been started on the BAO.

Get metadata for the custom fields for the merge.

Get conflicts for proposed merge pair.

Get any duplicate merge pairs that have been previously cached.