Print

Print


We don’t know whether the AAP conflicts with another in a catalogue at the cataloguer’s own institution. Conflicts are not restricted to LC/NAF. And as has been pointed out, the addition may in any case be made, optionally.

The AAP shouldn’t be changed now that it has been established.


Regards
Richard

________________________
Richard Moore
Authority Control Team Manager
The British Library

Tel.: +44 (0)1937 546104
E-mail: [log in to unmask]<mailto:[log in to unmask]>



From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Michael Borries
Sent: 28 July 2016 19:22
To: [log in to unmask]
Subject: Re: [PCCLIST] Dennis, Andrew K (NAR no2015077748)

This may be true, however, “Dennis, Andy” does not seem to conflict with any other headings, either.  At least, I didn’t see any.  In addition, instead of using a subfield $c, the cataloger could have used a subfield $q with the fuller form of name.

Michael S. Borries
Cataloger, City University of New York
151 East 25th Street, 5th Floor
New York, NY  10010
Phone: (646) 312-1687
Email: [log in to unmask]<mailto:[log in to unmask]>

From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Alberts, James
Sent: Thursday, July 28, 2016 1:54 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: [PCCLIST] Dennis, Andrew K (NAR no2015077748)

My guess would be that the cataloger wanted to avoid having one of the variant access points (Dennis, Andy) conflict with a preexisting VAP for a different Dennis, Andy. However, it’s my understanding that VAPs are allowed to conflict, so I’m not sure why the cataloger took the trouble to do this. Anyone out there who is more conversant with VAPs in conflict (we tend to avoid allowing VAPs to conflict in music cataloging, so I’m not exactly a specialist here) than I am, please feel free to chime in.

Best,
Jim Alberts
Recorded Sound Section
Library of Congress

Only my opinions, not those of my employer, etc., etc.

From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Michael Borries
Sent: Thursday, July 28, 2016 1:44 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: [PCCLIST] Dennis, Andrew K (NAR no2015077748)

Dennis, Andrew K., without any qualifier, was unique in the authority file and in OCLC.  Yet the person who established the heading felt compelled to add a subfield $c “(Software engineer).”  It is my understanding that this type of heading is added only if there is some need to differentiate between two otherwise identical headings.  So why was it added here?  Does it still need to be retained, since the heading has now been established this way?

Michael S. Borries
Cataloger, City University of New York
151 East 25th Street, 5th Floor
New York, NY  10010
Phone: (646) 312-1687
Email: [log in to unmask]<mailto:[log in to unmask]>



******************************************************************************************************************
Experience the British Library online at www.bl.uk<http://www.bl.uk/>
The British Library’s latest Annual Report and Accounts : www.bl.uk/aboutus/annrep/index.html<http://www.bl.uk/aboutus/annrep/index.html>
Help the British Library conserve the world's knowledge. Adopt a Book. www.bl.uk/adoptabook<http://www.bl.uk/adoptabook>
The Library's St Pancras site is WiFi - enabled
*****************************************************************************************************************
The information contained in this e-mail is confidential and may be legally privileged. It is intended for the addressee(s) only. If you are not the intended recipient, please delete this e-mail and notify the [log in to unmask]<mailto:[log in to unmask]> : The contents of this e-mail must not be disclosed or copied without the sender's consent.
The statements and opinions expressed in this message are those of the author and do not necessarily reflect those of the British Library. The British Library does not take any responsibility for the views of the author.
*****************************************************************************************************************
Think before you print