-
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
API #82
Comments
Hey @iltempe - cool idea! That was the sentiment behind #34, which uses the data.json specification. You can see your at http://iltempe.github.io/opendatagentediprato/data.json |
Yes! i've seen. My idea is to develop the API folder to create a complete API! have you some suggestions? |
Oh, I see. The only problem with that is that you can't generate an individual json file for each dataset because we're already generating an individual html file for each one, and you can only generate one file per collection item. We discussed that a bit in #72, but @Floppy has an interesting idea that may work out for it. |
I'm also currently proposing and working on an enhancement to Jekyll to allow >1 output file per item, in multiple formats, that would enable exactly this: jekyll/jekyll#3041 (WIP PR in jekyll/jekyll#4742) |
Nice! at the moment with solution like mine I think is possible create a single JSON file also making some query on datasets, for example to see all datatets of certain categories. |
Oh, awesome @Floppy! I ruled that possibility out after reading jekyll/jekyll#1305. Really looking forward to your PR being merged. |
I'm a bit confused: is there actually an unmerged PR linked to this discussion? |
No, and I never managed to get round to doing the Jekyll work I was doing that might have helped make this happen, unfortunately. Maybe one day when I retire 😆 |
HI! I've implemented a simple reading API to have access via http to all datasets and metadata.
You can look at this at http://iltempe.github.io/opendatagentediprato/ going to link http://iltempe.github.io/opendatagentediprato/api/datasets.json
regards!
The text was updated successfully, but these errors were encountered: