Tag Archives: appalachian trail

Trails, Paths, and Digital Literacy

Yesterday I had the good fortune to be the keynote speaker at the Winter Symposium on Digital Literacy in Higher Education at the University of Rhode Island. It was incredibly energizing to spend a day and a half with a diverse group of educators across disciplines, all of them committed to the idea that improving our students’ (and our colleagues’) digital literacy.

img_0820

Of course, there are few more amorphous topics than digital literacy, which made my task as keynote speaker challenging, to say the least. A quick survey of the literature yields almost as many definitions of the concept as there are authors who write about it.

Do we mean the ability to use digital technologies to accomplish a particular task? Or does it mean just being able to navigate the wilds of the Internet without being taken in by the false information floating around out there? Or does it mean being able to create digital objects, code something useful, or develop visualizations of large corpora of texts?

To help those assembled to try to find a way forward, I drew on my experiences on the Appalachian Trail, America’s oldest and still most iconic long distance hiking trail. Of late I’ve been mesmerized by Robert Moor’s On Trails (2016). Moor writes in ways I can only dream about, and in his first pages I found the quotation that I think helps us make our way through the echoing vastness of the Internet.

To put it as simply as possible, a path is a way of making sense of the world. There are infinite ways to cross a landscape; the options are overwhelming, and pitfalls abound. The function of a path is to reduce this teeming chaos into an intelligible line.” (14)

If we think about digital literacy more as choosing a path through the mountains and less like trying to sail across the open ocean, then I think we have a chance to find a way forward as educators and as scholars.

Of course, paths impose their own tyranny. Early into their hikes, long distance hikers find themselves less and less willing to leave the path marked out for them by others. Ask anyone who has through hiked the Appalachian Trail and they’ll tell you that “Blue Blazer” is a term of derision, because it connotes that long distance hiker who leaves the white blazes of the AT for side trail short cuts with blue blazes on the trees and rocks.

Despite the risk of being labeled a Blue Blazer, I think we have to admit that there are too many options, too many platforms, too many apps, too many new ways to navigate the Internet. If we accept this premise, then instead of trying to define or to teach something called “digital literacy,” we can instead decide “I’ll just do this,” or, “I’ll just teach my students that.” And not anything else.

Do we do them or ourselves a disservice by ignoring so much? My answer is no. Too often we forget that our students are with us for only a short time in what we (and they) hope are long and productive lives. Instead of teaching them everything they need to know about things digital, it strikes me as more than enough to teach them a few useful skills, a few useful ways of knowing. We need to give them the tools to find their own paths, and we need to model the willingness to reject the notion that to be competent means always being able to do more and more. Sometimes enough is plenty.

Just a little over 100 years ago, Benton MacKaye stood in a fire tower in Vermont and gazed out over the beauty of the Green Mountains. It was there that he first dreamed up a thing he later christened the Appalachian Trail. MacKaye’s mantra for those hiking on the trail he created was “Walk, see, and see what you see.” To put it another way, stop, look around, what can I see/learn here.

Stopping is a risk, because in doing so, the Internet will swoosh past us. But that’s ok. Really.

Maps, Walls, and Digital Public History

This coming fall I’m teaching a new course: History of the Appalachian Trail. As envisioned, the class is going to be many things at once (which is likely a structural problem). It is a conventional history of one of America’s longest national parks, it is a chance to introduce students to the basics of digital public history, and it is a chance for me to connect my avocation (long distance backpacking) with my vocation (educator, historian).

Today I want to focus on just one part of the course — the part that in some ways I’m the most excited about. Across the hallway from my office is a long, blank, pale blue wall. When I say long, I mean 82 feet long with not one thing on it except a thermostat sort of a small plastic box. This blank wall has bugged me for years, because we’re a university for goodness sake, and such a wall should be covered with student art, or history student research posters, or SOMEthing besides pale blue paint. Now I’m glad no one ever thought to do any of that stuff with what I now think of as “my wall,” because it is going to become the canvas for my students.

For their final projects, students in the class are going to create an Omeka exhibit for the website I’m developing (no formatting yet, so don’t judge) on the history of the Appalachian Trail. But they are also going to paint the Trail onto my wall. And yes, before you ask, I have permission from the powers that be in facilities to do that. Given that the wall is 82 feet long and the Trail is 2,190 miles long (this year), that works out to a scale of around 27 miles: 1 foot. That seems like a reasonable scale to me. Right now. Today.

Once we get the Trail painted on my wall, students will then attach connection points to their own work — images of people, or places, or texts, or whatever, along with QR codes that let passersby dive into the online exhibits themselves.

That’s the plan anyway. From a technological standpoint, it’s not a complicated plan. From a pedagogical standpoint, I have a fair amount of work to do this summer to make sure mys students have all the tools they need to succeed.

And yes, we’ll be doing some hiking…