<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
@font-face
{font-family:inherit;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Open Sans";
panose-1:2 11 6 6 3 5 4 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
h4
{mso-style-priority:9;
mso-style-link:"Heading 4 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.Heading4Char
{mso-style-name:"Heading 4 Char";
mso-style-priority:9;
mso-style-link:"Heading 4";
font-family:"Calibri",sans-serif;
font-weight:bold;}
.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;}
--></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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:14.0pt">Hello all:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">I mentioned this article that I saw on Twitter in our small group at yesterday’s LLC meeting and am forwarding it to everyone. I think it can spur interesting conversation with our librarians about IL.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">Gerie<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"><a href="https://crl.acrl.org/index.php/crl/article/view/24912">https://crl.acrl.org/index.php/crl/article/view/24912</a><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:14.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:14.0pt">My @CRL_ACRL guest editorial on one-shots (with accompanying CFP for a special issue) is now published! The Contested One-Shot: Deconstructing Power Structures to Imagine New Futures crl.acrl.org/index.php/crl/…
#critlib #infolit<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="vertical-align:baseline"><i><span style="font-size:14.0pt;font-family:"inherit",serif;color:black;border:none windowtext 1.0pt;padding:0in">Nicole Pagowsky<o:p></o:p></span></i></p>
<p class="MsoNormal" style="vertical-align:baseline"><span style="font-size:14.0pt;font-family:"inherit",serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="vertical-align:baseline"><b><span style="font-size:14.0pt;font-family:"Open Sans",sans-serif;color:black">Abstract<o:p></o:p></span></b></p>
<p class="MsoNormal" style="vertical-align:baseline"><span style="font-size:14.0pt;font-family:"inherit",serif;color:black">For so long the one-shot has been the dominating force of how we engage in library instruction. There is a lot of meaning and debate
saturated in this faux-innocuous activity, yet there is not always consensus as to how we define a one-shot. Is it doing a library “spiel” to demo a database, present the library website, or give a tour? Is it visiting a class once without an explicit connection
to an assignment? Is it even embedding a learning object in a class without assessment feedback or other interaction? To have a central, salient definition of the one-shot for the purpose of this editorial, I view it as a standalone session, superficially
(or not at all) connected to course content, that is tacked onto a class. Within a curriculum, the one-shot has no memory of where information literacy has been and no vision of where it is going. It is ephemeral within cycles of ineffectiveness. I am writing
this guest editorial to talk this through and share my thoughts, and then invite you to share yours in a special issue of <i><span style="border:none windowtext 1.0pt;padding:0in">C&RL</span></i> on the contested one-shot (see the Call for Proposals at the
end). We do not need consensus but sharing different perspectives and exploring what “effective” teaching means is important to support our instruction programs. This guest editorial will discuss one-shots in the context of effective teaching practices; assessment;
and power structures related to care-work and Equity, Diversity, and Inclusion (EDI). The hope is to expand our pedagogical imagination through questioning what appear to be common-sense practices in order to create better systems and structures.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:14.0pt"><o:p> </o:p></span></p>
</div>
</div>
</body>
</html>