Agile (Digital) Public History: Preparing a New Generation of Cultural Heritage Professionals

April 30th, 2012 § 0 comments § permalink

[This post was inspired by a panel on the Envisioning the Future of Public History Training at National Council of Public History 2012 in Milwaukee.]

The increasing interest number of courses and concentrations focusing on public history suggests that we need to have a serious conversation about what are the skills that are necessary for students to pursue careers in public history in the 21st century. In his presentation for our panel on the future of public history instruction, Steven Burg from Shippensburg University offered preliminary survey results that suggested that digital history is a core interest for course development in a of public history programs. Those results lead to questions about what kinds of digital history training these programs are offering.

The NCPH Curriculum and Training committee works hard to offer guidance on these questions by producing a series of recommendations for best practices in graduate and undergraduate education, and for internships and certificate programs. The document focused on masters programs [PDF] offers guideposts that address the need to train students to be effective research historians, but also to provide them with practical skills in an area of concentration, hands-on experience through internship work, and an in-depth capstone project of some sort. Despite the fact that the document was adopted by the NCPH Board of Directors in October 2008, there is almost no mention of digital skills or digital public history work in the recommendations.

While I don’t have any concrete data on what kind of digital skills individual public history programs are teaching to prepare their students to do public history in a digital environment, I do know what is being taught in the required set of digital history courses for candidates in the PhD program at Mason. We cover a range of areas that engage theoretical questions, methodological approaches, and practical skills. This approach helps graduate students begin to enter into the major conversations in the field of digital history and to start to conceptualize and produce their own digital projects. Based on this teaching and my experience collaborating with cultural heritage organizations on digital projects, I have some recommendations on the skills public historians need to demonstrate to claim competence in digital history.

First and foremost, students need to use digital technology to do good history and to model that practice in public. Of course, this is not really about the technology, but more about carefully considering the framing of historical questions and demonstrating the elements of historical thinking skills such as effective contextualization, and considering multiple perspectives, causality, and shifting interpretation. Engaging in this type of authentic work in public raises all sorts of questions about authority and expertise. In the digital space the public has so many venues in which to respond, question, and challenge based on their existing knowledge and assumptions. The trick is to meet these users where they are and bring them along through the process of inquiry so that they arrive at more nuanced understandings of the past. Done well, this dialogue can lead to deep attachment and investment for the public, so public history programs cannot neglect the central communicative aspects of good digital work.

Focusing on the ways that student can communicate the stuff of history and the practice of doing history in a rich context inevitably should lead to a conversation about disaggreggating the far-too-vague concept the “audience” or the “user.” Being able to identify and target specific audience segments will be essential for doing good digital public history work. There is no single or general user profile. Students need to know how to identify and assess the needs of their core constituencies. Retirees with an interest in local history will have vastly different concerns than middle school history teachers, who in turn will have different needs than scholarly researchers.

Next, students need an introduction project development and planning that embraces agile development. Most history majors never consider issues of collaboration and management in their course work, but public history is about project work. Students need to learn what it takes to plan a collaborative projects and see it to completion. In the digital realm, this will be both a question of clarifying intellectual goals and creating technical work plans. I have written elsewhere about teaching project management, but it’s worth emphasizing here why agile principles are important. Agile development began as a movement to resist the heavily managed and bureaucratic methods of software development. Based on the notion that frequent builds, assessment, and correction allow for more nimble and responsive development, agile methods offer a model for digital public history too. Projects can start small with existing tools and resources. From that base the project team can gather information about audience response and content framing that can then be rolled into the project work flows. The emphasis here is on moving quickly and learning constantly. These practices are particularly well-suited to small organizations with slim technical infrastructure and staffing.

Turning to the technical front, students also need a sense of sound design and development practices, including the basic forces that make the web work: HTML, CSS, content management systems, etc. It is too much to expect that students would graduate with deep knowledge of these building blocks, but they need to be familiar enough with the structural elements that they can interact with developers and designers who do possess the technical knowledge to build customized sites and applications.

