Don't allow duplicate endpoint to be submitted

[Ben-Hodgkiss]

Background

When an LPA submits an endpoint URL that is already active for that provision, they currently have no clear indication that their endpoint is being collected via the pipeline every night. This can cause them to resubmit, thinking they need to do that when they complete some of the tasks - creating unnecessary tickets.

Proposed solution

When an LPA checks an endpoint URL that already exists as an active endpoint for that provision in the system, the Check tool should:

• Still show the Check Results page as normal (do not block the check itself)
• When the user moves to the next page in the flow, update the content shown.
• Prevent the LPA from submitting again via the submit action
• Instead, the next steps page should display clear, reassuring content explaining that the dataset is already in the system, updates will be collected automatically overnight, and any task list issues will be resolved without needing to resubmit

Things to Consider

• This should only show when an endpoint is active for that provision... this means, we don't want it to show if:
  • That endpoint exists but for a different dataset or organisation - i.e. combined datasets
  • The endpoint has previously been retired. In this case, we need to flag this better in the Manage Service that this needs to be unretired. This may need to be done as a separate ticket.

Acceptance Criteria

• If the submitted endpoint URL matches an existing active endpoint for the same provision, the submit button/action is disabled or hidden
• A clear message is shown on the Check Results page explaining the dataset is already live
• The message communicates that the pipeline will automatically pick up any updates from the same URL
• The LPA is not left on a dead end - the message provides appropriate next steps or reassurance
• Existing flows for new (non-duplicate) endpoint submissions are unaffected
• If an active endpoint URL is submitted for a different dataset (or organisation), the LPA can still submit this (e.g. combined datasets)

[Ben-Hodgkiss]

We want to implement this on the Confirmation page - i.e. the one that looks like this...

@oli-rose-mhclg to provide content below.

[oli-rose-mhclg]

Content below:

Data checked

What happens next

We are already collecting data from your endpoint URL, so we will update your changes automatically.

You do not need to submit your endpoint URL again.

[Return to {dataset name} overview]

[pooleycodes]

Tech Approach:

Done in Submit Repo using Datasette: Query https://datasette.planning.data.gov.uk/digital-land/endpoint/ea98ea4d156ee47ff09af98d96d09951395b58e66d8b5fff55f50e3a537ff753 and JOINT on Resource_Dataset table, compare if params dataset and url is same, then show content message.

[paris-dp]

Spoke with Oli about content and page structure.

Content

Can the content be updated to:

What happens next

We are already collecting data from this endpoint URL, so we will process any changes you make automatically.

You do not need to submit this endpoint URL again.

Return to brownfield land overview

Page structure

Currently the page has two H1s. The content in the green box 'Data checked' is a H1, so 'What happens next' should be a H2- please can this change be made?

Aware this has been built on the existing confirmation page, so including here. @gibahjoe if this is better in a new ticket let me know.

Can this also be updated on the standard confirmation page (where the endpoint has not already been submitted) so that the headings move down a level as below;

Publish your data (in the green box)

What happens next

1. Publish data to your website

2. Provide your data

So rather than looking like this:

It looks like this;