<h1 id="exit-ticket"><a aria-hidden="true" tabindex="-1" href="#exit-ticket"><span class="icon icon-link"></span></a>Exit Ticket</h1>
<div><blockquote class="callout" style="border-left-color:#448aff;">
<div class="callout-title note" style="background-color: #448aff1a;"><span style="color:#448aff" class="callout-icon"><svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide-pencil"><line x1="18" y1="2" x2="22" y2="6"></line><path d="M7.5 20.5 19 9l-4-4L3.5 16.5 2 22z"></path></svg></span><strong><p>DUE DATE:  Dec. 7th, 11:59 pm</p></strong></div>
</blockquote></div>
<h2 id="format"><a aria-hidden="true" tabindex="-1" href="#format"><span class="icon icon-link"></span></a>Format</h2>
<p>The format of your Exit Ticket is up to you, but the final product will be housed in your Obsidian vault and published onto your personal Memex site. It can be as simple as a short essay (1000-1250 words), as complex as another website embedded into your Memex, or whatever floats your boat. You use it to tell the story of your engagement in this class; it will provide me with greater context for your work.</p>
<p>The goal is for you to objectively assess your ability to reflect on your growth throughout the term, analyze the evolution of your research topic for the course, and discuss the new insights you can apply to your future academic work. You will reflect on where you started and where you’ve arrived, what new insights you learned about your research topic, and you will indicate how you feel you’ve performed against the learning outcomes. You should revisit that original week's work where you imagined how the three different modules might play out. You will re-assess your proposal and determine if you achieved your research goals, or where you fell short and why?</p>
<div><blockquote class="callout" style="border-left-color:undefined;">
<div class="callout-title important" style="background-color: undefined1a;"><span style="color:undefined" class="callout-icon"></span><strong><p>MOST IMPORTANT</p></strong></div>
<div class="callout-content" style=""><p>You will answer the question: What does it mean to 'Craft' Digital History on your chosen topic?</p></div>
</blockquote></div>
<p>This question may seem opaque, and it is by choice because I want you to assess how meaning emerges from your research and the notes you have created throughout this course. It is a very personal question in the context of this course, the goal of which is not to come to some definitive answer or conclusion about your historical topic, but to think about the multitude of approaches on how digital history and digital public history are crafted and their influence on knowledge production and narrative construction.</p>
<p>Remember, I am assessing your evolution and process throughout the course. If you do not achieve your proposed goals, that is fine; however, you need to argue how and why you ended up where you did. You know the value of your work (which is different from the <em>effort</em> expended, of course, right?). The <code>exit ticket</code> is where you show me that you understand this, and since we are working in a system that uses letter grades, <strong>you'll indicate the corresponding grade. If I agree with you, that's the grade you'll get.</strong></p>
<p>If you’ve never done digital work before, it might be that you never quite manage to get as many of the tech things working as you might’ve wanted, but you now know what you didn’t know before. <strong>That’s a win.</strong> You might have some computer science background, and the tech materials don’t present you with much challenge, but figuring out how to tell a compelling story about an ancient or medieval historical topic was very difficult for you; you’re better at it now. <strong>WIN!</strong> Your <code>exit ticket</code> can explain your particular context, and it will point to the evidence that demonstrates how you’ve progressed from where you were at the beginning to where you are now.</p>
<p>As I mentioned, if I agree with your assessment, that is the grade you will receive. When I have disagreed in previous courses, this has been, 9.5 times out of 10, to raise the grade: <strong>You are all too hard on yourselves.</strong> And when it's been that 0.5 time, we'll have a face-to-face (virtual) conversation.</p>
<div><blockquote class="callout" style="border-left-color:undefined;">
<div class="callout-title danger" style="background-color: undefined1a;"><span style="color:undefined" class="callout-icon"></span><strong><p>Submission of Exit Ticket</p></strong></div>
<div class="callout-content" style=""><p>This needs to be completed by the assigned due date or your grade will be entirely up to me. And do you really want that?</p><p><strong>Submission</strong><br>
A bundled submission including a <code>.zip</code> file of your complete Obsidian vault and a live URL to your published Open-Access Notebook. Your 'Exit Ticket' is to be exported from your vault into PDF format and submitted here <a href="">googledoc</a></p></div>
</blockquote></div>

Welcome

1. Course Description

2. Learning Outcomes

3. Course Schedule

4. Evaluation

5. Course Communications

6. Common Regulations

6. Contact the Professor

how the course tech is built; how the course came to be

7. Colophon

8. Reuse

Orientation and Digital Setup

Week 1

Personal Knowledge Management and Linked Thinking

Week 2

Thinking about the “Craft” of Digital History

Week 3

Crusading into the Digital Age of LLMs

Week 4

Consolidation & Check-In Week

Week 5

Digital Excavation

Week 6

Defining Data, 'Dark' Data, & Identifiers

Week 7

Fall Break

Week 8

Seeing the Past?

Week 9

Week 10

Authority and Positionality in Your Digital Research

Week 11

Publicly Crafting a Historical Argument

Week 12

Open-Access Notebook Workshop

Week 13

Exit Ticket

Week 14

1 Setting up your vault

2 Create your first note

3 Templater Plugiin

4 What Goes into a Note?

5 Properties

Hypothesis

The Simplest Online Memex Worfklow

How To Read An Academic Article

FAQ for Common Tech Issues

Where to Find help

Text Formatting

Introduction to your vault

index note

Atomic Note

Literature Note

Process Note

Weekly Journal

Topic Proposal

Weekly Work & Tasks

Consolidation Reflection

Open Access Notebook/Memex

Benchmarking Your Memex

Exit Ticket/Final Project

1 Welcome to Crafting Digital History Transcript

2 Obsidian User Interface (UI) Guide

3 Templater and Hotkeys Setup

4 How to use PDF++

5 Canvas Core Plugin Introductory Tutorial

6 Hypothes.is and Annotating the Web

7 Omnisearch Plugin for Obsidian

8 How to Use Process Notes for Digital Research Projects in Obsidian

9 Properties, Identifiers and Data Management with Obsidian Core Plugin Bases

1 Welcome to Crafting Digital History

2 Some Logistical Updates

3 Welcome to Week Two

4 What is Digital History?

5 Crusading into the Digital Age of LLMs

6 Week Four Exercise Example

7 Using Obsidian for Digital History Research and Note-Making

8 Reflection Feedback Update and Hypothes.is

9 Week Five Update

10 Consolidation Reflection Submission

11 Module Two Wrangling and Critiquing

12 Week 7 Update

13 Week 9 Welcome Back

14 Consolidation Week Number 2

1. Course Overview

Module 1 Contextualizing

Module 2 Wrangling & Critiquing

Module 3 Arguing & Communicating

2. Schedule

01  memex help

8. Course Files

3. Tutorials

4. Assessment

5. VideoTutorials

Crafting Digital History

News