-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
240 lines (220 loc) · 10.9 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
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
<!DOCTYPE HTML>
<!--
Dimension by HTML5 UP
html5up.net | @ajlkn
Free for personal and commercial use under the CCA 3.0 license (html5up.net/license)
-->
<html>
<!-- This is the "Head" of the HTML document.
It contains information that isn't displayed on the actual page, but is useful
for the web browser when loading the page
-->
<head>
<!-- This is the title of the page. It is the text that appears inside this pages tab in your web browser -->
<title>Communities Sustaining Digital Collections</title>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no" />
<!-- This links to this page's CSS, which is contained in the folder assets/css and the file main.css.
If you want to edit the styling of this page, you should edit the file assets/css/main.css
If you have a new CSS file you'd like to add with custom styling, you should link to it here using:
<link rel="stylesheet" href="assets/css/my-new-css-file.css"/>
-->
<link rel="stylesheet" href="assets/css/main.css" />
<!-- In the case that the user's browser does not support JavaScript (unlikely, but possible), the page
will load a separate set of CSS stylings from the file assets/css/noscript.css
Any HTML contained inside <noscript></noscript> tags will be loaded in the event that JavaScript is not
available.
-->
<noscript><link rel="stylesheet" href="assets/css/noscript.css" /></noscript>
</head>
<!-- The body is the location where your site's content will go -->
<body class="is-preload">
<!-- This "div" wraps around all of our content and just changes how things are layed out -->
<div id="wrapper">
<!-- This is where the content that appears on page load exists -->
<header id="header">
<!-- This is the main content of the front page -->
<div class="content">
<div class="inner">
<!-- Here is a heading where you can put your name -->
<h1>
Communities Sustaining <br> Digital Collections
</h1>
<!-- Here is an image where you can put a picture of you.
You can change the width and height attributes below to change how large
your image is.
Try adding "border-radius: 50%;" to the style attribute.
-->
<!-- Here is a paragraph where you can put your position and institution, or
a short line about yourself.
-->
<!-- Here is a paragraph where you can put a link to your CV -->
<p>
<!-- Note you will want to change where this points to! -->
<b>What's the Issue?</b> </br>
• While various policy interventions and technical developments have advances the practices and impact
of digital stewardship, sustainability continues to be a systemic problem for digital scholarship.
<br>
• The least tractable challenge to sustaining digital schoalrship continues to be the most essential:
many digital humanities resources and digital community archives resist institutional collection due
to the depth of ongoing investment and control that communities wish to retain over the resources
they have created.
</br>
<b>Why?</b> </br>
• Outside of exceptionally well-resourced digital humanities centers and libraries,
community-driven digital collections and databases lack systemic support. Digital humanities collections
and digital community archives tend to be created and maintained by small, collaborative teams of community members,
researchers, and technologists, often without ongoing assistance from curation institutions. </br>
• The prevailing paradigm—of library, museum, or archive stewardship of digital collections—struggles to
accommodate the diversity, complexity, and community-centeredness of digital humanities scholarship and
digital community archives.
</p>
</div>
</div>
<!-- This is the navigation menu -->
<nav>
<!-- This element makes an "Unordered List" -->
<ul>
<!-- This is a "List Item" -->
<li>
<!-- Note that this links to #about, which will move the page to wherever
the element with the id "about" exists.
-->
<a href="https://fenlab.github.io/">Home</a>
</li>
<li>
<a href="#research">Research Goals</a>
</li>
<li>
<a href="#community">Communities</a>
</li>
<li>
<a href="#contact">Contributors</a>
</li>
<!-- You can add another button to your navigation menu by adding
another List Item with a link inside of it.
-->
<!-- <li>
<a href="images/Astronomy.jpg">My CV</a>
</li> -->
</ul>
</nav>
</header>
<!-- These are the "cards" that appear when you click the buttons on the main page -->
<div id="main">
<!-- Here is the "About Me" card. Note it has the id "about", which the previous
button links to.
-->
<article id="about">
<h2 class="major">Problem Statement</h2>
<!-- Here is an image that you can customize for this page -->
<!-- Here are three paragraphs where you can fill out information about yourself -->
<p>
<!-- Items contained in <b> tags are bolded! -->
<b>What's the Issue?</b> </br>
• While various policy interventions and technical developments have advances the practices and impact
of digital stewardship, sustainability continues to be a systemic problem for digital scholarship.
<br>
• The least tractable challenge to sustaining digital schoalrship continues to be the most essential:
many digital humanities resources and digital community archives resist institutional collection due
to the depth of ongoing investment and control that communities wish to retain over the resources
they have created.
</br>
<b>Why?</b> </br>
• Outside of exceptionally well-resourced digital humanities centers and libraries,
community-driven digital collections and databases lack systemic support. Digital humanities collections
and digital community archives tend to be created and maintained by small, collaborative teams of community members,
researchers, and technologists, often without ongoing assistance from curation institutions. </br>
• The prevailing paradigm—of library, museum, or archive stewardship of digital collections—struggles to
accommodate the diversity, complexity, and community-centeredness of digital humanities scholarship and
digital community archives.
</p>
</article>
<!-- Here is the "Research" card. -->
<article id="research">
<h2 class="major">Research Goals</h2>
<p>
<!-- A <br> tag puts in a break so that the text that follows it displays on
the next line.
-->
<b>Conduct Compratative Case Studies to:</b><br>
• Produce and evaaluate a preliminary framework of community-centered sustainability strategies <br>
• Understand how collections and communities mutually contribute to one another's long-term sustainability <br>
• Articulate sustainability requirements for diverse projects in a range of contexts <br>
• Identify contextual factors that affect sustainability of collections and other resources <br>
• Choose and implement stragies to increase sustainability of digital collection
</p>
<p>
<b>Investigate Sociotechnical Workflows to:</b><br>
• Identify how workflows facilitate or compromise ongoing collection development and maintenance, and ultiamte durability <br>
• Identify how these workflows can effectively center collection constituencies <br>
• Refine models for equitable partnership among cultural institutions and communities <br>
• Identify roles that cultural instiutions may play to support community-determined and community-led sustainability strategies
</p>
</article>
<!-- Here is the "Community" card. -->
<article id="community">
<h2 class="major">Case Study Partners</h2>
<p>
We have gratefully partnered with the following projects and organizations as part of this research:
</p>
<p>
<a href = "https://lakelandchp.com/"> <b>The Lakeland Digital Archive:</b> </a> </br>
<a href= "https://mith.umd.edu/research/lakeland/"> The Lakeland Community Heritage Project and the </a>
<a href="https://mith.umd.edu/"> Maryland Institute for Technology in the Humanities</a>
</p>
<p>
<a href = "https://enslaved.org/"> <b>Enslaved.org:</b> </a>
</p>
<p>
<a href ="http://kitab-project.org/openiti/#:~:text=The%20Open%20Islamicate%20Texts%20Initiative,corpus%20of%20premodern%20Islamicate%20texts.">
<b>The Open Islamicate Texts Initiative and the Kitab Project:</b> </a>
</p>
<p>
<a href ="https://music-encoding.org/"> <b>The Music Encoding Initiative:</b> </a>
</p>
</article>
<!-- Here is a the "Contact" card. -->
<article id="contact">
<h2 class="major">Contributors</h2>
<p>
<b>Jessica</b>
</p>
<p>
<b>Alia</b>
</p>
<p>
<b>Courtnie</b>
</p>
<p>
<b>Will</b>
</p>
<!-- Here are the fancy icons that link to your social media.
These icons are rendered using Font Awesome fonts, and you can find more icons
here: https://fontawesome.com/icons
-->
</article>
</div>
<!-- This is the footer that appears at the bottom of the page -->
<footer id="footer">
<!-- You can change "Untitled" to your name to show everyone that
this is your work.
-->
<p class="copyright">© Untitled. Design: <a href="https://html5up.net">HTML5 UP</a>.</p>
</footer>
</div>
<!-- This is the background image of the site.
All configuration of the background is done with CSS.
Look in the file assets/css/main.css and search for "#bg" to
see how this element is styled. Look for comments pointing
to where you can set a new background image.
-->
<div id="bg"></div>
<!-- Scripts -->
<script src="assets/js/jquery.min.js"></script>
<script src="assets/js/browser.min.js"></script>
<script src="assets/js/breakpoints.min.js"></script>
<script src="assets/js/util.js"></script>
<script src="assets/js/main.js"></script>
</body>
</html>