Programmatic access of data quality metrics and submit.planning.data.gov.uk statuses #389
jessicamcinchak
started this conversation in
Ideas and feedback
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi ! As a longtime consumer of Planning Data, we (the PlanX team) are excited about the work happening on the "Submit & update your planning data" subdomain around measuring the health of an organisations published datasets and would like to query (and even possibly contribute to!) some of these metrics via API.
Here's two examples:
GETUser story: As a council building digital services on PlanX, I want to understand if my Planning Data integration is healthy, so that I can feel confident that applicants are going to be presented with accurate information about constraints that apply to their application.
Context: PlanX is a platform for building digital services. Specifically, these digital services query publicly available data like planning constraints whenever possible to prevent the number of questions & external research prompts that need to be put to applicants.
As planners build and test their services overtime, they often spot inconsistencies or inaccuracies in their own data but don't always understand how or where to troubleshoot these issues. We want to raise their awareness of their Planning Data "organisation" submission pages. Currently we provide a simple link to this page - eg this external link points to https://submit.planning.data.gov.uk/organisations/local-authority:SWK

Idea: Within the PlanX editor, we could show additional "Needs attention"-type notification badges directly on this external link if we could query some of the top-level quality statistics like "number of datasets submitted", "number of errors", "needs fixing" etc. Beyond this organisation-level menu, we'd also be excited to access dataset-level quality metrics within a given organisation which we could display when editors are selecting which constraints they'd like their service to check (and help discourage them from going "live" before a given dataset is healthy)
POSTissue_typecodelist could possibly include an "informational" value like "User feedback". The request body might include: the specific PD entity ID of the inaccurate record, a freetext "reason", timestamp when it was received, and PlanX "source" service name. We would not intend to include any personally identifiable information about the applicant.Thanks for considering !
Beta Was this translation helpful? Give feedback.
All reactions