Citation, Citation, Citation (30-45 minutes)

Example: Read the below paragraph and rate each sentence from 1-5, where “5” is very clear whether an idea is from the writer or from a source and “1” where you are very unsure if the idea is from the writer or from the source.

Tomeka M. Davis, an Associate Professor of Sociology at Georgia State University, found that for most parents, they want to choose a school that matches their racial identity and economic background (Davis). And for many White parents, that means sending their children to predominantly white and affluent schools. To them, the higher the percentage of minority students within a school equals a lower status of that school. That perceived notion that a school isn’t of high status makes White parents think that sending their children to that school will be a threat to their children’s life chances.

Let’s take this sentence by sentence and see how it goes.

Rhetorical and Pedagogical Purpose of Citation

So, so many people will drone on and on about how citing things properly is about intellectual property and “stealing” and all that kind of cop stuff. While that is a concern, it is far less interesting concern because what it ultimately does is produce scared writers. You should be motivated to cite because of what it can do for your rhetorically and what it can teach you. Mostly about two things:

1. Makes it easier for reader to go back to source and see for themselves if they want to. This is something that researchers will do a lot to help with the research they are doing.
2. It is good learning practice. Making sure you are linking what you read with what you think increases likelihood you are not being sloppy and “filling in the blanks” of what you read with what you already believe.

I want you to look at the following draft which does some pretty great things with citation but also shows some examples of how to make things easier to find and also clear up whose idea is whose in ways that can help learning.

Read this draft to yourself and look for two things:

1. Sentences where you think it might be hard to know how to find the cited information for yourself.
2. Times where information should be cited or if you are uncertain if it is the writer’s idea or a source’s idea.
3. Mark anything you liked about the draft or thought it was doing well.

Letting Works Cited Page Guide Citations

What goes in the parentheses? In what circumstances?

Every documentation style has different rules, so please keep that in mind. Most (but not all) documentation styles that use in-text citation will go by the order of the works cited or reference list for what goes in any parentheses.

Let’s take a look at some examples from here:

MLA In-Text Citations: The Basics // Purdue Writing Lab

MLA Works Cited Page: Basic Format // Purdue Writing Lab

Another thing unique to MLA is the emphasis on citing page numbers. When you are talking general findings, most documentation styles will say you don’t need a page number (our earlier example is arguably in that category), but in MLA, I would still put page numbers because, since most disciplines that use MLA are heavily invested in the preciseness of language, they will want to know where you got your language from even in the “general results” category (not always, but as beginners, I think it is a good place to stick to). It is also good since you are learners as it will help you stick to specific locations that you can read carefully and then align with what you write about those locations.

Let’s take a look at some examples.

MLA In-Text Citations: The Basics // Purdue Writing Lab

That said, not all sources have page numbers and thus you do not need to include them in those cases. Just make sure you cite as specified by the type of source: MLA Works Cited: Electronic Sources // Purdue Writing Lab

 

Prompt Check-in (10 minutes)

Let’s take a look at the prompt. It is on Blackboard in the Labor Instructions folder for October 26.

 

Podcast Planning (45 minutes)

Let’s brainstorm all the possibilities of what this podcast can be about. Think back to past Discord posts we have made, past conversations, what we have written about in other places, etc. Put it in today’s Discord text thread

Same for form of podcast. All possibilities. The webtext by Detweiler and Discord posts about that would be helpful here. Put it in today’s Discord text thread.

Let’s take about 5 minutes to write down everything we can think of.

Okay, now let’s get into some discussion groups to talk through some of these ideas. Take about 10-15 minutes to talk through some thoughts with your group and make sure you are ready to report back in the Discord thread for today toward end of time with group.

 

Podcast Creation Infrastructure

Roles: project managers, editors, narrators, tech support, tone meetings across episodes

WORRY LESS ABOUT EXPERIENCE AND COMFORT. What do YOU want to learn? This is not about producing the best podcast ever, it is about learning some cool stuff through a collaborative writing experience….something you will do a lot in your careers.

Responsibilities of project manager: keeping tabs on work schedule and roles for each group member, in charge of meetings, coordinates team charter, progress reports. Project manager for each episode or different “departments”?

Writing to Coordinate activity: team charter, scripts, more research writing, meeting agendas, meeting minutes, progress reports, task schedule

Deadlines for getting things done. Wanted to finalize podcast by December 2.

Workflow Options (from Joanna Wolfe, Team Writing, p. 6):

• All Together: Entire team sits down and works on project together. Usually one or two team members “drives” at the computer and others give feedback as the work happens.
• Divided: The group breaks project down into sections and assigns individual team members to different sections or parts of project.
• Layered: Each person on team is assigned one or more specific roles. Each person works on project in turn, adding their own expertise to product. Document slowly accumulates in layers as each team member revises as project moves forward.

 

 

 

Quick Audacity Check-in (5 min)

Let’s open up Audacity and just going through a VERY quick intro (more on getting acquainted with Audacity on November 2). Also, want to see if there was any downloading issues.

 

Close out (2-5 minutes)

-Revision Plan by tonight

-Podcast Post 1 by tonight, comments by tomorrow at latest

-November 2 you will do an audio file focused on podcast ideas

-Keep working on Research Project, second draft due November 9