Where is this information coming from? Incorrect burial info or correlation
LegacyUser
✭✭✭✭
Justin Masters said: I found the following problem seen on this source linker page and personal page.
https://www.familysearch.org/search/l...
The family tree data says:
burial
Elephant, Bedminster Township, Bucks, Pennsylvania, United States
But that's not what's shown on the person's page in Family Tree here:
https://www.familysearch.org/tree/per...
Burial • •
St. John's Black Oak Ridge Cem, Snyder, Pennsylvania, USA
Can anybody figure out where this is coming from? I think it's pulling it from the wrong record.
https://www.familysearch.org/search/l...
The family tree data says:
burial
Elephant, Bedminster Township, Bucks, Pennsylvania, United States
But that's not what's shown on the person's page in Family Tree here:
https://www.familysearch.org/tree/per...
Burial • •
St. John's Black Oak Ridge Cem, Snyder, Pennsylvania, USA
Can anybody figure out where this is coming from? I think it's pulling it from the wrong record.
Tagged:
0
Comments
-
-
Gordon Collett said: All dates and places in Family Tree are stored as two separate pieces of data. The display date and place and the Standardized Value of that date and place.
If you are not familiar with this concept, you may want to take a few minutes and review this very unofficial presentation I put together.:
https://docs.google.com/presentation/...
The displayed information is what you want other researchers to read. The Standardized Value is what the computer works with for hinting, searching, possible duplicates and all other routines.
Part of making sure our relatives information in Family Tree is accurate is making sure that an appropriate Standardized Value is linked to the displayed information.
On some of the pages of Family Tree, the Standardized Value is displayed instead of the Display data, most notably here in the source linker and on the merge pages. If you hover you arrow cursor over the data in a person's detail page, a tool tip will pop up to show the Standardized Value:
or open the editing box to see it:
This information for the burial has a last edited date of June 2012, so this may have come in this way from New Family Search.
To correct this, when you know the true name of where this person is buried, open the editing box, click at the end of the place name data, then press your downward arrow key. This will open a drop down menu:
Click on the top line of the menu to keep what is currently typed and set the standard to what you see in the second line. Or click on the second line and use that to replace what is typed and also set it to the standard.0 -
-
Tom Huber said: I don't know, Gordon. There is no indication in the change log that the problem existed, other than the original entry came from the previous tree (in nFS). Going over to the Beta site only indicated that the original place had not been standardized. But there is no way the thing, if it was operating correctly should have brought up the Buck county place.
Hovering over the date produced no bubble. Opening the event with Edit showed that no standard had been selected. Dates of "Last Change" and person are the same for the beta site.
Could this be a browser problem of some sort? I'm running Chrome on a Windows 7 computer for the beta site.0 -
Gordon Collett said: No browser problem at all. I wouldn't trust what the beta site has to say about standardization, because if you look around the beta site, you will find that all the standards have vanished from there.
In any event, how the record got in this state back in 2012 is a rather moot point. The only important thing is that the record has a data problem that can easily be fixed.0 -
Justin Masters said: At this point (sometime last night) I think I went back and just changed it. There were two different counties involved, and I don't think the boundaries extended there or changed from there. (they're a hundred and fifty-ish miles away from one another.)0
-
Justin Masters said: I'm again seeing information that has no relevancy showing up in the source linker screen.
This time I'm attaching an obituary that came courtesy of GenealogyBank Obituaries, and the woman has married a number of time. The last marriage is shown as Jimmy Hancock, with a marriage date of 26 Oct 1957. (NOT ACCURATE)
https://www.familysearch.org/search/l...
I tried switching husbands... and HE shows the SAME marriage date, even though it's not accurate.
So I'm trying to figure out WHERE this marriage date is coming from, and I see it's from a COMPLETELY DIFFERENT marriage. (well, she DID marry 4 times)
So there's SOMETHING wrong with source linker and updating the screen information. It's holding on to remnants of OTHER people or events with OTHER people.0
This discussion has been closed.