Skip to content
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

Question/correction regarding example https://co-cddo.github.io/ukgov-metadata-exchange-model/assets/examples/Dataset-os-postcodes-datset.yaml.json #69

Open
PeterParslow opened this issue Nov 6, 2023 · 1 comment
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed Model

Comments

@PeterParslow
Copy link

Feedback on Dataset

Describe the bug
It's great to give examples, and I'm fine with them being in "RDF / YAML / JSON" format.

My question concerns how the examples were created and whether this on in particular could be fixed. It declares its similarity to https://www.data.gov.uk/dataset/2dfb82b4-741a-4b93-807e-11abb4bb0875/os-postcodes-data and that appears to be the source of much of it.

BUT: the MEM example states that the OS CodePoint Open dataset is published by "department-for-work-pensions" whereas the Data.gov.uk source states (correctly) that it is published by Ordnance Survey.

To Reproduce
Steps to reproduce the behavior:

  1. Go to
  1. look at the "publisher" property
  2. compare it to the publisher shown if you browse to the URL given as "identifier"
  3. See error

Expected behavior
Credit dataset to correct publisher

Screenshots

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@AlasdairGray
Copy link
Contributor

You are right, it would be clearer to a wider set of users if we updated this example to be published by OS.

The background here is that this was originally based on a record in the DWP catalogue, but was then supplemented with information from the data.gov.uk entry in order to provide realistic values for each of the properties in the metadata exchange model. It would be cleaner and more accurate to update the rest of the values to be based on the data.gov.uk entry rather than some weird hybrid record.

@cyberdudeuk cyberdudeuk added documentation Improvements or additions to documentation help wanted Extra attention is needed Model labels Nov 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed Model
Projects
None yet
Development

No branches or pull requests

3 participants