Ryan
What you have found is a missing link. In what you have pasted, "368"
should be a hyperlink to the section of the BL Guide headed "Other
Attributes - Personal Names", which begins with this:
Please note that subfield |d of MARC 21 field 368 may not yet (July
2013) be used in LC/NACO authority records
I've put this link in, now. It was at the end of the section:
Qualifiers in Access Points Requiring RDA Review - Title of the Person.
The same reference, and link, were already present in these sections:
Authorized and Variant Access Points - Personal Names - Title or Other
Designation Associated with the Person
Authorized and Variant Access Points - Personal Names - Other Term of
Rank, Honour or Office
Thanks for taking the time to read this, and please let me know if you
find anything else that looks unusual ;-)
Regards
Richard
_________________________
Richard Moore
Authority Control Team Manager
The British Library
Tel.: +44 (0)1937 546806
E-mail: [log in to unmask]
From: Program for Cooperative Cataloging
[mailto:[log in to unmask]] On Behalf Of Finnerty, Ryan
Sent: 22 July 2013 22:53
To: [log in to unmask]
Subject: Re: [PCCLIST] BL Guide to RDA Name Authority Records - July
2013 changes
Hi everyone,
I was just going through the BL Guide and I find it enormously helpful.
I did notice one conflict between the guide and the DCM Z1.
In the BL Guide it says to record the title of the person in 368$d:
Title of the Person (9.4
<http://access.rdatoolkit.org/document.php?id=rdachp9&target=rda9-4630&t
arget=rda9-4630#rda9-4630> ) is also recorded in MARC 21
<http://www.loc.gov/marc/authority/ad368.html> field 368 subfield |d:
1001 |a Appleby, Robert, |c Sir
368 |d Sir
However, the DCM Z1 says not to use 368$d:
Until further notice LC/PCC catalogers are asked NOT to supply the
following subfields: $d (Title of person)
<http://desktop.loc.gov/template.htm?view=document&doc_action=setdoc&doc
_keytype=foliodestination&doc_key=maauth368SPACEDOLLARd&hash=368SPACEDOL
LARd> , $s (Start period)
<http://desktop.loc.gov/template.htm?view=document&doc_action=setdoc&doc
_keytype=foliodestination&doc_key=maauth368SPACEDOLLARs&hash=368SPACEDOL
LARs> , $t (End period)
<http://desktop.loc.gov/template.htm?view=document&doc_action=setdoc&doc
_keytype=foliodestination&doc_key=maauth368SPACEDOLLARt&hash=368SPACEDOL
LARt> , $u (Uniform Resource Identifier)
<http://desktop.loc.gov/template.htm?view=document&doc_action=setdoc&doc
_keytype=foliodestination&doc_key=maauth368SPACEDOLLARu&hash=368SPACEDOL
LARu> , and $v (Source of Information)
<http://desktop.loc.gov/template.htm?view=document&doc_action=setdoc&doc
_keytype=foliodestination&doc_key=maauth368SPACEDOLLARv&hash=368SPACEDOL
LARv> .
Same with the LC guidelines to MARC authority format:
368
<http://desktop.loc.gov/template.htm?view=document&doc_action=setdoc&doc
_keytype=foliodestination&doc_key=Maauth368&hash=368> may be supplied
in a name authority record coded 008/10 c
<http://desktop.loc.gov/template.htm?view=document&doc_action=setdoc&doc
_keytype=foliodestination&doc_key=Maauth008SLASH10SPACEDASHSPACEc&hash=0
08SLASH10SPACEDASHSPACEc> or z
<http://desktop.loc.gov/template.htm?view=document&doc_action=setdoc&doc
_keytype=foliodestination&doc_key=Maauth008SLASH10SPACEDASHSPACEz&hash=0
08SLASH10SPACEDASHSPACEz> .
Do not use subfields:
$d
<http://desktop.loc.gov/template.htm?view=document&doc_action=setdoc&doc
_keytype=foliodestination&doc_key=Maauth368SPACEDOLLARd&hash=368SPACEDOL
LARd> , $s
<http://desktop.loc.gov/template.htm?view=document&doc_action=setdoc&doc
_keytype=foliodestination&doc_key=Maauth368SPACEDOLLARs&hash=368SPACEDOL
LARs> , $t
<http://desktop.loc.gov/template.htm?view=document&doc_action=setdoc&doc
_keytype=foliodestination&doc_key=Maauth368SPACEDOLLARt&hash=368SPACEDOL
LARt> , $u
<http://desktop.loc.gov/template.htm?view=document&doc_action=setdoc&doc
_keytype=foliodestination&doc_key=Maauth368SPACEDOLLARu&hash=368SPACEDOL
LARu> , $v
<http://desktop.loc.gov/template.htm?view=document&doc_action=setdoc&doc
_keytype=foliodestination&doc_key=Maauth368SPACEDOLLARv&hash=368SPACEDOL
LARv> , $0
<http://desktop.loc.gov/template.htm?view=document&doc_action=setdoc&doc
_keytype=foliodestination&doc_key=Maauth368SPACEDOLLAR0&hash=368SPACEDOL
LAR0> , $6
<http://desktop.loc.gov/template.htm?view=document&doc_action=setdoc&doc
_keytype=foliodestination&doc_key=Maauth368SPACEDOLLAR6&hash=368SPACEDOL
LAR6> or $8
<http://desktop.loc.gov/template.htm?view=document&doc_action=setdoc&doc
_keytype=foliodestination&doc_key=Maauth368SPACEDOLLAR8&hash=368SPACEDOL
LAR8>
I thought that maybe the DCM Z1 and the LC guidelines were just waiting
for revisions to be published in light of the new release of RDA, so I
tried adding a 368$d to a record in OCLC and Connexion would not
validate it. I got this error message:
368 occurrence 1 - invalid relationship - when element is present, then
368 $a, 368 $b or 368 $c must be present
This doesn't make any sense at all since $d is not dependent on $a, $b,
or $c.
So my question is, is it okay to begin using the 368$d? If so, can OCLC
change its validation rules?
Ryan J. Finnerty | Head, Database Management & NACO Coordinator
UC San Diego Library | Metadata Services Department
[log in to unmask] | (858) 822-3138
From: Program for Cooperative Cataloging [
mailto:[log in to unmask]] On Behalf Of Amy Turner
Sent: Wednesday, July 10, 2013 7:46 AM
To: [log in to unmask]
Subject: Re: [PCCLIST] BL Guide to RDA Name Authority Records - July
2013 changes
Richard et al.,
I see that new rule 9.19.1.6 Other Term of Rank, Honour, or Office has
the example:
Wood, Captain, John
I hope that the order of elements is not prescriptive! I would expect
Wood, John, $c Captain.
I am very glad to have more options to avoid undifferentiated names.
Thanks to all those who made it so.
Amy
Amy Turner
Cataloger and Authority Control Coordinator, Duke University Libraries
[log in to unmask]
From: Program for Cooperative Cataloging [
mailto:[log in to unmask]] On Behalf Of Moore, Richard
Sent: Wednesday, July 10, 2013 9:35 AM
To: [log in to unmask]
Subject: [PCCLIST] BL Guide to RDA Name Authority Records - July 2013
changes
Importance: High
Dear colleagues
Changes to RDA were published this week, to implement the decisions of
JSC last November. The BL Guide to RDA Name Authority Records has been
updated to reflect these changes. It can be found here:
RDA Toolkit
-Tools
--Workflows
---Global workflows
----BL Guide to RDA Name Authority Records
The updated Guide has been reviewed by colleagues at LC/PCC, who were
kind enough to take the time to plough through it and suggest additions
and amendments, which have all been incorporated. The Guide is
consistent with the LC-PCC-PS, DCM:Z1 and the Post-RDA Test Guidelines.
Sections of the Guide are not numbered (to avoid confusion with RDA
instruction numbers), but navigation is by hyperlinks starting at the
Contents page. Links are provided throughout the Guide to the relevant
RDA instructions, to the LC-PCC-PS, and to MARC 21.
At the end of the Contents page is a section called 2013 Changes to RDA,
that summarises the changes affecting name authority records, with links
to the more detailed information within the Guide.
From our perspective I would like to draw attention to some of the
changes that we first proposed (6JSC/BL/3 and 6JSC/BL/4):
Title of the Person has a new sub-element "Other Term of Rank, Honour or
Office" (9.4.1.9, 9.19.1.6), which includes terms indicating academic
office, terms of respect for clergy, military ranks, and other terms of
honour. It can be used to distinguish an authorised access point if
dates of birth/death, periods of activity and occupations are not
available.
Other Designation Associated with the Person (9.6, 9.19.1.2) now
includes terms for Persons Named in Sacred Scriptures or Apocryphal
Books (9.6.1.6), the terms Fictitious character, Legendary character,
etc. (9.6.1.7), and terms for the type, species or breed of Real
Non-human Entities (9.6.1.8).
Other Designation Associated with the Person also has a new sub-element
"Other Designation" (9.6.1.9, 9.19.1.7). This element is intentionally
broad, and is designed to help remove the few remaining cases where an
authorised access point can not be made unique. It therefore encompasses
almost any sensible designation, that does not fall within the scope of
another element that can be used in an access point. It can be used to
distinguish an authorised access point if dates of birth/death, periods
of activity, occupations and other terms of rank, honour or office are
not available.
Other significant changes are covered in the Guide, notably the
combination of the two lists of corporate and government bodies entered
subordinately, which have been combined into a single set of
instructions at 11.2.2.13-11.2.2.28 (6JSC/ALA/18).
This revision of the Guide also contains a section on our practice for
relationship designators in name authority records, which follows the
"FAQ - LC/PCC RDA and AACR2 practice for creating NARs for persons who
use pseudonyms" [1], and recommendations by the Task Group to Formulate
or Recommend PCC/NACO RDA Policy on Authority Issues [2].
I hope this is useful.
Regards
Richard
_________________________
Richard Moore
Authority Control Team Manager
The British Library
Tel.: +44 (0)1937 546806
E-mail: [log in to unmask] <mailto:[log in to unmask]>
[1] http:// <http://www.loc.gov/catdir/cpso/pseud.pdf>
www.loc.gov/catdir/cpso/pseud.pdf
<http://www.loc.gov/catdir/cpso/pseud.pdf>
[2]
http://rwww.loc.gov/aba/pcc/rda/RDA%20Task%20groups%20and%20charges/TG%2
0to%20Formulate%20PCC%20NACO%20Policy_Medium%20Priority%20Issues.docx
<http://rwww.loc.gov/aba/pcc/rda/RDA%20Task%20groups%20and%20charges/TG%
20to%20Formulate%20PCC%20NACO%20Policy_Medium%20Priority%20Issues.docx>
**************************************************************************
Experience the British Library online at http://www.bl.uk/
The British Library’s latest Annual Report and Accounts : http://www.bl.uk/aboutus/annrep/index.html
Help the British Library conserve the world's knowledge. Adopt a Book. 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 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
