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

Adds jekyll-get plugin #83

Open
wants to merge 10 commits into
base: main
Choose a base branch
from
Open

Adds jekyll-get plugin #83

wants to merge 10 commits into from

Conversation

JJediny
Copy link
Contributor

@JJediny JJediny commented Apr 9, 2016

Optionally Plugin to get dataset.json and data.json from another instance of JKAN to cache and potentially use on another site

@JJediny
Copy link
Contributor Author

JJediny commented Apr 9, 2016

See #77 for context

@timwis
Copy link
Owner

timwis commented Apr 9, 2016

Thanks for the PR! This sounds really interesting but I'm a little confused about how you'd use it. I assume it's something you'd need to do on the command line since github pages doesn't support plugins, but would you mind elaborating a bit? or do you have an example you're using somewhere?

@dportnoy
Copy link

Fascinating! Let's see if it takes off.

@JJediny
Copy link
Contributor Author

JJediny commented Apr 12, 2016

@timwis my taught on this is that someone could run jekyll build to pull in a json file either from a JKAN and/or CKAN API or agency.gov/data.json... and push the file created local into the git repo

While gh-pages doesn't support plugins its not needed as the json is committed as a new file for use in the site. One could potential use this to mash up datasets remotely host with those on their JKAN... or maybe offer a search functionality that includes those remote datasets along with those on JKAN.

@patcon
Copy link

patcon commented Apr 25, 2016

If I'm understanding correctly, I really like this idea!

Slight aside for my context:

My city currently has a few competing data portals, and we're building community one to boot. I think I can perhaps convince one of the portals to use JKAN. The other is eventually migrating to CKAN. It would be nice if our community one could pull in /data.json files from each so that all our datasets show in one place, without requiring massive amounts of bureaucratic collaboration :)

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

Successfully merging this pull request may close these issues.

None yet

4 participants