Change issue count on LPA dashboard dataset card

CharliePatterson commented 1 month ago

Context:

We've recently changed how we handle instances where a dataset is missing an entire column, so that we're treating it as a single issue for the user to fix, rather than counting each record/entity as a separate issue.
We've changed the content on the issues tasklist page to reflect this:

However, when you view the dataset card on the LPA dashboard page, it's showing the total issue count on a 'per record/entity' basis:

I'm presuming that we should just treat this as a single issue in the count - @alextea can you confirm that's the best approach?

alextea commented 1 month ago

@CharliePatterson yes, as a single issue

gmatchett commented 3 weeks ago

Samriti Sadhu [10:28 AM] FYI - I am talking to Roland now as he messaged me with the same issue. "It looks like the two queries are addressing different issues: For the 'article-4-direction' pipeline, there are 12 entities, and each entity has issues with two fields: document-url and documentation-url. Since all rows have missing values for both fields, the total count of issues is 24. For the 'article-4-direction-area', there are 233 entities, but the issue reported in your query is a warning for invalid geometry in just one row. You can verify this here: Datasette Query. Additionally, the error count isn't displayed in your query, possibly due to an issue with the query itself. You can cross-check the results with these queries: Provision Summary Issue Summary Let me know if you need any help with this or further clarificatin

rosado commented 2 weeks ago

Moving back to dev due to performancedb changes.

digital-land / submit

Change issue count on LPA dashboard dataset card #439

Context: