<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>I can confirm that Randy's understanding is correct: all dcrm codes and predecessors are protected from de-duping. I'm inquiring about gihc.</div>
<div><br>
</div>
<div>As for new codes: first a request is submitted to LC and the code is added to MARC, from which OCLC knows that the code must be authorized for use in WorldCat. It's then added in the next OCLC MARC update (typically along with MANY other MARC updates)—these
are done twice a year, if memory serves. DCRM-L had a considerable thread about this a couple months ago in the context of getting dcrm(g) added.</div>
<div><br>
</div>
<div>--Jackie</div>
<div>
<div>
<div><br>
</div>
<div>--</div>
<div>Jackie Dooley</div>
<div>Program Officer, OCLC Research</div>
<div>Past President (2012-2013)</div>
<div>Society of American Archivists</div>
<div><br>
</div>
<br>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Randy Brandt <<a href="mailto:rbrandt@library.berkeley.edu">rbrandt@library.berkeley.edu</a>><br>
<span style="font-weight:bold">Reply-To: </span>Randy Brandt <<a href="mailto:rbrandt@library.berkeley.edu">rbrandt@library.berkeley.edu</a>>, DCRM-L <<a href="mailto:dcrm-l@lib.byu.edu">dcrm-l@lib.byu.edu</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, 19March, 2014 5:17 PM<br>
<span style="font-weight:bold">To: </span>DCRM-L <<a href="mailto:dcrm-l@lib.byu.edu">dcrm-l@lib.byu.edu</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [DCRM-L] For RBMS/BSC review: draft letter to OCLC<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">Nina,
<div><br>
</div>
<div>For point 1, the attached letter to OCLC may assist with background. Also, please see the BSC minutes of 2011 Midwinter (at which Annie Copeland volunteered to draft the attached letter) and 2011 Annual (which report that the letter was sent to OCLC). </div>
<div><br>
</div>
<div>My understanding was that all dcrm(x) codes <i>and </i>the predecessor codes bdrb and dcrb were being protected But, it would be a good idea to get that confirmed, and also to confirm whether OCLC needs to be contacted whenever a new dcrm code is added
or whether they are being automatically protected. </div>
<div><br>
</div>
<div>Stylistically, in your 4th sentence sentence, I would use the actual 040 $e code values, e.g. dcrmb instead of DCRM(B). And, you've got DCRM(M) twice; the second instance should be DCRM(MSS) [or dcrmmss, if you go that route].</div>
<div><br>
</div>
<div>Thanks for drafting this letter!</div>
<div><br>
</div>
<div>Randy</div>
</div>
<div class="gmail_extra"><br>
<br>
</div>
</div>
</div>
</span>
</body>
</html>