No Person Found! Improving Usability and Privacy for living person
Hello,
I am trying to set up familytree for my son who is 12 years old and getting him to find me as his father using my ID. But this came up "No Person Found No person was found with the ID you entered. Please try again". Following this intruction, I have tried many times making sure I have entred my own ID correctly. I hope you understand how stressful this is. Based on the forum discussion I learned that because I am a 'living person', due to privacy concern, even my son cannot find me and he needs to create another me as a duplicate record and all my children have to create lots of duplicate records. Now may I provides a few suggestions to improve usability of this app.
- Change the inaccurate error message from "No Person Found No person was found with the ID you entered. Please try again." to "The ID you entered is for a living person. We cannot add a living person's record due to a privacy concern. Please create a duplicate record for this person. For more information, please visit XXX." This suggestion can be implimented easily and will save frustrations and waisted time of many new users.
- Create an option for the living person to "Approve" his/her direct family member to add him/her in the familysearch. Allow options to make some privacy information visible such as memory photos. The user who is trying to add a living person will see a message like "The ID you entered is for a living person. This person needs to approve his/her record to be added to your family tree through FamilySearch." This suggestion involves more technical and regulatory work. However, please remember how the LDS tool is making many privacy information available to members in the ward. It is definitely possible.
Thanks for considering my suggestions to improve usability of this app/system.
Comments
-
Change the inaccurate error message from "No Person Found No person was found with the ID you entered. Please try again." to "The ID you entered is for a living person. ..."
I know that it is frustrating if you don't appreciate already what's going on, but I suspect that nobody would accept the suggested error message. The reason is that if there is a failure to match on security details and rules, it is a general principle to give the minimum hint necessary about what's gone wrong. For instance, very often if you want to log onto a site and get the password wrong, the best response is "Incorrect UserId or Password" - it's not that the system can't know - it can find out perfectly well if that UserId exists - it must do at some point. But if the error message just said "Incorrect Password", then the person attempting to crack the system now knows that the UserId is correct.
It might be a better message to replace "No person was found with the ID you entered" with "No deceased person was found with the ID you entered" - my bolding is on the change. That might be enough to prompt an understanding that the search (after looking in the user's private space) is now looking at the rest of FS FamilyTree.
2 -
Unfortunately the system is working as designed. IDs of live people cannot be shared. The only person that will see an ID of a living person is the one who created it. Your son will have to create his on profile and ID, then he will have to create a duplicate person page of you which will have a different ID. In fact, the two of you will have to create duplicate persons for every living relative you share until you get to a deceased shared ancestor. That is the only type of ID the two of you can share. All of your shared work will have to be on deceased people only.
Once some one becomes deceased, everyone can mark that ID deceased and then they can be merged.
3 -
Rootstech 2023 announced that soon (probably within a year or so) Living Family Groups will be able to share living PID to reduced duplicates (or at least that is what I recall). Looking forward to the changes...
0
