Requesting correction - error in name in info taken from Find A Grave

LegacyUser

Beth Macdonald said: May I suggest a correction? I searched for my great-grandmother Carrie E. White, maiden name Beal, and found that you have used faulty info from Find A Grave. I have informed the creator of that memorial and asked that it be corrected. I found Carrie in your "Search Results from Historical Records" listed as Caroline E. Williams! The memorial correctly states that she married Ernest Linwood White, and her name in the accompanying photo of her "headstone" is Carrie E. Beal White. There is no reason that she should have acquired the last name "Williams". Thank you.

LegacyUser

Tom Huber said: If you create an account on Find a Grave, you can make corrections to any Find a Grave entry. The original / owning contributor will review your information and act accordingly. I have never had a problem with contributors to Find a Grave wanting to make the records as correct as possible.

Family Search Indexes should automatically respond to Find a Grave corrections, rather than remain static where they cannot be corrected. This is an on-going problem that is known, but little priority seems to have been given to the need to correct bad index entries.

LegacyUser

joe martel said: It may take a while to update the FindAGrave indexes. They are loaded into the FS search system in large batches and is dependent on when they send a new load and then to pipe that in.

LegacyUser

Beth Macdonald said: Thank you both. I've made contact with the 'creator' of the memorial. He's found a woman with a similar name, same age, in a nearby state and, so far, insists that she is my great-grandmother. He's even invented a middle name for her in the last couple of days. I hope that I can convince him that he's wrong.

It's good to know, Joe Martel, that if/when it finally is correct on FindAGrave, it eventually will be corrected at Family Search.

LegacyUser

Tom Huber said: That's wonderful to know that Find a Grave corrections will eventually make it into the Family Search index.

LegacyUser

Brett said: FamilySearch

Help.

The the Name on the "Find.A.Grave" Record (ie. Memorial) is correct (well, as correct as can be with "Find.A.Grave"); as, I created the Record in "Find.A.Grave" back in July 2016.

But ...
That said ...

The Name in the (so-called) "Index" record in "FamilySearch", is way off!

In the (so-called) "Index" record in "FamilySearch", after her 'Given'/'Christian' Name (which is correct), the remainder of of her Name is a combination of that of her "Maiden" 'Family Name'/'Surname' and the 'Family Name'/'Surname' of one of her Son-In-Laws!?

Whereas, there is NO reference in that (so-called) "Index" record in "FamilySearch" to that of her "Married" 'Family Name'/'Surname' which is the 'Family Name'/'Surname' of, both, her Registered, "Death"; and, "Burial"!

There is NO reference (anywhere) in the "Find.A.Grave" Record to the 'Family Name'/'Surname' of that of her Son-In-Law.

But, there IS a reference in the "Find.A.Grave" Record to, both, her "Maiden" 'Family Name'/'Surname'; and, that of her "Married" 'Family Name'/'Surname'.

So, as such is the case, HOW does a Record from "Find.A.Grave", get so badly (so-called) "Indexed" in "FamilySearch"!?

Worst thing is there is NO way to CORRECT the Index ERROR - as, the "Find.A.Grave" Record (ie. Memorial) is CORRECT.

How can the (so-called) "Indexed" Record in "FamilySearch" be so far off?

Plus, just so it does NOT get raised as a possible reason, that "Find.A.Grave" Record appears to have been loaded into "FamilySearch" back in September 2016 - a few Months AFTER I created the Record in "Find.A.Grave".

Any thoughts.

Any reasons for the ERROR.

I am totally baffled.

'Thank You' in advance.

Brett

.

LegacyUser

Jeff Wiseman said: The only thing I can think of is that the Find A Grave record loaded into FS in 09/2016 was an index record. That would indicate that the actual act of indexing those find A Grave memorials would have taken place long before the final Find A Grave INDEX file was loaded into FamilySearch's database. I would assume that FS does NOT own that Index.

All I know is that the values in the Find A Grave index have NOT all come from the photo of the headstone. I.e., there are no sources for them, so they cannot be used as sources

LegacyUser

Brett said: Jeff

'Yes', I had considered that; but, as there is NO reference (anywhere) in the "Find.A.Grave" Record to the 'Family Name'/'Surname' of that of her Son-In-Law, I am at a loss as to how it got so badly indexed in the (so-called) "Indexed" Record in "FamilySearch"!

Hence, my question.

Brett

.

LegacyUser

Justin Masters said: I'm not sure it makes it into attached sources though, does it?

LegacyUser

Justin Masters said: I think the short answer is (as Joe explained), the Findagrave data is "slurped up" every once in a great while. Meanwhile, what you see in FamilySearch is a "snapshot" of what it looked like at the last "data slurp" (I'm trademarking that. LOL)

Until the next data slurp... you're going to see the OLD "point in time" info.

LegacyUser

Brett said: Justin

Sorry, to have missed your latest post (after mine of 18 Hours ago), we have been at the "Temple" all day and night.

'NO', the Original DATA in the "Find.A.Grave" Record BEFORE given to "FamiilySearch" was OK (and, still is), nothing to do with the "Dump" from there to "FamilySearch"!

The problem/issue seems to be bad indexing in the (so-called) "Indexed" Record in "FamilySearch" - nothing to do with what was, in; or, from, "Find.A.Grave"!

There seem to be something else at play,

What I am really trying to find out is; IF, the DATA from "Find.A.Grave" is MANIPULATED in ANY, way; shape; or, form; BEFORE it appears as the (so-called) "Indexed" Record in "FamilySearch"!?

In this case SOMETHING, SOMEWHERE, has gone astray ( way, way, astray)!

Brett

.

LegacyUser

Justin Masters said: Sorry if I misunderstood Brett. I am aware that there is some standardization that goes on. This is evident in that Findagrave insists on using the word "county" in putting the county level designation in a place field. That disappears in familysearch.

I'm rushed for time right now, so I can't review what the original complaint was.

"Temple" in quotes? Perhaps you can elaborate later...

oh wait... after I saved this and went on for a minute... you might have been "praying at the throne"..

no need for elaboration. I hope you have a better day.

LegacyUser

Tom Huber said: Glancing through the above and from my experience with thousands of burial records over several years:

1) The FamilySearch index for Find a Grave records comes from Find a Grave.
2) FamilySearch tweaks that index by erroneously adding a burial date entry to its index, even though Find a Grave contains no burial date.
3) FamilySearch also tweaks the place by removing the word "county" where it appears.
4) FamilySearch adds the 'tweaked' place name to the cemetery name from Find a Grave's record.
5) FamilySearch (as Justin correctly points out) performs a periodic 'data slurp', then tweaks the index.
6) The time between slurps is inconsistent and months in length.
7) We have no way to tell when FamilySearch performs its 'slurps' and subsequent 'tweaks' to Find a Grave's index.

LegacyUser

Juli said: Justin, Brett uses quotation marks on everything. I don't know what he thinks they mean.

LegacyUser

Tom Huber said: I have complained about Brett's excessive use of quotes, since they often make his posts very difficult to read. I'm not sure why it does this, since they appear to be used in place of italics, underlines, and bold type. It just appears to be a habit and as such, I no longer complain. All of us have our own idiosyncrasies.

LegacyUser

Juli said: I haven't paid close attention, but add somewhere in that list that FS sometimes fails to get the names from the correct fields on Find a Grave. For example, I entered the Find a Grave entry for my grandmother, with her complete name as it appears on the gravestone:
https://www.findagrave.com/memorial/1...
On FS, this somehow turned into just her surname:
https://www.familysearch.org/ark:/619...
(And the location has a gibberish HTML entity in place of the long ő at the end of temető "cemetery".)
Like Brett's, this error cannot be attributed to timing or stale data: prior to my entering it, there was no entry on Find a Grave, and the entry has never been changed on Find a Grave. The transfer to FS did something wrong.

LegacyUser

Tom Huber said: I think most tweaking is by computer routine, which likely messed things up. FamilySearch needs to do something to make sure that errors like these do not occur.

LegacyUser

joe martel said: I have just briefly scanned this really old thread that has been replied to yesterday. Perhaps it would be better to create a new thread describing the issue today along with a URL to show the problem.

LegacyUser

