Calculate and visualize timeliness separately from the data quality score

[georgiana-b]

Currently timeliness can be optionally included in the data quality score. @jobarratt proposed that timeliness should be calculated and visualized separately.

• Pros:
  • cleaner handling of timeliness since integrating it in the current scoring algorithms is a bit forced
  • makes scoring more transparent for users
• Cons:
  • adds some complexity to the dashboard

As I imagine this, we would add a column months_late and display that number in the dashboard in a pretty and colorful way.

[jobarratt]

To explain a little more about my thinking is for a lot of reasons it does make sense to have a general 'open data' score which would naturally, i think, include timeliness. But from a purely Frictionless Data point of view, this would obscure one of the issues we are trying to solve, which is getting people to improve their workflows and understand the quality of the data.

[georgiana-b]

Since it's a bit unclear, the issue is about data-quality-cli scoring algorithms, so also " from a purely Frictionless Data point of view".