Group items tagged

Here are a few specific examples you can apply to your instructional design process to help learners with metacognition: Model the metacognitive process during instruction (or in one-on-one consultations) to ask and reflect on big picture questions such as: “What questions can you answer with this tool?” “What can you not do with this tool?” Keep in mind some answers may be simple (e.g., this tool can only work with data in this way, so it is excluded automatically). Also, “Did I get the results I expected? What could I have done differently?” Start with inquiry and build conversations based on the learner’s answers. “Is it the data that does not work? Or is the research question fundamentally wrong to begin with?” Collaborate with faculty to teach together, modelling your practices while demonstrating a specific tool. This could include thinking aloud as you make decisions so learners can self-correct assumptions. Also, be aware of your own expert bias so you can demonstrate how to clear obstacles. Ask learners to specifically define what is difficult for them during the process of instruction. Digital humanities tools are complex and are based on complex methodologies and research questions. By constructing opportunities for learners to self-question as they move from one task to another, they learn to self-assess their progress and adjust accordingly. There are several instructional design activities that promote metacognition: think-pair-share, one minute paper (“share a key concept learned” or “what comes next?”), and case studies.

There are specific strategies we can implement to help learners escape the recursive spiral of the liminal state they experience while managing complex digital projects: One of the most challenging aspects of teaching digital tools is forgetting what it is like to be a novice learner. Sometimes being a near-novice oneself helps you better prepare for the basic problems and frustrations learners are facing. But recognizing liminality is a reminder to you as a teacher that the learning process is not smooth, and it requires anticipating common difficulties and regularly checking in with learners to make sure you are not leaving them behind. When meeting with learners one-on-one, make sure to use your in-depth reference interview skills to engage in methods discussions. When a learner is in the liminal state, they are not always able to “see the forest for the trees.” Your directed questions will illuminate the problems they are having and the solutions they had not seen. Pay close attention to the digital humanities work and discussions happening on your own campus, as well as across the academic community. Working through the liminal space may require helping learners make connections to others facing similar problems. Also follow online discussions in order to point your learners to a wide variety of group learning opportunities, such as the active digital humanities community on Slack.9 When designing instructional opportunities, such as workshops and hackathons, pay particular attention to outreach strategies that may bring like-minded learners together, as well as diverse voices. For example, invite the scholar whose project was completed last year to add a more experienced voice to the conversation. By encouraging the formation of learning communities on your campus, you are creating safe spaces to help learners navigate the liminal state with others who may be on the other side of struggling with specific digital project issues. In designing instructional activities, guide learners through visualization exercises that help to identify “stuck” places. Making graphic representations of one’s thoughts (e.g., concept maps) can highlight areas that require clarification.

Although sometimes confused with digital scholarship centers, digital humanities centers are often specialized research centers led by a group of faculty and serving only select disciplines rather than a broad campus community. Also, libraries often play only a peripheral role in digital humanities centers.1 In contrast, libraries or IT organizations have a key role in digital scholarship centers.

Our medical systems have terrible Internet security… MRI machines you can connect to with USB that still have “admin:password” to gain root access. That’s horrifying, sure, but that’s not an attack at scale. More frightening: we’re busily uploading all our medical records to the cloud. Take down that cloud, and no patients can be treated, because nobody will know what they have, what meds they are on. Software swallows your insulin pumps and your pacemakers. To kill people, all you need is to hack that database, or simply erase it or block access to it. After all, we don’t tend to realize that in an Internet of Things, humans are just Things too. As this software monster has encroached on stuff like election systems, the common reaction has been to go back to paper. So let’s consider a less obvious example. We should be going back to paper for our libraries too! We’ve outsourced so much of our knowledge to digital that the amount of knowledge available in analog has dropped notably. There are less librarians in the fewer libraries with smaller collections than there used to be. If the net goes down, how much reference material is simply not accessible that was thirty years ago? Google Search is “critical cultural infrastructure.” How much redundancy do we actually have? Could a disconnected town actually educate its children? How critical is Google as a whole? If Google went down for a month, I am pretty sure we would see worldwide economic collapse. How much of the world economy passes through Google hosting? How much of it is in GMail? How much is dependent on Google Search, Google Images, Google Docs? The answer is a LOT. And because financial systems are now also JIT, ten thousand corporate blips where real estate agencies and local car washes and a huge pile of software companies and a gaggle of universities and so on are suddenly 100% unable to function digitally (no payroll! no insurance verification!) would absolutely have ripple effects into their suppliers and their customers, and thence to the worldwide economic market. Because interconnection without redundancy increases odds of cascades.

But just as critically, governments and state actors seem to be the source of so many of the problems precisely because the Internet is now too many forms of critical infrastructure, and therefore too juicy a target. If software eats everything, then the ability to kill software is the ability to kill anything. Net connectivity becomes the single point of failure for every system connected to it. Even if the Net itself is designed to route around damage, that doesn’t help if it is the single vector of attack that can take down any given target. It’s too juicy a target for the military, too juicy a target for terror, too juicy a target for criminal ransom. The old adage goes “when they came for this, I said nothing. When they came for that…” — we all know it. Consider that the more we hand gleefully over to the cloud because we want convenience, big data, personalization, and on, we’re creating a single thing that can be taken from us in an instant. We’ve decided to subscribe to everything, instead of owning it. When they came for your MP3s, your DVDs, fine,. not “critical infrastructure.” When they came for your resumes, OK, getting closer.

As we rush towards putting more and more things “in the cloud,” as we rush towards an Internet of Things with no governance beyond profit motive and anarchy, what we’re effectively doing is creating a massive single point of failure for every system we put in it.

At the Digital Pedagogy Lab Institutes where we’ve taught, there’s one exercise in particular we return to again and again. In our “crap detection” exercise (named for Rheingold’s use of the term), participants use a rubric to assess one of a number of digital tools. The tools are pitted, head to head, in a sort of edtech celebrity deathmatch. Participants compare Blackboard and Canvas, for instance, or WordPress and Medium, Twitter and Facebook, Genius and Hypothes.is. We start by seeing what the tools say they do and comparing that to what they actually do. But the work asks educators to do more than simply look at the platform’s own web site, which more often than not says only the very best things (and sometimes directly misleading things) about the company and its tool. We encourage participants to do research — to find forums, articles, and blog posts written about the platform, to read the tool’s terms of service, and even to tweet questions directly to the company’s CEO.

Here’s the rubric for the exercise: Who owns the tool? What is the name of the company, the CEO? What are their politics? What does the tool say it does? What does it actually do? What data are we required to provide in order to use the tool (login, e-mail, birthdate, etc.)? What flexibility do we have to be anonymous, or to protect our data? Where is data housed; who owns the data? What are the implications for in-class use? Will others be able to use/copy/own our work there? How does this tool act or not act as a mediator for our pedagogies? Does the tool attempt to dictate our pedagogies? How is its design pedagogical? Or exactly not pedagogical? Does the tool offer a way that “learning can most deeply and intimately begin”? Over time, the exercise has evolved as the educators we’ve worked with have developed further questions through their research. Accessibility, for example, has always been an implicit component of the activity, which we’ve now brought more distinctly to the fore, adding these questions: How accessible is the tool? For a blind student? For a hearing-impaired student? For a student with a learning disability? For introverts? For extroverts? Etc. What statements does the company make about accessibility? Ultimately, this is a critical thinking exercise aimed at asking critical questions, empowering critical relationships, encouraging new digital literacies.

One problem is that participation is largely taken for granted and under theorized in many classrooms. The way we make use of a term like participation is in need of rescuing: moving away from a limited view of participation as it is often linked to motivation, engagement, or hand-raising and toward the view that participation as a concept is more generative when connected to the idea of membership in communities of practice (Wenger, 1998). Our limited view of participation is evident by simply turning to the language included in most syllabi: often, syllabi list “participation points” as part of the grade of the course. I find this to be an odd way to think about participation. What we often mean is that we will give students some points for “talking in class” and “raising their hands.” But demonstrating engagement by hand-raising and talk are fairly limited views of participation, and in fact, these ways of being are more connected to performance — acting like a student — than participation. We certainly want students to participate more than 10 percent, or even half, of the time. Are they participating when they are listening and pondering the ideas of their peers? Of course they are, but how do they demonstrate that? In thinking about course design, we should consider how students become members of our classroom community and our disciplines. Social media sites can open up other avenues for participation, and further, connect students to communities of practice outside our classrooms that they hope to enter.

This is why a survey coming from IT asking me about the usefulness of the technology in the classroom seems tone deaf to me. The problem isn’t the technology or if there are problems with the technology then they are obscured by the limits of the physical space. I would like for students to have enough space to bring their laptops, move around, work in groups, share their screens (even if only by all moving around in front of a laptop), and have conversations without getting in each others way.  I’d also like to be able to move among those groups without worrying about pulling a muscle.