Question about a read-only record KWCV-V8H
Just wondering why my Uncle Paul Dee's record (KWCV-V8H) is read only?
I found a note under the collaboration tab that said, simply, "Living" which is incorrect (he would be 113 years old).
The confusion might be because he has a son of the same name Paul Dee Lyman Jr. (KWCV-VFK). The younger Lyman died of cancer in December of 2020.
Thanks for your help!
Answers
-
The solution should be straightforward in this example. Just change his status from Living to Deceased and his profile will be visible to all. Obviously, I would only encourage this where the individual would have been over 110, or if there is firm evidence of a death with other persons marked as Living.
0 -
@Paul W, the profile is public, so it's not a matter of marking him deceased. For some reason, the profile has been made read-only. The change appears to have been relatively recent, as there are changes from various users as late as 2019. (After that, every change is labeled "FamilySearch" in the change log and "Unknown Contributor" in the Latest Changes box.)
1 -
I see I should have checked-out this specific case before commenting. I thought the record itself was marked "Living", but after re-reading the original post I can see my misunderstanding.
0 -
@Kevin Millecam Just to guess at your question of "Why", most of the other read-only records I've seen were latter-day Apostles or their immediate family. I'm not sure exactly what the highest calling your grandfather had was, but your great-great-grandfather also named Amasa Mason Lyman (KWJ8-467) is also read-only, was an Apostle, and was twice excommunicated. See http://archives.lib.byu.edu/agents/people/7435 .
According to https://www.familysearch.org/en/help/helpcenter/article/what-are-read-only-records-in-family-tree , you've made the right first step. Unfortunately, the next step depends on a moderator. @N Tychonievich or @BarryJohnson , can you help?
0
