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

Discussion: should we cover JSON? #72

Closed
gvwilson opened this issue May 21, 2019 · 4 comments
Closed

Discussion: should we cover JSON? #72

gvwilson opened this issue May 21, 2019 · 4 comments
Labels
discussion discussion before a proposal on hold Issues to come back to later.

Comments

@gvwilson
Copy link
Contributor

  1. Should we cover JSON (and/or YAML) as an example of nested data?
  2. If so, should this go in the novice or intermediate material?
@gvwilson gvwilson added the discussion discussion before a proposal label May 21, 2019
@ljdursi
Copy link
Contributor

ljdursi commented May 23, 2019

I think it could make a lot of sense to cover it in intermediate material, perhaps in the context of ETLing some data into structured format, not least of which because once you have JSON in your toolbox now basically every open web API is available to you.

I would leave it out of novice because for it to make any sense you'd have to cover a lot of material, and because I think it's harder to teach in R than python (could be wrong).

@lwjohnst86
Copy link
Contributor

Completely agree with with @ljdursi, I think JSON in intermediate material would be useful to know, at the least to have some mention about. As for teaching in R vs Python, I don't really know. There are several R packages to work with JSON, but not sure how "teachable" they are.

@joelostblom
Copy link
Contributor

Maybe - intermediate. Depends a bit on personas... For basic usage both dplyr and pandas makes it really easy to read jsons without extensive knowledge of the format. I guess yaml. Will be talked about when we talk about markdown?

@lwjohnst86
Copy link
Contributor

As per #70, leave and focus on current content. Closing and adding "on hold" label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion discussion before a proposal on hold Issues to come back to later.
Projects
None yet
Development

No branches or pull requests

4 participants