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

Create a data validation protocol to minimize human error and bias #89

Open
4 tasks
theecrit opened this issue Feb 14, 2022 · 0 comments
Open
4 tasks
Labels
comments wanted Extra attention is needed documentation Improvements or additions to documentation

Comments

@theecrit
Copy link
Contributor

Description

Manually pulling data from PDF into structured spreadsheets introduces the potential for human error and bias. We can reduce this potential by maintaining a process for pulling, reviewing, and publishing data.

Proposed solution

  • Start with another brigade's process or other frameworks and adapt. The only alternative I can think of off-hand is to start from scratch, which is a larger lift.

Things to consider:

  • Pulling data, reviewing data, and publishing data each introduce particular challenges. Are there other stages that should be addressed?
  • Some ideas:
    • Use forms validation, conditional formatting, etc during data entry to help catch errors as they occur.
    • Require each handler of data to complete a short checklist that triggers a "gate unlock" to the next step on completion (eg you can't skip a step when handing off).

To close this issue, the following conditions should be met

Check off as you go to track progress. This list can be changed and/or broken out into individual issues during the discussion phase if needed.

  • Team discussion on the issue, with key decisions documented in the comments (even if just a summary of asynch or live conversation).
  • Draft protocol created and documented.
  • Draft protocol shared with brigade and publicly via OO channels for comment.
  • Protocol revised and published publicly (at minimum, with project documentation).
@theecrit theecrit added comments wanted Extra attention is needed documentation Improvements or additions to documentation labels Feb 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comments wanted Extra attention is needed documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant