-
Notifications
You must be signed in to change notification settings - Fork 0
/
schedule_content.html
498 lines (426 loc) · 24.5 KB
/
schedule_content.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
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta http-equiv="X-UA-Compatible" content="IE=EDGE" />
<title>Step 4: Developing the Program Schedule & Content</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 4: Developing the Program Schedule & Content</h1>
</div>
<p>Once we had a planning committee, a clear vision, a tentative budget, and approval from administration to proceed, we turned our attention to building out our schedule. Through some scaffolded brainstorming exercises, we determined the following components to be the foundation for the program we wanted to build:</p>
<ul>
<li>Technical workshops</li>
<li>Q&A panels with current library tech workers</li>
<li>A “technology showcase” session to highlight the types of projects library tech workers do</li>
<li>Sessions with Libraries HR + administration to cover resume + interview advice</li>
<li>Mentoring + networking</li>
<li>Cohort building</li>
</ul>
<div id="technical-workshops" class="section level2">
<h2>Technical Workshops</h2>
<p>In developing our menu of technical workshops, we acknowledged up front that we wouldn’t be able to go in depth with any given topic. Our goal, therefore, was to introduce participants to a range of technologies and leave them with next steps for delving deeper after the program wrapped. We tried to select a variety of technologies that were focused on skills that we would like to see in applicants to our entry level positions at the Libraries, but also ones that are broadly applicable across the different areas of library technology. Workshop leaders met as a group several times leading up to the program to ensure that the workshops had some connection and flow between them.</p>
<p>Jumpstart workshops for 2021:</p>
<ul>
<li><a href="https://docs.google.com/document/d/1mtxuzZEBdFzFx-JS62eF-XIPb6N7WMsKR07CnQb_Qg8/edit?usp=sharing">Day 1: Intro to Git & GitHub</a> – We began with an introduction to version control using Git & GitHub so that participants could develop an understanding of the type of collaborative workflows they might encounter in library technology positions. Starting with Git & GitHub also allowed participants to get used to saving their work in a repository early on so that they might continue to practice using Git & GitHub as a place to keep their work throughout the rest of the workshops. Our hope was that GitHub could serve as a portfolio for participants that they could continue to add to and build up after the program ended as well.<br />
</li>
<li><a href="https://jumpstart-frontend.netlify.app/">Day 2: Building Blocks of the Web</a> – This workshop was a new addition for the 2021 offering which was added based on feedback and observations we received about our workshop lineup for the 2020 program. In this workshop, we gave participants a crash course in html & css with the knowledge that this would serve as a great foundation for the rest of the workshops thorughout the week.<br />
</li>
<li><a href="https://github.com/robincamille/bot-tutorial-jumpstart-2021">Day 3: Intro to Python with Twitter Bots</a> – We chose Python as the programming language to use throughout the rest of the workshops. Because participants were mostly early on in their journey of building their tech skills, we thought standardizing this was important and know Python to be a common first language for beginners and one that is widely used in the field. In this workshop, we introduced participants to Python by walking them through the process for how to create a Twitter bot – a challenging but accessible and engaging exercise with clear outputs that left participants feeling accomplished.<br />
</li>
<li><a href="https://jumpstart-webdev-2021.netlify.app/">Day 4: Intro to Web Development</a> – Much of the work we do in libraries and archives involves discovery and delivery of resources and information to end users. And the foundation of how we do that work is the web. In this workshop, we built on some of the Twitter bot work to create a web application where users could add, display, edit and remove content generated by their bots. Participants were introduced to how information flows on the web, and gained hands-on experience creating web applications that stored/retrieved information from a database and displayed it back to users using technologies like HTML/CSS.<br />
</li>
<li>Day 5: Intro to Machine Learning: <a href="https://github.com/vrtompki/Jumpstart-ML-Workshop/blob/master/Setup/Setup_Guide.md">(2020 version)</a> – We wanted to look at mostly foundational skills, but also choose one that would be a “stretch” day, giving participants a glimpse of an up and coming area in library technology. In 2020, we used this workshop as a chance for participants to be introduced to the area of machine learning and how it is being applied in the LIS context as well as tools commonly used in this type of work, such as Jupyter Notebooks. They also gained hands-on experience creating a machine learning model using real library data. In 2021 & 2022, we scaled this workshop back a bit to be more of a discussion based engagement in which participants were introduced to some of the key ethical considerations of machine learning in its current and future applications. This felt to us to be a more accessible introduction to this large and complex topic and a better “food for thought” note to end on as the final workshop of the week.</li>
</ul>
</div>
<div id="day-in-the-life-and-career-path-panels" class="section level2">
<h2>“Day-in-the-Life” and “Career Path” panels</h2>
<p>In addition to our technical workshops, we also thought that it was important for participants to hear from current library technology professionals about how they arrived in their current role as well as what it is like to work in the field. We created the “Day-in-the-Life” and “Career Path” panels to touch on these topics and to include perspectives from a wide array of staff at various levels, from early career to mid-level management and administration, to a range of technical departments and roles across the library. Our goal with these panels was to draw connections between the skills we were introducing the participants to and the work that actually happens in libraries. We wanted to make it clear to participants that you don’t necessarily need a computer science background to get into library technology, and that you can begin the process of setting yourself up for success as a library technologist early on in your library school program. By curating a diverse set of panelists, we hoped that participants could make connections with some aspect of their own background or experience, and that the panelists’ messages would resonate with them.</p>
</div>
<div id="technology-showcase" class="section level2">
<h2>Technology Showcase</h2>
<p>In a similar vein, the technology showcase panel was a chance for participants to get a better sense of the types of projects that they might get to work on someday as a library technologist. Participants were introduced to projects that spanned a wide array of topics and departments – from a IIIF annotation project out of our Digital Library Initiatives department, to a workflow automation project from Collections & Research Strategy, and a web accessibility project from User Experience. Participants reported that this session in particular allowed them to truly envision what a career in library technology might look like and how the skills they were learning with us fit in with that.</p>
</div>
<div id="high-level-hr-admin-sessions" class="section level2">
<h2>High Level HR & Admin Sessions</h2>
<p>The types of sessions led by Libraries HR and administration included an ‘Applying to Your First Library Tech Job’ panel and a Q&A with Libraries Administration session. In the <a href="https://drive.google.com/file/d/1DwLwPVbdh4ZxZ4CrlTZn-USQjiNo7XNT/view?usp=sharing">‘Applying to Your First Library Tech Job’</a> panel Jennifer Garrett, our Associate Director for Organizational Design, Equity, and Talent and Jason Ronallo, the Department Head of Digital Library Initiatives, topics covered things such as resumé dos and don’ts, what to expect from a technical interview session, what a sample in-person interview schedule and set of questions might look like, etc. The Q&A session with Greg Raschke, Senior Vice Provost and Director of Libraries, and Jill Sexton, Associate Director for Digital and Organization Strategy, was a chance for participants to learn about the organizational structure of a library system from a high level perspective and to gain insight into what Libraries administrators see as the future of library technology.</p>
</div>
<div id="mentoring-and-networking" class="section level2">
<h2>Mentoring and Networking</h2>
<p>The way we approached mentoring and networking involved setting up a formal one-on-one mentorship program and hosting daily office hours. In pairing participants with a mentor, we referred to their application materials and notes from our interviews with each participant to ascertain their interests and career goals so that we might pair them with a mentor with a similar background. We gave each mentor <a href="https://docs.google.com/document/d/1C4BodMDGf__QVyf6Meo3XnSjivth0-qczrRUnrjEZWU/edit?usp=sharing">a guide with which to establish the relationship</a>, and set the expectation that each mentor and mentee would meet at least once during the week of the program and at least once sometime afterwards. Based on feedback from mentors for the 2020 cohort, we added a kick-off meeting in 2021 with all of the mentors to further go over expectations and answer any questions or concerns that they might have about their role. Additionally, we have scheduled a debrief session with our mentors as well to collect additional feedback on how the process went overall.</p>
<p>The daily office hours were an optional half hour tacked on to the end of each day of the program where the day’s workshop leaders as well as the planning committee were present to answer any additional questions they may have had that weren’t able to be addressed during the day. In addition to the formal mentorship program and the optional office hours, we were also sure to consistently reiterate that participants should consider any person that they met during the week as a new professional contact that they could feel free to reach back out to when needed. We wanted to establish a friendly atmosphere in which participants felt part of a supportive professional community.</p>
</div>
<div id="cohort-building" class="section level2">
<h2>Cohort Building</h2>
<p>We facilitated cohort building by kicking off the program with a group norm setting exercise, starting each day with an icebreaker and a reflection session, and encouraging participants to engage with one another in a Slack community that they created and maintained. Had we been in-person, there would have been the opportunity to host social events and prompt more casual conversations, but the strategies we used in lieu of these options were a decent stand-in. (See: ‘Step 5: Program Lead-up’ for more information)</p>
</div>
<div id="asynchronous-content-bundle" class="section level2">
<h2>Asynchronous Content Bundle</h2>
<p>Given that the program was originally scheduled as an in-person event but had to be converted to a virtual format, we had to cut several of our synchronous sessions. Rather than cutting them entirely, however, we organized <a href="https://drive.google.com/drive/folders/1kWSW5rN7-6GiXENiiiNcpWE9LUvwt5Wh?usp=sharing">a bundle of asynchronous content</a> and offered participants this material in a variety of mediums.</p>
<p>Our asynchronous content included…</p>
<ul>
<li><a href="https://drive.google.com/drive/folders/14f2wUTqKzuk6KsMndurdNIqlpj2kRzyk?usp=sharing">‘Day-in-the-Life’</a> and <a href="https://drive.google.com/drive/folders/1HQleHg6Ed-ZZgyU_TT-H6mkwyxC4UMg8?usp=sharing">‘Career Path’</a> profiles – One-pager summaries of each of our panelists’ job duties and career advice for students and early-career professionals.</li>
<li><a href="https://drive.google.com/drive/folders/1PfruiKFZAhNSD6Qww6YEinQ-SquOHV_i?usp=sharing">Tech showcase profiles</a> – This folder includes links to the presentations that were part of the synchronous panel as well as links to slide-deck and video presentations highlighting additional projects.</li>
<li><a href="https://drive.google.com/file/d/1TOEftxcxBwEqnyZazGcSxWweiPCEkKoE/view?usp=sharing">Building A Portfolio + Your Web Presence</a> – “Your business card is the Internet! In this session, we will discuss how to control how you appear in a web search and how to showcase yourself and your work. This slide deck covers the pros and cons of joining academic social networks and walks you through the process of writing a reusable bio for yourself and sketching out a plan for your web presence.”</li>
<li>Navigating the Profession – A Vimeo video showcase in which panelists answer questions about navigating the profession as an early career librarian.</li>
</ul>
<p>Participants reported that having access to this content to go over in their own time and to have to refer back to later, perhaps when they are looking to begin the job application process,was an added bonus that they appreciated.</p>
<blockquote>
<p>Tip: In developing your slate of content, revisit your program vision and goals and think carefully about what skills make sense to teach given your particular context. What is it that you want your participants to walk away knowing? What is your capacity as an organization – do you have folks who have the expertise and bandwidth to lead a workshop on X or Y? If not, can you bring in external partners? These are the types of questions you need to think through early on.</p>
</blockquote>
</div>
<div id="constraints-considerations" class="section level2">
<h2>Constraints & Considerations</h2>
<p>There were many challenges we had to work through in developing a cohesive program schedule. Chief among them was the switch from an in-person schedule to an online one as well as recognizing that our time with participants was limited and that we wouldn’t be able to go particularly in depth with any specific skill. In dealing with the switch from online to in-person, we leaned in to the affordances of online delivery by taking it as an opportunity to streamline our schedule in a way that provided room for a more reasonably paced slate of workshops and panels with plenty of built-in breaks and the development of the reusable asynchronous content mentioned above. And while we weren’t able to dive deep into any of the tech skills we touched on, we instead put our energy into leaving participants with a solid foundation and set of resources from which to grow on their own while emphasizing the value of our other sessions on career advice and preparedness. In addition to developing tech skills, we were focused on having participants come away with a renewed sense of clarity and excitement around careers in library technology.</p>
<div class="figure">
<img src="images/brainstorm.png" alt="" />
<p class="caption">In our initial brainstorming exercise, we gave each session its own sticky note and moved them around until we arrived at a schedule that seemed reasonable.</p>
</div>
<div class="figure">
<img src="images/original_sched.png" alt="" />
<p class="caption">Our original in-person schedule was rather ambitious, featuring very full days with shorter breaks.</p>
</div>
<div class="figure">
<img src="images/revised_sched.png" alt="" />
<p class="caption">Our final virtual schedule for 2020 was much more reasonable, beginning at 12pm ET and ending at 6:00pm ET with plenty of built in breaks. This allowed us to accommodate for multiple time zones and accessibility considerations. This schedule remained much the same for 2021.</p>
</div>
<blockquote>
<p>Tip: Don’t forget to factor in things like time zones, school and work schedules, and accessibility when filling in your schedule. In thinking through the flow of each day, it’s best to balance workshop material with presentations and panels to provide the kind of variety that fosters sustained engagement.</p>
</blockquote>
<p><a href="https://ncsu-libraries.github.io/jumpstart-framework/leadup.html">Next >> Step 5: Program Lead-up</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>