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

Use data.json as dataset model/yml #34

Closed
JJediny opened this issue Mar 24, 2016 · 5 comments
Closed

Use data.json as dataset model/yml #34

JJediny opened this issue Mar 24, 2016 · 5 comments

Comments

@JJediny
Copy link
Contributor

JJediny commented Mar 24, 2016

This would allow Data.gov to register data from future forks:

@timwis
Copy link
Owner

timwis commented Mar 24, 2016

👍 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.

@timwis
Copy link
Owner

timwis commented Mar 28, 2016

👍 sold on using data.json as the schema for JKAN. Posting this here for reference:

https://project-open-data.cio.gov/v1.1/metadata-resources/

This was referenced Mar 29, 2016
@aborruso
Copy link

aborruso commented Apr 2, 2016

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

@timwis
Copy link
Owner

timwis commented Apr 3, 2016

Wow @aborruso, that's a really cool project idea! Thanks for pointing it out!

@timwis
Copy link
Owner

timwis commented Apr 3, 2016

Resolved by befd4e0

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

No branches or pull requests

3 participants