<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Dear Colleagues,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
In response to your concerns regarding transcription and data provenance raised by the option to add diacritical marks (<a href="https://bsc.rbms.info/DCRMR/general-rules/Transcription/#0412-letters-and-diacritical-marks" title="https://bsc.rbms.info/DCRMR/general-rules/Transcription/#0412-letters-and-diacritical-marks">0.4.12.2</a>),
the RBMS RDA Editorial Group has decided to remove this optional instruction from DCRMR. We will remove it in the coming weeks before the official publication of the standard.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
As both Deborah and Bob noted, the discussion around this instruction touches on broader issues of data provenance, which may be recorded using new guidelines in Official RDA. The Editorial Group plans to revisit these broader issues and provide guidance in
a future iteration of DCRMR.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
We are grateful for the feedback from our community regarding DCRMR and rare materials cataloging. Your contributions to discussions raised in threads like this one go a long way toward making DCRMR a clear and useful standard for all who use it.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Best,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Jessica Grzegorski, co-editor of DCRMR</div>
<div>
<div id="appendonsend"></div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> DCRM-L <dcrm-l-bounces@lib.byu.edu> on behalf of Robert Maxwell <robert_maxwell@byu.edu><br>
<b>Sent:</b> Thursday, December 9, 2021 11:47 AM<br>
<b>To:</b> DCRM Users' Group <dcrm-l@lib.byu.edu><br>
<b>Subject:</b> Re: [DCRM-L] Diacritic transcription in DCRMR</font>
<div> </div>
</div>
<div lang="EN-US" style="word-wrap:break-word">
<div class="x_WordSection1">
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
What Deborah suggests is, I think, right in line with “new” RDA’s guidelines and possibilities for recording data provenance information. See Guidance >
<a href="https://access.rdatoolkit.org/Guidance/GuidanceById/5aa610aa-92b9-482e-80ab-af983151e311">
Data provenance</a> in the “official” RDA. Of all communities that would want to make use of (and maybe even expand on) these new data provenance guidelines, I would think the rare materials cataloging community would be right at the front of the line.</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
To quote from RDA: “Data provenance provides information about the metadata that is recorded in an element or set of elements.” Transcription options followed would be a good example of information about the metadata.</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
Bob</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<div>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:10.0pt">Robert L. Maxwell<br>
Ancient Languages and Special Collections Librarian<br>
6728 Harold B. Lee Library<br>
Brigham Young University<br>
Provo, UT 84602<br>
(801)422-5568</span></p>
</div>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
<b>From:</b> DCRM-L <dcrm-l-bounces@lib.byu.edu> <b>On Behalf Of </b>Deborah J. Leslie<br>
<b>Sent:</b> Thursday, December 9, 2021 9:05 AM<br>
<b>To:</b> DCRM Users' Group <dcrm-l@lib.byu.edu><br>
<b>Subject:</b> Re: [DCRM-L] Diacritic transcription in DCRMR</p>
</div>
</div>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:12.0pt; font-family:"Georgia",serif; color:#1F497D">This option was added during early stages of the of what we were then calling DCRM2, on analogy with ijuv. If memory serves, it was along the lines of "well, if we do this with IJUV,
shouldn't we do it with diacritics too?" Conceptual rather than practical or experiential grounds. Bob makes a really good case for removing the option.</span></p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:12.0pt; font-family:"Georgia",serif; color:#1F497D"> </span></p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:12.0pt; font-family:"Georgia",serif; color:#1F497D">The method of transcription is really significant in how far it is used to identify variants and the like, and is even more significant with original vs normalized punctuation. I would
like to see it become a required note in every record identifying it. It may seem tedious, but DCRM(G) requires that every record identify the source of the title, and serials cataloging gives a "Description based on" note. If we were to go this route, this
community could come up with normative wording that is brief but descriptive enough to alert catalog users to the parameters of transcription.
</span></p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:12.0pt; font-family:"Georgia",serif; color:#1F497D"> </span></p>
<div>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="color:#1F497D">______________________________</span></p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:10.0pt; color:#5E327C">Deborah J. Leslie, MA, MLS | Senior Cataloger | Folger Shakespeare Library | 201 East Capitol St., SE, Washington, DC 20003 |
<a href="mailto:djleslie@folger.edu">djleslie@folger.edu</a> | <a href="http://www.folger.edu">
www.folger.edu</a></span><span style="font-size:10.0pt; color:#1F497D"> </span><span style="font-size:10.0pt; color:#5E327C">| Opinions her own</span><span style="font-size:10.0pt; color:#1F497D"></span></p>
</div>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:12.0pt; font-family:"Georgia",serif; color:#1F497D"> </span></p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
<b>From:</b> DCRM-L <<a href="mailto:dcrm-l-bounces@lib.byu.edu">dcrm-l-bounces@lib.byu.edu</a>>
<b>On Behalf Of </b>Jessica Janecki<br>
<b>Sent:</b> Thursday, December 9, 2021 10:21<br>
<b>To:</b> DCRM Users' Group <<a href="mailto:dcrm-l@lib.byu.edu">dcrm-l@lib.byu.edu</a>><br>
<b>Subject:</b> Re: [DCRM-L] Diacritic transcription in DCRMR</p>
</div>
</div>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
I agree Robert, it is so important to know what was actually printed on the piece!
</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
I also feel that the easier to interpret one can make a rule, the better. Case conversion is fraught enough, optionally inserted diacritics is really too much.
</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
Jessica Janecki</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
<b>From:</b> DCRM-L <<a href="mailto:dcrm-l-bounces@lib.byu.edu">dcrm-l-bounces@lib.byu.edu</a>>
<b>On Behalf Of </b>Robert O. Steele<br>
<b>Sent:</b> Thursday, December 9, 2021 10:06 AM<br>
<b>To:</b> <a href="mailto:dcrm-l@lib.byu.edu">dcrm-l@lib.byu.edu</a><br>
<b>Subject:</b> [DCRM-L] Diacritic transcription in DCRMR</p>
</div>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<div>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;margin-bottom:8.0pt; line-height:105%">
Hello, </p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;margin-bottom:8.0pt; line-height:105%">
I note with some surprise that the draft edition of DCRMR includes the option of adding diacritics where they are not present on the piece at hand. Granted, this is in the limited situation of converting from upper to lower case, but I think it introduces potential
confusion for researchers trying to distinguish between states or issues… or even editions, in the case of anonymous and clandestine but oft-reprinted works, such as some French Revolutionary pamphlets.
</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;margin-bottom:8.0pt; line-height:105%">
I have attached the detailed response I posted as feedback on the Public Review of DCRMR site. Please feel free to comment.</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;margin-bottom:8.0pt; line-height:105%">
The main points: 1) Since the rule is optional, I will not know which rule you are applying, so I will not know if what you saw is really different from what I see on the piece in hand. 2) The rule only applies to case conversion, so in French EDITION can be
édition, but not Édition. Why? 3) The “pattern of the text” in early modern spelling can be difficult to discern without some advanced knowledge, so I suspect anyone applying the rule will merely add diacritics where they would be expected in modern usage,
which in my opinion is the equivalent of correcting spelling rather than using [sic].</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;margin-bottom:8.0pt; line-height:105%">
Thanks for any feedback you might have.</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;line-height:105%">
Robert O. Steele</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;line-height:105%">
Cataloging Librarian</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;line-height:105%">
Jacob Burns Law Library</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;line-height:105%">
George Washington University</p>
<p class="x_MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;margin-bottom:8.0pt; line-height:105%">
</p>
</div>
</div>
</div>
</div>
<p><br>
<span style="font-size: 12px;"><strong>Jessica Grzegorski </strong><br>
<em>Principal Cataloging Librarian</em> <br>
(312) 255-3650 <br>
Newberry Library <br>
<a href="https://www.newberry.org/">www.newberry.org</a> </span><span><br>
</span><br>
<span style="font-size: 11px;">Located near the confluence of several waterways, the Newberry Library sits on land that intersects with the aboriginal homelands of several tribal nations: the Council of the Three Fires: the Potawatomi, Odawa, and Ojibwe Nations;
the Illinois Confederacy: the Peoria and Kaskaskia Nations; and the Myaamia, Wea, Thakiwaki, and Meskwaki Nations. The Ho-Chunk, Menominee, Kiikaapoi, and Mascouten Nations also call the region of northeast Illinois home. Indigenous people continue to live
in this area and celebrate their traditional teachings and lifeways. As a Chicago institution, it is the Newberry’s responsibility to acknowledge this historical context and build reciprocal relationships with the tribal nations on whose lands we are situated. </span><span><br>
<br>
Help keep the Newberry free and open to all. <a href="https://www.newberry.org/give" target="_blank" title="https://www.newberry.org/give">
Learn</a> how you can support the Newberry. <br>
<br>
</span><span style="font-size: 11px;">CONFIDENTIALITY NOTICE: This communication is confidential, may be privileged and is meant only for the intended recipient. If you are not the intended recipient, please notify the sender ASAP and delete this message from
your system.</span></p>
</body>
</html>