Despite the need for this general technical knowledge, students must have a sense of how effectively to use existing software and services to stand up quickly a digital project. In some cases this will be as simple as meeting audiences where they are already gathering on the web by sharing collections and expertise on HistoryPin or Wikipedia. In other cases, it will mean using existing outreach and communication venues such as Twitter, YouTube, Tumblr or WordPress to share the exciting work of public historians and their organizations. Furthermore, students need to have a sense of how to use software-as-service tools such as Omeka.net, Drupal Gardens, Dipity, Viewshare, and GeoCommons to produce narrative exhibits and data and geospatial visualizations that can communicate historical complexity and can engage audiences with historical questions and materials.

These are just the basics, but I don’t see how we can ask anything less from our public history students if we are to claim to send them out into the world with training in digital history.

On DH Work Load and Creativity

March 25th, 2012 § 8 comments § permalink

I shouldn’t be writing this. I should be commenting on student project proposals and working on an article that is three weeks overdue. And, that is exactly why I’m writing this.

Recently at RRCHNM we’ve been having a lot of discussion about why some of us offer much less in the way of public commentary on the field, our work, and the various and ongoing controversies, such as the relationship between “Maker DH” and “Theoretical DH.” As someone who is a little bit on the quiet side of this divide, I have been considering how I got there. It’s not as if I’m not deeply engaged in the work of DH–and here I mean Digital History, not Digital Humanities, because that is the primary work I do. In fact, I think that the deep engagement with work, DH and otherwise, is the reason for the quietude.

Let me explain.

As the director of the public projects division at RRCHNM, I am currently responsible for the forward progress of nine projects (soon to be ten — Thank you, NEH Division of Public Projects, for funding our mobile site on the history of the National Mall). That means nine work plans, nine sets of reporting requirements, and nine sets of deliverables. None of that work would be possible without the incredibly hard work of the twelve people who make up the public projects team (if you don’t know them yet, you should). Together, twelve months a year, we do the work of digital history, producing websites, software, implementation guides, and whitepapers. It is tremendously fulfilling work, but it is a lot. And there will be more since we are grant-writing non-stop (two major applications in the last 6 weeks).

Then, I have my own commitment to teaching, which is not part of my job at RRCHNM at all. For someone who is not a natural in the classroom, I love teaching. I love interacting with students and helping them develop the skills they need to pursue their own interests. That is why I have taught each semester for the last seven years. In addition, I usually find myself with a senior thesis or two to advise or a directed reading to oversee, or both. Again, this is tremendously fulfilling work, but it is a lot.

As for my own work, I have a book manuscript slowly grinding through the process of becoming one of those old-school traditional monographs. Since, my work on that is basically done (I hope), I am hatching another project in the back of my head. I’m reluctant to let it come to the foreground because I don’t really have the time to dedicate to it, and I could do without the distraction of a project that I can’t realistically pursue. And, then, there is the article for the edited collection that is three weeks overdue.

While this may sound like an extended whine about my work load or a covert call for help in learning how to say no, my real point here is to suggest that with all of these balls in the air, my brain doesn’t rest long enough for me to do nearly as much productive, innovative, and creative work as I would like. If I worked less, I would blog more. Sad, but true.

And I know that there are many many more like me–inside DH and out. One way I know is that we’re beginning to see more and more research telling us that we need to slow down in order to be more productive (See this article urging a return to the forty hour work week, or listen to Krista Tippet’s interview with neuroscientist Rex Jung).

So, as an experiment in April, I’m going to try to heed this advice to slow down some in hopes of thinking more, and being more creative.

Anyone care to join me?

(But, for now, I’m gonna go do that work for the kids….)


Blogging for Engagement and Understanding

March 4th, 2012 § 2 comments § permalink

Prompted by a twitter conversation with Miriam Posner about the need for a really basic introduction to using blogs in the college classroom, I’ve been reflecting on the ways that I’ve come to use public writing in my own teaching over the last fifteen years or so — both on the level of changing technology, and on the level of the scholarship of teaching and learning.

First, some background….

