-
Notifications
You must be signed in to change notification settings - Fork 0
/
leadup.html
476 lines (404 loc) · 18.8 KB
/
leadup.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
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta http-equiv="X-UA-Compatible" content="IE=EDGE" />
<title>Step 5: Program Lead-up</title>
<script src="site_libs/jquery-1.11.3/jquery.min.js"></script>
<meta name="viewport" content="width=device-width, initial-scale=1" />
<link href="site_libs/bootstrap-3.3.5/css/simplex.min.css" rel="stylesheet" />
<script src="site_libs/bootstrap-3.3.5/js/bootstrap.min.js"></script>
<script src="site_libs/bootstrap-3.3.5/shim/html5shiv.min.js"></script>
<script src="site_libs/bootstrap-3.3.5/shim/respond.min.js"></script>
<script src="site_libs/navigation-1.1/tabsets.js"></script>
<link href="site_libs/highlightjs-9.12.0/textmate.css" rel="stylesheet" />
<script src="site_libs/highlightjs-9.12.0/highlight.js"></script>
<link href="site_libs/font-awesome-5.1.0/css/all.css" rel="stylesheet" />
<link href="site_libs/font-awesome-5.1.0/css/v4-shims.css" rel="stylesheet" />
<style type="text/css">
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
ul.task-list{list-style: none;}
</style>
<style type="text/css">code{white-space: pre;}</style>
<style type="text/css">
pre:not([class]) {
background-color: white;
}
</style>
<script type="text/javascript">
if (window.hljs) {
hljs.configure({languages: []});
hljs.initHighlightingOnLoad();
if (document.readyState && document.readyState === "complete") {
window.setTimeout(function() { hljs.initHighlighting(); }, 0);
}
}
</script>
<style type="text/css">
h1 {
font-size: 34px;
}
h1.title {
font-size: 38px;
}
h2 {
font-size: 30px;
}
h3 {
font-size: 24px;
}
h4 {
font-size: 18px;
}
h5 {
font-size: 16px;
}
h6 {
font-size: 12px;
}
.table th:not([align]) {
text-align: left;
}
</style>
<link rel="stylesheet" href="styles.css" type="text/css" />
<style type = "text/css">
.main-container {
max-width: 940px;
margin-left: auto;
margin-right: auto;
}
code {
color: inherit;
background-color: rgba(0, 0, 0, 0.04);
}
img {
max-width:100%;
}
.tabbed-pane {
padding-top: 12px;
}
.html-widget {
margin-bottom: 20px;
}
button.code-folding-btn:focus {
outline: none;
}
summary {
display: list-item;
}
</style>
<style type="text/css">
/* padding for bootstrap navbar */
body {
padding-top: 41px;
padding-bottom: 40px;
}
/* offset scroll position for anchor links (for fixed navbar) */
.section h1 {
padding-top: 46px;
margin-top: -46px;
}
.section h2 {
padding-top: 46px;
margin-top: -46px;
}
.section h3 {
padding-top: 46px;
margin-top: -46px;
}
.section h4 {
padding-top: 46px;
margin-top: -46px;
}
.section h5 {
padding-top: 46px;
margin-top: -46px;
}
.section h6 {
padding-top: 46px;
margin-top: -46px;
}
.dropdown-submenu {
position: relative;
}
.dropdown-submenu>.dropdown-menu {
top: 0;
left: 100%;
margin-top: -6px;
margin-left: -1px;
border-radius: 0 6px 6px 6px;
}
.dropdown-submenu:hover>.dropdown-menu {
display: block;
}
.dropdown-submenu>a:after {
display: block;
content: " ";
float: right;
width: 0;
height: 0;
border-color: transparent;
border-style: solid;
border-width: 5px 0 5px 5px;
border-left-color: #cccccc;
margin-top: 5px;
margin-right: -10px;
}
.dropdown-submenu:hover>a:after {
border-left-color: #ffffff;
}
.dropdown-submenu.pull-left {
float: none;
}
.dropdown-submenu.pull-left>.dropdown-menu {
left: -100%;
margin-left: 10px;
border-radius: 6px 0 6px 6px;
}
</style>
<script>
// manage active state of menu based on current page
$(document).ready(function () {
// active menu anchor
href = window.location.pathname
href = href.substr(href.lastIndexOf('/') + 1)
if (href === "")
href = "index.html";
var menuAnchor = $('a[href="' + href + '"]');
// mark it active
menuAnchor.parent().addClass('active');
// if it's got a parent navbar menu mark it active as well
menuAnchor.closest('li.dropdown').addClass('active');
});
</script>
<!-- tabsets -->
<style type="text/css">
.tabset-dropdown > .nav-tabs {
display: inline-table;
max-height: 500px;
min-height: 44px;
overflow-y: auto;
background: white;
border: 1px solid #ddd;
border-radius: 4px;
}
.tabset-dropdown > .nav-tabs > li.active:before {
content: "";
font-family: 'Glyphicons Halflings';
display: inline-block;
padding: 10px;
border-right: 1px solid #ddd;
}
.tabset-dropdown > .nav-tabs.nav-tabs-open > li.active:before {
content: "";
border: none;
}
.tabset-dropdown > .nav-tabs.nav-tabs-open:before {
content: "";
font-family: 'Glyphicons Halflings';
display: inline-block;
padding: 10px;
border-right: 1px solid #ddd;
}
.tabset-dropdown > .nav-tabs > li.active {
display: block;
}
.tabset-dropdown > .nav-tabs > li > a,
.tabset-dropdown > .nav-tabs > li > a:focus,
.tabset-dropdown > .nav-tabs > li > a:hover {
border: none;
display: inline-block;
border-radius: 4px;
background-color: transparent;
}
.tabset-dropdown > .nav-tabs.nav-tabs-open > li {
display: block;
float: none;
}
.tabset-dropdown > .nav-tabs > li {
display: none;
}
</style>
<!-- code folding -->
</head>
<body>
<div class="container-fluid main-container">
<div class="navbar navbar-inverse navbar-fixed-top" role="navigation">
<div class="container">
<div class="navbar-header">
<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar">
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="index.html"></a>
</div>
<div id="navbar" class="navbar-collapse collapse">
<ul class="nav navbar-nav">
<li>
<a href="index.html">
<span class="fas fa-home"></span>
Home
</a>
</li>
<li>
<a href="about.html">About this Guide</a>
</li>
<li>
<a href="timeline.html">
<span class="fas fa-gear"></span>
Process Overview
</a>
</li>
<li class="dropdown">
<a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button" aria-expanded="false">
<span class="fas fa-gear"></span>
Step-by-Step
<span class="caret"></span>
</a>
<ul class="dropdown-menu" role="menu">
<li>
<a href="environmental_scan.html">Step 1: Environmental Scan</a>
</li>
<li>
<a href="planning_committee_vision.html">Step 2: Forming a Planning Committee & Honing a Vision</a>
</li>
<li>
<a href="application.html">Step 3: Application Process</a>
</li>
<li>
<a href="schedule_content.html">Step 4: Developing the Program Schedule & Content</a>
</li>
<li>
<a href="leadup.html">Step 5: Program Lead-up</a>
</li>
<li>
<a href="delivery.html">Step 6: Program Delivery</a>
</li>
<li>
<a href="assessment.html">Step 7: Assessment</a>
</li>
<li>
<a href="resources.html">Further Reading/Suggested Resources</a>
</li>
</ul>
</li>
<li>
<a href="contact.html">
<span class="fas fa-gear"></span>
Contact Us
</a>
</li>
</ul>
<ul class="nav navbar-nav navbar-right">
</ul>
</div><!--/.nav-collapse -->
</div><!--/.container -->
</div><!--/.navbar -->
<div class="fluid-row" id="header">
<h1 class="title toc-ignore">Step 5: Program Lead-up</h1>
</div>
<p>While transitioning to an online program did have its affordances, it also required more direct attention to be paid to certain areas. This included the type and frequency of communications we engaged in with participants leading up to the program, namely the creation of thorough documentation and a number of pre-program surveys to help determine participants’ needs.</p>
<div id="pre-program-communications" class="section level2">
<h2>Pre-program communications</h2>
<p>In order to take stock of participants accessibility requirements and technology set-ups, we sent out a pre-program survey to gather the following information:</p>
<p><i>“This survey is intended to gather information about your work environment and tech set up, your baseline skills and knowledge heading into the program, as well as what accessibility accommodations you may require. We acknowledge that some of you will be beginning from a place of no previous technical experience, and that others of you may have some working knowledge. Both starting points are valid. Knowing where everyone stands will allow us to properly prepare and tailor content. Please complete this survey by Wed, June 18th. It should take roughly 10 minutes to complete. Thank you for your participation” </i></p>
<ul>
<li>Equipment:
<ul>
<li>Do you have access to a laptop or desktop computer to work with the week of the program? (<em>Please note that for the purposes of the program, using an iPad or tablet will not suffice. If you have questions or concerns about the device you will be using for the week, reach out to us! We will work with you to identify accommodations.</em>)</li>
<li>Do you have permissions to install new software on this computer?</li>
<li>Do you have a reliable internet connection at the location you will be joining us from? (<em>If not, let us know and we can discuss potentially shipping you a hotspot or work to find some other solution.</em>)</li>
<li>What operating system & version will you be using? (e.g. MacOS Mojave, Windows 10, Ubuntu Linux, etc.) (<em>If you are unsure, that’s okay! Note that here and we will reach out to you to help you figure it out.</em>)</li>
<li>Please list any technical courses you have completed (through your program or otherwise) as well as any intensive workshops and/or tech-related bootcamps you may have taken part in here:</li>
<li>Please indicate which tools you have some experience working with. (check all that apply) [the command line/terminal; a text editor; python; git/github; html; css; a web framework, such as flask or django; I really haven’t used any of these things before. (and that’s ok!)]<br />
</li>
<li>If you have a GitHub username, please provide it below: (<em>This will help us plan our Git & GitHub workshop. If you don’t have a GitHub username, we’ll help you set one up later.</em>)</li>
<li>What’s your experience with programming? Choose one of the following levels:
<ul>
<li>Level 1 - Totally New to Programming: You might have done a little bit with HTML or CSS, but not necessarily; You’re unfamiliar with terms like methods, arrays, lists, hashes, or dictionaries.</li>
<li>Level 2 - Somewhat New to Programming: You might have done an online programming tutorial or two, but don’t have a lot of experience with programming; You know what an array is</li>
<li>Level 3 - Some Programming Experience: You have some experience with a programming language and version control; You understand general programming concepts, like collections and scope, but aren’t a power user</li>
<li>Level 4 - Ready for the Next Challenge: You’re comfortable with the terminal and are proficient in at least one programming language; You want to problem-solve instead of copying others’ code</li>
</ul></li>
<li>What is your familiarity with machine learning?
<ul>
<li>I have no clue what machine learning is.</li>
<li>I have heard of machine learning before and kind of understand what it’s about, but would have trouble describing it to someone else.</li>
<li>I have a basic conceptual understanding of machine learning, but don’t know how it works on a technical level.</li>
<li>I understand how machine learning works on a conceptual and a technical level.</li>
</ul></li>
</ul></li>
<li>Accessibility & Accomodations:<br />
<em>In compliance with the Americans with Disabilities Act, NC State University Libraries will gladly honor requests for reasonable accommodations. Please note your accommodation requests below or send them directly to Tori Culler (<a href="mailto:[email protected]" class="email">[email protected]</a>) by Monday, July 12th, 2021. All sessions will feature automated captioning. We are happy to provide live captioning by a professional captioner upon request. Recordings and transcripts for most sessions will be available to participants for a period of time after the Jumpstart Program concludes.</em>
<ul>
<li>Do you require any accessibility accommodations for the week of the program? (<em>We can offer, for example, alternative formats for recorded videos, additional break time, etc.</em>)</li>
<li>Do you have access to any assistive technology you might need for the week? (<em>The NC State University Libraries is committed to providing access to collections, services, and spaces for all library users. When we use the phrase “assistive technology”, we are referring specifically to technologies used to facilitate access to materials for participants with a variety of vision, hearing, and/or mobility-related disabilities. Outside of Zoom (which will be live captioned), we’ll provide you with materials in these formats: Google Docs, videos on Vimeo (captioned), PDFs, and downloadable code files on Github. At your request, we can offer things like JAWS screen-reading software to facilitate your access to those materials.</em>)</li>
</ul></li>
<li>General questions, comments, concerns:
<ul>
<li>Is there anything else you would like us to know? Do you have anything to add concerning your answers to the above questions?</li>
</ul></li>
</ul>
<p>We were able to use the information gleaned from this survey to plan our technical workshops around folks experiences and skill levels. In 2020, information obtained in this survey also prompted us to begin working on the process of securing live captioning and inserting more break time into our schedule. For live captioning, we worked with <a href="https://www.automaticsync.com/captionsync/">CaptionSync</a> to secure services. In 2021, we learned from this survey that we would need to ship a participant a loaner laptop.</p>
<p>In addition to the pre-program tech & accommodations survey, we also sent out a pre-program knowledge & attitudes survey as part of our assessment plan (see Step 6: Assessment, for more information).</p>
<p>A couple weeks before the program, we gave participants access to a shared Google Drive folderthat we pitched as their one-stop-shop for all things Jumpstart, including all pre-program support materials such as the program schedule with Zoom links and the code of conduct, program support materials (such as workshop slides and glossaries), as well as all post-program support materials (including guides for continued learning, etc.). We outlined the folder’s contents in a README document.</p>
<blockquote>
<p>Tip: Frequent and clear communication with participants leading up to the program is key to a successful delivery. Seek input from participants about what their technology and access needs are very early on to ensure that you have adequate time to meet them. Consider creating a comprehensive information packet/shared drive that includes all needed information to share with participants beforehand.</p>
</blockquote>
</div>
<div id="install-fest" class="section level2">
<h2>Install-fest</h2>
<p>One challenge that often occurs with technical workshops is making sure that participants have the software that they need installed and configured. This is often even more of a challenge when participants use different versions and flavors of operating systems (such as Mac vs Windows vs Linux, and different versions of each one). Using tools such as <a href="https://colab.research.google.com/">Google Colaboratory</a> helps with this problem, as you can do the coding live in a browser, and not require users to install anything on their own machines. We felt, however, that participants would benefit from learning how to set up a programming environment on their own machines they could continue to use after the end of the Jumpstart program. This would also help us ensure that all requirements were installed, tested, and working before the week of the program. To this end, we offered what we called “Install-fest”.</p>
<p>A few weeks before the program, we reached out to participants with <a href="https://docs.google.com/document/d/1UBtvsXuAiqBGFWCQNV4__28cE5toGxpCYYr0HcR0cR8/edit">instructions</a> on how to get a programming environment setup on their machines, and how to install dependencies for each of the workshops we offered. We also asked them to schedule a one-hour one-on-one session with us, where we could either run through the instructions together, answer specific questions they had, or just verify their environments were set up properly and working. We had volunteers to help with the one-on-one sessions that were familiar with the operating system that the participant used.</p>
<p>This approach ended up working out well – most of the issues that we ran into during the hands-on workshops were not related to the environment set up of participants. It was also a good chance to begin to develop a rapport with participants and help them get comfortable with sharing their screens and troubleshooting issues together. We were able to offer participants one-on-one support because our cohort size was fairly small. If we had a larger cohort size, we could have considered having small group support sessions instead of one-on-one.</p>
<blockquote>
<p>Tip: Create a plan to make sure participants are as prepared as they can be in advance of any technical workshops you plan to offer so that they can focus on the content of the workshop rather than on issues with their computing environments.</p>
</blockquote>
<p><a href="https://ncsu-libraries.github.io/jumpstart-framework/delivery.html">Next >> Step 6: Program Delivery</a></p>
<p><br></p>
<p>Last updated on September 26, 2022.</p>
</div>
<p>
From NC State University Libraries.
<a href="https://www.lib.ncsu.edu/jumpstart">https://www.lib.ncsu.edu/jumpstart</a>
</p>
<img src="images/wordmark.png" alt="jumpstart wordmark">
</div>
<script>
// add bootstrap table styles to pandoc tables
function bootstrapStylePandocTables() {
$('tr.odd').parent('tbody').parent('table').addClass('table table-condensed');
}
$(document).ready(function () {
bootstrapStylePandocTables();
});
</script>
<!-- tabsets -->
<script>
$(document).ready(function () {
window.buildTabsets("TOC");
});
$(document).ready(function () {
$('.tabset-dropdown > .nav-tabs > li').click(function () {
$(this).parent().toggleClass('nav-tabs-open')
});
});
</script>
<!-- code folding -->
<!-- dynamically load mathjax for compatibility with self-contained -->
<script>
(function () {
var script = document.createElement("script");
script.type = "text/javascript";
script.src = "https://mathjax.rstudio.com/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML";
document.getElementsByTagName("head")[0].appendChild(script);
})();
</script>
</body>
</html>