Repository navigation
Documentation update across data quality pages - #464
Merged
Merged
Conversation
| Importantly, being non-authoritative is **not** a hard cap on the rest of the score — a non-authoritative provision can still independently reach _trustworthy_ (level 3) if its data quality is otherwise clean. Authoritative status only ever determines which half of the scale a provision sits in (1-3 vs 4-6), not whether it can reach the top of its half. | ||
| Authoritative status determines which half of the scale a provision sits in: 1-3 for non-authoritative provisions, 4-6 for authoritative ones. Importantly, this is **not** a hard cap on the rest of the score — a non-authoritative provision can still independently reach _verifiable_ (level 3) if its data quality is otherwise clean. Authoritative status only ever determines which half a provision sits in, not whether it can reach the top of its half. | ||
|
|
||
| Within each half, the specific level is set by the most severe issue found on the provision: an **error** (e.g. an invalid date) scores the bottom of the half (1 or 4); a **warning** (e.g. converting the geometry's CRS to be WGS84) scores the middle (2 or 5); and no errors or warnings scores the top of the half (3 or 6). This is our current thinking on where to draw the line between severity levels, and it may become more nuanced as the framework develops. |
There was a problem hiding this comment.
Let's use a different example for a warning here as I'm not sure conversion will remain one... Maybe flipping a long/lat?
Also, we might want to mention here that we'll also create notice tasks for some things but these explicitly won't change the quality score.
Contributor
Author
There was a problem hiding this comment.
Added those in now - thanks Ben!
| ### Determining authoritative status | ||
|
|
||
| Rather than inferring provenance indirectly (e.g. via a geospatial check against a provider's boundary), authoritative status is read directly from a signal the platform already computes: every dataset's own `entity` table carries a `quality` value per entity (`none`, `some`, `indicative`, `authoritative`, `usable`, or `trustworthy` — defined with a priority ordering in the `quality` reference table). A provision counts as authoritative if any of its entities reach `authoritative` priority or above. | ||
| Rather than inferring provenance indirectly (e.g. via a geospatial check against a provider's boundary), authoritative status is read directly from a signal the platform already computes: every dataset's own `entity` table carries a `quality` value per entity, which in practice is set to either `authoritative` or `some`. A provision counts as authoritative if any of its entities are `authoritative`. |
There was a problem hiding this comment.
This is true as of now - I think this may change when we get further into this, but no changes needed yet. Just flagging!
Ben-Hodgkiss
approved these changes
Sep 22, 2026
1 of 5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this? (check all applicable)
Description
This PR updates the documentation across the two data quality pages with:
Related Tickets & Documents