-
Notifications
You must be signed in to change notification settings - Fork 0
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
Revise R practical #35
Comments
Edits made for draft version. They include:
All in commit: 53beadb |
I've been moving the data for these case studies into the new package. I've realised that the six datasets loaded are actually just two files - one is a linelist and duplicated in different formats, the other is an aggregate table and also duplicated in different formats. I don't think we need to load duplicate files to make the point that import() can handle different file types. We just need the linelist as one filetype and the aggregate data as another filetype. Are you happy with me reducing the number of datasets in this practical from 6 to 2 (one csv and one xlsx)? |
As long as there are still two different file types to show the strength of import(), which you have clearly said above, I have no problem reducing the datasets down to two. I was wondering why there were so many to begin with. Great job cleaning up the case study! |
Further edits made:
Still want to
|
No description provided.
The text was updated successfully, but these errors were encountered: