<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:"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:"Calisto MT";
panose-1:2 4 6 3 5 5 5 3 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calisto MT","serif";
color:#44546A;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calisto MT","serif";color:#44546A">We’ve been going through this process for the last several years. We evaluated every journal package in terms of overall use, overall cost-per-use, cost per
title, CPU for each title, distribution of use across titles (as in 80% of uses were for what % of titles), and the list-price CPU.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calisto MT","serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calisto MT","serif";color:#44546A">There were some packages which were clearly not good deals. These were packages where the distribution of usage across titles was very limited (80% of uses were
from < 15% of titles), and which, when we calculated the alternative of subscribing to the most used titles, would be more economical to split up.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calisto MT","serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calisto MT","serif";color:#44546A">There were other packages which clearly
<i>were</i> a good deal – low overall CPU, high distribution of usage across titles, and, most importantly, they were affordable. These we continued.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calisto MT","serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calisto MT","serif";color:#44546A">Then there are those packages which were a good deal, but were unaffordable to continue. These were the biggest of the big deals. These were the hardest to
cut. By any measure, attempting to subscribe to the better-performing titles individually would have exceeded the cost of the package. But, taken as a single source of expenditures, they were unsustainable. It was only after making these cuts (and explaining
our intention to have to cut the biggest of the big deals) that the library was appropriated more funds. But this is only temporary…no more than 3 years. This decision will have to be revisited.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calisto MT","serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calisto MT","serif";color:#44546A">The point it, breaking up a well-performing package is very, very hard to do. At some point, you have to cut titles that have very low CPU’s or otherwise are
a good value. It’s like getting very heavy mortgage at a very low rate. Yes, it’s a good deal, but if you don’t have the money in the budget, you have to pass on it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calisto MT","serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calisto MT","serif";color:#44546A">Karen Harker<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calisto MT","serif";color:#44546A">Collection Assessment Librarian<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calisto MT","serif";color:#44546A">940-565-2688<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calisto MT","serif";color:#44546A"><a href="http://librariesareforuse.wordpress.com/"><span style="color:blue">Libraries are for Use</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calisto MT","serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> Eril-l [mailto:eril-l-bounces@lists.eril-l.org]
<b>On Behalf Of </b>Colleen A McGhee-French<br>
<b>Sent:</b> Monday, November 09, 2015 10:05 AM<br>
<b>To:</b> eril-l@lists.eril-l.org<br>
<b>Subject:</b> [Eril-l] Is Breaking Up THAT Hard to Do?<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi all,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I tried searching the archives of this list, but perhaps I am not doing it correctly. I couldn't find any discussion of the idea of/implementation of/success with breaking up journal packages. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Yet I would think we all have them - huge, huge journal packages, each containing more than 1200 or so journals, only a fraction of which are important/used - sometimes very important/highly used, each also containing hundreds of journals
that we're paying for that have not been used in the last several years, at least to our knowledge. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Has your institution thought about this? Tried it? Succeeded/failed at it, and why? What were the largest obstacles to success?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Or has your institution thought about it and figured, Hey - the very important journals are used SO MUCH that the package overall is actually fairly economical and that
<i>those</i> are the journals to concentrate on (rather than the huge number of unused journals)?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thoughts?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Colleen<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>