Idea for living people being promoted to deceased
Comments
-
gasmodels said: Usually it goes in the private space of the creator of the record. Sometimes that is mixed up because of merges or other issues. In some cases, I have heard of them essentially hiding the record because the person whose space it gets put into keeps marking it as deceased. So as you suggest Jeff it depends on the history of the record, but the bulk I believe are placed in the creator's private space.0
-
Christina Sachs Wagner said: I've always lost visibility when a case I opened for changing dead to living once it is approved, because I was not the one to create them.0
-
Juli said: I put in two dead-to-living requests this morning and just got the confirmation emails:
"Thank you for contacting FamilySearch Support and bringing your concern to our attention. A correction has been made to the record, indicating the individual is living. Due to rights of privacy, you will no longer see this record if you did not create it. You can create a new record for this living person, and that record will only be visible to you as the contributor. You will then be able to link the record to the records of the person’s deceased parents. FamilySearch encourages its users to add living individuals only as a bridge to deceased ancestors."
I conclude from that (and from the fact that I can no longer see the profiles in question) that the standard procedure is for the living profile to go into the profile creator's private space. I'd be interested in the details of any cases where they ended up in the requestor's space instead.
(Got news last night that a friend's father died. While conveying the news to spouse, I went looking online for a picture [to show that yes, they'd met], and then one thing led to another and I found his mother on FSFT -- with all of her offspring listed as "deceased". I verified with my mother that the aunt and uncle were still living, so I put in the actual death date for the dad and the requests on the aunt and uncle.)0 -
Tom Huber said: I've recently run into two profiles where they were marked as deceased (no sources to validate). In both instances, no search provided any evidence that they were deceased and, in fact, showed just the opposite. I submitted requests (by changing deceased to living) and got relatively quick responses (within a day) and the profiles disappeared (likely to the private space of the person who originally created the profile).
I don't know what FamilySearch can do to prevent users from declaring someone has died without offering evidence in the form of a source, such as a newspaper clipping or obituary (even a Facebook entry by a family member would suffice).0 -
Adrian Bruce said: I have not run into this issue, so won't pretend to talk from experience, but if a profile is un-deceased and goes back into the private space of its creator, isn't this a flawed process - because isn't there every chance that the creator will say, "Hey, I killed them off!" and do it again? After all, it surely must have been the creator of that profile who declared them dead - either when the profile was created or afterwards - which has to have been in their private space???
Not wholly sure what the best way of overcoming this is, but it sounds like we need that Warning Tab with an "I ain't dead yet!" marker?0 -
isn't there every chance that the creator will say, "Hey, I killed them off!" and do it again?
In light of the fact that FamilySearch staff communicate directly with me whenever I request a change from Deceased to Living, I expect they also communicate directly with the creator of the profile.
Whatever they do, it seems to work. I have not seen any profiles where I requested the change reappear prematurely on the public tree.
0 -
What if the people who had their copies of these previously living people were notified to check out a possible match
This already happens. If I have a duplicate in my private tree space it will show a Hint when a duplicate is detected out in the public tree space or a death record is added to the FamilySearch historical records database.
0