The Person Merge resource is used to analyze and perform a merge between two persons. The conclusion and source reference on the survivor person (pid) is replaced with the information on the duplicate person (dpid).
If you make a
GET request, specify the data format using the
POST something, specify the media type using the
|X-Reason||header||The reason for the merge.|
|Authorization||header||The authorization carrying the OAuth 2.0 access token. See OAuth 2.0 Bearer Tokens.|
|pid||path||The id of the survivor.|
|dpid||path||The id of the duplicate.|
|filter||query||The filter to apply to the merge analysis. One of "CoupleRelationships", "NonVitalConclusions", "ParentChildRelationshipsAsChild", "ParentChildRelationshipsAsParent", "SourceReferences", "VitalConclusions".|
|access_token||query||The ID of the OAuth 2 access token used for identification and authorization of the user (and agent) making the request.|
The OPTIONS method supplies information about the viability of this merge, using the Allow HTTP header. If this merge is viable, the Allow will indicate that both GET, POST may be applied. If the merge is available when the roles of the survivor and non-survivor are switched, a Link header will be supplied linking to the "merge mirror." When the merge is NOT viable, the Allow header will NOT include a GET or POST, but the Warning header may be used to obtain details as to the reasons the merge is not viable.
Read the current state of the potential merge by performing a merge analysis. The filter request parameter may be specified indicating which categories of information need to be analyzed. If no filter is specified then all categories will be used. The valid filter categories are listed below.
POST - This method performs a person merge as specified by a Person ID (survivor) and Duplicate Person ID along with the list of resources to be merged. All resources from the survivor person that need to be deleted must be specified. All resources that should be copied from the duplicate person to the survivor must be specified. If a resource is copied and a resource of the same type already exists on the survivor then that resource must be deleted from the survivor.
|Read Person Merge Analysis||How to read an analysis for a merge of two persons.|
|Read Person Merge Constraint (Can Merge Any Order)||How to read the constraints for a merge between two persons that can be merged in either order.|
|Read Person Merge Constraint (Can Merge Other Order Only)||How to read the constraints for a merge between two persons that can be merged only in the other order.|
|Merge Person||How to merge two persons.|