search

datacarpentry / spreadsheet-ecology-lesson

Data Organization in Spreadsheets for Ecologists
https://datacarpentry.org/spreadsheet-ecology-lesson
Other
37 stars 141 forks source link

Revised Learning Objectives for "Data Organization in Spreadsheets" #197

Closed mcnabbkb closed 6 years ago

mcnabbkb commented 7 years ago

After reading through the Ecology Workshop, I thought these learning objectives from "Data Organization in Spreadsheets" could be revised and improved.

After this lesson, you will be able to: • Model good data entry practices - formatting data tables in spreadsheets • Identify and address common formatting mistakes • Compare approaches for handling dates in spreadsheets • Prepare spreadsheets using basic quality control and data manipulation principles • Demonstrate methods for exporting data from spreadsheets using applications like R

This is my contribution for my instructor training.

amandawhitmire commented 6 years ago

I'm looking through issues for my instructor training, and I just wanted to second these recommendations. The wording change to what someone will be able to DO (identify, compare, etc.) is better practice than the current "you will learn...." framing. Just my $0.02.

Who decides whether or not to make these changes and then close the issue? I'm not going to submit my comment as any sort of task toward checkout, but I'm curious about how this process works.

hoytpr commented 6 years ago

Would @mcnabbkb consider putting in a pull request with these changes? Or since this is an older issue, maybe @amandawhitmire would want to develop a PR. Then the maintainers can decide if the changes are suitable for immediate or future merging into the lesson.

amandawhitmire commented 6 years ago

I'd be happy to finalize wording and submit a PR.

amandawhitmire commented 6 years ago

I'd like to suggest these changes, and will submit a PR to this effect, unless @mcnabbkb objects:

After this lesson, you will be able to:

amandawhitmire commented 6 years ago

The pull request has been completed, so this issue can be closed. ::thumbs up::

fmichonneau commented 6 years ago

Great, thanks! In your future contributions, if you add "fix #xxx" where the xxx represent the number of the issue (here it would have been "fix #197"), then the issue gets closed automatically when the pull request is merged! See this page of the GitHub documentation to learn more about it.