Friday, May 08, 2009

The third view

First, I want to shout that I like the article as it is! Mumble Grumble. @#$%^&*

Okay now that is off my chest. Here are my thoughts about cuts. I reread the article twice, noting likely slash sites. I found that most of my sites were the same as J's, except that I agree with Mike that a big chunk of the history section should come right out. Details:

1. I agree with all of the cuts regarding bios and citations. It the history section is shortened, a chunk of those citations go, too.

2. Start with the second paragraph (or maybe with "Writing today means writing digitally . . ." and go to "Even so, . . . ")

3. Cut the quote from Starr, the WRT 106 description, and the first paragraph of the Teaching section.

4. We could cut the diagram, although this will entail rewriting, since a discussion of the diapgram is so embedded in the text. I vote that we wait on this cut until the others are completed; maybe it will not be necessary.

5. Cut the Yancey section. The flow is fine without it.

6. Cut the history section as Mike indicated. Keep the first two sections, then go to the fourth iteration paragraph. Savings = more than 2 pages. The text adjustment can be minimal between paragraph #2 and #6. Something like: "The development and application of the writing environment concept-metaphor came somewhat naturally out of the several iterations of the course. WRT 235 was originally designed and adopted by our program in 1991 as an analog to business writing, as that seemed to be both the environment and the rationale for a course in writing with computers. Within two years, the course's purposes, goals, design and assignments changed, and then changed again, and again, until by 2005 it had gone through four iterations, each time designed with more critical analyses about computer mediated discourse, with more rhetorical demands for writers writing in that an electronic environment, while the where of such writing became both more omnipresent and metaphorical. The fourth iteration of the course included an explicitly rhertorical dimensiton . . . ." continue with paragraph #6 of the history section. (If you do not like this bridge, feel free to edit it, please.)

7. Michael suggests shortening the collaboration stations section. I disagree. The assignment is a wonderful realizatoin of the environment metaphor, and the more we help readers see its full potential the better.

8. Michael suggests shortening the conclusion, and this is a possibilitity if the previous cuts do not add up to 9 pages. It could be two paragrpahs, perhaps beginning with "We look forward to a time when we . . . " Then skip the next paragrpah, and finish with the current last paragraph. I would rather cut this section than the diagram section.

L.

Monday, May 04, 2009

MP's possible cuts

After looking over the 39 pages of the manuscript, I've got some ideas for cuts. Hopefully, many of these overlap with Jeremiah's and we'll find 9 pages shortly.

1. Redundant bios at beginning and end of manuscript; I vote we delete the bios on p. 39 as this gains us a page.

2. For me, some deleting and tightening can occur in the metaphors section. In particular, I think the information architecture section could be one paragraph (p. 6). We can cut the paragraph quoting Nicole Brown and combine the others. The ecology section could be two paragraphs (down from 4).

3. The where section, in which we outline infrastructure, can be trimmed. I nominate the paragraph beginning with Borgmann and including the long quote from Starr (pp.10-11). Also, on p.11, the paragraph beginning "We believe..." can be cut except for the first line, which can maybe be placed in next paragraph. This gets us more quickly to how what we are doing is different/new.

4. To my mind, p. 13, which focuses largely on how this focus impacts our majors, can be significantly cut. This is frustrating as I think the reviewers asked us to add some of this in.

5. I find it hard to say this next potential cut, since the practitioners' history has always been an important element to me. However, what if we revised the history section so that it opened with the most recent iteration of the course. We could then include a few sentences looking back at previous approaches.

6. The section on collaboration stations can be shortened--especially towards the end. This would allow us to delete Figure 1 (the course handout, p.23). I don't have specific paragraphs to delete but I'm wondering how we can get to the reason for including collab station section sooner. Then by deleting the figure, we can also delete references to using the handout in class.

