Good / bad intentioned people duplicating registers: How vulnerable is the family tree?
Maybe this have been addressed in another question, maybe my problem is due to the changes in the search bar result, or maybe the problem has never been addressed.
Some people in my Stake, me included, have had problem with people duplicating or changing names, dates, etc. in our family trees. Just last week, someone duplicated (in some cases triplicated) the same children of an ancestor. So instead of 6 children, the couple now had 14, with 2 or 3 with the same names, birth dates, birth places, dates and places of death (clearly the same person). Even spouses were the same. It made that part of my tree a mess and I had to unify each register and go over the tree to see where else the damage was made (and I didn't finish it yet). Important to note that the Temple ordinances had already been made between the 80's to the 00's, but it was showing that there were still ordinances to be done to the "other 8 kids" that don't even exist.
Now, I suspect the user that caused this mess was a "good intentioned" but inexperienced person. Maybe suffering with the system updates, or in the process of learning, or maybe just a "good intentioned" individual that doesn't have some common sense to use a "communal" tree. But there are people who's hobby is to mess up Wikipedia pages. If anyone can change my family tree (deceased ancestors) with their "good intentions", as long as they have an account, and cause me to have double, if not 10x the work just to fix it, what of an ill intentioned individual?
Temples in my country doesn't even give us the papers back anymore, they say it is saved on Family Search. Is anyone aware of the HUGE problem that can be and represent for all the work that is done? How big this vulnerability is???
Is there a function in which only I (and whoever I authorize) get access to my tree? Like a public tree version (one anyone can consult the deceased's names) + a private one where no new registers or alterations can be done UNLESS I allow someone access to it?
If there isn't, PLEASE consider the creation of this function! I know it will have to increase your data base and back up space and memory. However, what I just narrated above is a dangerous and huge vulnerabity to all the Family History and Temple work we do.
Waiting for the Family Search response.