skadauke / intro-to-r-for-clinicians-chop Goto Github PK

Would need to administer surveys in appropriate time frame.

Leila Bateman has a great slide on this

Could use {glosario} for this

00 - Welcome

• Add chopr sticker to title slide
• Replace Monaco with Consolas font
• Update TAs
• Add slide with schedule for sessions and breaks - update this at the end.
• Clarify purpose of Meeting-style: (1) limited group exercises; (2) tech help: Joy will arrange for that learner to have 1:1 with a helper
• Clarify purpose of chat window: ask for help; feel free to disregard, not necessary to follow the lecture.
• Update Zoom window slide with updated title slide :)
• Update script

01 - Introduction

• Add chopr sticker to title slide
• Replace Monaco with Consolas font
• Your Turn title font should be Tw Cen MT not condensed
• Rename "MISC" to "Files" pane, get rid of all-caps
• Shorten Duke Cancer section
• Break down slide 14 into "Running a single code chunk" and "Rendering an R Markdown Document" slides
• Your Turn 2 slide is ugly and wordy. Fix.
• Your Turn 3 slide: change MISC to Files
• Recap slide is crowded, make text smaller. Also animate recap slide.
  - [ ] Before "What Else" add a section "How to Get Un-Stuck" using pipe-delimited values as an example
• Databases slide: images are tiny, make them larger
• Update script
• Make sure animations work as expected
• Create coursepack version with extra slides deleted

02 - Visualize

• Add chopr sticker to title slide
• Replace Monaco with Consolas font
• Your Turn title font should be Tw Cen MT not condensed
• YT4: Have an answer for why axis labels, etc aren't aesthetic mappings
• Update script
• Make sure animations work as expected
• Create coursepack version with extra slides deleted

03 - Transform

• Add chopr sticker to title slide
• Replace Monaco with Consolas font
• Your Turn title font should be Tw Cen MT not condensed
• Replace Arial in tables with Twin Cen MT
• Have a slide very simply showing select columns vs filter rows. This is always weirdly counter-intuitive to me - which is which! - and spelling it out clearly/visually might help.
• Consider calling attention to the double equals on the slide visually, as single vs double equals is going to come up a bunch in next few slides.
• Recap animation is broken - fix.
  - [ ] More dplyr functions slide: text is too small, rearrange
• Update script
• Make sure animations work as expected
• Create coursepack version with extra slides deleted

04 - Dashboard