7. Our concluding section could be two paragraphs. Jeremiah just told me he thinks the Yancey can be cut (or that's what I heard!). At the least, it could be shortened considerably and briefly noted in opening of para. 3 in that section. The last paragraph could be cut or, actually, maybe the final two paragraphs could be cut.

I don't know how many pages those cuts get us, and some of that will depend on the domino effect caused by the deletion of sources and footnotes (JD mentioned footnote 11 as a possible cut and I agree). After looking over the draft, however, I'm much less worried about how the loss of 9 pages will hurt the article. It will still make its point.

mp

Saturday, May 02, 2009

JD's ideas for cuts

Hi guys--

Lydia and Chloe are out at a birthday for a few hours, so I thought I'd take a whack at identifying some possible cuts. We have to get rid of 9 pages!

In my notes here, I am referencing the draft I forwarded from Danielle Aquiline yesterday ("DyehouseEtAl.Dec07. . . ").

p1: fix Shamoon bio formatting--it looks like it isn't adjusted to the current margins. Savings: 1 line

pp1-2: cut the first paragraph of our article, which merely repeats our abstract. I suppose that we would have to cut the first heading, too. Savings: .5 page

p10: cut the big block quote from Starr. This would mean revising the second half of this paragraph to eliminate its reliance on that quote. Savings: .5 page

pp12-13: cut the paragraph describing WRT 106 and community service writing. (I know: we added this for the reviewers. But as I read the ms., I am not seeing how this particular paragraph adds anything.) Savings: .5 page

p14: "Last semester"--ha ha! No real savings here, but we do have to change it.

pp16-17: cut the paragraph detailing the "roles and identities" focus of the course's 3rd iteration. I like this paragraph, but I think we can do without it. Savings: .5 page.

pp19-20: cut the first paragraph of the "Teaching Writing Environments" section. Savings: .5 page

pp22-24: cut figure 1 and the paragraph that explains it. If we do this, we'll have to quickly summarize the ideas that students are working with in the paragraph beginning "In class, the discussion begins with the emphases diagram. . . " Or perhaps we'll have to rework this whole little section. Still, it may be worth it. . . Savings: 1.5 pages.

p26: cut the Yancey invocation paragraph. Savings: .25 page

p29: rewrite our acknowledgments as a first endnote. Savings: .75 page

pp31-32: cut endnotes 9, 10, and 11 (on existing collaboration stations, on figure 1's "risks," and on the B.A.'s required courses). Savings: .75 page

pp33-38: cut citations no longer needed and "archival" citations of course documents (plus updating our MLA citation style to eliminate URLs) Savings: .5 page

p39: cut redundant biography paragraphs (in Danielle's ms., they appear on the manuscript's first page) Savings: 1 page

If I've estimated the savings correctly, these cuts would rid us of 7.25 pages. What do you think?

Thanks for considering--

J

Monday, April 27, 2009

Danielle's message (from Deborah Holdstein)

Dear Professor Dyehouse:

I write regarding your accepted _CCC_ manuscript. As you most likely know, my term as editor ends in December, 2009, and I am trying to publish all accepted manuscripts in one of my remaining issues. While Danielle Aquiline (my editorial assistant) and I first indicated to you that we would be passing along your manuscript to the incoming editor, we have other, very exciting news to report, and we ask that you read this memorandum with care.

Recently, a decision has been made to publish all of these manuscripts in two blockbuster issues: September, 2009 and December, 2009. These issues will each feature a good number of articles published in what we’ve called “hybrid” fashion—that is, having print and online components, as I have explained in several “From the Editor” essays.

As you may know, anything published in print or hybrid form in _CCC_ has undergone the same, full level of review as every other article we publish, and, of course, it has been accepted for publication. In this hybrid format, two pages of your article will appear in the print journal—and the title of your manuscript is listed in the full Table of Contents in the print journal—with clear direction to view the entire piece online in “The Extended CCC,” which replicates the print journal on screen with consecutive pagination.

Owing to budgetary constraints that make online publishing only slightly less costly than print, the majority of the articles will be featured in this hybrid/online “Extended _CCC_” (on the very permanent NCTE website).

We hope you understand that for your manuscript to appear in an upcoming 2009 issue of _CCC_, it is necessary for us to publish it in this part print-fully online form. Articles appearing in this manner are eligible for the Braddock Award and are searchable for scholarly work. As you may have seen, again, “The Extended _CCC_” appears on the secure and carefully monitored NCTE website. I have scheduled your article to appear in the December, 2009 issue.

Further, as we may have already indicated to you regarding your particular manuscript, we must ask that you cut your manuscript to a maximum of 30 pages. (If your manuscript is currently thirty double-spaced pages or fewer, then you can disregard this warning.) This, too, is to keep within our allotted costs. These pages must include your bibliography, brief bio, and abstract. So that we can meet our deadline and have the issues in production according to NCTE’s schedule, you must make these cuts and return your manuscript to us by Thursday, May 14. (And in doing so, please re-title the electronic file with your name, partial title of the ms, and the date of the current revision.) Keep in mind that after we receive and review your final version, it will have to be fact-checked and go through several layers of copyediting; there also needs to be time to respond to queries from one of the copyeditors. Then, you will see page proofs, and we will need a quick response at that time, as well.

As always, Danielle and I will be happy to assist you in any way possible as you do this important work.

We are very pleased to be able to publish all the manuscripts accepted during this editorship; we acknowledge that “hybrid” publication (part in print, all online) might not be what you had anticipated. If you do not wish for your work to be published in this way or if you are unable to make the required cuts, you may be released from your consent to publish so that you can submit your manuscript elsewhere. Of course, we hope you will choose to publish with us in the flagship journal in rhetoric and composition. Should you have a chair, tenure or promotion committee, or other contact person or evaluation committee that will want further affirmation of the review process and the reasons for these forms of publication, I am happy to write such letters, and I have already agreed to do so for several authors.

Please feel free to look at a recent issue—December, 2008 or February, 2009—and check online for “The Extended _CCC_” (www.ncte.org/cccc/ccc) to see more specifically the way your article will appear.

We greatly appreciate your willingness to work with me and with Danielle during this exciting and transitional time. Please let us know immediately (writing to me and copying Danielle) that you have received this e-mail and intend to send us a revised manuscript if yours currently exceeds thirty pages. And if you need Danielle to send to you the most recent version in our files to expedite your work and to make sure we’re operating from the same version, she will be glad to do so.

Please let either of us know if you have any questions or concerns.

Best,
Deborah Holdstein

Friday, February 02, 2007

Revised Environment/Information/Ecology section

Well, here's a new version using Jeremiah's draft as a frame. I'm also sending it out in a Word document since it is a bit lengthy.

mp
_________

"Environment": A Core Concept for a Core Course

The present iteration of WRT 235 hinges on students' and teachers' explicit consideration of "writing environment" as a concept. In the context of the opportunities the course makes available for learning functional literacies, students and teachers conceptualize writing environments spatially and materially—in terms of how actual writers can effectively work with (and through) literacy technologies. In the context of more specifically critical literacy learning, students and teachers consider the social and technical limits of literacy technologies, thinking through writing environments as "built" (i.e., as information architectures) and as "found" (as information ecologies). Finally, as an overture toward the rhetorical focus of the major, students and teachers combine these conceptualizations in thinking about writing environments as environments for social action. Whereas in a previous iteration of the course, students and teachers focused on writing environments as productive of (written) identities, the contemporary course highlights both what "writing environments" may be and why writers might want to engage with them.


Why envinroment?

We rely on the use of environment as not just another information metaphor but as more representative of the information contexts within which our students compose. The common metaphors for understanding and envisioning information systems are architecture and ecology. While these metaphors influence our use of environment, we see environment as more reflective of the networked situations of our digital writing/writers. As the WIDE Research Center Collective notes in their argument “Why Teach Digital Writing?” the networked computer created a “changed writing environment.” This environmental approach allows for the continued dispersement of writing in both small and large applications, creating a plastic metaphor for the writing we encourage in our writing and rhetoric major. As outlined in the “CCCC position Statement on Teaching, Learning, and Assessing Writing in Digital Environments,” composing digitally refers to a variety of literacies, applications, genres, classrooms, and technologies. This variety requires a more networked metaphor, such as environment. In what follows, we highlight the key aspects of information environment in contrast with the more frequently used concepts of architecture and ecology.

Describing composing in an environmental framework, appeared in the mid to late 1980s as the possibilities of composing with personal computers spread. In particular, John B. Smith and Marcy Lansman, in “A Cognivitive Basis for a Computer Writing Environment,” connect the “revolution” in computers to the new “writing environment” possible for writers. However, these conceptions of writing environments focused on their role in producing “effective writing” (Glynn, Oaks, Mattocks, and Britton 1). And examples of early computer writing environments were “commercially successful word-processing programs” (Glynn, Oaks, Mattocks, and Britton 1). Our understanding of writing environments evolved with the rise in the networked computer. In fact, it has become commonplace to reference digital environments, which, we assume, encompasses a networked computer with a variety of composing software. For example, the field’s current understanding of “computer writing environments” has achieved its most public usage in Michigan State University’s Writing in Digital Environments (WIDE) Research Center. In their “Why Teach Digital Writing, the WIDE Research Center Collective points to a “changed writing environment—that is, to writing produced on the computer and distributed via the Internet and World Wide Web” (WIDE Collective).

While we owe a debt to WIDE’s use of environment, we see it as more than a descriptive concept for the digital writing of today’s students. We see environment as a pedagogical concept that can offer our students a rhetorical framework for encountering composing situations in our classrooms and without. While the networked nature of digital writing is important, the concept of an environment must encompass the variety of composing situations that our students find themselves in. Technology foregrounds the materiality of literacy, according to Christina Haas, and environment, in our use, and with our students, highlights the materiality of a composing situation—networked or not. As Christine Borgman notes in From Gutenberg to the Global Information Infrastructure, “People [Writers] select and implement technologies that are available and that suit their practices and goals” (3). Our understanding of environment echoes Jon Udell’s depiction in “The New Freshman Comp”: “A social application [such as wikis/Wikipedia] works within an environment that it simultaneously helps to create. If you understand that environment, the application makes sense. Otherwise it can seem weird and pointless.” Writers and applications work together to create and sustain environments, as those same writers work through or within environments. As Johnson-Eilola and Selber write, “Technologies are no longer tools to users; they are environments, spaces, worlds, and conversations” (emphasis added x).

Recent work on the infrastructure of digital writing adds an institutional and material aspect to environment that we appreciate. Specifically addressing the production of new-media compositions, Devoss, Cushman, and Grabill target the “institutional infrastructures and cultural contexts necessary to support teaching students to compose with new media” (16). A “productive and activist understanding of infrastructure,” they contend, is necessary for writing programs “to come to terms with how to understand and teach new-media composing” (22). Our use of environment illustrates that an awareness of infrastructure is necessary in all composing situations, not only new-media composing. Students respond to communicative problems that are not necessarily new-media problems—but they are problems with material and infrastructural problems and constraints. Perhaps our implementation of environment echoes Mary Hocks’ depiction in her approach to visual rhetoric: “Critiquing and producing writing in digital environments actually offers a welcome return to rhetorical principles and an important new pedagogy of design” (632). While an understanding of infrastructure—and the materiality of all composing—is key, that understanding must be pedagogically feasible for teachers and students in our program. Borgman’s use of infrastructure describes it as outside of a composer in which, we interact with different infrastructures but are not a part of them: “a global information infrastructure is a means for access to information” (30). Environment lends us a flexible framework for talking about composing from the composer’s perspective.

Beyond having a strong infrastructural component, our understanding of environment reflects an attempt to reconcile our teaching situation, program, and students with the concepts of information architecture and information ecology.

As outlined by Richard Wurman, information architecture, engages in the “building of information structures that allow others to understand” (17). Of late, information architecture has blossomed in the networked possibilities of the World Wide Web (Rosenfeld and Morville; Lipson and Day; Morrogh).
Some in the field of technical communication have pushed for information architecture as a useful and productive area of study and example for the education of technical communicators. Michael Salvo, in particular, pushes for the inclusion of information architecture in our technical communication pedagogy. In his “Rhetorical Action in Professional Space: Information Architecture as Critical Practice,” Salvo convincingly describes information architecture as a “user-centered art of rhetorical design” (41). Rather than merely describing situations, information architecture, according to Salvo, allows for and illustrates the potential for action on the part of technical communicators in the designing of information objects. In other words, it is a “critical rhetorical strategy for intervention” that “ensures opportunities for agents to participate in long-term design and planning” (Rhetorical 54). In an effort to jettison the overused concept of community, Nicole Brown, in “The Regionalization of Cyberspace: Making Visible the Spatial Discourse of Community Online,” points to information architecture as a strategy for “defining” and “constructing” “informational paths,” as well as “conceptualizing online learning spaces and the writing and reading that occurs in these contexts.”

While I am convinced by both Salvo and Brown of the possibilities for information architecture, especially by Salvo’s claims for its importance in technical communication pedagogy, the concept holds less promise for our purposes in designing and implementing a writing and rhetoric major—and for creating a productive approach to our students’ composing situations. With its history in architecture and online information, information architecture might be too technical or professional for our programmatic and pedagogic needs. Information architecture revolves around a (professional) concern for users interacting with/in online contexts that does not capture the online and offline networked environment within which our writing and rhetoric major operates.

Seemingly more closely aligned with an environmental approach, information ecology represents an oppositional metaphor, in many cases, to information architecture. Even within Salvo’s illustration of the possibilities information architecture offers technical communication, he introduces information ecology in order to distinguish the two metaphors (Teaching). Gaining one of its first treatments by Marilyn Cooper in her 1986 article, “The Ecology of Writing,” ecology provided an alternative to the solitary author of cognitive models of writing. Ecological systems, according to Cooper, are “inherently dynamic,” and reflect the fact that “all the characteristics of any individual writer or piece of writing both determine and are determined by the characteristics of all the other writers and writings in the system” (368). Focused on the act of writing, Cooper described a model of writers mediating information systems as they compose.

Although Cooper was not looking at information technology in particular in her conceptions of an ecological approach to writing, she was providing an alternative to the cognitive model of writing. Similarly, Bonnie Nardi and Vicki O’Day, in their book Information Ecologies: Using Technology with Heart, rely on information ecologies as a metaphor for our interaction with and understanding of information technology. They define an information ecology as “a system of people, practices, values, and technologies in a particular local environment” (49). Rather than focusing on technology, information ecologies highlight human interaction with technologies. The authors push for people to “get involved in the evolution of their information ecologies—jump into the primordial soup, stir it around, and make as many waves as possible” (58).

In the field of technical communication, the ecology metaphor has been employed in the study of workplaces, especially the proliferation and evolution of genres within workplaces. In particular, Clay Spinuzzi has developed the analytical framework of genre ecologies as means for investigating compound mediation in workplaces through a “community-centered interpretive view” (Compound). Through his investigation (tracing) of genres in organizations, he shows how genres mediate the interactions between humans and technology (Tracing). In other words, genre ecologies are the “dynamic and unpredictable clusters of communication artifacts and activities” mediating humans’ interactions with complex technologies (Spinuzzi and Zachary 170-1). Echoing Wurman’s vision of information architecture, Spinuzzi and Zachary see genre ecologies as a means for analyzing and aiding the (over)flow of information.

In this sense, we agree with Salvo and his criticism that an information ecology approach is too descriptive, limiting the involvement of users in the design of artifacts and systems. For our purposes, many information ecology approaches take an overly technology-centric focus. Even in the genre ecologies metaphor, technology, or genre, is given too much agency. We want to focus on writing and the writing done in local environments. Ecology works for describing a scene and examining how technology functions in that ecology but, at least in the work of Nardi and O’Day, the concept relies on its biological roots. Just as humans and nature share an ecology, humans and technology share information ecologies. While Spinuzzi bypasses this biological approach, he relies on genres as the mediating artifact for examining an open/ecological system. As writers enter different environments they have different technologies, needs, goals, audiences, etc. Environments are more transferable than ecologies while at the same time giving agency back to the writer, without reasserting a cognitive approach. Essentially, we want our students to analyze and produce in a variety of environments that result from a communicative problem.

Relying on Johndan Johnson-Eilola, we see environments as more similar to his depiction of the datacloud. Writers inhabit information environments and rely on information as a resource. Johnson-Eilola labels our work with information in these environments as “rearranging, filtering, breaking down, and combining” (4). These activities are required as users reconstruct technologies within specific contexts. In essence, users are designers/writers in environments. In his depiction of information environments, Earl Morrogh separates the users from the designers, or information architects; he then defines information environments as “physical and/or computer-mediated information space within which context is defined by real and conceptual structures” (109). While we agree with Johnson-Eilola that the “moment of use” is crucial to the “specific nature of uses,” we see that moment of use and reconstruction due to the numerous forces in that moment as culminating in an environment. Therefore, unlike in Morrogh’s use of environment, writers are the users and designers of an environment. As writers work within an environment, the “separation between online and IRL is tenuous” resulting in a “spilling over” of relationships, communication, documents, and identities. Environment more closely encapsulates this inhabitation of information represented by the datacloud.

But, we are interested in environment, ultimately, as a teaching concept. It must be a concept that is descriptive and productive for students both in and outside of the classroom. Echoing Hocks, environment must be a transferable and flexible “pedagogy of design.” While it is introduced in WRT 235: Writing in Electronic Environments, the concept must resonate with WRT 201: Writing Argumentative and Persuasive Texts, as well as upper division and capstone courses such as WRT 495: Capstone in Electronic Portfolios. Leaving the confines of Writing in Electronic Environments should not parralellel a departure from the environment concept.

Friday, January 26, 2007

new 1st para. draft

For many of us, Kathleen Blake Yancey captured an opportunity—what she called a "moment"—for composition as a field in her 2004 CCCC Chair's Address, "Made Not Only in Words: Composition in a New Key" (297). In that address, Yancey describes a "tectonic change" under way in the ongoing development of literacy practices linked to the digital computer, a change that reorganizes literacy both in and out of schools (298). "We have a moment," Yancey argued, and it calls for the accommodation of schooling to our students. Our students, like others in the newly developed "writing publics" that Yancey evokes, do not seem to require our aid or certification: in their technologically-constituted literacy activities, they "think together . . . organize . . . and act within [digital and online] forums" (301). Teaching these students, Yancey suggests, means paying attention to Cynthia Selfe's "technology-literacy link," accommodating our teachings to what we discover in that connection. Measuring our concerns against our optimism, teaching these students means engaging them in the ongoing development of their literacy practices and "literate lives" (Selfe and Hawisher)—meeting, them, that is, in the development of their written and writing selves and in the places or environments in which they write.

Friday, December 22, 2006

conversation with a student

Just finished the following conversation with Barry, a former student in my WRT 235 class.

J: Barry, you took a course with me entitled "Writing in Electronic Environments." How would you define an electronic environment for writing?

B: Ah--uuh--hmm. How about anytime you're using a computer to write?

J: OK, but how would you define it? In terms of space? The spaces where you work? In terms of technologies? The technologies that you use? Socially? In terms of social context?

B: All of those?

J: OK. Hmm.

B: Well, it sort of depends on what you mean by writing, doesn't it? . . .

J: Wow! Great answer! Great question! Thanks, Barry! [Walks away, mumbling: "It depends on what you mean by writing. . ."]

B: Do I get an "A" for that?

---

Great stuff, and a great question from Barry. I think it may be that we ought to focus on the connection Barry offered: how we conceptualize "electronic environments for writing" depends centrally on how we conceptualize writing--and vice versa. So: discussion of "environments" offers a kind of alternate approach to talking about definitions of writing. . .