A van Helsdingen said: I agree. It can be very difficult to decipher all his quotes and CAPITAL LETTERS.

LegacyUser

Brett said: Joe

I purposefully looked through previous posts, like I always do.

I found this post.

'Yes', it is an OLD post.

But ...
That said ...

The Problem/Issue from OVER 4 Years ago DOES NOT seem to have been addressed/fixed.

Hence, WHY I "Resurrected" this post.

I am at a loss as to how the "Find.A.Grave" Record got so badly indexed in the (so-called) transition of the "Indexed" Record in "FamilySearch"!!!???

Brett

ps: Hence, 'NO' need for a NEW post.

.

LegacyUser

Brett said: Each to their own.

If you do not like my "Style"; then, you DO NOT have to, "Read"; and/or, "Respond".

LegacyUser

David Newton said: It's not just stylistic though. It's incorrect usage from a grammar and syntax point of view. It's incorrect usage from a readbility point of view.

Beyond that it simply looks silly and makes you seem to be extremely self-absorbed, pompous and pretentious. It doesn't do your credibility any good.

LegacyUser

Brett said: David

We can all be "... extremely self-absorbed, pompous and pretentious ..." at times.

You do not seem to care how you come across; well, in fact, neither do I.

Honestly, I do not give 'two hoots' what others thinks of my credibility ...

I am just happy helping, were I can.

I have better things to do than 'whinge' about others 'style'.

I certainly do not like others 'style', just try not to dwell on it.

Obviously, some others having nothing else better to do.

Brett

ps: Certainly not going to make me change my 'style'.

pps: Each to their own - read it or not, I care not.

.

LegacyUser

Justin Masters said: Hey guys (addressing everyone) take a look at what's going on. People pointing out and criticizing other saints on a forum where we're supposed to be helping one another in furthering the work of our Heavenly Father...

Is this really what we want to be doing in the cause?

LegacyUser

A van Helsdingen said: Justin, I am not a 'Saint'-i.e. a Latter Day Saint. I do genealogy with secular motivations, not religious ones. Please do not input to me a religion I do not belong to. Thank you.

LegacyUser

Brett said: Justin

So I thought.

It is O.K., I have a reasonably 'thick hide', all 'water off a duck back' to me.

And, in fact, I do "Genealogy" or "Family History" (as we Members of the Church call it) for, both, 'secular' and 'religious' reasons/motivations/beliefs.

I was doing "Genealogy" long before I became a Member of the Church, you might say I have 'the best of both Worlds' ...

Brett

.

LegacyUser

Brett said: Juli

We are not alone ...

Findagrave database links not being updated
https://getsatisfaction.com/familysea...

Brett

.

LegacyUser

terry blair said: There is also an issue with records that have been deleted on Findagrave, but they continue to appear on FSFT.

LegacyUser

Brett said: Terry

'Memorials' that have been "Deleted"; OR, would that be "Merged"/"Combined"!?

I had not even considered that.

But, the "Up-Dating" of such "Sources" ALREADY in "FamilySearch" has ALWAYS been a problem/issue in "FamilySearch".

I have submitted countless requests to "FindMyPast" to correct Records, for which they have subsequently done; but, those Corrections (ie. "Up-Dates", have NOT (and, possibly, never will) appear in "FamilySearch".

Although, I believe that "FindMyPast" has sent/provided "FamilySearch" with those Corrections (ie. "Up-Dates").

Of course, the problem/issue being HOW to you "Up-Date" such Records (ie. "Sources" ALREADY in "FamilySearch".

Brett

ps: WHY I resurrected this post, was to find out HOW the ORIGINAL (ie. Unchanged, NOT "Up-Dated") "Find.A.Grave" Record got so BADLY indexed in the (so-called) transition of the "Indexed" Record in "FamilySearch"!?

.

LegacyUser

Ron Tanner said: Cremation is available in Other Information

LegacyUser

Brett said: Ron

I am totally confused with your "Reply", what has "Cremation" got to do with this matter, at hand, about the HOW the ORIGINAL (ie. Unchanged, NOT "Up-Dated") "Find.A.Grave" Record got so BADLY indexed in the (so-called) transition of the "Indexed" Record in "FamilySearch"!?

Brett

.