Skip to content
This repository was archived by the owner on Jun 18, 2024. It is now read-only.

distribution vs accessURL in data.json metadata #16

Closed
kachok opened this issue May 10, 2013 · 2 comments
Closed

distribution vs accessURL in data.json metadata #16

kachok opened this issue May 10, 2013 · 2 comments
Labels

Comments

@kachok
Copy link

kachok commented May 10, 2013

distribution property is not part of metadata, but defined in expanded description of properties.

Not clear how multiple versions of the same dataset (e.g. JSON, XML, CSV) should be represented in data.json:
a) {"accessURL":"http://www.agency.gov/vegetables/listofvegetables.csv"} (allows only single link)
b) "distribution": [{"accessURL": "http://data.mcc.gov/example_resource/data.json", "format":"JSON", "size":"22mb"},{"accessURL":"http://data.mcc.gov/example_/data.xml", "format":"XML", "size":"24mb"}] <- there is example but not clear how to use

@MarinaNitze
Copy link
Contributor

The "distribution" field is only a concatenation of the accessURL, format, and (optional) size fields. We discussed including it as a field up top, but were concerned it would seem like "another field" to agencies when in fact it's not asking for any additional information.

You must use the "distribution" field whether the entry has 1 associated dataset or 100.

Would love to see suggestions from folks on how to make this relationship clearer.

@MarinaNitze
Copy link
Contributor

Clarified this in #44 -- provided a better example, and added distribution to the field list at the top too.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants