 |
 |
“now mythical Phase 3B LC/NAF RDA conversion”? I’ve been wondering about this. Is it definitely off the table, or just on indefinite hold? If there is not going to be an automated AARCR to RDA conversion for records that are fine either way, can we stop recoding to RDA when we edit a record that falls into that category? I vaguely recall a study that showed that the majority (95%?) of authorized access points in the LCNAF met the requirements of both AACR2 and RDA. As we get further and further away for AACR2, there will be more and more confusion about the actual differences. And as we move toward linked data, does the standard used for character strings really matter? From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Moore, Richard Sent: Tuesday, January 23, 2018 2:13 AM To: [log in to unmask] Subject: Re: [PCCLIST] NARs for princesses That 667 field was added to any NAR with a 100 $c, that wasn’t on a list of valid RDA qualifiers that a Task Group I participated in could agree in fairly short order. An awful lot of perfectly good RDA qualifiers weren’t on that list – if anyone had the slightest doubt about a qualifier, or thought the facts might need looking at again, it was left off. Some qualifiers just need punctuation changing. Much of this was due to be done in the now mythical Phase 3B LC/NAF RDA conversion. I agree the current example is probably fine. 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 Hostage, John Sent: 22 January 2018 20:29 To: [log in to unmask]<mailto:[log in to unmask]> Subject: Re: [PCCLIST] NARs for princesses That 667 field was added to any authority record with a subfield $c in the 100. It doesn't necessarily mean that the heading is not a valid RDA heading. The examples in 9.4 are used as additions to the preferred name. See 9.19.1.2.1. The heading for the princess is probably OK as it is. ------------------------------------------ John Hostage Senior Continuing Resources Cataloger Harvard Library--Information and Technical Services Langdell Hall 194 Harvard Law School Library Cambridge, MA 02138 [log in to unmask]<../../owa/redir.aspx?C=fff0248a4daa423caadeb2f835259a11&URL=mailto%3ahostage%40law.harvard.edu> +(1)(617) 495-3974 (voice) +(1)(617) 496-4409 (fax) ISNI 0000 0000 4028 0917 ________________________________ From: Program for Cooperative Cataloging <[log in to unmask]<mailto:[log in to unmask]>> on behalf of Jessica Janecki <[log in to unmask]<mailto:[log in to unmask]>> Sent: Monday, January 22, 2018 14:26 To: [log in to unmask]<mailto:[log in to unmask]> Subject: [PCCLIST] NARs for princesses I turn to the collective wisdom for help with a NAR for a Duchess of York, Frederica Charlotte of Prussia. I find the RDA rules for royals (see 9.4 and 9.2.2.14) to be extremely hard to parse. She’s a royal both by birth and by marriage (daughter of a king and wife of a king’s son). She also doesn’t have a last name in any real sense and the examples in 9.2.2.14 all involve people with last names. The examples at 9.4 only show the title and don’t show the whole preferred name. There is currently a NAR in the NAF, but it has a 667 THIS 1XX FIELD CANNOT BE USED UNDER RDA UNTIL THIS RECORD HAS BEEN REVIEWED AND/OR UPDATED and I want to do the right thing and clean up the record while I am looking at it. Current heading: Frederica Charlotte Ulrica Catherina, ǂc Princess, Duchess of York, ǂd 1767-1820 https://en.wikipedia.org/wiki/Princess_Frederica_Charlotte_of_Prussia<https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_Princess-5FFrederica-5FCharlotte-5Fof-5FPrussia&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=O9-UIVab7e9YxpBphmOmeEQruoCpRWXNPKDBg9tfb88&m=vwQ0ZocCFh8N0STS3zRHrSiMN24lB4jNew1Is-wqTJ4&s=Cu-5qDUzuaf36uSQA-DrK4n6jU91OHjymJ2DjF2bO9g&e=> Thanks in advance, Jessica ****************************************************************************************************************** Experience the British Library online at www.bl.uk<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.bl.uk_&d=DwMGaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=Dc2zJWQZhGVM4krkr2m4NTiSqZ5Ld3IvJ8wM_1HzJMc&m=x5kx-4_mdP0dKKcRhPemHJY_DNpeec5G4W5aLt7nQVg&s=0V1jOoO2CcbwlF4k7Z1lBZJQg88JbAj7xkwgaxX4KE8&e=> The British Library’s latest Annual Report and Accounts : www.bl.uk/aboutus/annrep/index.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.bl.uk_aboutus_annrep_index.html&d=DwMGaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=Dc2zJWQZhGVM4krkr2m4NTiSqZ5Ld3IvJ8wM_1HzJMc&m=x5kx-4_mdP0dKKcRhPemHJY_DNpeec5G4W5aLt7nQVg&s=VcqYMEz0eOM2fT7RoYK73EI268zFIV7VVJ0vQBYn6M4&e=> Help the British Library conserve the world's knowledge. Adopt a Book. www.bl.uk/adoptabook<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.bl.uk_adoptabook&d=DwMGaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=Dc2zJWQZhGVM4krkr2m4NTiSqZ5Ld3IvJ8wM_1HzJMc&m=x5kx-4_mdP0dKKcRhPemHJY_DNpeec5G4W5aLt7nQVg&s=DORqL6Tx0WpqnQcRWh8J_aiILdS9VyxWNnYZqxXZSVg&e=> 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