Skip to content
This repository has been archived by the owner on Jul 14, 2024. It is now read-only.

Data quality #111

Open
mdutoo opened this issue Oct 9, 2015 · 0 comments
Open

Data quality #111

mdutoo opened this issue Oct 9, 2015 · 0 comments

Comments

@mdutoo
Copy link
Collaborator

mdutoo commented Oct 9, 2015

(to be spinned off in several issues)

1 a priori data quality, using an evented business rules engine.

  • OPT conf'ble behaviour when fails: HTTP error, kept but with odq:valid={failed, timestamp} Data quality - incomplete data (Model non-compliance properties) #21 , kept but only in contributions...
  • either custom using ex. Javascript engine and conf + test web UI in DC Playground, OR / AND by integrating an existing Data Quality solution (ex. Talend) or separate components (ex. Google Open Refine, common address checking web service...)

2 a posteriori data quality, more like business KPIs on resources / aggregation of resource data quality at top (project) level (and integrated in Playground project portal, OPT with high level quality threshold alerts), or for models that don't have a priori DQ enabled

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant