<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Century;
panose-1:2 4 6 4 5 5 5 2 3 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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
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;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Tahoma",sans-serif;
color:#44546A;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.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:1218587500;
mso-list-type:hybrid;
mso-list-template-ids:1870029660 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
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:;
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:;
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:;
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:;
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:;
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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif;color:#44546A">Hi everyone-<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif;color:#44546A">We have not figured out a best practice for reconciling title lists, beyond hand-checking lists, which is extraordinarily time-consuming. If someone can come up with a better
means of getting accurate lists, which can be easily loaded into our various systems, then please share this information
</span><span style="font-family:Wingdings;color:#44546A">J</span><span style="font-family:"Tahoma",sans-serif;color:#44546A">.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif;color:#44546A">Three or four years ago, at ER&L, someone, whose name I didn’t catch, used the phrase, “holdings entropy” to describe this phenomenon of inaccurate holdings. It starts with a
title list from the publisher which may or may not include previous titles, or may not be precisely correct, even with current titles. On our end, we may forget or not realize that a title has ceased, changed to a new title, or changed publisher, furthering
the inaccuracies. As the years go by, and titles come and go, our various knowledgebases become even more inaccurate as there is a constant drift.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif;color:#44546A">Since we are not yet at the point of getting easy to load, easy to maintain, 99%+ accurate lists, I am at least hoping to get to the point of manually checking our big publisher
lists, and then doing minimal maintenance on them each year. This goal is still out of reach, but we are slowly getting there.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif;color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif;color:#44546A">I agree with Athena Hoeppner, who wrote in earlier, about her list of needs for vendor entitlement lists, which I will repeat here for emphasis:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif;color:#44546A"><o:p> </o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:#44546A;mso-list:l0 level1 lfo1"><span style="font-family:"Century",serif">Consistent IDs for each journal on invoices, KBs, and vendor downloadable files (not just ISSN)<o:p></o:p></span></li><li class="MsoNormal" style="color:#44546A;mso-list:l0 level1 lfo1"><span style="font-family:"Century",serif">Clear and consistent title history info:
<o:p></o:p></span>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:#44546A;mso-list:l0 level2 lfo1"><span style="font-family:"Century",serif">Current ISSNs with previous title and ISSN info and volume/years for each title/ISSN<o:p></o:p></span></li><li class="MsoNormal" style="color:#44546A;mso-list:l0 level2 lfo1"><span style="font-family:"Century",serif">Display both current and historical title/ISSN on vendor sites. Lots of publishers show the full run for a journal under the current title and ISSN
<o:p></o:p></span></li></ul>
</li></ul>
<p class="MsoNormal"><span style="font-family:"Century",serif;color:#44546A">Accurate, custom entitlement reports upon request, with an option to show all-accessible or perpetually owned entitlements<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif;color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif;color:#44546A">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif;color:#44546A">Liisa<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif;color:#44546A"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif;color:#1F497D">Liisa Mobley
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D">Electronic Resources Unit Supervisor, Cornell University Library, Ithaca, NY 14853<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:#1F497D"><a href="mailto:lsk24@cornell.edu"><span style="color:#0563C1">lsk24@cornell.edu</span></a>, phone (607) 255-3241, fax (607) 255-6110<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif;color:#44546A"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<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>Diane Westerfield<br>
<b>Sent:</b> Monday, November 28, 2016 3:49 PM<br>
<b>To:</b> eril-l@lists.eril-l.org<br>
<b>Subject:</b> Re: [Eril-l] Procedures (and/or documentation) for matching e-journal entitlements lists against knowledge base coverage lists?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This has been on my mind for years. The entitlement lists often don’t match exactly what you have access to on a vendor website, for reasons unknown to me. Not open-access,
but often some partial run or ceased journal that’s not on the entitlement list but you still have full text access. Also you may have extra years of full text beyond what the entitlement list is showing. I’m currently marching through one journal package
and seeing that access frequently begins some or many years before the entitlement start year.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Also these entitlement lists don’t match up with link resolver lists or consortial lists. There is so much variability in how titles are listed, and title changes. And do you
go through your scanned license PDFs and check for every title on those as well? And then there are those journal archives that somebody bought, before you started working there, so some journal runs start way early and others start at the same year. And then
there’s the journal package where sometimes full text starts at 1996 and sometimes it’s 1997, and there’s no rhyme or reason as to which is which.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The other librarians here want me to reflect accurately what we have access to “in real life”, the maximum amount of full text access. If they find that 1999-2001 full text
access to a random journal on XYZ Journal Package, they want it in the link resolver and catalog, entitlement list doesn’t matter. Similarly if ZYX journal package has a journal with full text access 1997-current but the entitlement started in 2008, they still
want me to reflect the access back to 1997. So I can’t simply dump entitlement data into the link resolver without then going back through it – either the link resolver data title by title, or stepping through the title browse of the journal site, or both.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In general I would love to hear about best practices. How often should you do this? Are some journal vendors more tied to their entitlement lists than others? I’m the only
one at my institution who does the “checking by hand” and you all know what a grind it is. If anyone has tips on dealing with title reconciliation burnout, I would love to hear it. No one else wants to work on this, and the fixes involved are so complicated
(link resolver, ILS records, and ILS coverage database) that it scares other people off anyway.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">To look for matches in two title lists: you can do a huge amount of title cleanup in Excel and Python. With two cleaned title lists in hand, run a query through MS Access;
you can get all the fields from a matched title to sit neatly on the same line, eliminating the need for Excel VLOOKUP which is rather unwieldy. Don’t try to clean data in MS Access, it’s terrible for that. You can also use Conditional Formatting in Excel
to find duplicates, but that’s only suitable for smaller data sets and won’t line up your data.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Diane Westerfield, Electronic Resources & Serials Librarian<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Tutt Library, Colorado College<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><a href="mailto:diane.westerfield@coloradocollege.edu">diane.westerfield@coloradocollege.edu</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">(719) 389-6661<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> Eril-l [<a href="mailto:eril-l-bounces@lists.eril-l.org">mailto:eril-l-bounces@lists.eril-l.org</a>]
<b>On Behalf Of </b>Rebecca Kemp Goldfinger<br>
<b>Sent:</b> Monday, November 28, 2016 11:53 AM<br>
<b>To:</b> <a href="mailto:eril-l@lists.eril-l.org">eril-l@lists.eril-l.org</a><br>
<b>Subject:</b> [Eril-l] Procedures (and/or documentation) for matching e-journal entitlements lists against knowledge base coverage lists?<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal">(Cross-posted)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Dear Colleagues,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Do you have a good method or set of procedures worked out for comparing e-journal entitlements lists against what is activated and/or able to be activated in your knowledge base (KB)? I'm defining "entitlements lists" as lists of the e-journal
titles and the subscribed/purchased coverage to which we are entitled. These lists can be e-mailed by publisher representatives or downloaded from publisher websites. Our knowledge base is WorldCat KB, and the KB files we compare against are KBART files,
but I am interested in looking at procedures that anyone may be using, regardless of which KB you have.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">We have tried using Excel's VLOOKUP functionality to match titles by unique identifier, but it seems as though there are lots of problems in the vendor supplied data that make it hard to compare coverage (and even titles, sometimes).
A few problems we've run up against are entitlements lists that do not show all title changes with separate titles, ISSNs, and coverage for all the titles in the history, and entitlements lists that show separate lines for each subscribed year of the title,
which makes it hard to pull together the true start date and end date into one KB entry.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If you have a process that you think works pretty well for matching up entitlements with what's available in the KB, would you mind contacting me? I would love to learn about your process(es) and the tools you use. We are especially interested
in automating the process with Excel or Google Sheet templates, if anyone has been doing that. Or are there any workshops or presentations that anyone knows of on this topic?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Has anyone had any success in getting better entitlements data from publishers?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Let me know if I need to clarify my request. Also, if there is interest in my gathering together responses and sharing to the lists, I would be happy to do that.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Many thanks for considering,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Rebecca<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888"><o:p> </o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:#888888">Rebecca Kemp Goldfinger<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888">Continuing Resources Librarian<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888">University of Maryland, College Park<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888">Acquisitions Department, Room 2200<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888">McKeldin Library, 7649 Library Lane<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888">College Park, MD 20742<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888"><a href="tel:301-405-9309" target="_blank">301-405-9309</a> (phone)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#888888"><a href="tel:301-314-1200" target="_blank">301-314-1200</a> (fax)<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>