I must say, I often rely on German cataloging records of individual
volumes to sort out multipart sets that aren't described in detail by
Anglo-American set records. (Though this may not be much to influence
final German RDA implementation decisions ;-)
Diana Brooking
I also understood Heidrun's proposed project in the same way that Ed did.
As a reader and a cataloger, I would be very interested in not just a
translation of RAK into English, but a larger consideration of (past)
German cataloging practice interpreted for a non-German audience. I think
it
I am rather confused about the purpose of the new 3xx fields in authority
records. So I share Ben's unease. It seems that the needs of linked data,
where you could ideally be using a URI to stand for a place name in a 370,
doesn't mesh well with the need to recreate our (basically AACR2)
John, that is a beautiful, eloquent explanation, one that
works for me. Thank you.
Diana Brooking (206) 685-0389
Cataloging Librarian (206) 685-8782 fax
Suzzallo Library dbroo...@u.washington.edu
University of Washington
Box 352900
Seattle WA
Yes, I agree with you Jonathan. *Both* the rules and the machines are
tools to try to provide services for patrons. Just the means to an end.
I think a lot of the confusion arises because of the very varied
environments where our data are living. It's not always clear where the
problem
Disclaimer: I don't care that much about capitalization.
But Robert Maxwell did bring up an interesting point about aesthetics
(pretty records and the professional appearance of catalogs).
I have thought about this in relation to RDA itself as a product.
Concerns have been expressed about
Have you ever used the Internet Movie Database? There they have a simple
way of qualifying people, even if it does make people look like kings or
popes.
Ed Jones (I)
Ed Jones (II)
Ed Jones (III)
I thought of this simple numbering system when CC:DA was discussing how
best to qualify names at
As I understand it, the idea is not to have too many *separate*
cataloging content standards. If RDA were developed just for some formats
but not for all, I think it would be possible that the different standards
could begin to really diverge over time, if there were nothing overarching
holding
I agree that trying to combine both display and access in one field (data
element, whatever) is very problematic. I would like to see RDA avoid
that.
Cataloging Cultural Objects recommends having both controlled fields and
free-text fields. They make a distinction between display and indexing.
The users tasks you give, and the user tasks in FRBR, seem to me to be
too narrow for today's dynamic, networked world.
It seems to me that Martha is not suggesting that a catalog should be
confined to FRBR tasks alone, but that a catalog should have the data it
needs to continue to support
re: RDA Chap. 6
Can anyone explain what an embedded description is?
I don't think I understand. But one idea I have... do the other
conventions for recording relationships assume that there is a separately
existing description/record for the related resource, and that an embedded
description
and Access
[mailto:[EMAIL PROTECTED] On Behalf Of D. Brooking
Sent: Friday, July 28, 2006 1:40 PM
To: RDA-L@INFOSERV.NLC-BNC.CA
Subject: [RDA-L] What is an embedded description?
re: RDA Chap. 6
Can anyone explain what an embedded description is?
I don't think I understand. But one idea I have... do
12 matches
Mail list logo