As an undergraduate at Georgetown University, I had the good fortune of working for and with Randy Bass, who even in the very first years of the web was leading the charge to encourage faculty to use technology to improve their teaching. (It is no surprise for those of you who read his blog and Profhacker posts that Mark Sample, aka “The Naked Professor,” then a masters student in the English Department, was also an integral part of those conversations and that work.) Randy often used to begin conversations with teachers by asking them what kinds of things they would like to change about their teaching. What would you like to do better? And, what tools can we use to help make that happen? To me, this is the essential heart of the right approach to using technology in teaching. It begins with an issue with the teaching and learning and then turns to the the task of implementing an appropriate intervention. These are the basic building blocks, regardless of the content focus or the digital tools at hand. What could be going better in your teaching? What do you wish your students would do more of? Do better? What do your students need to improve their learning?

These conversations coincided with work on several really important efforts at Georgetown. Mostly, I was marking up things in HTML, but Randy and Mark and other were working with faculty around the country on Engines of Inquiry: A Practical Guide for Using Technology in Teaching American Culture (1997), published through the American Studies Association’s Crossroads Project. (Sadly both of those projects are no longer available on the web, but Mark is working to resurrect the essays from Engines of Inquiry.) This work rolled into the first summer gathering for faculty interested in technology and pedagogy, where the main conversation was about deepening student engagement and increasing their ability to communicate the complex ideas that might result from that deepened engagement. That meeting has continued to be held summer after summer, eventually coming to be institutionalized in the Teaching, Learning, and Innovation Summer Institute. So, as I was making the transition from being an undergraduate who worked on some basic web projects to beginning a graduate student who was developing my own approach to teaching, my thinking was infused with the findings of these scholars who were committed to doing research on how to improve teaching and learning.

In Fall 1997, I arrived at the American Studies Department at the University of Minnesota with a graduate research assistantship that called for me to help implement some web elements for the department, particularly with respect to the core curriculum. Over the course of that year, I built a bunch of websites (by hand, using tables) that offered support for those courses, some of which had six recitation sections. That spring we installing threaded discussion boards to support the small group work in a large American Indian Studies course. I wasn’t in the classroom on a regular basis to see how the asynchronous discussion supported engagement, but from what I did see students seemed to be in conversation with one another and the materials. It was a good lesson about priming the pump, but in my own teaching at the UofM I mostly used websites as a way to deliver the syllabus and course materials.

I returned to the DC area in the August of 2004 to start work at CHNM. That return coincided with the closing meeting of the Visible Knowledge Project, begun by Randy Bass and his colleagues at the Center for New Designs in Learning and Scholarship in 1999, to encourage research on teaching and learning. So Roy Rosenzweig and I spent several days absorbing the research and work that the project scholars had been conducting on the pay off of asking students to externalize their cognitive processes. My own thinking on teaching has been heavily influenced by the project’s resulting findings, which eventually were published in January 2009 in a special issue of Academic Commons: “New Media Technologies and the Scholarship of Teaching and Learning.”

The biggest take away for me from the VKP research was that students need to see their own process in order to repeat it in an independent way, and that the more they can think of themselves as being part of a larger public conversation the better their work will be. I took these two principles into my teaching with undergraduates and graduate students in subsequent semesters. To this, I added the goal of having the students significantly process and question the course materials before they came together for our face to face meetings. Unlike most teachers, I have only very rarely taught classes that met more than once a week, so making the most of a single almost-three-hour block is essential to running a successful course.

Now, onto the details…..

I have approached using blogs as a way to encourage engagement with course materials and peers in two ways over the last five or six years: with a network of individual blogs, and with a single place for shared writing. Both approaches have advantages and disadvantages, but generally, I find that using a single blog with lots of student authors works well with undergraduates, and that asking each individual to create an separate site works better for graduate students.

Regardless of whether the students each have their own blogging space, I always set up my course materials in WordPress. I provide the course schedule, required readings, general procedures, and a description of major assignments. For several years, I used the ScholarPress Courseware plugin to facilitate the mechanics of plugging the readings into the schedule, but for the last couple of semesters I’ve been using a newer version of WP, so I just created pages using basic HTML.

One approach to integrating public writing with a course is to ask each student to set up an individual blog. This has the advantage of assuring that they leave your course with the skills necessary to set-up and use a blog should they need to do that for another situation. While there are many platforms available, including Blogger and TypePad, I usually suggest that students go to WordPress.com for an account. It doesn’t get much simpler than that, and they learn the administrative interface for the most common stand-alone blogging software. Once the students have set up their sites, I use Google Reader to create a bundle of their RSS feeds so that I can follow their work through a single feed rather than having to check many different ones (thanks to the PressForward staff for the tips on doing this). Then, I post the bundle to the main course site so that everyone can subscribe to it. I find that this method is good for the graduate students who seem to have more willingness to maintain their own space over the long term, and to put a little bit more effort into the interaction of commenting. I ask the graduate students to blog each week in response to the major questions raised by the assigned materials.

Alternately, everyone can blog in the same site. This has the advantage of making for a single source of work. When asked this semester if they would rather set-up their own blogs or work within the course site, my undergraduates opted for using the main blog suggesting that a stronger sense of conversation was easier when everything is together. I generally agree with them. The only exception may be for undergraduates who have established an e-portfolio for their major and who might want to concentrate their writing in that space. When we all work in the same blog, I set up categories for each major author or thematic concentration so that we can easily navigate the large quantities of writing produced during the semester.

Whether using a network of blogs or a single course site, I don’t ask the undergraduates to blog each week. I divide the students into groups of four or five. Each week the students in one group are responsible for writing a blog post that engages the reading for the week and the larger questions of the course, which is due by 5pm two days before class. Then the rest of the class is responsible for commenting on at least one post (due by midnight the day before class). This results in students having to write at least two major reflections and to comment six or seven times during the semester. By requiring comments, I am forcing conversation and a sense of public accountability. Some semesters students do get into the spirit of conversation, but even if they are just fulfilling the requirements, we end of with a solid base for a conversation when we get to class. I’m happy to enter the conversation at that point, but I very rarely enter the space of the blogs, in part because I would like the students to feel like they can offer their thoughts and engage with one another without the sense that I’m waiting swoop in and turn the conversation or correct them. I do, however, read all the posts and the comments, and that writing significantly shapes the approach I take to the materials when we get to class. Finally, I grade all the main posts, and two randomly selected comments from each student. The random selection process of grading was suggested by Mills Kelly many years ago, and has, as he promised, generally guaranteed a reasonably high quality of response from the students. That isn’t too much writing for them, and it isn’t a ton of grading for me.

Of course, I’m neither the first, nor will I be the last, to write about this. One good place to start are the many useful posts on Profhacker in the teaching category.

Content and Context: Visualizations for the Public?

February 18th, 2012 § 4 comments § permalink

[Cross-posted from the Visualizing the Past blog for the NCPH2012 working group "Graphs, Maps, and Trees: Imagining the Future of Public Interfaces to Cultural Heritage Collections"]

In the very useful survey of the “history web” in their 2005 book Digital History: A Guide to Gathering, Preserving, and Presenting the Past on the Web , Dan Cohen and Roy Rosenzweig identify the range of genres that encompassed the historical content on the web: archival sites, exhibits and scholarly essays, teaching and learning sites, and discussion forums and organizational sites. Even though Cohen and Rosenzweig failed to account for the way that blogs, YouTube, and social media would eventually permeate the history web, I like their categories because they continue to the give us a way to think about what we do when we create public history online. We tend to provide access to collections, to offer interpretation, to offer instruction, and to offer a forum for conversation, both general and professional. So, as I began to think about the critical issuing in effectively using data visualizations in public history, I wanted to consider them in relationship to the activities above. Since Sheila has already written a great post on collections and enhancing access with visualizations, I’d like to focus both on their interpretative and instructive use, building on Trevor’s thoughts from his last post on discovery and communication.

For public historians, the mode of online outreach that has the longest history is that of interpretative exhibits, whether as companions to a physical exhibit or as independent works of scholarship. Despite the liberating possibilities for disjunction, many of exhibits hue very closely to the linear narrative structure of traditional narrative history. In doing so, they have demonstrated varying degrees of success in offering the public a glimpse of the richness of the past. Two sites from the National Museum of American History demonstrate the wide range of approaches. Both “The Price of Freedom” and “A More Perfect Union” are beautiful sites, but one presents a linear and reductive narrative of military history and the other presents the difficult topic of Japanese internment during World War II with a range of voices and perspectives that highlights historical complexity. The difference here is in the effort to bring together evidence in a user interface that allows for the consideration of many perspectives and multiple causality, as opposed to offering a single perspective that simplifies the past.

Successful or unsuccessful, most exhibit sites have the benefit of offering visitors a range of contextual information in both the text of the basic narrative and in the descriptions that accompany individual artifacts, images, or documents. This contextual information is essential for a public who may not have a deep background to bring to their encounter with primary historical materials. Data visualizations can short circuit the tendency to present simplistic narratives about our collections. Unfortunately, however, data visualizations that concentrate the user interface into a single interactive screen can also significantly reduce our ability to offer the public necessary historical context if we’re not careful.

Take, for example, the great interactive correspondence visualization created by the historians and computer scientists at Stanford for the Mapping the Republic of Letters project. This complex interface really only makes sense to individuals who are content experts, and sometime then only after they’ve read the accompanying pdf explaining the different facets of the tool. For a content novice, the tool is little more than a colorful toy because it links to primary sources in a subscription database, and because it lacks the biographical data on the correspondents that might make their network connections intelligible. If the visualization included access to a larger context of the enlightenment and background on the individual correspondents, it could be a powerful and concentrated way for the public to learn about the development of this period in Euro-American intellectual history. To some extent, we can excuse the Stanford project because it is explicitly a research venture targeting scholars of the enlightenment, rather than members of the general public

The Digital Vaults site from the National Archives and Records Administration, on the other hand, was created precisely to engage the public. Unfortunately, the project is completely hampered by its abstraction. The Flash version of the site gives users access to a seven randomly selected sources from a database of over 1,200. Clicking on a document, the user enters a web of connections to other documents based on shared tags. (The HTML version simply offers an alphabetical list of tags.) The sources have minimal accompanying metadata–usually title, date, and a brief description. While this environment is attractive and fun to play with, it fails to offer users enough context to make any historical sense out of the materials they encounter. Rather than offering and entree into NARA’s rich collections, the site leave users at sea with only their pre-existing historical knowledge to support them.

Unlike Digital Vaults, visualizations that make use of geospatial and temporal cues offer users more necessary orientation. One successful example is Minnesota Historical Society’s True North project, which offers users the ability to layer information in space in time to glean some understanding of the state’s history. While the interface does not link out to individual primary sources, it manages to offer enough cohesiveness that users can start to construct their own narratives of change. The National Museum of Australia’s History Wall is even more successful. Built on the backbone of a flexible timeline, the interface allows users to explore the lives of Irish in Australia between 1770 and the present, drawing on, among other things, the Australian Dictionary of Biography, and amazing Trove database that aggregates over 280 million sources from National Library of Australia. Together these elements let a user to explore within a much more deeply layered context that can push them to use heuristics that are important to historians as they make sense of the evidence from the past.

Considering this range of examples, I hope that we can begin to have a conversation about how to create and frame data visualizations that provide the public with new ways to access our content but also offer them enough context to help them begin to make sense of those materials in meaningful ways.

Some notes on process

February 14th, 2012 § 0 comments § permalink

