<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
span.EmailStyle17
{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:#1F497D">Greetings:<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">I’d like to respond to one point in Nina’s letter (without addressing the question of whether OCLC should be making some of these changes on
<i>any</i> records)<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">Nina writes (under #2):<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">“… it is this institution’s policy to omit adding dcrmb in the 040 since the materials are late 19<sup>th</sup>- century or early 20<sup>th</sup>-century.”<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">However, DCRMB states (in I.2, p. 11): “Unlike its predecessors, which were intended to apply exclusively to pre-1801 imprints, DCRM(B) may be used for printed
monographs of any age or type of production.”<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">Since it seems that protection from both merging
<i>and</i> auto-editing depends entirely on the date and the $$e field, perhaps institutions should re-visit their policies about when to use rare book rules and when to code dcrm(x). If newer materials require rare treatment for any reason, it’s entirely
permissible to use dcrm, along with the appropriate codes.<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">Elaine<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">Elaine Shiner,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Rare Book Cataloger<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Houghton 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>
<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>Dooley,Jackie<br>
<b>Sent:</b> Friday, March 21, 2014 8:15 PM<br>
<b>To:</b> DCRM-L<br>
<b>Subject:</b> [DCRM-L] Info from OCLC quality group group re edits to rare book records<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Greetings--<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">I've gathered some intelligence about editing of WorldCat records to address concerns raised on this list over the past week. Our colleagues in the quality control
group are always happy to clarify things in order to keep the community informed and knowledgable about how this work is done. The quality control group has about a dozen MLS-qualified catalogers who know their stuff.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Macro for auto-editing of various fields: </span></b><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">The macro is a zillion lines
of code, so not possible to articulate everything it does, but it's a combination of RDAifying and correcting routine common errors. Also stuff like adding the FF country code based on 260$b if it's missing and adding 043 based on subject headings. <b>The
script bypasses rb records based on 040$e and/or date (pre-1800). </b>Many elements of OCLC's script can be found in the public documentation about Connexion macros that OCLC writes for catalogers to use: <a href="http://www.oclc.org/content/dam/support/connexion/documentation/client/basics/macros/macros.pdf">http://www.oclc.org/content/dam/support/connexion/documentation/client/basics/macros/macros.pdf</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Expanding abbreviations: This is never done in rb records.
</span></b><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">For others, they're totally cognizant of the need to have item in hand before making a change. Some catalogers send a PDF to show the original data.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Adding RDA 3xx fields:
</span></b><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">They do automatically add these to records when there's another reason to "touch" them, whether in response to a member error report or elsewise. The values are taken straight
from coded data (leader, fixed fields, 008) and translated into the valid RDA terms that match. The 3xx's have been added to OCLC indexes and so enhance retrieval. If rb catalogers see any terms missing, let OCLC know so they can pursue additions. If RDA terms
were changed, OCLC would change records in accordance. In the meantime, is there harm in their presence? For the details, see the link to which Kate Moriarty pointed us the other day: <a href="http://www.oclc.org/en-US/rda/new-policy.html">http://www.oclc.org/en-US/rda/new-policy.html</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Edits made in response to member change requests:
</span></b><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">The volume of requests they receive isn't huge (at least by OCLC standards! About 3,000/month)--but some identify a pattern that affects lots of records. For example, the
6.2k error requests received in Jan/Feb 2014 resulted in more than a million edits.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Correcting access points:
</span></b><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">a really high percentage of the edits made by OCLC are done by machine to bring headings of all kinds into accord with authority records. I'm guessing this wouldn't be
controversial to this audience—eh? In addition to ongoing edits to match headings that come in on new inputs, lots are being made to conform to RDA (e.g. spelling out "dept"). It's all spelled out here: <a href="https://urldefense.proofpoint.com/v1/url?u=http://www.oclc.org/en-US/news/announcements/2012/announcement1.html&k=AjZjj3dyY74kKL92lieHqQ%3D%3D%0A&r=Epy0%2BbwECk089dbPLkByUrrIgIl9%2BPzyUI6irqGT6UE%3D%0A&m=v4O0Amxnay5ROsXHmhKQmyV5ONFO%2F%2BF766mZ0OmHwzA%3D%0A&s=063b9575d513fc80d8c7ae1b3435d78aaa01bd367c77a7b9e1785676aa0b46a2">http://www.oclc.org/en-US/news/announcements/2012/announcement1.html</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Adding 040$e for gihc and amrem:
</span></b><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">They'll make this happen. It's not a simple matter of plugging the values into one bit of code; they have to determine which other systems may be affected by the addition,
etc etc. So it takes some time.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Happy cataloging! Best wishes, Jackie<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">--<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Jackie Dooley<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Program Officer, OCLC Research<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Past President (2012-2013)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Society of American Archivists<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
</div>
</body>
</html>