<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" 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 12 (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;}
@font-face
{font-family:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 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;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@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'>Let me assure you, Richard, that it was an ironic “hmm.” This is
indeed a big problem, and one that RDA—if adopted—will make significantly
worse. I’m pretty deficient in my RDA knowledge and was not happy to learn on
Monday about its implications for edition statements.<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'>Quite right that OCLC has to be conservative about establishing
its own guidelines that depart from cataloging rules.<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'>--Jackie<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 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>Noble,
Richard<br>
<b>Sent:</b> Wednesday, November 03, 2010 7:33 AM<br>
<b>To:</b> DCRM Revision Group List<br>
<b>Subject:</b> Re: [DCRM-L] FW: Slides and Recording from Nov. 1 "When to
Input a New Record" Webinar<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Garamond","serif"'>Thanks,
Jackie. But it's more than "Hmm". It is most peculiar that DCRM(B),
concerned as it is with the direct representation of evidence that, among other
things, distinguishes editions; and now RDA, concerned (at least as its
creators profess it to be) with the usefulness of metadata across the
boundaries of various activities, should so utterly frustrate our
ability--anybody's ability--to ensure that recognition of fundamental entity
distinctions should be easily programmable in so basic a database process as
de-duping.</span><o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Garamond","serif"'>Jay
said up front that the <i>best</i> way to protect a record against false
de-duping is to add a 250.* Dupes are a scourge--the body of pre-1801 records
is now hopelessly infected with them--but at least they are for the most part
available for inspection in the result set of a sufficiently broad search.
False merges are infinitely worse: unrecognizable without an "item in
hand" (and, even with one, seldom recognizable) and all but impossible to
reverse. (How does one re-assign correct holdings to a record or records
resurrected from the limbo of 019?)</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:13.5pt;font-family:"Garamond","serif"'>If
the makers of RDA prove resistant to further change, is there not a role for
OCLC to provide for effective "defensive cataloging" by way of its
own bibliographic standards? It seems to matter to the folks in Quality
Control, and I don't see why they should have to throw up their hands and say
"Sorry--you're defenseless."</span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-family:"Courier New"'>___________________________________</span></span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:18.0pt;
font-family:"Garamond","serif"'>*This is not a MARC-specific problem--in
general terms, it's an instance of functionally inadequate data definition. It
is, by the same token, too bad that the 503 was killed--at least a programmer
could have worked with that, absent the 250. There are, however, unassigned 25X
values, one of which (251?) could be established, if only in the OCLC database,
as the distinctive tag for a supplied edition statement backed up by a note.
Obviously OCLC is reluctant to depart from the "rules"; but it could
be said that there are such things as rules that depart from acceptable
standards.</span></span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><i><span style='font-size:18.0pt;
font-family:"Garamond","serif"'>Obiter dictum</span></i></span><span
class=apple-style-span><span style='font-size:18.0pt;font-family:"Garamond","serif"'>:
I have very dark feelings about the mind-set that clearly regards the
minimizing of expertise as the governing imperative for the creation of
metadata. "Cataloger judgment" is what we are supposed to "get
over", along with ourselves. But we are, in this instance at least,
talking about the integrity of the database as an accurate record of
bibliographical entities. What else is it for? Retrospective quality control of
metadata that turns out to be inadequate is a lot harder than quality control
in its creation--i.e. ("in english"): Doing it over is more expensive
(and often less possible) than doing it right in the first place.</span></span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-family:"Courier New"'>RICHARD
NOBLE : RARE BOOKS CATALOGER : JOHN HAY LIBRARY : BROWN UNIVERSITY</span></span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-family:"Courier New"'>PROVIDENCE,
RI 02912 : 401-863-1187/FAX 863-3384 : <a
href="mailto:RICHARD_NOBLE@BROWN.EDU" target="_blank">RICHARD_NOBLE@BROWN.EDU</a> </span><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>On Tue, Nov 2, 2010 at 5:44 PM, dooleyj <<a
href="mailto:dooleyj@oclc.org">dooleyj@oclc.org</a>> wrote:<o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Calibri","sans-serif"'>Some of you no doubt attended this OCLC
webinar yesterday and have already received this message. For those who didn’t,
Jay Weitz gave an overview of how the guidelines for when to input a new record
intersect with OCLC’s latest de-duping algorithms. While much of the
information was quite basic, he did touch on some issues particular to rare
materials during the Q&A—including verifying that no records for pre-1800
imprints are ever de-duped.<br>
<br>
Lots of questions about supplying edition statements in various contexts, in
response to which Jay repeatedly noted that RDA doesn’t allow catalogers to add
ed. Statements in the 250 if they don’t appear on the piece. Putting them in a
5xx field won’t get picked up by the de-duping algorithms. Hmm.<br>
<br>
</span><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'>-- <br>
Jackie Dooley<br>
Program Officer<br>
OCLC Research and the RLG Partnership<br>
<br>
949.492.5060 (work/home) -- Pacific Time<br>
949.295.1529 (mobile)</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>