<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=us-ascii">
<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:"Georgia Pro";}
/* 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;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Georgia Pro",serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-compose;
font-family:"Georgia Pro",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-family:"Georgia Pro",serif">Hi Erin.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif">I see the appeal in your suggestion. If there is consensus for such a change, is it possible that there’d be benefit to having a parallel mechanism available in other transcribed fields (250,
26x, 490)? I haven’t thought it through.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif">I also wonder if the scope of your suggestion overlaps (in part, at least) with the following MARC discussion paper on the agenda for Midwinter:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in">MARC DISCUSSION PAPER NO. 2021-DP06<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Recording Data Provenance in the MARC 21 Formats<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><a href="https://www.loc.gov/marc/mac/2021/2021-dp06.html">https://www.loc.gov/marc/mac/2021/2021-dp06.html</a><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif">Francis<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b>From:</b> DCRM-L <dcrm-l-bounces@lib.byu.edu> <b>On Behalf Of
</b>Erin Blake<br>
<b>Sent:</b> Monday, January 11, 2021 4:55 PM<br>
<b>To:</b> DCRM Users' Group <dcrm-l@lib.byu.edu><br>
<b>Subject:</b> [DCRM-L] Potential addition of $i to record source of title for the 245?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">What do people think about potentially authorization of $i to record the "source of title" in the 245?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The idea came up over the weekend, when a friend and I were talking about how we routinely use the 246$i "Introductory text" subfield to show "source of title" for variant titles of graphic material, and she wondered about advocating that
$i be extended for use in the 245, not just the 246. This came up in the context of balancing how a resource "describes itself" with being culturally respectful when a transcribed title is disrespectful.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Here's a snippet from the Folger's OPAC as an example of how we use 246 for 'source of title' with prints:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><img border="0" width="412" height="109" style="width:4.2916in;height:1.1354in" id="Picture_x0020_1" src="cid:image002.png@01D6E8C9.1AF0AF60" alt="image.png"><o:p></o:p></p>
</div>
<p class="MsoNormal">Per DCRM(G) there's always a 500$a giving source of title, and per Folger practice, we always include a 246 for the title from a standard reference source, if applicable (shown here with the introductory text "Hollstein title:" -- the record's
510 gives the full reference for Hollstein).<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Catalogers know that the lack of square brackets in the 245 means it's a transcribed title, but patrons sometimes don't. This is especially the case with scholars accustomed to seeing the same prints in museums' catalogs, where transcribed
titles are not the norm. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><i>Cataloging Cultural Objects</i> (CCO) handles this with a "Title Type" element, see p. 50: "for example,
<i>repository title</i>, <i>inscribed title</i>, <i>creator’s title</i>, <i>descriptive title." </i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Linking source of title to the 245 is also a concern when it comes to future-proofing data for migration: even when there is a bracketed title, its source is given in a free text 500$a, not in a structure that would let us keep "title"
and "title source" paired, the way they are in the 246.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thoughts?<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>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><a name="SignatureSanitizer__MailAutoSig"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">______________________<br>
Erin Blake, Ph.D. | Senior Cataloger | Folger Shakespeare Library | 201 E. Capitol St. SE, Washington, DC, 20003 |
</span></a><a href="mailto:eblake@folger.edu" target="_blank"><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"> |
</span><a href="https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fprotect-us.mimecast.com%2Fs%2F-t5RCjRgpBtArRXC7R7_2%3Fdomain%3Durldefense.com&data=04%7C01%7Cfrancis.lapka%40yale.edu%7C30950c63e1a94142640308d8b67ba672%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637459989491586421%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=2gry5zJnYgcrt2g5vMe2PAgBr%2FGDbmu7npeeSzuepuY%3D&reserved=0" target="_blank"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">www.folger.edu</span></a><span style="font-size:7.5pt;font-family:"Arial",sans-serif">
| Pronouns: she/her/hers</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>
</div>
</div>
</div>
</body>
</html>