<div dir="ltr"><div class="gmail_default" style="font-family:georgia,serif;font-size:small">Ultimately we need to make a strict distinction between transcription--as conscious optical character recognition--and data interpretation. We have far too many fields in which we run up against the limitations and confusions of trying to do both things at once. I suppose image matching might be the way forward, since that's what transcription is aiming for, by way of crude intermediate translation; as in the too many cases I've seen, in the latest discussions, of transcriptions that cannot be read unambiguously back to the source.</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><font face="'courier new', monospace">RICHARD NOBLE :: RARE MATERIALS CATALOGUER :: JOHN HAY LIBRARY</font><div><font face="'courier new', monospace">BROWN UNIVERSITY :: PROVIDENCE, R.I. 02912 :: 401-863-1187</font></div><div><span style="font-family:'courier new',monospace"><</span><a href="mailto:RICHARD_NOBLE@BROWN.EDU" style="font-family:'courier new',monospace" target="_blank">Richard_Noble@Br</a><span style="font-family:'courier new',monospace"><a href="http://own.edu" target="_blank">own.edu</a></span><span style="font-family:'courier new',monospace">></span></div></div></div>
<br><div class="gmail_quote">On Mon, Jan 8, 2018 at 2:08 PM, Gillis, Jane <span dir="ltr"><<a href="mailto:jane.gillis@yale.edu" target="_blank">jane.gillis@yale.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="m_-6667364167588896369WordSection1">
<p class="MsoNormal">I think the alternatives in the RBMS instructions are what is needed for rare materials cataloging. When we find something other than MARC21 in which to do cataloging and there is a way to say the this phrase is transcribed, this phrase
is recorded, this phrase (or word? Or number?) is a corrected one, then we might be able to follow RDA. They have made it more difficult for us by instructing us to input all punctuation, but then also instructing us that we can just add punctuation to make
something clear. This makes using square brackets and ellipses unreliable. Also, if there is a typo in the title, one can always make a 246 for the corrected title. This is not possible for some other fields, like the 362 or 588. It is misleading cataloging.
One recent serial I cataloged had the “Description based on” issue as XIII, instead of VIII. It is more helpful to put XIII [i.e. VIII] than to make a note that is separated from the 588.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">This is one of the problems with RDA itself. It is meant to be used in a linked data environment, which does not exist yet. Not only linked date but a much more robust cataloging system with corresponding OPAC in which you could say “this
is transcribed” and “this is recorded/corrected”. Perhaps something like Google translate where you can hover your mouse over the translation and the original appears. I fear that RDA will be changing every couple of years, waiting for a cataloging system/OPAC
that will actually take advantage of linked data and what RDA is attempting to do.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt">Jane Gillis<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">Rare Book Cataloger<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">Beinecke Rare Book and Manuscript Library<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">Yale University Library<u></u><u></u></span></p>
<p class="MsoNormal"><a href="mailto:jane.gillis@yale.edu" target="_blank"><span style="font-size:10.0pt;color:blue">jane.gillis@yale.edu</span></a><span style="font-size:10.0pt"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">phone: <a href="tel:(203)%20432-2633" value="+12034322633" target="_blank">203-432-2633</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt">fax: <a href="tel:(203)%20432-4047" value="+12034324047" target="_blank">203-432-4047</a><u></u><u></u></span></p>
</div><span class="">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> DCRM-L [mailto:<a href="mailto:dcrm-l-bounces@lib.byu.edu" target="_blank">dcrm-l-bounces@lib.<wbr>byu.edu</a>] <b>On Behalf Of
</b>Mascaro, Michelle<br>
<b>Sent:</b> Wednesday, December 13, 2017 2:22 PM<br>
<b>To:</b> DCRM Users' Group <<a href="mailto:dcrm-l@lib.byu.edu" target="_blank">dcrm-l@lib.byu.edu</a>><br>
<b>Subject:</b> [DCRM-L] RBMS PS Review Q2.5: Transcription of Inaccuracies<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</span><p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-family:"Georgia",serif;color:black">As a follow-up to the initial discussion topics on transcription that I posted last week, I would like to solicit some discussion on the
transcription of inaccuracies (RDA 1.7.9). Under RDA, inaccuracies and misprints on the source are transcribed as, and, if considered important, the cataloger may make a note, correcting the inaccuracy. The AACR2/DCRM practice of using interpolations, such
as sic and i.e., to note/correct the inaccuracy within the transcribed element is not permitted. The rationale being since transcribed fields are manifestation level elements, their purpose is to identify how the manifestation represents itself and corrections
for access, etc., belong elsewhere.<u></u><u></u></span></p><div><div class="h5">
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-family:"Georgia",serif;color:black"><u></u> <u></u></span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-family:"Georgia",serif;color:black">Whether there is a rare materials reason for the RBMS Policy Statements to vary from RDA and continue to follow the AACR2/DCRM practice
of correcting transcribed inaccuracies via interpolation, prompted several discussions within the task force. Some of the arguments made for continuing interpolation included that inaccuracies are not uncommon in early print materials, and it is important
for our users to be able to readily identify that the error is on the piece itself and not introduced by the cataloger. Members of the task force were split on this issue, and whether the practice of interpolation was too much of a departure from RDA proper
to be justified.<u></u><u></u></span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-family:"Georgia",serif;color:black"><u></u> <u></u></span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-family:"Georgia",serif;color:black">As a compromise, in the current draft, the default approach is to follow RDA (correct inaccuracies in notes) with an alternative to provide
correction via sic. or i.e. within the transcription for catalogers interested in doing so. (The argument for using Latin abbreviations is that they are common usage in the rare materials bibliography and known to our users (RDA principle 0.4.3.7)). One concern
that has since been raised is by allowing two options, the transcription for the same resource would be different depending on if the cataloger is electing to follow the alternative or not.<u></u><u></u></span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-family:"Georgia",serif;color:black"><u></u> <u></u></span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-family:"Georgia",serif;color:black">Since this is one of the most significant variations from RDA proposed in the RBMS PS, I would like to extend this discussion on how the
PS should handle the transcription of inaccuracies to the broader community and solicit your thoughts. Comments to the questions I posed last week are still encouraged as well.<u></u><u></u></span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-family:"Georgia",serif;color:black"><u></u> <u></u></span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-family:"Georgia",serif;color:black">Also, attached is an updated version of the RBMS PS to 1.7, with some improved examples from the examples group. With the holidays approaching,
this will be the last discussion question I post before the new year. <u></u><u></u></span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-family:"Georgia",serif;color:black"><u></u> <u></u></span></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-family:"Georgia",serif;color:black">Best,
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#002060">Michelle Mascaro<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif">Head, Special Collections Metadata<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif">University of California, San Diego
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri Light",sans-serif">(</span><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif"><a href="tel:(858)%20534-6759" value="+18585346759" target="_blank">858) 534-6759</a>
<u></u><u></u></span></p>
<p class="MsoNormal"><a href="mailto:mmascaro@ucsd.edu" target="_blank"><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif">mmascaro@ucsd.edu</span></a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div></div></div>
</div>
</blockquote></div><br></div>