Default preferred parents messed up upon a duplicate PID being added.
When patrons add a new duplicated person, the preferred becomes set to the new person. The preferred which was previously set to the well established and documented person is usurped and set to the new person which often is erroneous data and will need being merged to the established line. The problem is until it is noticed and merged, the preferred is set to the bad line and when folks do a "First Ancestor", it fails to find the first ancestor.
I suspect right now, the system simply sets the preferred based on the last PID acted upon. Can you instead have the system set the preferred based on the PID with the most sources/memories/collaborations associated with it? As that is most likely to be the well established vetted and correct line?
If you look at the above example, a Patron today added Mattathias ben Amos, and the system set it as the preferred parents. In this case, this PID is the grandparent of the child it was added to. When someone does an "First Ancestor" function it will route down this wrong erroneous line now. Whereas if the preferred had been left assigned to the original and well established correct line, it would work and show path correctly.
I am well aware that I can reset the preferred for me under my profile. However, it remains an issue for many other patrons, many who aren't aware that they can reset the preferred. And when new PIDs are added, MY setting gets nuked and I have to reset AGAIN when I discover it messed up.
Can the code which determines setting the preferred to the latest added PID, be adjusted to evaluate the number of sources/memories and set preferred to the PID with the most?
Also, in the cases where some PIDs can't be merged, I end up choosing to delete the association all together, forcing the system to reset the preferred to the correct parents and thus any patrons who do a "First Ancestor" option, can have success. Meanwhile a unassociated PID is floating around loose in the system.
Bottom line, can the preferred setting upon a new PID being added, defaulting to and staying with the original well established PID, instead of nuking that and assigning it to newer and usually erroneous PID?
Thank you very much! Best regards, LeEric