… for American Studies Senior Seminar participants. Below are some places to start with work for a larger project of historical research. These are by no means prescriptive, but rather are drawn from my own years of work — including the year I spent working on a thesis for American Studies at Georgetown 15 years ago.

  • You need a question! Nothing is more important that having a strong inquiry question to keep your research and writing on track through the course of the project. You’ll need to refine it and elaborate it continually through the process.
  • You need a method! Mine is generally centered around historical approaches with assistance from cultural theory.
    • What is the process of history? At its most basic, history is the practice of learning about the past based on evidence from primary sources. Generally, historians look at questions of change and causation, and then try to offer interpretations about what happened and why. This is not as easy as it seems.
  • You need a field, or several! Historians care what other historians have thought about events in the past. These interpretations change over time and need to be accounted for in historical work.
    • Read as widely as possible in scholarly fields that are related to your topic. This forms your base of secondary sources, offers, context, and provides you with possible interpretations to engage.
    • Have an organizing system for your work from the beginning. Absolutely use Zotero. [Here is my current library.]
    • Search the databases that are related to your field for relevant articles. Start with the American Studies Research Guide. I really like American History and Life, but JStor, and ProjectMuse are also good places to start.
    • Consult Reviews in American History to get a sense of the scholarly conversations going on in the field.
    • Use your library. Search and browse the stacks. Skim and summarize individual works (what is the argument and how is it related to my work?). Be sure to read several reviews on each of the important secondary sources.
  • You need primary sources! The choices are endless here, but you might want to consult Archive Finder or the searchable catalog of website reviews from teachinghistory.org to be begin locating materials that might start to offer answers to your inquiry question.
  • You need to work through your sources!
    • Create a Zotero entry for each primary source. Take notes there. Sync often.
    • Cognitive science research tells us that there are particular ways that historians approach primary sources.
    • Write all the time: outline, make notes on significance, revisit your questions, constantly articulate your understanding of meaning. I do this with handwritten free writing, and plain text notes.
  • You need to draft! Write and rewrite. Writing is a craft that needs to be practiced with conscious attention. Even after doing this for 15 years, I rarely produce anything worth reading without three full drafts. Plan ahead for the amount of time that this drafting process takes.
    • Use models. Find a writer or work that you really admire and use that a guide for possible approaches and structures.
    • Use your writing groups and your advisor. It is almost impossible to write well in isolation. We need readers who offer thoughtful commentary and criticism.
    • Writing environment is really important. I need a clean, full-screen place to draft if I am working on a computer (Try OmmWriter or WriteRoom).
    • Scale matters to me. I have trouble writing on a large screen, and if I get really stuck, I go to paper and pencil. I write a lot by hand and then type it up. The transfer process gives me a chance to take a second pass and make an initial revision as I make things digital.
    • I do my notes as I go (Chicago Manual of Style endnotes, including discursive notes). Never leave them to the end of the process; you will never catchup and you will end up with lots of mistakes. Use Zotero to drag and drop citation information into your documents.
  • You need a platform to communicate your conclusions! Historical interpretation can take many forms, not just traditional linear narrative. We can talk more about this if you want.

All the Colors Mix Together to Grey

February 11th, 2012 § 2 comments § permalink

It’s snowing here in Pittsburgh–been coming down for hours in a fineSnow powder, resulting in a monochromatic morning. Just like everywhere else in the country, there hasn’t been much real winter here this season. I’m pretty sure that this is only the third or fourth substantial coating so far. The slow start to the day has allowed me to continue with some thoughts from my travels yesterday.

I’ve driven the route from DC to Pittsburgh at least half a dozen times for the last 17 years or so. I’ve come to know the landscape of Western Maryland and West Virginia along Route 68 fairly well. Unlike the mess and stress that is the Pennsylvania Turnpike, I find this a remarkably renewing drive. The landscape itself has a lot to do with it. The route literally cuts through the mountains rising from Frederick to Sidling Hill and then Town Hill and across to Garrett County and on to Morgantown. As a result, I get a good deal of time with dairy and evergreen farms and occasional mining sites that roll along the horizon to the left and right, punctuated by the sheared layers of rock that rise up on the edges of the highway as it slices through the mountains. Some days this is a brilliant green scene of new vibrancy, but at this time of year, it is a scene with a muted pallet–browns and greys, scrub and trees stripped of their foliage.The Ark And, that’s just the way I like it. The barrenness of the winter landscape leaves me space to think.

Just as it should be, particularly given the occasion for my journey. I was on my way to hear Maya Lin speak about her art, architecture, and memorials at the Carnegie Museum of Art. Her talk was the launch event for the installation of her current traveling exhibit at the Heinz Architectural Center. I’d seen the remarkable works in the exhibit when it was at the Corcoran a few years ago. True to form, it is art of the landscape, reflecting actual places in the world, both above and below the surface of the land and the water line, made of wood, particle board, recycled silver, wire, and pins. And, her talk was a discussion of the ways that landscapes and environments are constantly in flux, and how her work tries to illuminate the spaces of absence and void more than anything else.

Lin’s theme for the evening rolled into an introduction of her new project: whatismissing.net, which offers us all a chance to think about the ways that we are actively causing pieces of our natural world to disappear. She invites us to pause and question what is missing from our environment, and to remember those elements as a step to making a commitment to change.

LandscapeRoute 68 is a landscape of sparsity and I’m sure that there are legions of species missing in this region. For me, over the course of the last nearly twenty years, it has been a place for my mind to roam, working through difficult places in critical projects and important relationships, meditating on the deeply incarnational aspects of natural world–some of which only appear in the grey. New work emerges from the grey.

Introduction to Project Management in Digital Humanities

October 22nd, 2011 § 0 comments § permalink

Here is the outline for my workshop this morning on project management at THATCamp New England.

Conceptualizing the project

  • Collaboration — reach out to others in the field; know the field

Writing the Grant: Necessary fictions

  • Follow the guidelines
  • Select the staff
  • Create the workplan
    • Key Deliverables
    • Estimating work
  • Budgeting: personnel, materials, travel, indirect
    • Office of Sponsored Programs

Get the Grant==>Hooray!! What’s next?

  • Redo the workplan — reassess in light of changing technologies and staff availability and skills
  • Collaboration — reach out to others in the field; know the field

Team management: Trust

  • Protect the staff: administrative concerns, competing demands
  • Supply the staff: software, hardware, space
  • Meetings (syncronous and asyncronous communication)
    • Individual (how are things going? what can I do for you?)
    • Larger group (where are we? what problems do we foresee? how shall we proceed? concensus building)
    • Small group (paired programming, etc.)
  • Tracking systems
    • Github/SVN for tracking coding tasks and issues
    • Basecamp for tracking other project activities and deliverables

PI Responsibilities:

The buck stops with you, so it helps if you are at home with complex organizational systems and detail oriented.

  • Budget and Deliverables
  • Conflict management
  • Individual time management
  • Communication with the grant officers
  • Communication and work with the institutional systems
    • Administration
    • Office of Sponsored Programs
  • Learning enough about all of the elements of the project and the technologies to make decisions comfortably.

Looking Back and Looking Forward: 911digitalarchive.org

September 9th, 2011 § 0 comments § permalink

With just a few days to go before the 10th Anniversary of the September 11th terrorist attacks, cultural heritage institutions and the press have been doing a wonderful job of covering the complicated issues associated with preserving and presenting the history and memories of that day. At the Roy Rosenzweig Center for History and New Media, we’re pleased to be able to reopen the collecting portal for the September 11 Digital Archive as a way to contribute to this effort. With over 150,000 items, 911digitalarchive.org presents the public with one of the best ways to get a sense of how individuals have reflected on the tragedy of September 11th and its impact over the course of the last decade.

Much has changed in the world of digital archives and preservation since we embarked upon this work with our partners at the American Social History Project|Center for Media and Learning (CUNY) in 2002. As a result, we are embarking on the work of migrating the Archive to Omeka so that it will have a infrastructure that will improve both popular and scholarly access to the materials for years to come.

This work is being supported by a “Saving America’s Treasures” grant administered by the National Endowment for the Humanities and the National Park Service. Unfortunately, the SAT program was a casualty of the most recent budget fights, and it will no longer be a route to preservation and stabilization for our cultural heritage materials. The funding for this type of work from the National Endowment for the Humanities, the Institute for Museum and Library Services, and the National Historical Publications and Records Commission is all similarly endangered in the current political environment.

Perhaps as we reflect on the meaning and impact of September 11th on our nation and our cultural life, we might all contribute a reflection to the Archive. Second, we might write to our Congressional representatives to tell them how essential it is that we maintain our commitment to the preservation and presentation of the cultural heritage materials that play such an important role in those reflections. That commitment demands continued public support for the grant making institutions that make our work possible.

Why Crowdsourcing? Why Scripto?

March 10th, 2011 § 0 comments § permalink

As we approach the alpha launch of Scripto with the Papers of the War Department, 1784-1800 project, it seems appropriate to step back and consider why we at CHNM would be interested in building a tool to facilitate the crowdsourcing of documentary transcription.

A survey of the current landscape in public history, archive, and museum projects suggests that a tide of interest in crowdsourcing is building in the community. Just recently, the participants in the Digital Humanities API Workshop at the Maryland Institute for Technology in the Humanities produced an excellent summary of recent work and current needs. The list of projects launched recently is long and includes projects such as:

