New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

BUG: Invalid date discovered #666

Open

2 tasks

afred opened this issue Jul 7, 2022 · 0 comments

Contributor

afred commented Jul 7, 2022 •

edited

Loading

To Reproduce

This record has a bad date of "2032-05-22"

Expected behavior

should have a valid date

Background

Since most records in AMS2 come from ingest, start there. Specifically, look for whether:

was the input data valid to begin with, but translated improperly?
was the input data missing, and faulty logic injects a bad default date?
was the input data invalid to begin with, and AMS2 just took it as-is?

Done when

We've determined the source of the bad date
if the fix is simple, then fix it. Otherwise, make an explicit ticket for the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment