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

Data Errors Detection #25

Closed

gicaz opened this issue Feb 20, 2017 · 0 comments

Labels

next

Contributor

gicaz commented Feb 20, 2017 •

edited by Zigur

Loading

To keep track of data creation and changes:

There are three complementary approaches to be considered

Email report to a supervisor / a number of admins
Historical tables on db (administrator level, return to a previous state (operator, date, old data, changes))
Double control (supervisor, data list with check boxes: "confirmed"/"quality assured" true - false) for Quality Assurance (QA)

gicaz added the next label

gicaz closed this as completed

gicaz reopened this

Zigur closed this as completed

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