You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Action item: Tim can look into this and respond to suggest starting points; the idea would be to look out for dependencies;
Background
from @ragamouf: This is a question from the trainer community for Library Carpentry’s Open Refine lesson. I’m wondering if the Curriculum Advisory Committee could look into the Open Refine lesson, and expand the number of useful starting points for using Open Refine in a teaching demo. Typically instructor trainees go all out preparing for the whole lesson, but never get ‘tested’ on the one part of the lesson that actually uses a form of participatory coding. My gut feeling is that the “all other episodes have dependencies” caveat means trainers don’t bother to explore the lesson, and the trainee typically performs their teaching demo with the slightly deflating task of showing peers how to open a file. But comparing against what you’d need to load for an R or python lesson, it’s not substantially different, is it? Note, this may be a moot point, since the instructor training checkout proceddure will be changing, so there’ll likely be less emphasis on the teaching demo. But, as a trainer, the OR lesson is a perennial favourite with teaching demos. The ultimate motivation for this question is how to improve the LC presence in the instructor certification process.
Additional comment: Instructor trainees will typically work hard on the GREL components where they are able to do some participatory live coding.
The text was updated successfully, but these errors were encountered:
Notes from LC-CAC 2023-03-16
Problem statement: Right now only loading data is included for starting points at Instructor Training checkout demo https://carpentries.github.io/instructor-training/demo_lessons/index.html
The checkouts will be changing in the future, but we can open up more episodes for use in the demos.
Action item: Tim can look into this and respond to suggest starting points; the idea would be to look out for dependencies;
Background
from @ragamouf: This is a question from the trainer community for Library Carpentry’s Open Refine lesson. I’m wondering if the Curriculum Advisory Committee could look into the Open Refine lesson, and expand the number of useful starting points for using Open Refine in a teaching demo. Typically instructor trainees go all out preparing for the whole lesson, but never get ‘tested’ on the one part of the lesson that actually uses a form of participatory coding. My gut feeling is that the “all other episodes have dependencies” caveat means trainers don’t bother to explore the lesson, and the trainee typically performs their teaching demo with the slightly deflating task of showing peers how to open a file. But comparing against what you’d need to load for an R or python lesson, it’s not substantially different, is it? Note, this may be a moot point, since the instructor training checkout proceddure will be changing, so there’ll likely be less emphasis on the teaching demo. But, as a trainer, the OR lesson is a perennial favourite with teaching demos. The ultimate motivation for this question is how to improve the LC presence in the instructor certification process.
Additional comment: Instructor trainees will typically work hard on the GREL components where they are able to do some participatory live coding.
The text was updated successfully, but these errors were encountered: