
Jeff Rice posted
a brief reflection on the
Institute for the Future of the Book meeting we just attended. And Steve Krause posted
a response with some further thoughts about book publishing. I have some comments and hope to keep talking about publishing textbooks in the field but wanted to journal some of my thoughts on the meeting before they dissipate:
In some ways I’m a bit surprised that a concrete way forward failed to materialize. I guess, though, I’m not that worried about it. Jeff makes a good point about the need to simply talk over things and also made a good point in the meeting regarding not trying to hit a home run when integrating technology into teaching for the first time. The morning blue sky session went well, with large concerns about creating a new “book” that allowed a hybrid model that blended scholarship with typical textbook instruction. The idea was to make pedagogical authorship easier to recognize in terms of promotion and provide an extra layer of information for teachers using the book or students wishing to take things to the next level. We also moved toward a model that includes folksonomy-based interaction and filtering. We wanted the ability to tag items already in the collection and to customize the materials based on key terms. A big focus was on developing something modular that would allow instructors to combine models as needed to construct a course. To my mind, the assignment or syllabus creation piece of a new book could serve as the main entry point (at least for thinking about how to create and organize the materials). This is something I’ve wanted for a long time and something Johndan mentioned trying to implement with publishers in the past—a course builder tool that operates on a semester-based timeline. Much as one can drag, drop, arrange, and edit video clips in something like iMovie, an instructor can compose a course based on these modules that come with layers like the pedagogical and scholarly component that might contextualize the work as she puts together the syllabus. We also spent time talking about how to integrate content-oriented resources into the project—a media archive, links to openly available online materials, possible functions for uploading sample projects and additional readings. So, the highlights for me that we came up with were the hybrid text that includes a scholarly layer, the folksonomy participation tools, the modular organization with syllabus composing tools, and the fluid access to rich resources in many modes—all terrific specifications for a next-generation teaching text.
Our afternoon session, however, was more remarkable (to my mind) for what it revealed about the readiness of the academy to implement such a project. After an initial attempt to think about the project modules that might go into the collection and the listing of a few possibilities we began to try to more carefully spec out the functionality, but quickly took up questions of how radically we were altering the existing model of knowledge creation and textbooks. This was a frustrating conversation to my mind as it ultimately hinged on terminology and priorities, Some members had problems with calling projects things like “audio essays” or the notion of the syllabus, the assignment, and assessment. Ultimately we ended up debating the pitfalls of replicating print logic and pedagogy in a discussion that centered on the inadequacy of these terms and of the project to capture a free-wheeling, remix-based composition that could not be addressed or assessed in conventional terms—at least that was the question under discussion as I heard it.
To me, however, this debate reduces to the familiar saw about the shape and certainty of language and the level of abstraction we should bring to our work. Wondering whether we might call the module an assignment rather than a project, doing away with assessment, or calling something a studio, or kitchen, or whatever instead of a syllabus builder is really a debate about the influence of language and culture and our ability to resist their control. Yes, we replicate when we work within the system or extend rather than tear down the system, but whether it’s even possible to escape such inevitabilities is also open to debate. Replace the essay with the mash up? Sure, but don’t imagine that will break the bonds of institutional and linguistic control or that everyone agrees about the nature of those bonds or that control. Arguing against a potential system because it falls prey to the vagaries of language, institutions, and culture is a bit disingenuous unless one recognizes that the debate boils down to the cracking of the epistemological walnut of knowledge status and creation. Sure, at some level the nut cracks revealing the fundamental uncertainty within its fragmented shell, but even the most radical dissolutionist recognizes the others may want to leave their walnut whole, or move forward using the leftover pieces, And here’s where taste comes in. I prefer my metaphysics with some certainty and pragmatics stirred in. I’m comfortable working with the existing structures of knowledge, trying to tweak them, build on familiar terms, even tradition. Bringing some inescapable printcentricity into the project poses no problems for me. I suppose it’s not surprising that questions about the status and shape of knowledge circulated a good deal in the meeting. For the most part the questions lead to helpful insights, but they also pulled attention away from how we might go about actually making something rather than talking about it.
Well, attach slash soapbox to the end of that paragraph. I’m excited about the demonstration of Sophie that we had. My experience using TK3 tells me that authorware offers great promise as a way of making multimedia publishing a viable option for teachers and students. I have worked on electronic accompaniments with the outsourced-production-team and content-provider model and can say they really miss the boat in terms of asking book authors to work as composers with new media. Every book now has gobs of media magic in its content. The next step is to get some into the production of the ideas and the book itself. My sense is that it will be slow going, but that since Sophie will be open source and extendable it may be one of the main avenues to go down in the next few years. I’ve resolved myself to compose some sample book stuff with it as soon as the beta version comes out and to see about working on the DRM and licensing issues as part of any project I take on with a publisher.
I’ll say more on that in the near future. I’m eager to open up the book and its production process to exactly the kinds of ideas we started hashing out in the meeting.