Skip to content
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.

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

Research issue: Come up with a way of proactively assuring data quality of high profile committees after filing deadlines #2939

Closed
2 of 3 tasks
jwchumley opened this issue Feb 20, 2018 · 0 comments
Assignees
Milestone

Comments

@jwchumley
Copy link
Contributor

jwchumley commented Feb 20, 2018

This is a research task to create a plan for checking high-profile reports as they come in. Can we set this up as a new relic test? What should we test? This will be an ongoing process we build on, so our results don't need to be comprehensive.

  1. Entirely in FECP - checking for issues after nightly load such as:
  • Amended report has vastly different number of transactions compared to previous report
  • Ops log pass3 entry date is done but number of transactions obviously disagrees with number of pages
  • etc
  1. Between FECP and PG (I think this is already in place making sure data transfer has no issues)
  2. Entirely in PG
    • Using Operations log pass 3 entry done date to know when to test for transactions added to API
    • Comparing base tables with API output
    • Check count of filings each day

Completion criteria:

  • In FECP: Figure out what to check?
  • Between FECP and PG is it already being checked or do we need more checks there?
  • In PG Figure out what to check and how to check it
@jwchumley jwchumley added this to the Sprint 5.2 milestone Feb 20, 2018
@AmyKort AmyKort changed the title Come up with a way of proactively assuring data quality of high profile committees after fling deadlines Come up with a way of proactively assuring data quality of high profile committees after filing deadlines Mar 15, 2018
@AmyKort AmyKort modified the milestones: Sprint 5.2, Sprint 5.3 Mar 15, 2018
@AmyKort AmyKort changed the title Come up with a way of proactively assuring data quality of high profile committees after filing deadlines Research issue: Come up with a way of proactively assuring data quality of high profile committees after filing deadlines Mar 15, 2018
@AmyKort AmyKort modified the milestones: Sprint 5.3, Sprint 5.4 Apr 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants