<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:943462877;
mso-list-type:hybrid;
mso-list-template-ids:-410452614 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hi Diane,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I just finished a recorded presentation on exactly this topic, so I’ve been thinking through many of the things than can and do help. Since there won’t be any overlap or training, here are some of the highlights that I wish I’d had or
that I think would be helpful for our other open positions.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Create workflows that will be accessible by your replacement. These can be Excel spreadsheets, Word documents, or even recorded videos of common tasks. They can be generic enough
that they specify a position that completes the task rather than named individuals who may change over time.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Be sure to share usernames and passwords. We use LastPass and Alma (previously Intota), but the next person will need to know where and how to access admin profiles.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">A shared email account can be very handy and make transitions easier. My last two positions had accounts like
<a href="mailto:libacq@yourinstitution.edu">libacq@yourinstitution.edu</a> or something similar that can be accessed by you or your team and any replacement who joins your institution. That helps retain email histories so that the relevant individuals can
find important details from vendors or from each other.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">Cross-training can also be valuable, so even if you can’t pass along your wisdom directly to a replacement, there will be others who remain who can do so. For example, if I know how
to perform several key workflows in Alma, at least one other person here should also understand those processes, even if it isn’t all done by the same back-up individual. That’s tough with smaller staffs, but may be an option.<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">That’s probably plenty of info already, but the last thing I’d mention is to be sure your administration understands what you do. That can mean creating a broad outline of responsibilities,
but it helps to avoid gaps in tasks for your replacement. For example, if you periodically check database links or update LibGuide links, that won’t make your replacement’s job description, but should be something they know was being done in the past so that
they can continue that work.<o:p></o:p></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I hope that you find something here helpful, although you’ve probably already considered many or all of these things.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks, and congrats on your retirement!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Chris<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><b>Christopher D. Vidas<o:p></o:p></b></p>
<p class="MsoNormal">Electronic Resources Librarian<o:p></o:p></p>
<p class="MsoNormal">Clemson University<o:p></o:p></p>
<p class="MsoNormal">Library Depot<o:p></o:p></p>
<p class="MsoNormal">103 Clemson Research Blvd<o:p></o:p></p>
<p class="MsoNormal">Anderson, SC 29625<o:p></o:p></p>
<p class="MsoNormal">864-656-5175<o:p></o:p></p>
<p class="MsoNormal"><a href="mailto:cvidas@clemson.edu">cvidas@clemson.edu</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Eril-l <eril-l-bounces@lists.eril-l.org> <b>On Behalf Of
</b>Diane Westerfield<br>
<b>Sent:</b> Tuesday, June 1, 2021 11:31 AM<br>
<b>To:</b> eril-l@lists.eril-l.org<br>
<b>Subject:</b> [Eril-l] Retiring - thank you, and what documentation should I leave?<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:black">Hi all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">I’m retiring with my last day being June 30. Thank you all to everyone who has answered questions and given good advice, this listserv has been immensely helpful.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">I won’t have a chance to train the next person in this position. I started in 2008 when electronic resources hadn’t been handled by one person and there weren’t so many e-resources to begin with. There was a steep
learning curve for me: I had to pore over various things to get them set up properly in different systems, dig into old paperwork and order records to figure things out, and cobbled together new workflows. For those of you who stepped into an already established
Electronic Resources Librarian position, what documentation do you wish had been left for you?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">I’m furiously writing up documentation, but I know there are things I won’t think of until months later, or at all.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Diane Westerfield, Electronic Resources & Serials Librarian<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Colorado College, Tutt Library<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="mailto:diane.westerfield@coloradocollege.edu">diane.westerfield@coloradocollege.edu</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">(719) 389-6661<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
</body>
</html>