Adam and Kevin,
Thanks for the examples. Now I understand much better what this is all
about.
Perhaps a comparison with the German rules is of interest here. The
older German cataloging code, the Prussian instructions (1899/1908),
had elaborate rules for collective titles. But with the
Concerning the default procedure for collective titles, the LCRI says:
Except as noted in LCRI 25.9 and LCRI 25.10, assign a collective
uniform title to an item at the first instance of appropriateness, e.g.,
do not defer the adding of a collective uniform title until the file
under the
snip
For collocation purposes, there should eventually be other methods than
text strings anyway. Namely, and ideally, a link to a work record.
Then, it would become immaterial what kind of verbal designation
we add to it to become intelligible for the human reader. Only just
don't display that in
Thomas said
snip
No, there is no equation of 'preferred title for the work' and the
authorized access point for the work.
The preferred title for the work is one element only. Mapping it in MARC
would mean mapping it to 240 $a,$n,$p,$k -- but not to the rest of the 240
subfields.
RDA 5.3 says to
I'm working through today's name authority changes wondering why I'm finding:
‡a Wiggin, Ender (Fictitious character) but
‡a Wiggin, Peter ‡c (Fictitious character)
Is this simply two different agencies interpreting the rules differently?
We don't catalog a lot of fiction here so I've not
08.10.2013 15:20, Adger Williams:
snip
For collocation purposes, there should eventually be other methods than
text strings anyway. Namely, and ideally, a link to a work record.
Then, it would become immaterial what kind of verbal designation
we add to it to become intelligible for the human
Adger Williams wrote:
Actually, since these are collective titles for collections of works,
I am not quite sure to what kind of entity Bernard's link would
point. It wouldn't be to a single work record; it could be to some
kind of collective entity or to a position in a genre/form index or
I think the heading for Ender Wiggin should have $c before (Fictitious
character) and it was just left out accidentally. I did a search on the name
file for Fictitious character and found several others with the same problem.
Establishing fictitious characters in the name file rather than the
From: Resource Description and Access / Resource Description and Access
[mailto:RDA-L@LISTSERV.LAC-BAC.GC.CA] On Behalf Of Adger Williams
Sent: October-08-13 10:01 AM
To: RDA-L@LISTSERV.LAC-BAC.GC.CA
Subject: Re: [RDA-L] Uniqueness of titles proper
Thomas said
snip
No, there is no equation of
The first one is simply incorrect and should be fixed. The other
designation element (Fictitious character) should be coded in $c of the
personal name.
Adam Schiff
University of Washington Libraries
-Original Message-
From: FOGLER, PATRICIA A GS-11 USAF AETC AUL/LTSC
Sent: Tuesday,
smime.p7m
Description: S/MIME encrypted message
I would agree with Adam that the 100 field should be corrected. Since the 400
field has
the |c, I would take its absence in the 100 to be simply a typo or somebody's
oversight.
100 1_ |a Wiggin, Ender (Fictitious character)
Michael Bernhard said:
It seems to me, too, that the heading for Holmes should be Holmes, Sherlock
|c (Fictitious character).
I would like this clarified. In the same load I had a number of name
authorities the 2 that were presented as sometime authors of books no longer
had any qualifier.
This access point for Wiggin, Ender was first established by BYU *without* a
qualifier, following LC's instructions only to add qualifier to these access
point if there was a conflict. Somebody at BL took it upon themselves to add
the qualifier (without the appropriate subfield coding, as you
Hi all
We had an internal library discussion on this just as the questions started to
come in on the list! The LC PCC statement at 9.0 is:
Fictitious Entities and Real Non-Human Entities
LC practice/PCC practice: Apply this chapter to fictitious entities and real
non-human entities following
Surely we include fictitious character for these names? Do we really want
them to look like real people?
Pat
Patricia Sayre-McCoy
Head, Law Cataloging and Serials
D’Angelo Law Library
University of Chicago
773-702-9620
p...@uchicago.edu
-Original Message-
From: Resource Description and
Bernhard, S. Michael mbernh...@cabq.gov wrote:
It seems to me, too, that the heading for Holmes should be Holmes,
Sherlock |c (Fictitious character). Do
others agree? If I were still at a NACO library, I might go ahead and
correct both headings (unless I've missed
something somewhere with
No one should be correcting authorized access points that were correctly
established under current policy, which is to include the qualifier if there is
a conflict but otherwise not.
Bob
Robert L. Maxwell
Ancient Languages and Special Collections Cataloger
6728 Harold B. Lee Library
Brigham
Robert Maxwell robert_maxw...@byu.edu wrote:
No one should be “correcting” authorized access points that were
correctly established under current policy, which is to include the
qualifier if there is a conflict but otherwise not.
But the material of 9.6.1.7 falls under the 9.19.1.2 group of
In a message to the PCC list dated September 4, 2013, Kate James of the LC
Policy and Standards Division addressed this issue (with reference to the
record for Holmes, Sherlock):
***
...
Regarding the issue of whether 9.19.1.2 f) should be applied, this is a source
of ongoing debate because
Robert Maxwell robert_maxw...@byu.edu wrote:
In a message to the PCC list dated September 4, 2013, Kate James of the
LC Policy and Standards Division addressed this issue (with reference to
the record for “Holmes, Sherlock”):
Thanks for the reminder, Bob. Looking through my inbox, I held
Hi,
If a statement of edition includes a diference in geographic coverage, it
can be new edition.
Would you please offer an example?
Thanks
--
Maliheh Dorkhosh,
MLIS
Tehran North Branch of IAU
Head of cataloging department of the central library and documentation
center. University of Tehran
22 matches
Mail list logo
