Suggestion 102 Death in future

Date: 1 Apr 2016
Location: Worldwide
Surnames/tags: data_doctors db_error_102

Description of Error - 102: Death in future

Death date is in the future. The most common cause is a typo in the death date. This is checked on all profiles where a death date is recorded.

Content of info column: Empty.

Possible Causes

• The most common cause is a typo in the death date.

Action Steps

Edit the death date by:

1. Correcting the typo based on information found in the profile.
2. If no information is found, look for a source that will have the correct death date. Add a citation for this source to the profile.
3. If no source can be found, use a reasonable guess based on a date of birth or marriage or the birth/death date(s) of family members. Mark the date as "Uncertain."
4. If the profile has no sources and no relatives, delete the impossible death date. {if this leaves the profile with no date, it is important to add a note in the profile regarding what was in the date field and why it was removed}

Note: All of these profiles will be private. If you are not the Profile Manager or on the trusted list, you will need to post a message on the profile for the PM.

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_102.

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

Technical Stuff

1. When the full date is entered the date must not be in the future, compared to the date of the most recent database dump.
2. When an incomplete date is entered all missing components (day, month) will be assumed to have value 1 for comparison purposes. So 2016 would for this purpose be assumed to be January 1, 2016. May 2016 would be assumed to be May 1, 2016.
3. The death date in private profiles is available for validation only in decade format, i.e. date 2017-01-01 is decade 2010. In this case, all decades up to and including the current one are considered valid.

Suggestion reports

You can see the weekly prepared list of the latest suggestions prepared on April 21st 2024. You can also get the online report on WikiTree+.