When merging two people what happens to sources?
Answers
-
most of the items would get merged automatically - including Memories items.
thats the pupose of a merge.
but give it a try - just to prove it.
0 -
OK. I tried it and it was on the page after you click "continue" that Family Tree allows you to add information from the person being deleted to the other. The sources went automatically. Thanks for the encouragement to take thaat next step. If it didn't work I would have had to retrace several steps and locate several sources. It worked! Thanks!
0 -
For what it's worth, the assumption here is that if you have determined that those two records you want to merge really ARE duplicate records, then you MUST transfer all sources to the surviving PID. After all, they are the same person, right?
The same thing applies to all RELATIONSHIPS. Relationships attached to both of the duplicate records should be accumulated together. So by default, all the relationships are also set up to come over automatically as well. Unfortunately, FS has left in the ability to REMOVE relationships during the merge which should NEVER be allowed!
If you find that either of the PIDs to be merged have sources or relationships attached to them that will not belong in the surviving PID, they are evidence that one or both of the PIDs are schizophrenic and contain information representing more than one person. These issues need to be resolved BEFORE any merge is attempted. If you go on with the merge, it will be far more difficult to clean up the bad merges later.
That's why relationships (or sources) that don't apply during a merge should be individually removed from the original PIDs they are attached to BEFORE the merge. The severe weaknesses of the change history logs make trying to track such things in order to correct them pretty well impossible.
0 -
For what it's worth, the assumption here is that if you have determined that those two records you want to merge really ARE duplicate records, then you MUST transfer all sources to the surviving PID. After all, they are the same person, right?
The same thing applies to all RELATIONSHIPS. Relationships attached to both of the duplicate records should be accumulated together. So by default, all the relationships are also set up to come over automatically as well. Unfortunately, FS has left in the ability to REMOVE relationships during the merge which should NEVER be allowed!
If you find that either of the PIDs to be merged have sources or relationships attached to them that will not belong in the surviving PID, they are evidence that one or both of the PIDs are schizophrenic and contain information representing more than one person. These issues need to be resolved BEFORE any merge is attempted. If you go on with the merge, it will be far more difficult to clean up the bad merges later.
That's why relationships (or sources) that don't apply during a merge should be individually removed from the original PIDs they are attached to BEFORE the merge. The severe weaknesses of the change history logs make trying to track such things in order to correct them pretty well impossible.
0