<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" 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: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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.bibcontentsectiondefault
{mso-style-name:bibcontentsectiondefault;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Palatino Linotype","serif";
color:#1F497D;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-family:"Bookman Old Style","serif";
color:blue'>Well, it’s really an incomplete item, not an incomplete
manifestation (which is a class, the items being the individuals of the class).
I’ve never liked this situation either, and there’s no excuse for a
such rules-based disservice to our patrons. A lamb chop is not a lamb.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Bookman Old Style","serif";
color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-family:"Bookman Old Style","serif";
color:blue'>Might one approach the problem by declaring, at the outset, that a
fragmentary copy is not merely imperfect, but a different thing altogether, which
should be described as such? We don’t treat the leaf in a leaf-book as a copy
(I hope), and what we’re talking about is leaf-books without a book--ignoble
fragments. (Treating a fragment as an imperfect copy has an analogue in the
wrong-headed LC policy of cataloging reformatted manifestations by way of describing
the original and adding a note—fine, or at least workable for a single
institution, perhaps, but a perfect misery in a union database like the
WorldCat.)<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Bookman Old Style","serif";
color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-family:"Bookman Old Style","serif";
color:blue'>Is this something that Bib Standards might want to consider? I’ve
a sense that it may not have been a burning issue in the past, because many
libraries would have dealt with fragments in-house only; but add your leaf as a
holding to the OCLC master record for the book and it becomes everybody’s
problem. In any case, I don’t think FRBR, as it stands, comes to our
rescue, though the scattered fragments of individual books do constitute a roughly
definable class, a sort of post-production manifestation of which any one
fragment is an instance.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif";
color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Times New Roman","serif";
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-family:"Bookman Old Style","serif";color:blue'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Bookman Old Style","serif";
color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-family:"Bookman Old Style","serif";
color:blue'><o:p> </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>Dooley,Jackie<br>
<b>Sent:</b> Tuesday, April 06, 2010 1:04 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> </o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Would FRBR help? Does it get to
the level of stating whether it’s acceptable to describe an incomplete
manifestation in the main body of the record?<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Jackie Dooley<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Consulting Archivist<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>OCLC Research and the RLG
Partnership<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </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 10:01 AM<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> </o:p></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Palatino Linotype","serif";
color:#1F497D'>This is an interesting question. We do the same, even though
sometimes we only have a title page (legacy of Halliwell-Phillipps'
scrapbooking). And even though that particular note, as with all notes on
imperfections, is always the first note, I also am uncomfortable.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Palatino Linotype","serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Palatino Linotype","serif";
color:#1F497D'>What would alternatives be? Catalog the single leaf(ves) as
themselves, with links to the larger work? Maybe the latter as uniform title? <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Palatino Linotype","serif";
color:#1F497D'><o:p> </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>Ryan<br>
<b>Sent:</b> Tuesday, 06 April, 2010 12:40<br>
<b>To:</b> 'DCRM Revision Group List'<br>
<b>Subject:</b> [DCRM-L] Cataloging of single leaves<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Has anyone approached the cataloging of an individual leaf
(or leaves) in a manner in which the physical description reflects only what
you have (vs. DCRM(B) 5B1.1)? The question is prompted by a loan request in
which the requester did not realize that our "copy" was merely two
leaves of a publication. This information is stated in a local note, but one of
our public services librarians feels that this is not a very user friendly way
of saying we have only two leaves. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks,<o:p></o:p></p>
<p class=MsoNormal>Ryan<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>--<o:p></o:p></p>
<p class=MsoNormal>Ryan Hildebrand<o:p></o:p></p>
<p class=MsoNormal>Book Cataloging Dept. Head<o:p></o:p></p>
<p class=MsoNormal>Harry Ransom Center<o:p></o:p></p>
<p class=MsoNormal>University of Texas at Austin<o:p></o:p></p>
<p class=MsoNormal>P.O. Box 7219<o:p></o:p></p>
<p class=MsoNormal>Austin, TX 78713-7219<o:p></o:p></p>
<p class=MsoNormal>512-232-1681<o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.5pt'><a
href="http://www.hrc.utexas.edu/">www.hrc.utexas.edu</a><o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>