Why is Suggestions demanding match with Find-a-Grave data?

+12 votes
Why is the Suggestions tab now demanding birth and death dates in WikiTree profiles be corroborated, matched to, or stated to be correct over Find-a-Grave? Find-a-Grave has its place but is constantly inaccurate on birth, death and almost any other matter.

My response to this is to delete links to F-a-G. If there is a viable headstone photo use it, otherwise delete the link.
asked ago in Policy and Style by T Stanton G2G6 Mach 3 (30.3k points)
What do you mean "now"? It's been that way for quite a while now. If Findagrave is inaccurate (and you can prove it), submit a correction. Otherwise, you can ignore it.

Also, please don't steal headstone photos without asking.
I've not before seen it request a date corroboration. These are cropping up in merged or adopted profiles so perhaps not before encountered as I never use F-a-G as a source (once in a blue moon find a memorial there with a useful source but then cite the source once verified, not F-a-G). I do correct F-a-G on immediate family, otherwise it seems a duplication of effort to submit corrections to another place.
It's not a demand, just a suggestion.  A nudge or a nag, maybe.  The vast majority can be dismissed with False Error, 'FaG is unsourced.'
I use Find A Grave quite a bit and always corroborate any information I find there or make a note that the information is from FAG. If I subsequently find source material, I edit the profile to reflect my findings. Since I think information should be as accurate as possible, whatever the source, I always submit corrections when I find documentation on an individual. I do the same on Familysearch. I don't see it as duplication of effort but an attempt to make the information available as accurate as possible, no matter the source. Find A Grave information will remain suspect until and unless someone makes an effort to correct it. I'm willing to make that effort on the profiles I work on.

 @ T Stanton  is your error a "574 FindAGrave - Imprecise birth date" one?



I've had a findagrave error on an adopted profile for a while.  The date-plus-location given by findagrave are wrong.  The year may be correct, but the person was NOT born where findagrave said.  I tried years either side of the findagrave given date and got zero. 

Today, just because I've been doing a lot of my direct-line family research in Scotland, I typed in my "error" profile's name and got a hit.  Funny, I never knew northern Scotland was anywhere near Kent, England.

The relocation of Kent no doubt the result of a previously unknown tectonic subduction, Melanie. I don't now recall the error code as I simply marked them as F-a-G being in error (which was the case). I didn't mind seeing the occasional error that a F-a-G memorial number was wrong (often when memorials were merged) but it was just annoying to have solid profiles being checked against F-a-G data because a F-a-G link was on the profile.

The relocation of Kent no doubt the result of a previously unknown tectonic subduction. . .

commented ago by T Stanton


Thanks for the laugh!

I only knew about the error because I read on G2G that we should all be checking our own "suggestions" list, so I started doing that.  (I actually have NO idea what I'm doin, 'cause I ain't no data doctor!" (and, yes, I know there's a double negative in that statement, but it's meant to be facetious, flippant), so I'm winging it.) 

I can't remember now (from only a few minutes ago!) what I did today for that error, but is there something I can do on the profile to make sure it never comes back?  sameas=no doesn't seem to be the correct thing, as much of the findagrave data is correct .. and what is not, I noted in the profile after I adopted it.

(I'm sure I know WHY particular findagrave data are incorrect, but I'm not about to put that information on the profile at this stage, unless I hide it.  (It is potentially distressing to living relatives.))

Melanie, I don't think there's anything you can do on the profile.  If you mark the Suggestion a False Error and Hide Forever, it's gone for all intents and purposes.  I wish the Data Doctors would just give up on that one.

Moving Kent to northern Scotland is a pretty short trip for Kent.  It often finds itself in Kentucky.

Yeah, I think I did do the false error thing, with a comment regarding how findagrave was incorrect.

Am I allowed to do the same thing for a "unique name" error that nobody will tell me what part of the name is "unique" on? (Sorry, not a findagrave error!)

Moving Kent to northern Scotland is a pretty short trip for Kent.  It often finds itself in Kentucky.

laugh laugh 

Yes, don't worry about the unique names Suggestion.  If the name is right, it's right.  False Error, 'Name is correct as spelled.'  Hide forevah!

Done .. me hopes.  cheeky

Good for you!  I do the same.  Perhaps it comes from a lifetime of work as a secretary, where I was always proofreading--or it may be my own obsessive compulsiveness.  Whatever it is, I prefer facts over fiction and I appreciate your efforts on behalf of others to correct FindAGrave records.

7 Answers

+16 votes
Best answer
Hi T.  The feature of comparing our data to that on FAG was implemented several years ago.  If you were to go through old G2G posts, you would most likely find miles of commentary on it, much of it negative.  At least some of us who have been here a while believe that this feature is the single worst "improvement" that has ever been implemented in the history of WikiTree.  At one point one of the leaders said it's OK just to ignore those suggestions if you wish.  That's usually what I do, but that's not going to stop an over-zealous data doctor from coming along at some point and "fixing" your data to match FAG.
answered ago by Dennis Barton G2G6 Pilot (226k points)
selected ago by Gaile Connolly
That DD issue came up in one of the most active Projects just in the last week when a DD was messaging the project group about FAG having data that didn't match well-researched project protected profiles--suggesting the project take the time to make sure everything matched. Things got somewhat heated.
Ignoring the entire suggestion list is precisely what I do and it is because of the flagging of things that are not errors.  I am not willing to waste my time going through reams of items, mostly find a grave and unique name errors that are not errors, to mark them false errors.

In addition, it is very annoying to have to waste my time correcting changes made to profiles to add a find a grave date/place when the profile already had a paragraph about that find a grave record being for a different person with the same name as the profile subject.  Although data doctors seem to be more concerned with applying thought to the changes they make than they used to be, there are still instances when they make incorrect changes on profiles I manage.  I am thankful that I have not received messages about these things.  If I did, it would cause a classic dilemma - it would not be polite to not respond but responding would be in violation of the DWWT rule.
Thanks Gaile.  I'll be very surprised if that star lasts until morning!!
+12 votes
Most of the people I see this on don't have a documented birth and/or death date, so I just mark it as a false error and say it's an estimate.  I agree that it's very annoying.
answered ago by Kathie Forbes G2G6 Mach 5 (54.3k points)
+3 votes
OTOH, it is entirely possible for me to mistype 1908 vs 1809 . . . or something similar.  Most of the time it will be a false positive, but every now and again, esp. with no DOD and only DOB, it might be the prompt to let me know a correction is needed.

I'm one of those who both asks for FaG corrections and accepts them.
answered ago by Kathy Rabenstein G2G6 Mach 2 (21.2k points)
+3 votes
If you can find a sourced death date, add it to the profile, ensure the death is correct and check in suggestions resolution: false error, hide forever.
answered ago by Raewyn Vincent G2G6 Mach 1 (19.3k points)
+2 votes
Its not demanding a match -- on the contrary.

If the profile has a [source] link to find-a-grave, then it will compare and report the differences, for us to either "fix" or document and ignore.
answered ago by Dennis Wheeler G2G6 Pilot (374k points)
+3 votes
answered ago by Robin Lee G2G6 Pilot (453k points)
+6 votes
I would choose ignore/false suggestion rather than deleting the link. Chances are, at some point, someone else will come along and add the link back under a See Also tab.

The benefit of having a link to FindAGrave is that FindAGrave memorials are often maintained by descendents. If two different wikitree profiles point to the same Find A Grave memorial, that is helpful to know. Sometimes people get things wrong. Being able to document common mistakes on other sites on wikitree profiles helps to stop the profileration of inaccurate information. It also highlights areas where more research is neccessary.
answered ago by Lance Martin G2G6 Mach 6 (67.9k points)

Related questions

+18 votes
14 answers
+6 votes
0 answers
+5 votes
3 answers
+7 votes
1 answer
123 views asked Mar 8, 2018 in Genealogy Help by Juha Soini G2G6 Mach 6 (63.1k points)

WikiTree  ~  About  ~  Help Help  ~  Search Person Search  ~  Surname:

disclaimer - terms - copyright