<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:"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:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Corbel;
panose-1:2 11 5 3 2 2 4 2 2 4;}
@font-face
{font-family:"Trebuchet MS";
panose-1:2 11 6 3 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.m-4469232422746711448msolistparagraph, li.m-4469232422746711448msolistparagraph, div.m-4469232422746711448msolistparagraph
{mso-style-name:m_-4469232422746711448msolistparagraph;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Georgia",serif;
color:#1F497D;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
@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:816841843;
mso-list-template-ids:-1640095562;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:839858201;
mso-list-template-ids:-1060067670;}
@list l1:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:1328054070;
mso-list-template-ids:850851862;}
@list l2:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3
{mso-list-id:1919821427;
mso-list-template-ids:1915676070;}
@list l3:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
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:"Georgia",serif;color:#1F497D">Erin’s message sums up my thoughts too. An automated process to remove or add punctuation will
<i>probably </i>be fine, with few if any concerns unique to rare materials cataloging. For confirmation, it’d be reassuring to see more testing or an extremely detailed specification of the rules governing the conversion process.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">An eyebrow rises at one detail in the
<a href="http://www.loc.gov/aba/pcc/documents/NLM_File_Description.docx">NLM test spec</a>: remove opening and closing square brackets for 245 $h. That seems undesirable. It’s unclear if an OCLC conversion would do the same.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">Ben Abrahamse says I can share his email below. It sheds light. Ben writes on behalf of PCC’s Standing Committee on Automation, not OCLC.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">Francis<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt"> Benjamin A Abrahamse [mailto:babraham@mit.edu]
<br>
<b>Sent:</b> Friday, December 14, 2018 11:50 AM<br>
<b>To:</b> Lapka, Francis <francis.lapka@yale.edu>; bremer@oclc.org; xlli@ucdavis.edu<br>
<b>Subject:</b> RE: New policy regarding limited use of ISBD punctuation in bibliographic records<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;color:#1F497D">Francis,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;color:#1F497D">Thank you for the email.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;color:#1F497D">At the moment, we are not developing a batch process to change existing records, although it’s being discussed in various places.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;color:#1F497D">I believe OCLC will be working on scripts to support conversion between punctuated and unpunctuated data “on the fly” as it were, for users in the client. But that any
further implementation, such as retrospective conversion, will depend on how the community at large responds to the new policy.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;color:#1F497D">That said: certainly I think any proposed batch conversion of MARC records would necessarily be limited in scope to only those punctuations that appear at the end of
fields and subfields. And, at that point, we would want collections of records from various specialist communities. I hesitate to ask you to make one now, because I don’t know when that will happen.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;color:#1F497D">I hope this helps,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;color:#1F497D">Ben<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt"> Lapka, Francis <<a href="mailto:francis.lapka@yale.edu">francis.lapka@yale.edu</a>>
<br>
<b>Sent:</b> Friday, December 14, 2018 11:32 AM<br>
<b>To:</b> <a href="mailto:bremer@oclc.org">bremer@oclc.org</a>; <a href="mailto:xlli@ucdavis.edu">
xlli@ucdavis.edu</a>; Benjamin A Abrahamse <<a href="mailto:babraham@mit.edu">babraham@mit.edu</a>><br>
<b>Subject:</b> New policy regarding limited use of ISBD punctuation in bibliographic records<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<span style="font-size:10.0pt;font-family:"Georgia",serif;color:black">Dear colleagues,<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<span style="font-size:10.0pt;font-family:"Georgia",serif;color:black">The announcement on ISBD punctuation has begun to prompt discussion in the rare materials community (on our DCRM-L list). Initial reactions seem supportive.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<span style="font-size:10.0pt;font-family:"Georgia",serif;color:black">We’re very much keen to know more about the details of implementation. For at least a portion of our community, punctuation in
<i>transcribed </i>fields is considered vital. Our transcription policies for such punctuation sometimes vary from those used by the general community. We want to make sure that all batch processes correctly handle removal (or addition) of punctuation.
<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<span style="font-size:10.0pt;font-family:"Georgia",serif;color:black">LC, NLM, and OCLC have offered compiled sets of test records
</span><span style="font-size:10.0pt;font-family:"Georgia",serif;color:#1F497D"><a href="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Faba%2Fpcc%2Fdocuments%2Ftest-records-punctuation.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7Ccaafc32acf5e46725f4508d661e47915%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C1%7C636804031281478996&sdata=%2BXRFJmaGw%2BeqGfdoa8mNbJoku4njm6GAwNh1es4Uq48%3D&reserved=0">here</a>.
</span><span style="font-size:10.0pt;font-family:"Georgia",serif;color:black">At a skim, there appear to be only a few rare materials records tested (coded dcrmb, in the NLM set).
<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<span style="font-size:10.0pt;font-family:"Georgia",serif;color:black">If the RBMS Bibliographic Standards Committee were to compile a batch of records (in a .mrc file, say) representing rare materials cataloging of a variety of formats, would it be possible
to run the batch process against the file and return the output to us (in a .mrc file)? We are especially interested in the batch processes executed by OCLC. <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<span style="font-size:10.0pt;font-family:"Georgia",serif;color:black">Best,<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<span style="font-size:10.0pt;font-family:"Georgia",serif;color:black">Francis Lapka<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<span style="font-size:10.0pt;font-family:"Georgia",serif;color:black">Chair, ACRL/RBMS Bibliographic Standards Committee<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b>From:</b> DCRM-L [mailto:dcrm-l-bounces@lib.byu.edu] <b>On Behalf Of
</b>Erin Blake<br>
<b>Sent:</b> Friday, December 14, 2018 1:02 PM<br>
<b>To:</b> DCRM Users' Group <dcrm-l@lib.byu.edu><br>
<b>Subject:</b> Re: [DCRM-L] Fwd: [PCCLIST] New policy regarding limited use of ISBD punctuation in bibliographic records<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">I'd love for all ISBD punctuation to be machine-supplied, and I don't see any problem with
<i>new </i>PCC DCRM records following the three options.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The only conern I've got with the proposal is with step 4: we'd want to make sure adquate testing is done with DCRM records as part of "<span style="font-size:10.0pt;font-family:"Corbel",sans-serif">Work with bibliographic utilities and
other interested parties to develop tools and specifications to automate the process of removal or reinsertion of punctuation.</span>" There might well be "<span style="font-size:10.0pt;font-family:"Corbel",sans-serif">terminal periods integral to the data
(e.g., recorded as part of abbreviations, initials, etc.) </span>" that rarely come up outside Special Collections. Inadequate testing would let PCC say "the percentage of PCC records affected is statistically insignificant" rather than "the percentage of
PCC DCRM records affected is unacceptably large."<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Erin. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">Erin Blake, Ph.D. | Senior Cataloger | Folger Shakespeare Library | 201 E. Capitol St. SE, Washington, DC, 20003 |
</span><a href="mailto:eblake@folger.edu"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">eblake@folger.edu</span></a><span style="font-size:7.5pt;font-family:"Arial",sans-serif"> | office tel. +1 202-675-0323 |
</span><a href="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.folger.edu&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C8ea6d219c921409303d908d661ee47f1%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C1%7C636804073387073918&sdata=063k98ZRubfmdBNPpTc23gJp9SngGBeK%2Fi%2BX6T9FStg%3D&reserved=0"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">www.folger.edu</span></a> <o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Thu, Dec 13, 2018 at 12:53 PM Lapka, Francis <<a href="mailto:francis.lapka@yale.edu">francis.lapka@yale.edu</a>> wrote:<o:p></o:p></p>
</div>
<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 class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif;color:#1F497D">I think the new policy is sensible. Two questions, to start:</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<ol start="1" type="1">
<li class="MsoNormal" style="color:#1F497D;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;mso-list:l0 level1 lfo1">
<span style="font-family:"Georgia",serif">The statement below says that PCC will “</span><span style="color:windowtext">work with bibliographic utilities and other interested parties to develop tools and specifications to automate the process of removal or
reinsertion of punctuation.”</span><span style="font-family:"Georgia",serif;color:windowtext">
</span><span style="font-family:"Georgia",serif">Does RBMS/BSC have anything to add to those discussions? Will the general automated processes (in OCLC, for example) work well enough with DCRM descriptions, including those that employ “double” punctuation?
Has anyone in our community examined OCLC’s test record set, provided here: </span>
<a href="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Faba%2Fpcc%2Fdocuments%2Ftest-records-punctuation.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C8ea6d219c921409303d908d661ee47f1%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C1%7C636804073387083930&sdata=3LUBclwwMhV6ZLk7S6v%2BQmiTv79PnI42ck7aGGZtfJk%3D&reserved=0" target="_blank"><span style="font-family:"Georgia",serif">http://www.loc.gov/aba/pcc/documents/test-records-punctuation.html</span></a><span style="font-family:"Georgia",serif">
?</span><o:p></o:p></li></ol>
<p class="m-4469232422746711448msolistparagraph"><span style="font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<ol start="2" type="1">
<li class="MsoNormal" style="color:#1F497D;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;mso-list:l1 level1 lfo2">
<span style="font-family:"Georgia",serif">Editors of the forthcoming RBMS Policy Statements for RDA will probably have to consider these options for the PS guidance on punctuation. For *<b>DCRM</b>* descriptions, should we (or can we) allow the same three options
presented by PCC, when the policy is implemented in the spring?</span><o:p></o:p></li></ol>
<p class="m-4469232422746711448msolistparagraph"><span style="font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif;color:#1F497D">Francis</span><o:p></o:p></p>
<p class="m-4469232422746711448msolistparagraph"><span style="font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>From:</b> DCRM-L [mailto:<a href="mailto:dcrm-l-bounces@lib.byu.edu" target="_blank">dcrm-l-bounces@lib.byu.edu</a>]
<b>On Behalf Of </b>Deborah J. Leslie<br>
<b>Sent:</b> Wednesday, December 12, 2018 4:21 PM<br>
<b>To:</b> DCRM Users' Group <<a href="mailto:dcrm-l@lib.byu.edu" target="_blank">dcrm-l@lib.byu.edu</a>><o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><br>
<b>Subject:</b> Re: [DCRM-L] Fwd: [PCCLIST] New policy regarding limited use of ISBD punctuation in bibliographic records<o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif;color:#1F497D">I think we'd still want ISBD punctuation for display, but that's something machines are really good at.
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;color:#5F497A">Deborah J. Leslie | Folger Shakespeare Library |
</span><a href="mailto:djleslie@folger.edu" target="_blank"><span style="font-size:9.0pt">djleslie@folger.edu</span></a><span style="font-size:9.0pt;color:#5F497A"> |</span><o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif;color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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 [</span><a href="mailto:dcrm-l-bounces@lib.byu.edu" target="_blank"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">mailto:dcrm-l-bounces@lib.byu.edu</span></a><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">]
<b>On Behalf Of </b>Moody, Honor M.<br>
<b>Sent:</b> Wednesday, 12 December, 2018 16:11<br>
<b>To:</b> DCRM Users' Group<br>
<b>Subject:</b> Re: [DCRM-L] Fwd: [PCCLIST] New policy regarding limited use of ISBD punctuation in bibliographic records</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt;font-family:"Trebuchet MS",sans-serif">Personally, I’m lamenting the hours of my life wasted in adding ISBD punctuation to pre-AACR2 records and correcting
it when reviewing the records of others.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt;font-family:"Trebuchet MS",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt;font-family:"Trebuchet MS",sans-serif">Honor</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt;font-family:"Trebuchet MS",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>From:</b> DCRM-L <<a href="mailto:dcrm-l-bounces@lib.byu.edu" target="_blank">dcrm-l-bounces@lib.byu.edu</a>>
<b>On Behalf Of </b>Noble, Richard<br>
<b>Sent:</b> Wednesday, December 12, 2018 3:49 PM<br>
<b>To:</b> DCRM Revision Group List <<a href="mailto:dcrm-l@lib.byu.edu" target="_blank">dcrm-l@lib.byu.edu</a>><br>
<b>Subject:</b> [DCRM-L] Fwd: [PCCLIST] New policy regarding limited use of ISBD punctuation in bibliographic records<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt;font-family:"Georgia",serif">My first reaction is to be glad that dcrmb records with original punctuation retained might be a bit less cluttered. Others'
thoughts?</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt;font-family:"Georgia",serif"> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Courier New"">RICHARD NOBLE :: RARE MATERIALS CATALOGUER :: JOHN HAY LIBRARY</span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Courier New"">BROWN UNIVERSITY :: PROVIDENCE, R.I. 02912 :: </span><a href="tel:(401)%20863-1187" target="_blank"><span style="font-family:"Courier New"">401-863-1187</span></a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Courier New""><</span><a href="mailto:RICHARD_NOBLE@BROWN.EDU" target="_blank"><span style="font-family:"Courier New"">Richard_Noble@Br</span></a><a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttp-3A__own.edu%26d%3DDwMFaQ%26c%3DWO-RGvefibhHBZq3fL85hQ%26r%3DgfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk%26m%3DFXC_fIjOY6iqyFFAwuWAU0jWQfwciIVJUSBeiP5SojY%26s%3DnJxQ3Cy7j34ugPEM6j4wwm-dRmuykb9hgUUBDudUStI%26e%3D&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C8ea6d219c921409303d908d661ee47f1%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636804073387083930&sdata=LYPbAuPMs6oYqO132ymYz3c6x%2FgKo0rr7w0osFD8GGY%3D&reserved=0" target="_blank"><span style="font-family:"Courier New"">own.edu</span></a><span style="font-family:"Courier New"">></span><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"> <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">---------- Forwarded message ---------<br>
From: <strong><span style="font-family:"Calibri",sans-serif">Xiaoli Li</span></strong> <<a href="mailto:xlli@ucdavis.edu" target="_blank">xlli@ucdavis.edu</a>><br>
Date: Wed, Dec 12, 2018 at 3:17 PM<br>
Subject: [PCCLIST] New policy regarding limited use of ISBD punctuation in bibliographic records<br>
To: <<a href="mailto:PCCLIST@listserv.loc.gov" target="_blank">PCCLIST@listserv.loc.gov</a>><o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"> <o:p></o:p></p>
<div>
<div id="m_-4469232422746711448m_4684575907581016733divtagdefaultwrapper">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black">PCC colleagues,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black">At its recent</span><a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__www.loc.gov_aba_pcc_documents_PoCo-2D2018_PoCo-2DAgenda-2D2018.pdf%26d%3DDwMFaQ%26c%3DWO-RGvefibhHBZq3fL85hQ%26r%3DgfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk%26m%3DFXC_fIjOY6iqyFFAwuWAU0jWQfwciIVJUSBeiP5SojY%26s%3DPN8uoCAEqrLQrw1EC47rDM-_t_olzeAS5Tprvjdn2VI%26e%3D&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C8ea6d219c921409303d908d661ee47f1%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636804073387093934&sdata=NklBYdUsIfCKVzimgXqw1dGEyGw2TnVA0lnmLnYNWws%3D&reserved=0" target="_blank"><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black;text-decoration:none">
</span><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:#1155CC">meeting</span></a><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black">, the PCC Policy Committee reaffirmed its decision to allow bibliographic records
with limited ISBD punctuation to be treated as full-level PCC copy. This decision comes after reviewing feedback from test participants who evaluated three test sets of records provided by Library of Congress, the National Library of Medicine, and OCLC. For
more information about the test, please read the message below or click </span><a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttp-3A__www.loc.gov_aba_pcc_documents_test-2Drecords-2Dpunctuation.html%26d%3DDwMFaQ%26c%3DWO-RGvefibhHBZq3fL85hQ%26r%3DgfxDZP5m9KyeWhmono1ADELcLUOEQEwGHybTpd5N2Wk%26m%3DFXC_fIjOY6iqyFFAwuWAU0jWQfwciIVJUSBeiP5SojY%26s%3DIvzaL0LZeRpx3M4b5JKuaBJrnYUed2vSt7n866JOyjk%26e%3D&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C8ea6d219c921409303d908d661ee47f1%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636804073387103947&sdata=dSX0HpYVVyEhnDL31O2LzJhhj%2BnUPiqcfj5hbsPJx0k%3D&reserved=0" target="_blank"><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:#1155CC">here</span></a><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black">.
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black">Beginning in spring 2019, PCC libraries will have three options to handle ISBD punctuation when authenticating
new records: </span><o:p></o:p></p>
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;mso-list:l2 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Corbel",sans-serif">Continue current practice
</span><o:p></o:p></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;mso-list:l2 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Corbel",sans-serif">Omit terminal period in any field*; code Leader/18 (Descriptive cataloging form) “i”</span><o:p></o:p></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;mso-list:l2 level1 lfo3;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Corbel",sans-serif">Omit ISBD punctuation between subfields of descriptive fields and omit terminal period in any field*; code Leader/18 (Descriptive cataloging form) “c”
</span><o:p></o:p></li></ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black">* Exception: Terminal periods integral to the data (e.g., recorded as part of abbreviations, initials, etc.) should not be omitted.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black">Options 2 and 3 are optional, not mandatory. However, creating records with limited punctuation is expected
to save time for catalogers, simplify training of new catalogers, make it easier to map data to and from other formats, and allow for an easier transition to linked data or vice versa (e.g., mapping BIBFRAME to MARC). </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black">To facilitate the implementation, PCC will:
</span><o:p></o:p></p>
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;mso-list:l3 level1 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Corbel",sans-serif">Develop and maintain style guidelines for records with limited punctuation;
</span><o:p></o:p></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;mso-list:l3 level1 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Corbel",sans-serif">Provide adequate training resources for catalogers and revise PCC documentation to update policies and include examples with limited punctuation;
</span><o:p></o:p></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;mso-list:l3 level1 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Corbel",sans-serif">Request that LC Network Development and MARC Standards Office and bibliographic utilities revise MARC 21 documentation to include examples with limited punctuation;
</span><o:p></o:p></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;mso-list:l3 level1 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Corbel",sans-serif">Work with bibliographic utilities and other interested parties to develop tools and specifications to automate the process of removal or reinsertion of punctuation;</span><o:p></o:p></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;mso-list:l3 level1 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Corbel",sans-serif">Encourage vendors, bibliographic utilities, etc., to explore functionality to index and display records with limited punctuation as defined by the PCC;
</span><o:p></o:p></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;mso-list:l3 level1 lfo4;vertical-align:baseline">
<span style="font-size:10.0pt;font-family:"Corbel",sans-serif">Encourage vendors, bibliographic utilities, etc., to explore functionality to allow their users to easily add or remove punctuation as needed.
</span><o:p></o:p></li></ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black">The Policy Committee is in the process of developing a detailed implementation plan which will include
the aforementioned style guidelines. I will share more information with you as it becomes available. In the meantime, if you have questions, suggestions, or comments, please feel free to contact me.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black">Sincerely,</span><o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black">Xiaoli Li</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black">PCC Chair</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black">Head of Content Support Services</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Corbel",sans-serif;color:black">UC Davis Library</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</body>
</html>