{"id":474,"date":"2017-05-08T08:35:11","date_gmt":"2017-05-08T14:35:11","guid":{"rendered":"http:\/\/richardcolby.net\/writ3500\/?page_id=474"},"modified":"2022-04-18T13:39:12","modified_gmt":"2022-04-18T19:39:12","slug":"module-7","status":"publish","type":"page","link":"http:\/\/richardcolby.net\/writ3500\/schedule\/module-7\/","title":{"rendered":"Module 7"},"content":{"rendered":"<h2>Review<\/h2>\n<p>You\u2019ve no doubt done plenty of peer reviews. But what percentage of the comments that you gave were actually addressed? You\u2019ll be happy\/dismayed to know that your peers almost always follow the correctives (pointing out errors). More substantial argumentative or rhetorical comments, on the other hand, are often ignored. <a href=\"https:\/\/www.uc.edu\/content\/dam\/uc\/journals\/composition-studies\/docs\/backissues\/37-1\/Treglia%2037.1.pdf\">Research<\/a> has affirmed this. If you write 50 comments pointing out style and grammar issues and 2 comments about the rhetorical or argumentative stance, the author will see it as a matter of scale and think the \u201cmistakes\u201d are more important than the comment that pointed out the massive logic error in the argument. It\u2019s obviously not just about the scale\u2014as writers, we all know that fixing a comma error is far easier than fixing that error in logic or a rhetorical oversight. In the end, however, a flawed argument is more problematic than a few comma errors.<\/p>\n<p>This week, you will be reviewing your peers\u2019 Revisions. As experts in writing practices, you should understand a bit about what peer review comments work. Here are some things to recognize as you comment now and in the future.<\/p>\n<p>First, here are the top four LEAST helpful comments:<\/p>\n<ol>\n<li>One word, negative comments (e.g., unclear, awkward, wrong) (<a href=\"http:\/\/www.jstor.org\/stable\/43518858\">Hayes &amp; Daiker, 1984<\/a>; <a href=\"https:\/\/www.jstor.org\/stable\/40171265\">Straub, 1997<\/a>)<\/li>\n<li>Vague or general comments (<a href=\"http:\/\/www.tandfonline.com\/doi\/abs\/10.1080\/02602930500353061\">Weaver, 2006<\/a>; <a href=\"https:\/\/www.jstor.org\/stable\/40171265\">Straub, 1997<\/a>)<\/li>\n<li>Lack of guidance or suggestions (<a href=\"http:\/\/www.tandfonline.com\/doi\/abs\/10.1080\/02602930500353061\">Weaver, 2006<\/a>)<\/li>\n<li>Comments not connected to assessment criteria (<a href=\"http:\/\/www.tandfonline.com\/doi\/abs\/10.1080\/02602930500353061\">Weaver, 2006<\/a>; <a href=\"http:\/\/www.tandfonline.com\/doi\/abs\/10.1080\/03075070600572132?journalCode=cshe20\">Carless, 2006<\/a>)<\/li>\n<\/ol>\n<p>The first two directly feed into #3\u2014lack of guidance. Whether a positive \u201cthis is good\u201d or a negative \u201cthis is bad,\u201d without pointing to a direct instance, and offering direct suggestion, the comment isn\u2019t very helpful. Offering suggestions can be hard. You have to shift from left brain analytical to right brain creative, and it can be taxing. As you could surmise from the above list, here are the top four MOST helpful comments:<\/p>\n<ol>\n<li>Positive comments and reinforcement (<a href=\"http:\/\/www.jstor.org\/stable\/43518858\">Hayes &amp; Daiker, 1984<\/a>; <a href=\"http:\/\/www.tandfonline.com\/doi\/abs\/10.1080\/02602930500353061\">Weaver, 2006<\/a>; <a href=\"https:\/\/eric.ed.gov\/?id=EJ374887\">Dragga, 1985<\/a>; <a href=\"Responding%20to%20Student%20Writing:%20Teachers\u2019%20Philosophies%20and%20Practices\">Ferris, 2014<\/a>)<\/li>\n<li>Constructive comments, suggestions (<a href=\"https:\/\/eric.ed.gov\/?id=EJ1007081\">Calhoon-Dillahunt &amp; Forrest, 2013<\/a>).<\/li>\n<li>Corrections (<a href=\"https:\/\/www.jstor.org\/stable\/40171265\">Straub, 1997<\/a>)<\/li>\n<li>Negative comments from experts to experts (<a href=\"http:\/\/blogs.cuit.columbia.edu\/sf2559\/files\/2011\/08\/FF_JCR_Feedback.pdf\">Finkelstein &amp; Fishbach, 2011<\/a>)<\/li>\n<\/ol>\n<p>What peer review ultimately does is allow an authentic reader to respond to a piece of writing. It\u2019s not about expert writing advice and \u201cfixing\u201d writers\u2014it\u2019s about responding how a reader would respond.<\/p>\n<h3>How do you do a peer review?<\/h3>\n<ol>\n<li>Read the whole piece first without comment. It\u2019s tempting to think you are saving time, but you aren\u2019t. Sit down and read the whole thing first to see where it goes, what patterns develop, and what the author really needs to know.<\/li>\n<li>Tell the writer what they did well. Maybe this is a sentence, but maybe it is more. This claim should be supported with evidence. Not, \u201cGreat sentence\u201d but instead, \u201cgreat sentence; your details about the little house made me feel like I was there.\u201d<\/li>\n<li>Provide suggestions to the writer\u2014give examples, things to consider, or how you would have approached an issue, but leave it up to them to decide how to use your examples.\u00a0 Don\u2019t just cross something out and write something new.<\/li>\n<li>Remember there is a person behind the writing who has spent hours working on the project.\u00a0 They want help improving.\u00a0 Comment about the writing\u2019s effectiveness.<\/li>\n<li>Be brave. Sometimes writers say things that you find objectionable. Be mindful especially when confronted with examples and idioms of race, gender, and sexuality. It\u2019s not about being the PC police\u2014it\u2019s about making sure the writing remains meaningful for its intended audience. Let writers know when something might be objectionable, even if you qualify it with how you felt as a reader; for example, you might write, \u201cwhile some might find the line \u2018fat goth chicks\u2019 funny, it made me angry as a reader. Maybe the line would work better if you just said \u2018mascara clad goths\u2019 or \u2018awkward goth kids\u2019.\u201d<\/li>\n<li>Save grammar fixing for the last. If you notice patterns, then point them out, and feel free to mark individual errors as you see fit, but if you spend an hour just fixing comma errors then you aren\u2019t peer reviewing as a reader&#8211;you are editing.<\/li>\n<\/ol>\n<p>There are a lot of models for doing peer review including small-team collaborations, group review, and round robin style exchanges. Each has benefits. For the Revision and the Portfolio reviews, we are going to do collaborative reviews. What that means is that you are going to receive three reviews written on the same document, 1 from your professor and 2 from your peers. You will then have to decide what to do with these reviews (Module 9 is all about how to decide).<\/p>\n<p>For the Revision assignment, you will be doing a mostly holistic peer review. It is holistic because you will read the works as a reader would, on the whole, and provide general impressions about what worked or didn\u2019t work. It is \u201cmostly\u201d because you should also look at the RGA (included at the end of each document) to make sure the authors emulated the genre markers they say they are in the Revision.<\/p>\n<p>This week is all about reviewing your peers and figuring out what to do with their feedback.<\/p>\n<p><strong>Design this week<\/strong><\/p>\n<ol>\n<li><a href=\"http:\/\/richardcolby.net\/writ3500\/revision\/\">Revision<\/a> [email richard.colby@du.edu]<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>Review You\u2019ve no doubt done plenty of peer reviews. But what percentage of the comments that you gave were actually addressed? You\u2019ll be happy\/dismayed to know that your peers almost always follow the correctives (pointing out errors). More substantial argumentative or rhetorical comments, on the other hand, are often ignored. Research has affirmed this. If [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":37,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-474","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"http:\/\/richardcolby.net\/writ3500\/wp-json\/wp\/v2\/pages\/474","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/richardcolby.net\/writ3500\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/richardcolby.net\/writ3500\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/richardcolby.net\/writ3500\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/richardcolby.net\/writ3500\/wp-json\/wp\/v2\/comments?post=474"}],"version-history":[{"count":18,"href":"http:\/\/richardcolby.net\/writ3500\/wp-json\/wp\/v2\/pages\/474\/revisions"}],"predecessor-version":[{"id":2318,"href":"http:\/\/richardcolby.net\/writ3500\/wp-json\/wp\/v2\/pages\/474\/revisions\/2318"}],"up":[{"embeddable":true,"href":"http:\/\/richardcolby.net\/writ3500\/wp-json\/wp\/v2\/pages\/37"}],"wp:attachment":[{"href":"http:\/\/richardcolby.net\/writ3500\/wp-json\/wp\/v2\/media?parent=474"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}