Skip to content

Update designs for multiple endpoints #1059

@alextea

Description

@alextea

The design pattern for displaying endpoints should be updated to make it clearer to users which are their latest and which can be retired.

Each endpoint should display the following information:

  • Endpoint number (oldest active endpoint should be GitHub workflows #1, each additional endpoint should get an incrementing number)
  • Endpoint URL
  • Website URL (the source documentation URL the LPA submits with the endpoint)
  • Date added (the date the endpoint was added to the platform)
  • Endpoint last accessed (the date and time the platform last accessed the endpoint)
  • Endpoint last updated (the date the platform detected a change in the data)
  • Licence (should show whether the data is licenced using OGL)

The Edit and Retire links can be ignored for now. It is unlikely that LPAs will need this functionality regularly enough to warrant the development costs.

Acceptance critera

  • use the summary table component for displaying endpoints.
  • only display active endpoints
  • endpoints should be ordered by date added in descending (newest first) order.
  • if there are HTTP errors accessing endpoints then these should be displayed and highlighted as shown

Designs

Prototype link: https://provider-design.prototype.planning.data.gov.uk/multiple-endpoints/organisations/local-authority:PLY/conservation-area/

Image

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

Done - Consider for Weeknotes

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions