Skip to content

ambiguous birthdate years should not be future dates #237

@ericbuckley

Description

@ericbuckley

Summary

When parsing birthdates with ambiguous years, eg 2/19/40, we should assume it's a date in the past (1940) and not the future (2040).

Impact

Incorrectly parsing the date leads to poor BIRTHDATE matches when comparing records.

Expected behavior

When a date is parsed with a 2 digit year, we should always assume it's in the past. 2/19/40 == Feb 19th 1940. When possible, we should assume the current century and not every 2-digit year should be interpreted as the 20th century. For example, 5/15/04 == May 15th 2004 and not May 15th 1904. Additionally, we should be rejecting all values that are clearly future dates, eg 2050-01-01 or dates that are more than 150 years old eg 1885-01-01.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No fields configured for Bug.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions