"These two people can be merged but only in this order"
What is it that triggers this message? I have seen it twice today with no obvious to me reason why a particular order is required. In the end it doesn't make a difference to me, because I just ensure that all the information is preserved regardless of PID. I am curious though what are the requirements for a particular order to be forced.
Best Answer
-
its not that it makes a difference to you so much - as it makes a difference to FamilySearch (the merging program) and the logic being executed - because for example one item many have hundreds if not thousands of more data element items hooked to it than the other record. Its based on the amount of code processing and complexity that it takes - by choosing one path over the other- from the perspective of the merging logic - though in the end - as you say - you dont see the difference in the end result.
You are merely satisfied based on the end result
Familysearch is interested in how much time a process takes and related CPU time / database calls - that each path/order involves - and in many cases it is greatly different.2
Answers
-
This thread may be useful:
0
