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

Comments from Stavros #10

Open
hadley opened this issue Jan 30, 2014 · 0 comments
Open

Comments from Stavros #10

hadley opened this issue Jan 30, 2014 · 0 comments

Comments

@hadley
Copy link
Owner

hadley commented Jan 30, 2014

Re "observational unit" and "level", I still think a better definition would be useful, perhaps in 2.3, perhaps in 3.4.

I wonder if the observations about denormalization (parag 3 of 3.4 and last parag of 4.1) might be worth elaborating on? Or maybe not... the examples of join in 5 might be enough.

I really like the "tidy data" framework and the way it highlights the cleanness and unity of the tools you've developed.

On p. 22, line 4, I think the comma after "data" is inappropriate because the "which" starts a restrictive clause.

About the ETL literature, I agree that a lot of it is either commercial or very IT-ey (as opposed to CS-ey), but there does seem to be a fair amount of discussion around data warehouse schemas. Some other papers I've come across (I don't claim to have done a serious literature search!) include Boehnlein, Vassiliadis et al., and Vassiliadis (p. 9ff talks about the "pivoting problem").

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

1 participant