I knew I would be misinterpreted on this point! Here is how I replied to Richard Moore:
Richard,
No, you misunderstood me, which I thought might happen. Here is what I mean:
010 no2006105598
040 NjP ǂb eng ǂc NjP
1001 Avni, Eliran
670 Dorman, A. Sonata no. 1, p2006: ǂb label (Eliran Avni, piano)
010 no2006105598
040 NjP ǂb eng ǂc NjP ǂd PPi-MA
1001 Avni, Eliran, ǂd 1975-
670 Dorman, A. Sonata no. 1, p2006: ǂb label (Eliran Avni, piano) insert (b. 1975, Israel)
In other words, the birth date was given in the item cat, and therefore should have been cited and added to the heading.
More egregious are cases in which the date WAS cited in the 670 but omitted from the heading, which is what we were obligated to do when the heading appeared consistently in OCLC without the birth date, but that limitation was removed a few years ago. So if someone cites a birth date at the time the AR is created and it isn't added to the heading, I will revise that:
010 no2008182542
040 ViVb ǂb eng ǂc ViVb
1001 Archuleta, David
670 His David Archuleta, 2008: ǂb label (David Archuleta) 670 Allmusic.com, Dec. 10, 2008 : ǂb (b. Dec. 28, 1990 in Miami Fla.)
010 no2008182542
040 ViVb ǂb eng ǂc ViVb ǂd PPi-MA
1001 Archuleta, David, ǂd 1990-
670 Archuleta, D. David Archuleta [SR] p2008.
670 Allmusic.com, Dec. 10, 2008 ǂb (David Archuleta; b. Dec. 28, 1990, Miami, FL)
Chuck
I guess I should have hit "reply all" THIS time!
In summary, I would NEVER add the birthdate gratuitously to an EXISTING heading, only if it needed to be changed for some other reason. The cases I've noted above involve the correction of errors made at the time the heading was created. I hope this clarifies my position.
CH
-----Original Message-----
From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Gary L. Strawn
Sent: Wednesday, August 12, 2009 12:04 PM
To: [log in to unmask]
Subject: Re: [PCCLIST] Revising Date Spans in Name Headings
At 09:51 AM 8/12/2009, Moore, Richard wrote:
>Presumably you wouldn't revise an established NACO heading to add a
>birth date, unless there was a conflict with a new, dateless
>heading? The NACO Participants' Manual indicates that one shouldn't
>do this, because of the BFM issues it creates. Not that adding death
>dates to close off birth dates doesn't also create BFM; I'm just
>making a point about the NACO requirements. Some participants seem
>occasionally to add things to headings for which there is no need,
>which creates work even for a library such as ourselves, with global
>updating of our catalogue.
Amen! Don't change headings that don't need to be changed. In
processing names file 09.29, I've already found several cases in
which people have added both birth and death dates to a
non-conflicting existing heading sans dates. Here are a few:
n 83145574
nr2002004266
n 97076481 (looks like a fascinating biography!)
Gary L. Strawn, Authorities Librarian, etc.
Northwestern University Library, 1970 Campus Drive, Evanston IL 60208-2300
e-mail: [log in to unmask] voice: 847/491-2788 fax: 847/491-8306
Forsan et haec olim meminisse iuvabit. BatchCat version: 2006.51.826
This email message and any files transmitted with it are intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law.� Any use, distribution, copying or disclosure by anyone other than the intended individual or entity is prohibited without prior approval.� If you have received this information in error, please notify the sender immediately.
|