no image

Data Error 579: FindAGrave - Missing birth location

Privacy Level: Public (Green)
Date: 27 Mar 2017
Location: Worldwidemap
Surnames/tags: data_doctors db_error_579
This page has been accessed 570 times.

Categories: DD Suggestions Help.

Description of Error - 579: FindAGrave - Missing birth location

This WikiTree profile has a no birth location but FindAGrave has one.

Content of info column: Birth location used at Find A Grave

Possible Causes

No birth location entered in Wikitree

Action Steps

There are few possible actions:

  • Wrong link to FindAGrave. It is possible, that wrong FindAGrave memorial was matched to this wikiprofile. In such case, you can add a link to the correct FindAGrave memorial if it exists. If it doesn't set status to False error.
  • Error in FindAGrave. Mark error as false error.
  • Error in wikitree. Enter birth location in wikitree and error should be gone on monday. FindAGrave gives you the possible birth location but try to find other sources. If Find A Grave has a gravestone picture then that could be a source for a birth location. If no picture of a gravestone exists on FindAGrave, you can request it there. How to request a grave picture at FindAGrave

Error Status

For each Error you can set status. You can set it as Corrected, Not corrected, False Error, Proposed merge or just add a Comment.

If there are related errors for the profile, you will also see them on status page.

Full description is available on Status Help Page.

Questions and Discussions on this Error

You can read what other people have asked here db_error_579.

You can also share your best practices, experiences, problems about this Error by posting a questions in G2G. If you create a new G2G discussion for this Error add tag data_doctors and db_error_579.

Technical Stuff

All identified links to FindAGrave are compared to profile data. Link is identified by extracting memorial number from link, template or text Memorial #

Comparison is done by following rules:

  • If name is exactly the same, it is considered a match.
  • If it is a small difference, dates are also compared and if they are the same within 1 year, it is considered a match.
  • If it is a medium difference, dates are also compared and if they are exactly the same, it is considered a match.
  • If none of the conditions apply it is considered not identified.

All profiles where profile matches memorial on FindAGrave are checked for missing birth location. This is checked only if there is a birth location entered on FindAGrave.

This page is part of the Data Doctors Project.
Latest report: February 10th 2019 and the Spreadsheet.
Custom reports by: Suggestion lists, Unsourced lists, Unconnected lists.
See WikiTree+ for custom reports and statistics.
Data Doctors Challenge: Dates_VIII .







Collaboration

On 10 Nov 2018 at 19:01 GMT Lance Martin wrote:

I responded to Elizabeth

On 10 Nov 2018 at 18:48 GMT Elizabeth (Jones) Dallmann wrote:

I don't get this. I look at the FaG and it has the same death / burial location that I have. Which has been backed up by other sources as well. Why is it appearing?

On 30 Aug 2017 at 20:55 GMT Lance Martin wrote:

That is precisely it. Lacking any conflicting information, the information that has been available should be shared at Wikitree. Then, when someone does more research, and can prove or disprove it with a better source, that can be done on the profile. I have entered literally thousands of profiles on Wikitree. Some are sourced very well, some only have a source that is as poor as an ancestry tree or Find A Grave. Looking at them, you and I will know, that the information is not reliable, but having even the littlest information available can be very helpful to someone working on a related profile or family.

On 30 Aug 2017 at 20:50 GMT Russ Dill wrote:

Except that many people on FaG just fill in the birth location as a guess, usually just by copying the death location. I suppose if this incorrect information leads to the creation of duplicate individuals on WikiTree the profiles can be merged later.

On 30 Aug 2017 at 20:44 GMT Lance Martin wrote:

That is on point. I would agree the birth location should be blank if it is blank at Find A Grave. If Find A Grave has a value, it should be copied over if there is not a better source.

On 30 Aug 2017 at 20:36 GMT Russ Dill wrote:

That sounds good for death location. it's uncommon for someone to be buried somewhere other than where they died and or lived. But birth location is something different. FaG may say Tennessee, but the person was actually born in England. Also birth location is very important for searching records, especially census, and helping to differentiate between individuals born around the same time with the same name.

On 30 Aug 2017 at 17:28 GMT Lance Martin wrote:

Actually Russ in this case, barring any better sources, Find a grave is a source. The location should be marked as uncertain until a better source can be found. what this does is gives researchers a place to start in further research. It also help people from other countries in eliminating names to look at if their person of interest never came to the location. As wikitree grows and more people join from around the world, having a least a residence burial place or some other information listed in quick list of profiles is going to be vital to limit the number of profiles one has to cross che k to eliminate possible duplicates. By leaving location fields completely blank, it makes a researcher click through to each profile to determine if there is a possible clue as to what continent.

On 30 Aug 2017 at 17:14 GMT Russ Dill wrote:

I really disagree with this one. It's encouraging people to input information from findagrave that's unsourced.

On 24 Jun 2017 at 20:06 GMT Martha (Beaugh) Leger wrote:

tried to correct. if not right then I do not know of any other way to correct. if someone else corrects it & then send me info on what they did then next time I would know how to correct it.