Comments (5)
@ethanwhite agree. In fact I have been thinking about a bit of a different approach to the spreadsheet part. Here is what I thought:
- Based on the material we have, create 1-2 bad spreadsheet containing lots of problems, mistakes and errors.
- We start the workshop splitting people into groups of 3-4 and ask them to download these spreadsheets.
- They are given 30 (45?) min to identify as many issues with the spreadsheets as they can and note them down.
- Once their done, the instructor does a "round" table; looping over the groups - each group says one thing they identified wrong with the spreadsheet until we reach saturation (i.e. all groups told us what their found).
- We then show the learners the materials we have and the list of the problems we know were introduced in the spreadsheets (interesting to see how many they identified, whether they used similar terminology etc etc maybe even found new issues).
- And that's it - we move on to the next module...R.
I think in this way we make it interesting and engaging for the advanced and beginners. It's also a nice icebreaker.
@tracykteal @hlapp @karthik @kcranston @gvwilson @ethanwhite - what do you think?
from spreadsheet-ecology-lesson.
I like the idea of a exercise like this. Is the idea that we would do at the very beginning (prior to any other instruction) or that there would be some introductory material before the exercise? If the former, I would expect that the learners would not pick up on many of the problems, so we would need to go back and revisit, either later in the morning or during the R / spreadsheet lessons (remember this spreadsheet? what would happen if we tried to load that into SQLite?).
from spreadsheet-ecology-lesson.
I'd start with that without any instruction. I think we could try revisit depending on how many things people picked on. But remember that the idea is that the groups report back and it's likely that most problems will be picked up (it takes 2-3 people in the audience who are pretty experienced with spreadsheets). I may have a skewed experience but both times I taught the spreadsheet module - most people in the audience were aware of the issues. I suppose it would be more engaging for them to try to identify them.
I think I wasn't very clear on the 5 and 6 in my proposed module workflow: basically the instructor goes in rounds and asks groups what they identified (so in loops "Group 1 - provide 1 problem; Group 2 - provide another problem...Group N - provide a problem; and back Group 1 - problem...." until none of the groups has problems that haven't been already identified). Then the instructor compares this list concatenated from all the reported problems with the list we have (so that needs to be in the materials, we just don't link the materials explicitly before the workshop "security by obscurity". Anyways, if they find them, no problem. It's an exercise.
So eventually I think almost all problems will be identified.
Hence, this would be the whole spreadsheet module.
Though I like @kcranston idea to revisit that in further module (remember this spreadsheet? what would happen if we tried to load that into SQLite?).
from spreadsheet-ecology-lesson.
I think we've now constructed the lesson this way. Thanks for all the feedback! We haven't explicitly added the 'remember the messy spreadsheet? what would happen if we tried to load that in to SQL'. That's a good addition. I've filed an issue there to add that to the narrative/instructor notes'. datacarpentry/sql-ecology-lesson#50
Think we're OK to close this issue?
from spreadsheet-ecology-lesson.
Yep, awesome work!
from spreadsheet-ecology-lesson.
Related Issues (20)
- Where year 2015 in tab '2014' is coming from in the messy data is not clear nor explained HOT 5
- dates "in the future" are no longer in the future HOT 2
- Various lesson improvements in a separate repo HOT 8
- Suggested edits/updates for 'Quality Control' lesson HOT 2
- Broken weblink in contributing.md HOT 6
- Broken link in Data Cleaning with OpenRefine Introduction HOT 2
- Add more of the common mistakes to messy spreadsheet HOT 1
- Suggestion for adding some more common mistakes HOT 2
- Suggestion for more on the DATE function HOT 3
- Need jump lists (anchors) for headings HOT 2
- Including google sheets as a possible spreadsheet program HOT 3
- Reference for spreadsheet organization (Broman and Woo) HOT 4
- slide deck of images from lesson? HOT 3
- Accessibility: replace screenshot of table with HTML table HOT 7
- Add a larger practice Data Set HOT 1
- Text edit in "Dates as Data" HOT 1
- Spreadsheet ecology lesson HOT 1
- Scheduling early transition to Workbench HOT 1
- Transition To Workbench in May HOT 6
- Links need to be fixed in CONTRIBUTING.md
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from spreadsheet-ecology-lesson.