<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 12 (filtered medium)">
<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:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"Bookman Old Style";
        panose-1:2 5 6 4 5 5 5 2 2 4;}
@font-face
        {font-family:"Palatino Linotype";
        panose-1:2 4 5 2 5 5 5 3 3 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:blue;
        text-decoration:underline;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
        {mso-style-priority:99;
        mso-style-link:"E-mail Signature Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
p
        {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.E-mailSignatureChar
        {mso-style-name:"E-mail Signature Char";
        mso-style-priority:99;
        mso-style-link:"E-mail Signature";
        font-family:"Calibri","sans-serif";}
span.EmailStyle20
        {mso-style-type:personal;
        font-family:"Arial","sans-serif";
        color:navy;}
span.EmailStyle21
        {mso-style-type:personal;
        font-family:"Palatino Linotype","serif";
        color:#1F497D;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none;}
span.EmailStyle22
        {mso-style-type:personal-reply;
        font-family:"Bookman Old Style","serif";
        color:blue;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page Section1
        {size:595.3pt 841.9pt;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
        {page:Section1;}
-->
</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=blue>

<div class=Section1>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Bookman Old Style","serif";
color:blue'>I think that&#8217;s exactly the idea&#8212;to give the fragment
its own record. Or better, to provide a generic record descriptive of all
copies of this nature, which then require further copy-specific description. (It&#8217;s
a signal-to-noise ratio problem: separate records for each fragment would be
too noisy; identification by way of notes only is a weak signal.) The idea here
is to avoid creating descriptions that are too easily misread, since key
information is buried deep, and may in some cases be inaccessible, as in interfaces
that do not display notes. (E.g. WorldCat.org, yes?)<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Bookman Old Style","serif";
color:blue'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Bookman Old Style","serif";
color:blue'>In a way, it&#8217;s a matter of extending the FRBR hierarchy to encompass
the port-production history of material texts, with its significant
implications for efficient access.<o:p></o:p></span></p>

<p class=MsoNormal><span style='color:blue'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:10.0pt;color:blue'>RICHARD NOBLE :
RARE BOOKS CATALOGER : JOHN HAY LIBRARY : BROWN UNIVERSITY<br>
PROVIDENCE, RI 02912 : 401-863-1187/FAX 863-2093 : RICHARD_NOBLE@BROWN.EDU </span><span
style='font-size:11.0pt;font-family:"Bookman Old Style","serif";color:blue'><o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Bookman Old Style","serif";
color:blue'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Bookman Old Style","serif";
color:blue'><o:p>&nbsp;</o:p></span></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-bounces@lib.byu.edu
[mailto:dcrm-l-bounces@lib.byu.edu] <b>On Behalf Of </b>Deborah J. Leslie<br>
<b>Sent:</b> Tuesday, April 06, 2010 6:10 PM<br>
<b>To:</b> DCRM Revision Group List<br>
<b>Subject:</b> Re: [DCRM-L] Cataloging of single leaves<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal><span style='font-family:"Palatino Linotype","serif";
color:#1F497D'>That wouldn't be applicable if a library has one or more
complete copies, unless you wanted to give the fragment its own record.<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-family:"Palatino Linotype","serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></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-bounces@lib.byu.edu [mailto:dcrm-l-bounces@lib.byu.edu] <b>On Behalf Of </b>Jane
Stemp Wickenden<br>
<b>Sent:</b> Tuesday, 06 April, 2010 18:07<br>
<b>To:</b> 'DCRM Revision Group List'<br>
<b>Subject:</b> Re: [DCRM-L] Cataloging of single leaves<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>I was just heading towards the concept of <o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>245 $a Main title. $h [Fragment] when Dick Miller&#8217;s e-mail
arrived, which is simply how I would have dealt with it in the absence of finding
a rule, and supposing I could identify the title from the fragment anyway.<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span lang=EN-GB style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:navy'>Jane<o:p></o:p></span></p>

<p><span lang=EN-GB style='color:blue'><o:p>&nbsp;</o:p></span></p>

<p><span lang=EN-GB style='font-size:11.0pt;font-family:"Bookman Old Style","serif";
color:blue'><o:p>&nbsp;</o:p></span></p>

</div>

</body>

</html>