Stop marking people read only
This Read only person marking is crap.
This person has 11 DUPLICATE PEOPLE
Richard Brown Hodson
Male
13 November 1935 – 24 January 2021
•LFF2-ZJ2
None can be merged because his parent is marked "read only"
The read only should be removed from everyone. This makes for many duplicate people with different familysearch numbers.
Answers
-
I feel your pain.
You can merge the other 11 duplicates into one other profile. Then, request FamilySearch staff to merge the one duplicate with this profile.
Edit to add: never mind! I see 17 duplicates, all attached to the same parents.
0 -
Can the duplicates be detached from the read-only parents?
If you can't even do that, then this is an excellent illustration of just how ...ill-advised the whole read-only concept is.
0 -
Can the duplicates be detached from the read-only parents?
No, the duplicates cannot be detached by ordinary contributors.
His mother's profile is locked read-only. The lock on her profile is not the cause of the many duplicate profiles of him. He has so many duplicates because an LDS member with a large family. After he died his 18+ profiles in private tree spaces were released into the public tree.
The lock on his mother's profile means FamilySearch staff assistance is needed to merge the duplicates. But perhaps there is no rush and the family may as well wait a few years for more profiles to be released.
Notice that the change logs conceal each contributor except on the edit changing Living to Deceased. The change log reveals from whose private tree space the profile emerged. A. contributor who wishes to guard the privacy of living persons including themself would do well to delete rather than release profiles from their private tree space.
0