This ecosystem of relate projects all draw up on the interest and enthusiasm of members of the general public to advance the work of important intellectual ventures. In a sense, the participants in these projects work to support Clay Shirky’s thesis in Cognitive Surplus (2010) that new media is allowing individuals to redirect their free time away from passive consumption of media to active participation in social and cultural ventures that can be harness in positive ways. Shirky’s work is somewhat utopian, but we at CHNM share his enthusiasm for the possibilities that community-wide collaboration might have for our work in public history.

Our enthusiasm for community participation in public history comes from the mission of the Center, which includes using “digital media and computer technology to democratize history—to incorporate multiple voices, reach diverse audiences, and encourage popular participation in presenting and preserving the past.” This impulse to provide open access to historical materials and to build open source tools also includes an interest in welcoming the wider public to join us in our work. In 1998 CHNM founder Roy Rosenzweig entitled his closing thoughts of The Presence of the Past (co-authored with David Thelen) “Everyone a Historian,” in an effort to indicate the very complex interpretations individuals who are not professional historians make of their encounters with history. We wish to encourage this historical work by providing everyone with access to historical materials and opportunities to participate in the work of history.

In addition to these general goals for members of the interested public, we have several specific goals for Scripto and its role in crowdsourcing documentary transcription for documentary editors.

  1. For digital documentary projects, Scripto will allow users to provide text that is essential to improving the function of the archive’s search engine and the ability for users to locate the materials they need. As such we are not looking for perfect transcriptions, but rather the progressive improvement that users can provide over time. All of the text contributed by the crowd will provide more data to search, and will allow users to pursue topics and interests that might not be represented in the metadata created by project editors.
  2. For documentary projects with the fiscal resources for professional transcriptions, we hope that this initial and imperfect transcription data will provide project editors with a first pass from which they can build more robust transcriptions for scholarly editions. To some small degree, user contributed transcriptions will allow projects to reallocate resources toward the value-added materials they bring to scholarly editions in the form of annotations, glossaries, and other contextual elements.
  3. The landscape of documents that user choose to transcribe will provide documentary editors with vital insights about the topics and elements of their archives that are of interest to users. This information is central to informing future efforts at outreach and to prioritizing site enhancements, such as teaching materials and digital exhibits.
  4. Opening up an archive to crowdsourced transcription provides projects with an opportunity to think seriously about fostering and maintaining a vibrant community of users. Public history is meant to be public, and Scripto will help editors focus on seeking out interested users for their important holdings.

In the end, our work on Scripto and its implementation with the Papers of the War Department is an experiment in pursuing these goals. Eventually, editors from other digital documentary projects may wish to customized or extend Scripto’s functionality to serve the needs of their users and their collections, but these four essential goals will remain consistent across projects. As a free and open source tool, we have designed Scripto to be light-weight, flexible, and modular so that it represents a simple step forward for documentary editors.

[Cross-posted from the Scripto blog.]

Omeka.net Beta Launches

November 2nd, 2010 § 0 comments § permalink

After more than two years of planning and development, and six months of Alpha testing, CHNM is pleased to announce the public launch of Omeka.net Beta. Anyone may sign up for an account today.

Omeka.net is a hosted web service that brings standards-based online collections and exhibitions to the internet cloud. Simply create a username and password at http://omeka.net, and your online collection or exhibition website is up and running. Similar to cloud-based content management services offered by WordPress.com, Blogger, and PBWorks—but geared to the needs of scholarship and cultural heritage—no server or programming experience is required to launch an Omeka.net website. With Omeka.net, users can build digital exhibits, map photographs, collect memories from web audiences, or publish new scholarship in a few easy steps.

Omeka.net will offer five plans for users that include a range of options from building one site using a few plugins and themes to deploying an unlimited number of sites that uses an extensive set of add-ons and designs. These plans, including a basic free option, are available to accommodate a variety of individual and institutional users.

Omeka.net is an outgrowth of the Omeka project, in partnership with Minnesota Historical Society and funded by the Institute of Museum and Library Services, the Library of Congress, Alfred P. Sloan Foundation, Andrew W. Mellon Foundation, and Samuel H. Kress Foundation.

[Cross-posted from Omeka.net.]