Community partner project

For this assignment, we’ll be creating publication-quality graphics for the [our community partner]. They have provided us with the following datasets:

Initial idea

Pick a question

For the first step of this assignment, you will be identifying a question you would like to answer from the [partner] data. [Example questions]

Consider the “shape” of the data you would need to answer your question

What variables would the data need to contain? Do those variables exist in the current data?

Create some pseudocode

Write come pseudocode for the graphic(s) that you would like to generate. In your pseudocode, consider the geom_ you would need to make the graphic(s), as well as the variables you would want. The code does not need to run, so you can put #| eval: false in the top of the code chunk

#| eval: false
ggplot(MNDUL) + geom_col(aes(x=math_level, y = percent, fill = matched))

Deliverable

I would like you to submit a rendered document from Quarto that contains the question you want to answer, a description of the data you would need in order to answer it, and some pseudo-code. The code doesn’t need to run!

One other bit of code you may need:

embed-resources: true

First draft

I would like a complete first draft of a [community partner] visualization (just one is fine) so we can do peer editing. My preference for file submission would be a rendered document from Quarto (rendered as PDF or HTML), but other options are also fine. Try to get the basic “shape” of the visualization right, and make a couple of graphical customizations (e.g., change the axis labels, the colors, the order of items, etc).

Remember, if you want the plot(s) to appear in a rendered HTML document, it needs have embedded resources,

embed-resources: true

The other options that are sometimes nice are about including messages and warnings (we usually don’t want them)

execute:
    message: false
    warning: false

That stuff also goes in the YAML (stuff between the --- at the top of your document) or it can go into a code chunk for per-chunk options.

Peer editing

As with previous peer editing, you need to go back to the original assignment to find your peer’s work. It’s fine if you and your partner converge on one visualization that you both submit for the second draft

For the peer review, consider:

  • the geom_ your peer is using. Would there be a better one?
  • axis labels (should they be percents? dollars?)
  • title (is the year important?)
  • colors and other aesthetic choices
  • ordering of items

Make at least two suggestions for improvement!

Second draft

This is the version of the plot that we’ll show the [community partner] folks. I would like just your image (not a rendered Quarto doc) that I can paste into a PowerPoint presentation. You can either use

ggsave()

or the Export button on the RStudio plots pane to save this.

Final draft

This is the visualization I will be sending to the [community partner] folks. I would like two files:

  • a polished visual(s), saved as an image
  • your source file document (qmd)
  • [If you modified the Excel document before visualizing, please include that file as well]

Please take into account the comments from [the community partner] and the class on the drafts we saw. There were some common comments:

  • Colors in line with [the community partner’s color scheme]
  • Make sure labels are correct- several had the labels swapped
  • Think about graph titles, often want it to be the headline or the ‘so what.’
  • Consider making two versions– one that would be good for digital dissemination and one that could be printed on paper in black-and-white.