<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:"Calibri Light";
panose-1:2 15 3 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:"Bookman Old Style";
panose-1:2 5 6 4 5 5 5 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma",sans-serif;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Bookman Old Style",serif;
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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-size:11.0pt;font-family:"Calibri",sans-serif">I am in favor of retaining the interpolation of inaccuracies, mostly because in the grand world of shared metadata, the explanatory note is not always shared. Whether we like
it or not, the transcription fields get shot out into the metadata web, sometimes without context (and certainly without cataloging code attached). Something can easily get misrepresented out there and it takes a very dedicated and skilled person to drill
back down through the metadata threads to see what’s ACTUALLY going on. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Dorothy Auyong<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Principal Catalog Librarian/Archivist<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Acquisitions, Cataloging & Metadata Services<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Henry E. Huntington Library<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><a href="mailto:dauyong@huntington.org"><span style="color:#0563C1">dauyong@huntington.org</span></a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<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:dcrm-l-bounces@lib.byu.edu]
<b>On Behalf Of </b>Will Evans<br>
<b>Sent:</b> Wednesday, December 20, 2017 1:12 PM<br>
<b>To:</b> DCRM Users' Group <dcrm-l@lib.byu.edu><br>
<b>Subject:</b> Re: [DCRM-L] RBMS PS Review Q2.5: Transcription of Inaccuracies<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style",serif">I too am in favor of retaining the interpolation of inaccuracies in titles for reasons articulated by Helena and those outlined in the initial post--</span><span style="font-size:11.0pt;font-family:"Georgia",serif">
inaccuracies are not uncommon in early print materials, and it is important for our users (including other catalogers!) to be able to readily identify that the error is on the piece itself and not introduced by the cataloger. Additionally, I’m troubled by
the language in the RDA rule: “<u>if considered important</u>, the cataloger may make a note, correcting the inaccuracy.” Haven’t our users always considered it important to flag these inaccuracies.
</span><span style="font-size:11.0pt;font-family:"Bookman Old Style",serif">Nevertheless, should the practice of interpolation of inaccuracies in titles is to be abandoned, I would at least like to see a RBMS PS stating that a note correcting the inaccuracy
be mandatory. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style",serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style",serif">I would not, however, be in favor of the proposed comprise. As others have noted, the inconsistent approach across cataloging agencies would likely lead to confusion.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style",serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style",serif">Best,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style",serif">Will</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style",serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><u><span style="font-size:9.0pt;font-family:"Bookman Old Style",serif">~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</span></u></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Bookman Old Style",serif">Will Evans</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Bookman Old Style",serif">National Endowment for the Humanities
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Bookman Old Style",serif">Chief Librarian in Charge of Technical Services</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Bookman Old Style",serif">Library of the Boston Athenaeum</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Bookman Old Style",serif">10 1/2 Beacon Street</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Bookman Old Style",serif">Boston, MA 02108</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Bookman Old Style",serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Bookman Old Style",serif">Tel: 617-227-0270 ext. 243</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Bookman Old Style",serif">Fax: 617-227-5266 </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Bookman Old Style",serif;color:#1F497D"><a href="http://www.bostonathenaeum.org/">www.bostonathenaeum.org</a></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style",serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style",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"><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 [mailto:<a href="mailto:dcrm-l-bounces@lib.byu.edu">dcrm-l-bounces@lib.byu.edu</a>]
<b>On Behalf Of </b>Zinkham, Helena<br>
<b>Sent:</b> Tuesday, December 19, 2017 6:46 PM<br>
<b>To:</b> 'DCRM Users' Group'<br>
<b>Subject:</b> Re: [DCRM-L] RBMS PS Review Q2.5: Transcription of Inaccuracies</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I’d like to see the option remain to flag inaccuracies in titles.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">In preparing DCRM (G), we debated a long while about when text on a picture should be transcribed as a title and when to consider textual information to be a
subject annotation or identification note. Conclusion: Transcribe text visible on items, because users often consider printed or hand-written text to be a title, even if it’s incomplete or inaccurate. If a user has seen the picture before, they’ll look for
it by the visible textual information. This approach works well most of the time.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">There are more than a few examples, however, where a printmaker or photographer got key parts of a title wrong. For that circumstance, DCRM (G) 0.G7.1 allows
for interpolation of the correct information. A classic example is this glass negative, in which the words “Royal Palace, Warsaw” are etched in the plate. The building shown in the photo is actually the Kremlin Palace in Moscow. Another user behavior
is copy/pasting whatever title appears in an online catalog as the title for the image when they reproduce it in their own lecture, article, web page, etc. Putting the accurate information that identifies the building in a note, without any flags in the
title about inaccurate information, seems too misleading. (To look at the photo, go to
<a href="http://cdn.loc.gov/service/pnp/ggbain/19600/19657v.jpg">http://cdn.loc.gov/service/pnp/ggbain/19600/19657v.jpg</a> )</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Another example: Title: Bands of sheep [i.e. cattle] on the Gravelly Range at the foot of Black Butte, Madison County, Montana</span>
<a href="http://www.loc.gov/pictures/item/2017878798/">http://www.loc.gov/pictures/item/2017878798/</a>
<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">This exception to RDA seemed to be a ‘rare materials need’ because it happens chiefly with historical items that have survived in only one or a few copies.
To this day, of course, newspaper photo captions have errors in them, but it’s not usually the whole title that’s wrong anymore, or, a switched caption is quickly corrected. It’s the rare historical picture survivors that most need the warning mechanism.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">DCRM(G) text:</span><o:p></o:p></p>
<p class="MsoNormal"><img border="0" width="676" height="490" style="width:7.0416in;height:5.1083in" id="Picture_x0020_1" src="cid:image001.jpg@01D37E31.84D07E70"><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><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 [<a href="mailto:dcrm-l-bounces@lib.byu.edu">mailto:dcrm-l-bounces@lib.byu.edu</a>]
<b>On Behalf Of </b>Noah Sheola<br>
<b>Sent:</b> Tuesday, December 19, 2017 3:11 PM<br>
<b>To:</b> DCRM Users' Group<br>
<b>Subject:</b> Re: [DCRM-L] RBMS PS Review Q2.5: Transcription of Inaccuracies</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal">I'm more in favor of falling in line with RDA on this one. If the inaccuracy is corrected or commented upon in a note, it should be clear enough to the user that the inaccuracy appears on the item itself and is not a cataloger's error.
I'm not crazy about the compromise in the current draft (it's a compromise, so that is to be expected, I suppose). If there are benefits in continuing to permit interpolated corrections at the cataloger's discretion, I am not convinced the inconsistency across
cataloging agencies is worth it.<o:p></o:p></p>
<div>
<p class="MsoNormal">- Noah<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal">On Tue, Dec 19, 2017 at 11:48 AM, Lapka, Francis <<a href="mailto:francis.lapka@yale.edu" target="_blank">francis.lapka@yale.edu</a>> wrote:<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:"Georgia",serif;color:#1F497D">We’d really like to hear from the community on this question – especially from current BSC members and anyone who was not
on the task force.</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">This may be the only area where the draft RBMS Policy Statements are clearly at odds with RDA guidance (of if not the only
area, the area where they are <i>most</i> at odds). Do you agree with the outcome? Does it need clarification? Would you favor a different approach?</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="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>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<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-size:11.0pt;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.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:black"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-size:11.0pt;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.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:black"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-size:11.0pt;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.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:black"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-size:11.0pt;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.</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:black"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-size:11.0pt;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.
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:black"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt;vertical-align:baseline"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:black">Best,
</span><o:p></o:p></p>
<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="color:#002060">Michelle Mascaro</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:"Calibri Light",sans-serif">Head, Special Collections Metadata</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:"Calibri Light",sans-serif">University of California, San Diego
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="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" target="_blank">858)
534-6759</a> </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:"Calibri Light",sans-serif"><a href="mailto:mmascaro@ucsd.edu" target="_blank">mmascaro@ucsd.edu</a></span><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>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif">Noah Sheola</span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif">Special Collections <span style="background:#FAFAFA">Cataloging Librarian</span></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif;background:#FAFAFA">Burns Library</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Georgia",serif;background:#FAFAFA">Boston College</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>