• Add chopr sticker to title slide
• Replace Monaco with Consolas font
• Your Turn title font should be Tw Cen MT not condensed
• Swap slide 3 for UW COVID19 dashboard (> 1 million tests, R was essential to scale their operation; provide link to YT video from R/Medicine)
• Animate Your Turn 1 slide
• Slide 22 - have to explain why flexdashboards are limited and what Shiny can add
• Update CHOPR meeting slide
• Remove the Join the CHOP R User QR code or make smaller - it cannibalizes the final slide
• After R4DS slides, add Course Project section (can add a slide here: when your should use R and when you shouldn't)
• Update TAs in Thank You!! slide
• Add bullhorn to post-course slide (CTA)
• Update script
• Make sure animations work as expected
• Create coursepack version with extra slides deleted

99 - Tech Check

• Add one slide that explains what people are supposed to do: unmute self, say your name, get confirmation; then log into training environment.
• Make CHOP-branded

99 - RStudio.cloud setup

• Update project URL
• Update screen shots

Web site

• Provide recordings from last time (?)
• Provide downloadable PDF course pack (delete give-away slides from deck!)
• Add glossary of Data Science terms
• Individual cheat sheets: data wrangling, data viz
• CHOP R User group sign up

As per our meeting, here's the language to take a look at:

To avoid issues caused by the overzealous CHOP firewall, you may want to connect from a personal (not work-issued) device using a non-work wireless network (i.e. chopguest).

This looks great! I see that it's adapted from the R Project Conferences CoC and I think the language and framing works well for our communities. A few small suggestions below to tailor this specifically to workshops:

At the very beginning:

Consider adding a sentence of context about the R User Group, such as:

The CHOP R User Group brings together a diverse audience of learners and users for community events such as workshops, talks, and discussions. Our goal is to make our events safe, inclusive, and accessible to all participants. We are dedicated to providing a harassment-free experience....

Under Expected Behavior:

Consider a positive assertion of our community norms to the beginning, such as:

We strive to create a learning environment where all participants feel safe to share ideas, take risks, ask questions, and communicate their experiences to others. We expect all participants to engage in this environment respectfully and acknowledge the many diverse perspectives, identities, skill levels, abilities, etc. of their fellow participants.

Under What To Do If You Witness or Are Subject To Unacceptable Behavior

Will we clearly identify who the "event organizer" is? Is this assumed to be the instructor, or someone else? I know there's a norm of a "host" being responsible for the event, but I thought it would help to be extra-clear here who this person is, how the participants will know who that person is, how to contact them, etc. Maybe just an addition sentence clarifying this.

Under Pre-event concerns:

Same thing - make really clear who the event organizer is, how they'll know who it is, and how to contact.

I think that's my main first pass right now! I don't have specific guidance on exactly what constitutes harrassment and how to approach it, as I don't feel quite qualified to make those calls. Given this, I think deferring to workplace rules and expectations at CHOP, and the R Project language, is a great approach to take.

00-Welcome

01-Introduction

• update instructions for training environment (passwords)?
• draw attention to when you write code in the editor (e.g. Your Turn 2) vs console (e.g. install.packages)

02-Visualize

03-Transform

• Make Your Turn 1 into a poll instead of chat response
• Make Your Turn 3 into a poll, too

04-Dashboard

• slide 6: fix "chart 1, 2, c" in screenshot
• slide 27: chopr user group meeting?
• slide 28: mini projects (drop it?)
• slide 30: update helpers list

>1 Week pre-course

• Recruit TAs
• Set dates and calendar holds for:
  • Helper onboarding
  • Pre-course tech check
  • Post-course Intro CHOP R session
• Course sign ups and outreach

<1 Week pre-course

• Update slides and exercises
• Create course pack
• Update website
• Send welcome email and calendar holds (pre-course tech check, course, post-course CHOPR meeting)
• Set up training environment and backup
  • Resize training environment before and after pre-workshop tech check
  • Resize training environment before the workshop
• Set up Zoom rooms for tech check and main session
• Final pre-workshop reminder email with: start time, Zoom link, link to pre-course survey, link to course website, Excel sheet with usernames, course pack.

Post-course

• Send thank-you email with: post-course survey, CHOPR user group sign up link, link to website
• Recording
  • Upload to YouTube
  • Add link to website
  • Let participants know
• Send welcome email to course project participants, Rmd template
• Postmortem
  • Evaluate feedback forms
  • Write post-mortem notes
  • Have postmortem session
• Plan next iteration

Do it

Topics to cover:

• Pedagogy principles
  • Learner personas
  • Course objectives
  • Mental models
  • Formative assessments
  • Have learners write code
  • Do live coding
  • Have learners interact
  • Manage cognitive load
• Workshop mechanics
  • Zoom main session ~ lectures, formative assessments, live coding (after learners try for themselves)
  • Zoom breakouts ~ interactivity, 1:1 help with screen share if necessary, final exercise
• Training environment ~ learners write code
  • RSP training environment
  • Backup rstudio.cloud environment
• Dealing with participants
  • Code of conduct
  • Host monitors chat, dispatches TA to help participant
  • Common scenarios
• Preview of the final breakout session
  • flexdashboard review
  • examples of tweaks you can add

Resources:

• Teaching Tech Together
• CHOP R 101 Helper guide
• CHOP R Slack channel
• RStudio flexdashboard page
• RStudio instructor training
• RStudio education page
• Carpentries

>1 Week pre-course

• Recruit TAs
• Set dates and calendar holds for:
  • Helper onboarding
  • Pre-course tech check
  • Post-course Intro CHOP R session
• Course sign ups and outreach

<1 Week pre-course

• Update slides and exercises
• Create course pack
• Update website
• Send welcome email and calendar holds (pre-course tech check, course, post-course CHOPR meeting)
• Set up training environment and backup
  • Resize training environment before and after pre-workshop tech check
  • Resize training environment before the workshop
• Set up Zoom rooms for tech check and main session
• Course project sign-up form
• Final pre-workshop reminder email with: start time, Zoom link, link to pre-course survey, link to course website, Excel sheet with usernames, course pack.

Post-course

• Send thank-you email with: post-course survey, mini project sign up link, CHOPR user group sign up link, link to website
• Recording
  • Upload to YouTube
  • Add link to website
  • Let participants know
• Send welcome email to course project participants, Rmd template, and Doodle for course project kick-off session
• Postmortem
  • Evaluate feedback forms
  • Write post-mortem notes
  • Have postmortem session
• Send books
• Plan next iteration

Participants could be invited to sign on for a course project. The aim of the course project is to present at an upcoming CHOP R meeting (2-3 months down the line) a brief R Markdown document that solves a work need that they have.

To support this project, we could provide a physical copy for R for Data Science, an R Markdown template that gives helpful hints for starting a project, TechKnowledge time, office hours, the CHOP R Slack, and RStudio primers (https://rstudio.cloud/learn/primers)

We could time the Course Project presentations so that they fall within the same week as the next iteration of the course. This will encourage participants of the new iteration to see what's possible, and also show presenters just how far they've gotten within the past few months.

Course Projects could earn a certificate (from Arcus education) and also qualify learners to be TAs/helpers.

(Cross-posted from issue originally posted in intro-to-r-for-clinicians-rmed2020 - please ignore that issue and follow along with this one!)

Hi @skadauke ! Hhere are some notes for you on the first few slideshows (and I will add the second half next):

00- Welcome

• Slides 2-6: New instructor + TA listings
• Slide 8: Clarify “Meeting-style” is for tech help, people can indicate they need help and Joy will arrange for that learner to have 1:1 with an available TA
• Slide 17: Link to new CoC
• Slide 18: New version of this Your Turn appropriate for this workshop size/format

01 - Introduction

• Slide 22: Worth mentioning that library("tidyverse”) can be written without quotation marks as library(tidyverse) ? Up to you
• Slide 30: Consider reversing the order of these bullet points — I think Importing, functions, packages is more logical.
• Slide 32: Consider a link to cheat sheets and/or more explicit mention (eg titling this slide (R Studio Cheat Sheets are helpful!) and bringing up where to find them: https://rstudio.com/resources/cheatsheets/
• Slide 36: FWIW, R Markdown now natively supports many other languages including R using knitr language engines. This engine is based on the reticulate package but it may be helpful to present this as “R Markdown supports languages beyond R” and use this for framing: https://rmarkdown.rstudio.com/lesson-5.html

02 - Visualize

• Slide 10: Consider writing out the three upcoming steps either on this slide or on a new slide. I feel like this would work well as a “recipe” to get learners prepared for what comes next.
• Slide 15: The script here is a little verbose — consider consolidating language. I’d also consider explaining aesthetics as rules that tell ggplot how to draw on the screen. Aesthetic are things like colors, lengths, x/y placements, etc. The common thread is that they all take data and literally express that data as something visual.
  Also for the visual you use here, consider actually plotting a few of the observations on the plot to the right as a second animation. That would make it very clear!
• Slides 22-24: You focus on onside/outside aes(), but make sure you clearly describe the different use cases of whether you’re mapping the color from a column/varaible in your dataset (in which case it’s used inside aes() so mapping uses that variable), or whether you wish to set it manually without mapping. In other words, less focus on aes(), more on mapping or no mapping.
• Slides 39 and 41: Watch out for overspill with the cheat sheets! Off the slide in my view.

03 - Transform

• Before Slide 10: It might be nice to have a slide very simply showing select columns vs filter rows. This is always weirdly counter-intuitive to me - which is which! - and spelling it out clearly/visually might help.
• Slide 17: Consider calling attention to the double equals on the slide visually (either here or on separate slide), as single vs double equals is going to come up a bunch in next few slides.
• Slides 21-22: A little hard to compare differences in two consecutive slides. Consider a single slide with two columns (or animation/before-after style, so first slide with just the before code on left, second slide with before on left and after on right).
• Slide 29: Bolding the functions

04 - Dashboards

• Slides 5-6: I like this side by side a lot! For context, consider also showing a non-dashboard .Rmd and a dashboard-creating .Rmd side by side to emphasize how similar it is to what learners are already doing
• Before slide 16: Consider specifically calling out “this is YAML at the top of an .Rmd. it’s how we add settings to a markdown file.” You may already do this verbally earlier on in this section, but just noting here it’d be helpful to call this out with flexdashboard earlier on so here we can focus on theme.
• Bigger picture: If you expect to have any extra time in this session, it might help to showcase a few more examples of a dashboard with flexdashboard so that the concept and outcome is clear if people are still a little hazy on “what’s actually happening at this step?” Not necessary but could help make more concrete.
• Grammar: consider titling as "dashboard" (that is, using dashboard as a verb) so that it's consistent with the previous two action verb titles (which I like!)

Things to cover

• Manage expectations (limited hand holding)
• How to pick a good project (think minimal)
• How to get un-stuck
• Resources available to you
• Details about the course presentation (expectations)
• Info about certification? (requirements and bennies - not a promotion but can post on LI)