Skip to content
This repository has been archived by the owner on Dec 19, 2019. It is now read-only.

figure out how to create tiered json files #2

Open
gbinal opened this issue Oct 23, 2014 · 5 comments
Open

figure out how to create tiered json files #2

gbinal opened this issue Oct 23, 2014 · 5 comments

Comments

@gbinal
Copy link
Contributor

gbinal commented Oct 23, 2014

This is the hard part.

With the v1.1 schema, even the simplest of agency data listings will have multiple dimensions (see diagram and example file).

Questions:

  • Can the jsonify command be modified so as to somehow account for that?
  • If not, how can the original jsonify-created json file be transformed into a schema-compliant json file?

The latter question is the major element of this issue.

@gbinal
Copy link
Contributor Author

gbinal commented Oct 23, 2014

I think this is possible because of how the xml, csv, and html variants of the original model take the original json file and pull it into another structure. There's a slightly more complex version in play with the individual_apis.xxx files here.

@gbinal
Copy link
Contributor Author

gbinal commented Oct 23, 2014

This can wait until I address #1, but then I'll need some help probably.

@gbinal
Copy link
Contributor Author

gbinal commented Oct 23, 2014

Some answers might be found here - http://jekyllrb.com/docs/datafiles/

@parkr
Copy link

parkr commented Oct 23, 2014

If you can provide an example of input and desired output, I might be able to come up with the proper piping or modify Jekyll to accommodate this use-case.

@konklone
Copy link

You may simply have to avoid jsonify entirely and build a custom JSON file using a template, as you would an HTML representation. It's uglier, and you'll need to use filters to accommodate for encoding issues on every field (e.g. always escaping fields that might contain quotation marks), but it sounds possible.

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

No branches or pull requests

3 participants