Merging project protected profile (Walgrave-17) into non project protected profile (Waldegrave-94)

Question

A proposal has been made to merge profile Walgrave-17 into Waldegrave-94.  These profiles contain consistent information.  Waldegrave-20 and Waldegrave-63 were previously merged into Walgrave-17.  Parents, siblings and children of Walgrave-17 are listed as Waldegrave.  It appears that the name Walgrave is an anomalous spelling of Waldegrave.  Merging Walgrave-17 into Waldegrave-94 would remove this anomalous spelling and keep the lineage LNAB consistent through the generations. Walgrave-17 is listed as project protected, Waldegrave-94 is not listed as project protected.  Is there a problem with merging this project protected profile (Walgrave-17) into the non project protected profile (Waldegrave-94)?

Answer 1

Hi Michael,

Info about how PPP works, including with respect to merging, can be found here:

http://www.wikitree.com/wiki/Project_protecting_and_merging#How_to_protect_and_merge_a_project_profile

The protected profile can't be merged away, but other profiles can be merged into it.

Therefore, in your situation, you will need the project protection to be removed from Walgrave-17 and added to Waldegrave-94.  (I've seen a similar scenario when someone finds a lower-numbered profile than the one with the PPP on it.)

You can contact the leaders of the relevant project to assist you.  It looks like that's Magna Carta, so that's me.  :)  I'll go see what I can do.