This repository hosts the course website of Tilburg University's open education class on "Data Preparation and Workflow Management" (dPrep) - start managing your empirical research projects efficiently!
[x] incorporate making pull requests in first tutorial
[x] strengthen the workflow of Scrum and how to work w/ Git early on in the course & check/follow-up
[x] #144
[ ] add more make content: multiple targets vs multiple rules, all rule = first rule, gradually build, go in baby steps
[ ] ensure solutions are available for all tutorials
[ ] change standard template for assignments (makefile/automation)
[ ] use teamviewer link/meeting rather than ID/password?
[x] in exam instructions, say students should refrain from using their names in submitted documents and also in file names (the system handles these automatically) and it will ensure i can grade exams anynomously
Major content updates
[ ] develop a data source theory for wrangling
[ ] use new datasets for project (e.g., retailing)?
[ ] add some more examples for deployment
[ ] develop "level of reproducibility" roadmap
[ ] introduce SQL (select from where) as a way to retrieve data, without much of the SQL details
[ ] Revise project template w/ make -- make per module
Course structure
[ ] think about changing structure: week 1 (R bootcamp and running code from command prompt/terminal; relative directories; say clearly: top down, from command prompt, gradually build & test), week 2 (github issues, scrum, project board & versioning, gitigore, removing files, pull requests), week 3 (exploration and first make rule), week 4 (engineering and more complex make rules, ITO building blocks), week 5 (make)
[x] extra points for making a nice-looking github page?
[ ] Like in oDCM, facilitate finding teams w/ a pre-survey
[x] Try out hybrid coaching sessions
[x] Use datacamp signup link instead of email address based authentication via the library
[x] Make sure everyone knows how coaching sessions will be
[x] somewhat encourage students to prep better for coaching sessions (was a little slow at the beginning) / deadlines may help?
[x] check whether to change exam format (e.g., just one hour individual exam, and another form of individual testing)
[ ] include note about "special circumstances" so that students can register for exam extension
[x] implement assessment policy (see below)
Assessment policy:
Attendance and bonus points:
Attendance in itself does not qualify as a valid ground for awarding bonus points. Awarding bonus points must be done sparingly to motivate students and reward excellence. The award of bonus points can only lead to a mark-up of a sufficient grade, not of an insufficient grade. Moreover, the mark-up should not be higher than 0.5 point and may only be awarded once at the level of the final grade.
[ ] When introducing Git, it's not super clear to students they need to know (a) how to navigate on the terminal, and (b) they need to be present in the particular directory to execute Git commands. Make that clearer.
Minor content updates
make
a little earlier in the courseMajor content updates
Course structure
Assessment policy: