Skip to content

Explain that issues can arise after 'check'- development #1239

Description

@paris-dp

Background

Oli and I have agreed that the proposed content makes sense in the check confirmation page (there are two versions of this, one if a user checks a file and one if a user has checked a URL and can continue to provide this).

Ticket containing design discussion

Content to be added to both versions of the check confirmation page:

3. After you provide your data

We continue to check your data after you provide it.

We may identify new issues after you provide your data if:

  • we can no longer access your endpoint URL
  • you update the data at your endpoint URL

We may also identify issues when we process your data. For example, datasets that are linked together by a field will have an issue if those fields do not match.

You can review your data using the check and provide planning data service at any time.

How this should look

This is one version of the confirmation page for reference (when a user has checked a URL)

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    Status
    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions