/
index.html
107 lines (56 loc) · 4.92 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
<!DOCTYPE html>
<html>
<head>
<title> - Getting Started with ODATE</title>
<link rel="stylesheet" href="https://o-date.github.io/support/css/crab.css">
<meta name="viewport" content="width=device-width, initial-scale=1.0, minimum-scale=0.5, maximum-scale=3.0">
<meta name="generator" content="Hugo 0.40.3" />
</head>
<body>
<div id="container">
<div id="header">
<div id="site-logo">
<img src="https://o-date.github.io/support/img/odate.png" width = "100px">
</div>
<div id="site-title"><a href="https://o-date.github.io/support/">Getting Started with ODATE</a></div>
<div id="site-slogan">Graham, Gupta, Smith, Angourakis, Carter, & Compton</div>
</div>
<nav>
<ul class="first">
<li><a href="/support/">Home</a>
</li>
<li><a href="/support/classroom/">Classroom Use</a>
</li>
<li><a href="/support/contribute/">Collaborate with Us</a>
</li>
<li><a href="/support/annotation/">Annotation</a>
</li>
<li><a href="/support/jupyter/">Jupyter Notebooks</a>
</li>
<li><a href="/support/dhbox/">DHBox</a>
</li>
<li><a href="/support/contact/">Contact</a>
</li>
</ul>
</nav>
<div id="content">
<div id="article">
<h1></h1>
<h2 id="using-hypothesis">Using Hypothesis</h2>
<div id="summary">
<p><em>Use private reading groups with your students to identify and discuss the text. Threaded coversations each have a unique URL to the annotation; these can also be <a href="http://umwdtlt.com/hypothesis-aggregator-wordpress-plugin/">aggregated on student run blogs</a>. Here are some <a href="https://web.hypothes.is/examples-of-classroom-use/">examples of in-class use</a>.</em></p>
</div>
<p>When you read the text online, you will notice a stripe down the side of the screen at the right. That’s a tool-bar for annotating the text, using a tool called <code>Hypothes.is</code>. In the screenshot below, the highlighted text showed us there was some text that was annotated, and so we’ve clicked it to read the annotations.</p>
<p><img src="/support/img/hypothesis.png" width="80%"/></p>
<p>If you highlight any text a little pop-up will ask you if you want to annotate or highlight the text. If you choose annotate, a writing pane will open on the right. Using the Hypothesis tool requires a reader to create a login and account with Hypothesis, which is managed by the Hypothesis site, not us.</p>
<p>By default, such annotations are made public. Private annotations can only be viewed by the particular individual who made them. All annotations (both public and private) have their own unique URL and can be collated in various ways using the Hypothesis API (here’s an <a href="http://jonudell.net/h/facet.html">example</a>). Please tag your annotation with <code>odate</code> to allow easy curating of the public annotations.</p>
<p>Please note that any public annotations can be read by any other reader. These can also be responded to, as well - which might make a great classroom activity! A class can create group annotations which are only visible to participants in that group (<a href="https://hypothes.is/blog/introducing-groups/">instructions here</a>). Annotation is a tool for research; personal reaction to anything we’ve written in ODATE should be done via the reader’s blog while leaving an annotation on ODATE linking to the blog piece. Because the API or ‘application programming interface’ for Hypothesis allows one to retrieve annotations programmatically, there is a growing world of scripts and plugins for managing or retrieving those annotations. Kris Shaffer has created a Wordpress plugin to pull annotations to a new Wordpress post (<a href="http://pushpullfork.com/2016/08/hypothesis-aggregator/">details are linked here</a>), which might be another great option for a class blog working through ODATE.</p>
<p>Over time, the parts of the text that are heavily annotated will look as if someone has gone over them with a yellow highlighter. You can use this to help guide your reading - perhaps that’s a part where many people had problems, or perhaps it’s a part that sparked a really interesting discussion! Group annotation like this promotes ‘active reading’, which means that you’re more likely to retain the discussion.</p>
</div>
</div>
<div id="footer">
<a rel="license" href="http://creativecommons.org/licenses/by/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by/4.0/88x31.png" /></a><br />This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</a>.
</div>
</div>
</body>
</html>