- Teach everything you know
- Create every day
- Work in public
Simple rules that apply to a lot of areas of life and work.
Simple rules that apply to a lot of areas of life and work.
A wonderful essay in A List Apart titled Writing Is Thinking highlights the importance of understanding what you read.
Because writing—that first leap into taking your idea and making it a Thing People Read—isn’t really about wording. It’s about thinking. And if you can tell the difference between an article that knows what it’s about and one that exists purely to sell ad space, then you’re pretty good at that already.
Understanding what you read…That’s the core of information literacy. Pleasant surprise to reach the end of this article published in a Web design journal to see that it was written by someone with a background in librarianship.
An excellent overview of the current state of software development by one of the most reasonable voices in the industry.
Some thoughts in progress spurred by Don Waters, a program officer at the Mellon Foundation, who has written an overview of the digital humanities. Waters has had a distinguished career as Associate University Librarian at Yale, then as the first director of the Digital Library Federation, and has served Mellon for nearly fifteen years as a key decision-maker in what the foundation funds in the area of scholarly communication and digital content. Considering his stature in the profession it’s worth reading closely what he has to say about digital humanities (DH).
He dismisses the notion of digital humanities as a distinct discipline based on his own experience of funding many humanistic projects that centered around technology. Instead, he focuses on the tools and methodology approach in referencing DH. And that’s fine even though I don’t entirely agree. The key, however, is not to get bogged down into the “cloud chamber” attempting to define digital humanities. Waters clearly points out that a significant problem in the debate over DH is that “[p]art of the definitional problem is that more needs to be said about the nature of the tools and methods for interrogating evidence in the digital humanities.”
As librarians and technologists with expertise in those tools and methods our obligation is to ensure that we advise faculty and students appropriately as to which approaches to use when addressing research problems. This is an extension of our traditional mastery of research tools (e.g., databases, specialized resources) and how to use that material as part of the research process. Advising which approach to take in a DH project is similar to our advisory function at the research desk. Just as some questions at the research desk may best be answered from a set of ready reference materials while others require more in-depth consultation and research, some DH inquiries are relatively simple projects handled by a small set of available tools while other DH-based research questions are best served by more complex approaches.
In reflecting on the ways that critical intelligence is applied in humanistic research Waters identifies that the tools and methods of DH fall into three strands: textual analysis, spatial analysis, and visual studies. (Waters correctly pinpoints visual analysis as emerging from the field of media studies.) “As a rule of thumb, those who refer to the digital humanities, or to the use of digital tools and processes in humanistic study, are almost always pointing to activities and the types of tools needed in one of these three areas.”
Waters provides a brief, though admittedly simplified, intellectual history of each area, starting with how language and literary studies in DH emerged from the work of Jerry McGann at UVA. Spatial analysis emerged from GIS with one of the key humanists adopting mapping strategies being Ed Ayers in the Civil War history project at UVA. (Ayers is now President of the University of Richmond.)
While Waters doesn’t mention a specific person catapulting a change in media studies, a key figure in that area is Lev Manovich, author of The Language of New Media. Waters stresses that “the scholarly toolkit must include a suite of specialized digital tools including various kinds of visual representations, both because the visual objects of study are digitized or born digital, and because words alone may not be sufficient to understand visual evidence and communicate an argument about that evidence.”
If you don’t read any other part of Waters’ essay, then read the last two pages (8-9) that start under the heading Future Prospects in which he outlines “several areas that colleges and universities, particularly their libraries, might consider for possible additional investment.” In fact, these aspects have essential relevance to our own initiatives:
Waters ends this essay with “But we must also think broadly about curricular interventions, for it is only when the tools and processes for answering ‘why possible?’ questions are reliable enough to be introduced to and used productively by scores of students at once that the digital humanities could be said to have reached maturity.” Clearly, a challenge is figuring out how to adapt DH tools and methodologies for use in an undergraduate curriculum.
I’ve not yet read one of Guy Kawasaki’s books but many people have, especially those interested in entrepreneurship & startups. Alan Rinzler over at The Book Deal blog recommends Kawasaki’s latest book: APE, Author, Publisher, Entrepreneur . How to Publish a Book.
Rinzler explains that Kawasaki has coined the term artisanal publishing to describe a form of self-publishing where the author lovingly crafts a book without the restrictions of traditional publishing. I wholeheartedly agree with that approach.
I don’t mean for this post to be a promo plug but it’s relevant to this very topic: my wife is a book designer. Her clients are almost exclusively self-published. They all seek her out because they want a particular style cover or page layout. And she stays fully booked (which is why she hasn’t blogged in almost two years). I’ve closely observed the process and interaction between her and the authors. Many of those authors are clearly entrepreneurs and have been successful with their books (as success is defined by them). Others have been a bit naive about the challenges of marketing. It’s clear in their discussions with the designer that these authors really care about making a wonderful book. All of them embrace the spirit of artisanal publishing. And, I have to say, that my wife is pleased and satisfied to give them a lovely designed book.
Any great product takes a team, finally. Often the author, though, isn’t the best person to manage that process. Some authors can’t make decisions or they want to try everything. That brings up where the author needs to act like an entrepreneur. Self-publishing is a process that needs to be managed. Craft your book, be careful about who you hire, but trust the professionals you engage to aid you in the publishing process.
That brings up Rinzler’s lament that Kawasaki doesn’t even bring up the topic of a developmental editor. I totally agree with Rinzler about the importance of a developmental editor. Unfortunately, many self-published authors are so emotionally invested in the manuscript they’ve written that they feel almost offended if an editor suggests changes. Sadly, that’s the behavior of an inexperienced writer (the very kind that most needs a developmental editor). Authors – listen up: an editor simply wants to help you make your book better. Really.