-
Notifications
You must be signed in to change notification settings - Fork 311
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
Use data.json as dataset model/yml #34
Comments
👍 Good idea, and thanks for the example, that's perfect! Isn't there a table around somewhere that links POD fields to CKAN fields? I was planning on matching the CKAN schema under the hood (as much as there is a "schema" in a collection of YAML documents) since the field names are pretty human readable, but let me know if there's a case for using another schema, like POD, by default. |
👍 sold on using data.json as the schema for JKAN. Posting this here for reference: |
hi @timwis first of all thank you for JKAN: it's a great idea and a great product. I have written a blog post in Italian (my language) about it and a friend of mine, after reading it, created a JKAN portal. Moreover he is creating an italian how-to guide. But I'm off-topic. About github and publishing using "official" open data schema I think it's useful to look ad git-data-publisher Best regards |
Wow @aborruso, that's a really cool project idea! Thanks for pointing it out! |
Resolved by befd4e0 |
This would allow Data.gov to register data from future forks:
The text was updated successfully, but these errors were encountered: