777: Unique name in Last Name at Birth

Question

I enter thousand of German names, why doesn't wiki understand and know the names I am entering are correctly spelled--especially with the 'ö' ???
I know I am in the US, but shouldn't the system automatically know a correctly spelled German name?

Comments

Of course I could not find the others who questioned this until after I post my question.  Now to read those for an answer,  But it seems almost any unique name will end up on that list.  
And it seems there don't seem to be enough German members using wikitree or something.

Answer 1

WikiTree does not maintain a database of correct name spellings. Rather, these suggestions are generated when a computer algorithm sees a name spelling that does not occur anywhere else (or occurs only a very few times) in the WikiTree data. This is done primarily to check for typographical errors.

If the name is spelled correctly, just mark the suggestion as FALSE SUGGESTION and it will go away.

Comments

Thanks for the answer after I asked it I did find it down below here..  Now I would like to hide all FindAGrave suggestions.  I try to make sure all my dates are correct from the documents I enter, but if FAG doesn't match I do not wish to spend hours trying to correct their database.  Also often I use German documents--correct there, but US documents often have different dates on those records.
It's just not worth dealing with, can I hide all FAG messages?

---

If you are sure your dates are correct and you don't want to send an update to Find A Grave, you can mark the Find A Grave Suggestions as Fale, with a comment, Wikitree is sourced. That will hide them.  Adding a comment that it is correct will not hide them

---

I have to say, I dislike that method. If you wanted to just ignore the suggestions because you know them to be "not worth dealing with", then do that. But what if another relative or someone unrelated on wikitree finds it worth their time and wants to help by updating FindAGrave?

They are just suggestions, after all, I would only mark something as False when I know for a fact it is not valid, and it's a valid error to say they show different things.

---

Thanks,  I would love to have the time dig in further on each one.  It is hard when you have almost 5000 names on your watchlist.  So for now I'll just hide them and do a couple at a time.
No doubt it is best to have them match.  Someone said, if you help to improve one genealogist, you are helping you are helping all genealogists.

---

Jonathan, you can submit changes to Find A Grave and they are declined because their information 'is better than yours', or so they think. I send source citations when I submit changes and I normally get updates, but not always. With their auto updates, incorrect information can be introduced also. They are False Suggestions when the 2 systems differ and wikitree is correct. If Find A Grave is not going to update, you can't always make them the same. Gravestones also differ. Those pages will not be changed.

Anyone can always review false suggestions and correct them. I do that frequently. Many people mark all Find A Grave and Wiki Data suggestions as false stating 'I am not going to deal with it' or 'I don't understand it' or 'I didn't put that info in'. I find those reasons very unfortunate  and incorrect for people to use, which is why i review False Suggestions.

---

Some members simply ignore most findagrave suggestions.

---

Further to my last comment, I do not endorse the idea of marking a findagrave suggestion as false suggestion simply because the suggestion is annoying. If you don't want to deal with the suggestion, just ignore it. The false suggestion option should be used only when you have an actual basis for saying that the suggestion is wrong or inappropriate.

Many findagrave suggestions are legitimately false suggestions -- such as the cases where the findagrave memorial has a photo of an ancient gravestone that shows only a name and a year of death, with no hint at other information sources, yet the suggestion nags us with the information that findagrave has a birthplace and date of birth that are more precise than the information we have on WikiTree.

Answer 2

The suggestion report does check for ö. So ö on it's own is not the problem. 

In the Info column it states which word is unique. On the profile you provided it is the name Bemeth It is the only one on WikiTree for now. When you will add parents with the same name, the suggestion should go away.