<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
/* 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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Georgia","serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Georgia","serif";
color:windowtext;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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:11.0pt;font-family:"Calibri","sans-serif";color:#0070C0">For whatever it’s worth, I share the perplexity, and even vexation, of Francis and Will.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0070C0"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0070C0">I sat in on one OCLC session yesterday and found the “A” portion distinctly short of info—very terse “answers” to my questions about how we’ll avoid losing
local notes and info in this process when IRs get dumped, and just what the process will entail to ‘migrate’ local data from IRs to so-called LBDs; also how, in future, we’ll go about adding select locally-coded manifestation-level info from our Voyager records
to OCLC via this LBD mechanism. (We catalog in Voyager, and all our original master records and modified IRs get batch-uploaded to OCLC each quarter.) Basically, their answer to those question seemed to be, “e-mail us and we’ll discuss with your library.”<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0070C0"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0070C0">I imagine all will be revealed in the fullness of time, but it seems perplexing at this point.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0070C0"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#0070C0">Jeff Barton</span><span style="color:#0070C0"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#0070C0">Cotsen Children's Library Cataloger</span><span style="color:#0070C0"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#0070C0">Rare Books & Special Collections Department</span><span style="color:#0070C0"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#0070C0">Princeton University Library<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<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""> dcrm-l-bounces@lib.byu.edu [mailto:dcrm-l-bounces@lib.byu.edu]
<b>On Behalf Of </b>Lapka, Francis<br>
<b>Sent:</b> Thursday, May 14, 2015 11:36 AM<br>
<b>To:</b> DCRM Users' Group<br>
<b>Subject:</b> Re: [DCRM-L] OCLC's IR webinar (May 13)<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:"Georgia","serif";color:#1F497D">I omitted from my summary – for fear that it might come off as crankiness – the part where OCLC’s moderator said that he had no data on the usage rates of IR records
by catalogers (in the Connexion client). OCLC moderators also reassured us that in a proper cataloging workflow we don’t really need to see the IRs.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1F497D">Francis<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1F497D"><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"">
<a href="mailto:dcrm-l-bounces@lib.byu.edu">dcrm-l-bounces@lib.byu.edu</a> [<a href="mailto:dcrm-l-bounces@lib.byu.edu">mailto:dcrm-l-bounces@lib.byu.edu</a>]
<b>On Behalf Of </b>Will Evans<br>
<b>Sent:</b> Thursday, May 14, 2015 11:02 AM<br>
<b>To:</b> DCRM Users' Group<br>
<b>Subject:</b> Re: [DCRM-L] OCLC's IR webinar (May 13)<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Are we not users? <o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">I am vexed by OCLC's attitude and more than a little disheartened. Given our small numbers, data driven decisions hold little promise for accommodating present and future concerns of the rare materials community.
<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">While we are not an IR library, we frequently use the information within those records to aid in identification, when navigating a sea of inferior records.<o:p></o:p></p>
</div>
<p class="MsoNormal">How did a feudal business model, where we create the product but have no voice in how that product is maintained or delivered, survive into the 21st century?<br>
<br>
<o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Garamond","serif"">Will Evans</span></b><o:p></o:p></p>
</div>
<div>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-family:"Garamond","serif"">Chief Rare Materials Catalog Librarian</span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-family:"Garamond","serif"">Library of the Boston Athenaeum</span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-family:"Garamond","serif"">10 1/2 Beacon Street</span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-family:"Garamond","serif"">Boston, MA 02108</span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-family:"Garamond","serif""> </span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-family:"Garamond","serif"">Tel: 617-227-0270 ext. 224</span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-family:"Garamond","serif"">Fax: 617-227-5266 </span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><span style="font-family:"Garamond","serif""><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.bostonathenaeum.org_&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=t7GDkvcZa922K6iya7a6MxgVxxw7OjL0m1rPBXkflk4&m=U2ok5q4kpAuk5J1D4k9nigDFjYjwYhQu1YLjshnWHHg&s=9LHwjCZaUPV4uhV_aeGFuhgwXmo9220nDSnSWffl2B8&e=" target="_blank">www.bostonathenaeum.org</a></span></b><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Thu, May 14, 2015 at 10:27 AM, Lapka, Francis <<a href="mailto:francis.lapka@yale.edu" target="_blank">francis.lapka@yale.edu</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p><span style="font-family:"Georgia","serif"">Yesterday’s webinar on the demise of Institutions Records and the transition to Local Bibliographic Data was primarily a Q-and-A. Compared to the discussion that Yale catalogers had with an OCLC rep in April, there
seemed much less ambiguity that OCLC has no plans to provide access to the local data of any institution other than your own, no matter how much we say that this is important to us. Moderators held firm to the talking point: OCLC data suggests that its users
don’t care about IRs.</span><o:p></o:p></p>
<p><span style="font-family:"Georgia","serif"">It’s tempting to think that the OCLC data is somehow wrong, but I’m inclined to accept their conclusion at face value: users who care about copy-specific descriptions generally don’t see OCLC as a useful discovery
tool. So is there much point in investing energy trying to make OCLC fulfill a role for which it is ill-suited? If we want a mechanism that enables searching of copy-specific data across institutions, we should probably look elsewhere.</span><o:p></o:p></p>
<p><span style="font-family:"Georgia","serif"">Francis</span><o:p></o:p></p>
<p> <o:p></o:p></p>
<p> <o:p></o:p></p>
<p> <o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Francis Lapka · Catalog Librarian</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Department of Rare Books and Manuscripts</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Yale Center for British Art</span><o:p></o:p></p>
<p><span style="font-size:10.0pt;font-family:"Calibri","sans-serif""><a href="tel:203.432.9672" target="_blank">203.432.9672</a> ·
<a href="mailto:francis.lapka@yale.edu" target="_blank">francis.lapka@yale.edu</a></span><o:p></o:p></p>
<p> <o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<br>
-- <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>