Any way to protect tree entries? Any way to edit locked index entries?
One of my great grandparents was scanned by a computer that misread the name. I can't edit the index because there's a padlock and I need "special authorization".
Then another computer auto-generated a tree with the wrong name and added a duplicate of my tree member but with the wrong name.
So that's two computers that made mistakes which tainted the tree I have worked hard to make.
On an unrelated note, a human user also made poor edits to my tree and I get "you can't contact this user"
So, any way to protect entries or to get at least requests for edits of these entries? Any way to stop computers from mucking up clean human work?
Answers
-
Please provide links to the records and profiles involved here, since, while the Community may be able to provide constructive advice, the context for this sort of grief can differ widely. In particular we will need to see which record collections are involved; and questions 2 and/or 3 may or may not relate to the various automated or semi-automated census/Numident projects.
1 -
Many indexes that have a padlock symbol have been recently edited. The gremlin in the editor created the lock. In many cases, it has also caused the record to vanish - it will not appear in searches. For example:
0
