<div dir="ltr">
<p class="MsoNormal" style="margin:0in 0in 8pt;color:rgb(34,34,34);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;line-height:15.6933px;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:11pt">To return to the matter of abbreviations, perhaps online translation tools have supplanted the purposes of international languages, such as Latin, in our day-to-day.</span><span style="font-size:11pt"> </span><span style="font-size:11pt">An international scholar looking for a resource in my institution's discovery tool clicks the “translate page?” button in their web browser.</span><span style="font-size:11pt"> </span><br></p><p class="MsoNormal" style="margin:0in 0in 8pt;color:rgb(34,34,34);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;line-height:15.6933px;font-size:11pt;font-family:Calibri,sans-serif"><span></span></p><p class="MsoNormal" style="margin:0in 0in 8pt;color:rgb(34,34,34);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;line-height:15.6933px;font-size:11pt;font-family:Calibri,sans-serif">Take the following extent statement an English language of cataloging (040 $b)<span> </span><span class="gmail-gr_ gmail-gr_23 gmail-gr-alert gmail-gr_spell gmail-gr_inline_cards gmail-gr_disable_anim_appear gmail-ContextualSpelling gmail-ins-del gmail-multiReplace" id="gmail-23" style="display:inline;border-bottom:2px solid transparent;background-repeat:no-repeat;color:inherit;font-size:inherit">dcrmb</span><span> </span>record:<span></span></p><p class="MsoNormal" style="margin:0in 0in 8pt;color:rgb(34,34,34);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;line-height:15.6933px;font-size:11pt;font-family:Calibri,sans-serif">[14], 240 (i.e. 220), 64, [28] p. ; ǂc 21 cm. (4to)<span></span></p><p class="MsoNormal" style="margin:0in 0in 8pt;color:rgb(34,34,34);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;line-height:15.6933px;font-size:11pt;font-family:Calibri,sans-serif">the web browser translates:<span></span></p><p class="MsoNormal" style="margin:0in 0in 8pt;color:rgb(34,34,34);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;line-height:15.6933px;font-size:11pt;font-family:Calibri,sans-serif">[14], 240 (<span class="gmail-gr_ gmail-gr_24 gmail-gr-alert gmail-gr_spell gmail-gr_inline_cards gmail-gr_disable_anim_appear gmail-ContextualSpelling gmail-ins-del gmail-multiReplace" id="gmail-24" style="display:inline;border-bottom:2px solid transparent;background-repeat:no-repeat;color:inherit;font-size:inherit">tj</span>. 220), 64, [28] str. ; 21 cm. (4to)<span></span></p><p class="MsoNormal" style="margin:0in 0in 8pt;color:rgb(34,34,34);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;line-height:15.6933px;font-size:11pt;font-family:Calibri,sans-serif">I gather that “<span class="gmail-gr_ gmail-gr_25 gmail-gr-alert gmail-gr_spell gmail-gr_inline_cards gmail-gr_disable_anim_appear gmail-ContextualSpelling" id="gmail-25" style="display:inline;border-bottom:2px solid transparent;background-repeat:no-repeat;color:inherit;font-size:inherit">tj</span>” is a lexical equivalent to “i.e.”<span> <span> </span></span>and that the online translation tool knows this.<span> <span> </span></span>Replace the “i.e.” with the phrase “that is” and the results are the same (curiously, it reverts the phrase “that is” back to the abbreviation “<span class="gmail-gr_ gmail-gr_27 gmail-gr-alert gmail-gr_spell gmail-gr_inline_cards gmail-gr_disable_anim_appear gmail-ContextualSpelling" id="gmail-27" style="display:inline;border-bottom:2px solid transparent;background-repeat:no-repeat;color:inherit;font-size:inherit">tj</span>”).<span> <span> </span></span>For these online translation tools to work in the best capacity, consistency is key which leaves me to think that a departure from the general RDA rules might be detrimental in the long term.<span> <span> </span></span>However, one might make the case that a reliance on online translation tools might be detrimental in the long term as well. ;)<span> <span> </span></span>It is interesting to note that the same online translation tool doesn’t know how to make heads or tails of the abbreviation “sic”.<span></span></p><p class="MsoNormal" style="margin:0in 0in 8pt;color:rgb(34,34,34);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;line-height:15.6933px;font-size:11pt;font-family:Calibri,sans-serif">As much as I like the use of brackets for unnumbered pages (and personally, dislike having to type those words so often in RDA).<span> <span> </span></span>I wonder how screen readers react to the brackets. I’m not an expert by any means in web accessibility, this is more of a personal curiosity than anything and<span> </span>I do prefer the brackets.<span></span></p><p class="MsoNormal" style="margin:0in 0in 8pt;color:rgb(34,34,34);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;line-height:15.6933px;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:11pt">kalan </span></p><p class="MsoNormal" style="margin:0in 0in 8pt;color:rgb(34,34,34);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;line-height:15.6933px;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:11pt">p.s. After many years a list-lurker, this is my first post to DCRM-list. My hope<span> </span><span class="gmail-gr_ gmail-gr_968 gmail-gr-alert gmail-gr_gramm gmail-gr_inline_cards gmail-gr_run_anim gmail-Grammar gmail-replaceWithoutSep" id="gmail-968" style="display:inline;border-bottom:2px solid transparent;background-repeat:no-repeat;color:inherit;font-size:inherit">it</span><span> </span>was well conveyed and constructed. </span></p>
<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 4, 2018 at 9:29 AM, Person, Mary <span dir="ltr"><<a href="mailto:person@law.harvard.edu" target="_blank">person@law.harvard.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="blue" vlink="purple">
<div class="m_-9026906190222170749WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style","serif";color:#1f4e79">I agree with Richard on this. When looking at a catalog record and encountering
something that could either be a catalogers’ typo OR a faithful transcription of a title page (or whatever) that question (“Really?”) does come immediately to mind and it’s so helpful to have [sic] right there and not buried in a note, which may not even be
noticed. <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style","serif";color:#1f4e79"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style","serif";color:#1f4e79">As for “i.e.” I’m one who uses it in every day conversation so am probably hopelessly
mired there. <u></u><u></u></span></p><span class="">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style","serif";color:#1f4e79"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style","serif";color:#1f4e79">Mary<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style","serif";color:#1f4e79"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style","serif";color:#1f4e79">Mary Person<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style","serif";color:#1f4e79">Rare Books Cataloger/Reference Librarian<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style","serif";color:#1f4e79">Historical & Special Collections<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style","serif";color:#1f4e79">Harvard Law School Library<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style","serif";color:#1f4e79"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style","serif";color:#1f4e79"><a href="mailto:person@law.harvard.edu" target="_blank"><span style="color:#00007f">person@law.harvard.edu</span></a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style","serif";color:#1f4e79"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
</span><p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> 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>Noble, Richard<br>
<b>Sent:</b> Wednesday, April 04, 2018 8:53 AM<br>
<b>To:</b> DCRM Users' Group</span></p><div><div class="h5"><br>
<b>Subject:</b> Re: [DCRM-L] RBMS PS review Q4: Extent of text<u></u><u></u></div></div><p></p><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Georgia","serif"">I quite agree with William Hale on this one. Interpolated "[sic]" is an immediate answer to the question "Really? Is this not a transcription error?"--a question that
is either left unanswered, raising real questions about discrepancies among copies, or answered only in a note that must be found by inspection of the record. It is equivalent to "[thus]", but that is not an established convention, and thus not as immediately
informative. There's also "[!]"--but that seems unduly judgemental.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Georgia","serif"">I suppose "i.e." is a lost cause, despite the fact that just about everyone likely to be interested in a rare book record will be accustomed to it; I still feel a
twinge of reader's whiplash in response to "[that is ...]", as if the statement were being read aloud to me: it gets in the way of comprehending the statement as a whole. (Then again, I'm a cataloger, so I talk to myself constantly...).<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Georgia","serif"">And yes, the extent statement
<i>must</i> admit editorial intervention to convey correct information, which can always be supported by an explanatory note, or even a formal collational formula/pagination statement that exhibits some analytical understanding of the physical book.<u></u><u></u></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Courier New"">RICHARD NOBLE :: RARE MATERIALS CATALOGUER :: JOHN HAY LIBRARY</span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-family:"Courier New"">BROWN UNIVERSITY :: PROVIDENCE, R.I. 02912 :: 401-863-1187</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><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><span style="font-family:"Courier New""><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__own.edu&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=EkkQFOGUCtF2osSJj7hvtyM31K6sxQSo34Z9RQpCmDw&m=lkD4cSrM8biUZ_9N6CcLjV6L6kYujytS4sRWAfyGb_8&s=DOsN_0FQHynMydZpJtWx_leN5eejojvKBbXuWMwRPd8&e=" target="_blank">own.edu</a>></span><u></u><u></u></p>
</div>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Wed, Apr 4, 2018 at 5:35 AM, William Hale <<a href="mailto:wah26@cam.ac.uk" target="_blank">wah26@cam.ac.uk</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1f497d">I don’t think I have ever used [sic] in an extent statement, though I do employ it occasionally in transcribed fields. I use [i.e.] fairly
often when printed pagination is incorrect, as it often is in early materials. Not to use it or an equivalent in such cases means that the extent statement will not represent the actual extent of the item, which is highly misleading. You can of course put
the actual extent in a note, but where does that leave the “granularity of RDA”? And it is making key information about the item less easy to find, which is the last thing we should be doing.</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Arial","sans-serif";color:#1f497d">--</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Arial","sans-serif";color:#1f497d">William Hale.<br>
<br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.lib.cam.ac.uk_deptserv_rarebooks_index.html&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=EkkQFOGUCtF2osSJj7hvtyM31K6sxQSo34Z9RQpCmDw&m=lkD4cSrM8biUZ_9N6CcLjV6L6kYujytS4sRWAfyGb_8&s=GLfwz6epBFLkIFOlib8w_2E-IYxlXvdWcO_7IjRR9vM&e=" target="_blank"><span style="color:#1f497d;text-decoration:none">Rare
Books and Early Manuscripts Department,<br>
Cambridge University Library,<br>
West Road, Cambridge, CB3 9DR.</span></a><br>
<br>
Telephone: <a href="tel:+44%201223%20333122" target="_blank"><span style="color:#1f497d;text-decoration:none">(+44) (0)1223 333122</span></a><br>
Email: <a href="mailto:William.Hale@lib.cam.ac.uk" target="_blank"><span style="color:#1f497d;text-decoration:none">William.Hale@lib.cam.ac.uk</span></a></span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-GB"><u></u> <u></u></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></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>Robert Maxwell<br>
<b>Sent:</b> 04 April 2018 00:25<span lang="EN-GB"><u></u><u></u></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"><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> Re: [DCRM-L] RBMS PS review Q4: Extent of text<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB"> <u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Actually, I think the RDA solution is not to use “sic” at all or any equivalent, just to copy exactly what is there with no “on the spot” explanation
and then explaining later in a note, if thought necessary. I’m not sure now often “sic” would be used in an extent statement—maybe if the numeral being recorded is known to be incorrect?—but I think RDA’s solution would be to record what’s there and explain
in a note if necessary. Which seems like a pretty “rare materials cataloging” way of doing things, to represent the item exactly as it represents itself.</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Bob
</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1f497d">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><span lang="EN-GB"><u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></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 <<a href="mailto:dcrm-l-bounces@lib.byu.edu" target="_blank">dcrm-l-bounces@lib.byu.edu</a>>
<b>On Behalf Of </b>Margaret F. Nichols<br>
<b>Sent:</b> Tuesday, April 3, 2018 3:37 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> Re: [DCRM-L] RBMS PS review Q4: Extent of text<span lang="EN-GB"><u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"> <span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">I’m a bit skeptical of the idea that an abbreviation of a Latin phrase is going to be easier for non-English users to understand than an English phrase
is, given that the lingua franca these days tends to be English rather than Latin. I do agree, though, that it’s hard to come up with a concise English equivalent for “sic.”</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Two cents,</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Margaret</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">______________________________<wbr>_</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Margaret F. Nichols</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Rare Materials Cataloging Coordinator</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Division of Rare and Manuscript Collections</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">2B Kroch Library</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Cornell University
</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Ithaca, NY 14853-5302</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Tel. (607) 255-9667
</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></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 <<a href="mailto:dcrm-l-bounces@lib.byu.edu" target="_blank">dcrm-l-bounces@lib.byu.edu</a>>
<b>On Behalf Of </b>Lapka, Francis<br>
<b>Sent:</b> Tuesday, April 03, 2018 12:59 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> Re: [DCRM-L] RBMS PS review Q4: Extent of text<span lang="EN-GB"><u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"> <span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif";color:#1f497d">I’m pleased to see all the useful input.</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif";color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif";color:#1f497d">On the matter of “i.e.” and “sic”: Would it be fair to say that the users for a given record describing a rare item are
likely to be more linguistically diverse, compared to the audiences for other resources described with RDA? If so, is that a sufficient rare materials reason for deviation – assuming “i.e.” is easier to understand than “that is” for the non-English audience
? The same linguistic neutrality might be evoked to justify the use of square brackets instead of “unnumbered.” If the premise is malarkey, the case for “i.e.” in this context is wobbly.</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif";color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif";color:#1f497d">Francis</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif";color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif";color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><b>From:</b> DCRM-L [<a href="mailto:dcrm-l-bounces@lib.byu.edu" target="_blank">mailto:dcrm-l-bounces@lib.<wbr>byu.edu</a>]
<b>On Behalf Of </b>Kathie Coblentz<br>
<b>Sent:</b> Tuesday, April 03, 2018 12:48 PM<br>
<b>To:</b> <a href="mailto:dcrm-l@lib.byu.edu" target="_blank">dcrm-l@lib.byu.edu</a><br>
<b>Subject:</b> Re: [DCRM-L] RBMS PS review Q4: Extent of text<span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"> <span lang="EN-GB"><u></u><u></u></span></p>
<div>
<p class="MsoNormal">I completely agree with Bob Maxwell on "i.e.," and I have no problems using "that is" instead. (It never ceases to surprise me how many educated people use "i.e." when they mean
"e.g.," and vice versa. Or "the other way around," I suppose I should say.)<span lang="EN-GB"><u></u><u></u></span></p>
<div>
<p class="MsoNormal"> <span lang="EN-GB"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal">However, "sic" is awfully hard to replace with an English word or concise phrase. Of course RDA gospel calls for omitting it altogether in transcribing "an element as it appears
on the source," and I can go along with that, as long as there is a note (and/or other title entry) "correcting the inaccuracy," though in the case of rare materials, I would not limit that to "if considered important for identification or access." <span lang="EN-GB"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"> <span lang="EN-GB"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal">But in quoted material from other sources, there is no other good way to call attention to typos, factual errors or other unexpected variations in the data. <span lang="EN-GB"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"> <span lang="EN-GB"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal">This doesn't really apply to the discussion of Extent of text, since I can't imagine using "sic" there for any reason, but it might be worth reflecting on for the rest of the catalog
record.<span lang="EN-GB"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"> <span lang="EN-GB"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal">Oh, and for what it's worth: for rare materials, I'm completely on board with using the square brackets convention instead of "unnumbered," for the sake of everyone's sanity. I
wish RDA would drop "unnumbered" altogether. Anyone who cares about the distinction between pages with page numbers on them and pages with no page numbers on them, understands the bracketing convention. As for the rest, how many noncatalogers even know what
"unnumbered pages" means?<span lang="EN-GB"><u></u><u></u></span></p>
<div>
<p class="MsoNormal"><br clear="all">
<span lang="EN-GB"><u></u><u></u></span></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Trebuchet MS","sans-serif"">------------------------------<wbr>--------------------------</span><span lang="EN-GB"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif"">Kathie Coblentz |
<span style="color:#cc0000">The New York Public Library</span></span></b><span lang="EN-GB"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><i><span style="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif"">Rare Materials Cataloger</span></i><span lang="EN-GB"><u></u><u></u></span></p>
</div>
</div>
<div>
<p style="margin-bottom:0in;margin-bottom:.0001pt"><span style="font-size:9.5pt;font-family:"Trebuchet MS","sans-serif"">Special Collections/Special Formats Processing</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif"">Stephen A. Schwarzman Building<br>
</span></b><span style="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif""><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3D476-2B5th-2BAvenue-2C-2BRoom-2B313-2C-2BNew-2BYork-2C-2BNY-2B10018-26entry-3Dgmail-26source-3Dg&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=EkkQFOGUCtF2osSJj7hvtyM31K6sxQSo34Z9RQpCmDw&m=lkD4cSrM8biUZ_9N6CcLjV6L6kYujytS4sRWAfyGb_8&s=nOmpcwg3Heecmlja3OjPBKpSncqkX174Clge38F_5I8&e=" target="_blank">476
5th Avenue, Room 313, New York, NY 10018</a></span><span lang="EN-GB"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><a href="mailto:kathiecoblentz@nypl.org" target="_blank"><span style="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#1155cc">kathiecoblentz@nypl.org</span></a><span lang="EN-GB"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"> <span lang="EN-GB"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal">My opinions, not NYPL's<span lang="EN-GB"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"> <span lang="EN-GB"><u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"> <span lang="EN-GB"><u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"> <span lang="EN-GB"><u></u><u></u></span></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">
<p class="MsoNormal"><br>
<br>
---------- Forwarded message ----------<br>
From: Robert Maxwell <<a href="mailto:robert_maxwell@byu.edu" target="_blank">robert_maxwell@byu.edu</a>><br>
To: "DCRM Users' Group" <<a href="mailto:dcrm-l@lib.byu.edu" target="_blank">dcrm-l@lib.byu.edu</a>><br>
Cc: <br>
Bcc: <br>
Date: Tue, 3 Apr 2018 16:05:50 +0000<br>
Subject: Re: [DCRM-L] RBMS PS review Q4: Extent of text<span lang="EN-GB"><u></u><u></u></span></p>
<div>
<div>
<p class="MsoNormal"><span style="color:#1f497d">I can just about accept the argument that there is a rare reason for departing from RDA extent instructions in the matter of bracketing vs. “unnumbered”—rare
book extent statements are much more likely than other types of extent statements to need to record unnumbered sequences.
</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">However, I do not accept the argument that rare extent statements should continue to use “i.e.” and “sic” when the rest of RDA practice does not. In
the first place, if 0.4.3.7 justified this it would have justified it for RDA as a whole—the rare materials community is not the only one that “commonly used” these forms,
<i>all</i> communities commonly used these forms before RDA came along and this was not thought to be a good reason to refuse to go along with the new instruction. So that argument simply won’t wash, for me at least. There is no compelling rare materials reason
in those cases why the rare rules should depart from the general RDA rules.</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d">Bob</span><span lang="EN-GB"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1f497d">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>
<a href="tel:(801)%20422-5568" target="_blank">(801)422-5568</a></span><span lang="EN-GB"><u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="color:#1f497d"> </span><span lang="EN-GB"><u></u><u></u></span></p>
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"> <span lang="EN-GB"><u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div></div></div>
</div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><br style="color:rgb(136,136,136)"><span style="color:rgb(136,136,136)">Kalan Knudson Davis, MLIS</span><div><span style="color:rgb(136,136,136)">Data Management & Access (DMA)</span><br style="color:rgb(136,136,136)"><span style="color:rgb(136,136,136)">University of Minnesota Libraries </span></div><div><span style="color:rgb(136,136,136)">160 Wilson Library </span>(612) 301-9521<span style="color:rgb(136,136,136)"> PH (note new number)</span></div><div><span style="color:rgb(136,136,136)">309 19th Ave. S. </span>(218) 779-9009 <span style="color:rgb(136,136,136);font-size:12.8000001907349px">Cell</span></div><div><span style="font-size:12.8000001907349px;color:rgb(136,136,136)">Minneapolis, MN 55455 </span><a href="mailto:kkdavis@umn.edu" style="font-size:12.8000001907349px" target="_blank">kkdavis@umn.edu</a></div></div></div></div></div></div></div></div></div></div></div></div></div>
</div>