-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show more dataset info #18
Comments
I think we need at least:
@benjystanton was wondering about publication date too. Indeed something like "latest reference period" (i.e. date of last observation) might be really useful for comparison (which is most up-to-date?). We can possibly wait for the coverage metadata. |
Yeah I think publication date is really useful. Users need to know "is this the latest data?" so we often need a few bits of information to help understand that. E.g. If something was published 11 months ago but it's only published annually then it's still the latest data. So anything we can to help them answer this question would be great. |
We've since added description and today I've added publisher label and altlabel (typically has the acronym). |
The question "is this the latest data?" is tricky to answer!
We should aim to show the publication-dates and observation-ref-dates side-by-side. We can reveal this once the upstream dataset tracking (https://github.com/Swirrl/cogs-issues/issues/35) and coverage metadata (https://github.com/Swirrl/cogs-issues/issues/92) are loaded. This will be really useful for OOK as we can show how robustness comes at the expense of recency - a key dataset-choosing criterion. We could load the metadata showing when the cubes were modified on IDP but I think it would be misleading (just because the cube was re-loaded, it doesn't follow that the data itself was any newer). I suggest we leave this issue open until those upstream ones are resolved. |
Right now selecting some codes just fetches the dataset id and the count of observations that match. We should also fetch the labels, descriptions, or whatever other information is relevant. Also generate the right urls so the "View data" buttons actually link to PMD.
The text was updated successfully, but these errors were encountered: