Is there anyway to freeze a ancestor so no one can add incorrect information?
I just had a ancestor who has 10 close cousins with the same name born around the same area of Germany with in 5 years. I log in to check it all and one person now is all 10. I just had to spend hours fixing it.
Best Answers
-
@Rachel Marie Ney
.
I totally understand the premise of your ...
.
But ...
That said ...
.
Short Answer: 'No'.
.
A User/Patron CANNOT "Change" an individual/person in "Family Tree" of "FamilySearch" to "Read-Only" status.
.
IF you believe that an individual/person in "Family Tree" of "FamilySearch" SHOULD be a "Read-Only" status; then, a User/Patron SHOULD submitted a 'Support' Case for such; but, there would have to exceptional grounds for such.
.
Here is a "Knowledge Article" in "FamilySearch" on the matter of "Read Only" status:
.
What are read-only records in Family Tree?
.
Quote:
----------
Read-only records show a gold banner and allow no additions or changes. In addition, for read-only records, the Discussions and Latest Changes features are unavailable. These records often have a notification that the record is confidential.
.
FamilySearch is a unique genealogical experience. It has a single tree of individuals linked together in families. We rely on a large amount of collaboration to form a single tree instead of individual private trees. Our focus is to connect the entire human family. When we mark records as "read only," it prevents collaboration. Consequently, we do not accept patron requests to mark a record as read only.
.
Reporting an error in a read-only record
.
If you find an error in a read-only record, please contact FamilySearch Support. Due to the specialized work required to resolve this type of issue, you will receive the fastest response if you submit your request using our online form. In your message, provide the following information:
.
• Category: Family Tree
• Subject: Read only
• Message:
- Your FamilySearch username and helper number. This information is in your FamilySearch Account settings.
- Your relationship to the individual needing attention.
- The case number. If you previously contacted us about this problem, the case number helps us find the information you have already provided to us.
- Information to help us find the person whose record is in question. Include the person’s name, birth date, and ID number. Also include the ID number and birth date of any other individuals involved.
- An explanation of what is wrong.
- Correct data. Explain how the data should read and why we should change it.
- Supporting documentation. Documentation is helpful and very often necessary.
----------
.
I know that this does not help; but, I hope it gives you some perspective.
.
Brett
.
0 -
From this article: https://community.familysearch.org/s/article/One-of-my-relatives-has-a-restricted-record
FamilySearch is a unique genealogical experience. It has a single tree of individuals linked together in families. We rely on a large amount of collaboration to form a single tree instead of individual private trees. Our focus is to connect the entire human family. When we mark records as "read only," it prevents collaboration. Consequently, we do not accept patron requests to mark a record as read only.
What most folks have done is two-part procedure. First, in the Possible Duplicates system, mark each of the cousins as Not-a-Match. This prevents other folks from seeing them as a possible duplicate. They can still over-ride this however, so the next step is to write up (I'd suggest working in a wordprocessing program until you get it the way that you want.) an explanation of why these folks are each individual persons, making sure that you give the IDs of all the different individuals. Then copy and paste that write-up into the Life Sketch section of each of the individuals that might be confused. You might consider adding that text into the Discussion tab for each individual as well.
Why this works: When folks first come to an individual page, the Life Sketch is usually at the top and the first thing visible. By putting a careful explanation of who this person is and other similar folks and why they are not the same person there, most people will see it. Since your message will show you spent a lot of time researching, most folks won't change it. In addition, by marking the duplicates as Not-a-Match they don't show up as possible duplicates (the number shows 0). So they are less likely to be incorrectly merged with your ancestor.
0 -
"Sources are not seen when merges happen but Life Sketch is seen."
Sources are visible, but you would need to click on them individually to see the detail. In a merge, they are automatically added to the left-hand person. You will note that the sources for the right-hand individual appear inside of a grey box and you can click Undo to move the ones which belong to the right-hand individual to the right-hand side of the screen.
0
Answers
-
I do understand as I spent a couple hours yesterday unmerging 2 people of the same name, similar dates yesterday and from the change log I am not the first one to have to do it. I find that posting information in the life Sketch section can help. For example after I unmerged I posted in both men's life sketch section that there is a man by the same name both born in Alabama and moved to Arkansas then added but you can see in the 1870 and 1880 census that each man had a unique wife and family so please do not merge this person with ____ the other man's ID #. Sources are not seen when merges happen but Life Sketch is seen. Putting a kind warning with some sources or information can help slow the merges. I have done this for an uncle and nephew before as well as others that I find this happening to. Try to write something in the life sketch even if it is there are 10 people with the same name in the village, please make sure you have correct details to make sure yours is the same.
0 -
You can also put a "watch" on a person's detail page and when someone makes a change to that individual you will be receive a notification. The "watch" location is on the top bar and the after you receive notification you can begin collaborating with them.
0
