Conflict on burial for someone who was reinterred several years after initial burial
https://www.familysearch.org/en/tree/person/sources/9W3G-8Z1
John August Eriksson Sjoblom 9W3G-8Z1 died in 1900 but he was moved to another cemetery in 1933. How should this be entered to avoid the conflicting data?
Answers
-
Almost all natural statistical data can be normalized and displayed on a standard distribution bell curve:
Usually the purpose is to determine the limits of what is normal, expected, or reasonable through choosing an upper and lower limit. For burial dates, the developers of the Data Quality Checker, as can be seen from the flags, have set these limits for days between death and burial:
There is a hard stop for a burials before death. These have a non-dismissible flag because this will never be correct.
There is a soft warning for burials more than 8 days after death. These have a dismissible flag because, as in the case you have, while this is unusual it is not impossible. If you like how you have entered the burial with his final burial as the main event and the original burial noted in the reason statement, just click on the quality flag and click dismiss. Do put in the reason you are dismissing it:
The quality checker is doing what it is supposed to do. It is warning us about funny looking data that either needs to be corrected or explained. There is always going to be a balance. Set the limit too tight and there will be too many false warning flags. Set the limit too loose and too much bad data will never be flagged.
More problematic in your example is the other flag under Conflict-Free Data which is there due to that Residence in 1910 which is ten years after he died. There is no reason statement and I can't see anything in the sources to explain what that entry really is. But it is clearly not a residence. He did not live anywere ten years after he was born. That you need to fix by creating a custom event with that date and place and with full information and a source:
Then delete the residence to get rid of the data quality flag.
0



