When issues appear in the dataset issues detail page we need to ensure the wording is clear and understandable by users.
Issues might affect a whole dataset (eg a missing column, missing values in an entire column or invalid data in an entire column) or they might affect individual rows.
A dataset might have multiple different types of issues.
Problem statement
LPAs need to know what issues they need to fix in their datasets
User stories
As an LPA
I need to know what issues exist in my dataset
So I can understand what I need to do to improve my dataset
As an LPA
I need to know how many rows and fields are affected by issues
So I know how many problems there are
What
When issues appear in the dataset issues detail page we need to ensure the wording is clear and understandable by users.
Issues might affect a whole dataset (eg a missing column, missing values in an entire column or invalid data in an entire column) or they might affect individual rows.
A dataset might have multiple different types of issues.
Problem statement
LPAs need to know what issues they need to fix in their datasets
User stories
As an LPA I need to know what issues exist in my dataset So I can understand what I need to do to improve my dataset
As an LPA I need to know how many rows and fields are affected by issues So I know how many problems there are
Acceptance criteria
Known Artefacts
I have extracted all the issue types from the database here: https://docs.google.com/spreadsheets/d/1hvffB4LuHEHR2WutAxp98CzG0WsZJFlx-2VmGeIM5Yk/edit?gid=813787384#gid=813787384
Current Design
https://design-sprint-prototype-8e5ca5d98540.herokuapp.com/overview/v2/local-authority:CAT/dataset/article-4-direction-area/error/349b331a9edfb8c64d03439a69a2dd1da841675d3becfa04c9e8755b287db090/invalid%20date
Linked Tasks