[DCRM-L] Cataloging of single leaves

[Noble, Richard]

I think that's exactly the idea-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'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?)

 

In a way, it's a matter of extending the FRBR hierarchy to encompass the
port-production history of material texts, with its significant
implications for efficient access.

 

RICHARD NOBLE : RARE BOOKS CATALOGER : JOHN HAY LIBRARY : BROWN
UNIVERSITY
PROVIDENCE, RI 02912 : 401-863-1187/FAX 863-2093 :
RICHARD_NOBLE at BROWN.EDU 

 

 

From: dcrm-l-bounces at lib.byu.edu [mailto:dcrm-l-bounces at lib.byu.edu] On
Behalf Of Deborah J. Leslie
Sent: Tuesday, April 06, 2010 6:10 PM
To: DCRM Revision Group List
Subject: Re: [DCRM-L] Cataloging of single leaves

 

That wouldn't be applicable if a library has one or more complete
copies, unless you wanted to give the fragment its own record.

 

From: dcrm-l-bounces at lib.byu.edu [mailto:dcrm-l-bounces at lib.byu.edu] On
Behalf Of Jane Stemp Wickenden
Sent: Tuesday, 06 April, 2010 18:07
To: 'DCRM Revision Group List'
Subject: Re: [DCRM-L] Cataloging of single leaves

 

I was just heading towards the concept of 

 

245 $a Main title. $h [Fragment] when Dick Miller'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.

 

Jane

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listserver.lib.byu.edu/pipermail/dcrm-l/attachments/20100406/db5ba9af/attachment.htm