Making Changes to Existing Name Authority Records
2
Overview
• You now know how to create a “perfect” RDA authority record!
• You now know to search thoroughly to find the authority record you need
• But …
3
It is Not a Perfect (NACO) World
• The training prepared you to create NEW NACO records and to SEARCH for existing NACO records
• But you will not always be creating new NACO records
• And you will not always find the perfect existing NACO record
4
Summary: Basic Principle
Authority records must conform to RDA practices!
• Remember 008/10 Rules = z• Remember 040 subfield $e rda
5
Summary: Checklist • You need an access point for a
bibliographic record, so:• Search multiple forms of the name• Search both bibliographic and authority
databases• Sometimes research is needed to clarify
relationships• Remember the 24-hour rule• Don’t overdo it!
6
Summary: Search Results Govern Workflow
1. You find a NAR -- Use it!2. You find a NAR -- Update it!3. You do not find a NAR -- Create a
new one!• OCLC Connexion and SkyRiver
have authority macros
7
Summary: Search Results Govern Workflow
You find a NAR -- Update it!Let’s look at some typical cases– some where an update is optional, and some where it is required
8
Why Update an Existing NAR ?• To enhance it by adding new attributes
or new variant access points that assist the catalog user
• To change an existing variant access point to avoid a NACO conflict
• To change an existing authorized access point to avoid a NACO conflict
• To change an authorized access point to close an open birth date, or to add a birth date to an authorized access point containing only a death date
9
Why Update an Existing NAR ?• To consolidate information when a
duplicate NAR will be reported for deletion
• To evaluate and re-code an existing AACR2, AACR2-compatible, or earlier rules NAR that is not RDA-acceptable to RDA
• To evaluate and re-code an existing RDA-acceptable AACR2 NAR to RDA
• To correct an RDA authorized access point “error of fact”
10
To Enhance by…• Changing or updating attributes,
for example:• Dates (046 field)• Locations (370 field)• Address (371 field)• Field of Activity (372 field)• Profession/Occupation (374 field)• etc.
11
Changing or Updating Attributes
12
Adding Variant Access Point(s)
13
Adding Variant Access Point(s)
14
Showing New Relationship(s) Between Entities in 5XX fields
15
Showing New Relationship(s) Between Entities
16
To Change an Existing Variant Access Point to Avoid a NACO
Conflict
17
To Change an Existing Variant Access Point to Avoid a NACO
Conflict
18
To Change an Existing Authorized Access Point to Avoid a NACO
Conflict
19
To Change an Existing Authorized Access Point to Avoid a NACO
Conflict
20
To Change an Authorized Access Point to Close an Open Birth Date
21
To Change an Authorized Access Point to Close an Open Birth Date
22
To Consolidate Information in an Existing NAR when a Duplicate NAR
Will be Reported for Deletion
23
To Consolidate Information in an Existing NAR when a Duplicate NAR
Will be Reported for Deletion
24
To Evaluate and Re-code an Existing AACR2, AACR2-Compatible, or
Earlier Rules NAR to RDA when the 1XX is not RDA-Acceptable
25
To Evaluate and Re-code an Existing AACR2, AACR2-Compatible, or
Earlier Rules NAR to RDA when the 1XX is not RDA-Acceptable
26
To Evaluate and Re-Code an Existing RDA-Acceptable AACR2 NAR to RDA
27
To Evaluate and Re-Code an Existing RDA-Acceptable AACR2 NAR to RDA
28
To Evaluate and Re-Code an Existing RDA-Acceptable AACR2 NAR to RDA
29
To Correct an RDA Authorized Access Point “Error of Fact”
30
To Correct an RDA Authorized Access Point “Error of Fact”
31
What About Linking References?
Make a see reference for the old valid form of 1XX, with $w nnea, unless the reference itself is a valid RDA variant access point, in which case use $w nne. In case of doubt, use $w nnea
32
7 Exercises
33
Exercise 1
New resource in hand:
34
Exercise 1 – Suggested Answer
35
Exercise 2
New resource in hand:
36
Exercise 2 – Suggested Answer
37
Exercise 3
New resource in hand:
38
Exercise 3 – Suggested Answer
39
Exercise 4
New resource in hand:
40
Exercise 4 – Suggested Answer
41
Exercise 5
New resource in hand:
42
Exercise 5 – Suggested Answer
43
Exercise 6
New resource in hand:
44
Exercise 6 – Suggested Answer
45
Exercise 7
New resource in hand:
New resource in hand:
46
Exercise 7 – Suggested Answer
47
Nothing Found, Create NAR• What fields are absolutely required?• What information must be included?
48
Name of Persons• Preferred name [CORE]• Birth and/or Death Date associated with
the person [CORE]• Title of the person [CORE]• Other designation associated with the
person [CORE]• Fuller form of name for the person [CORE
if…]
49
Name of Persons• Period of activity of the person [CORE if…]• Profession or Occupation [CORE if…]• Gender• Place of birth• Place of death• Country associated with the person• Place of residence• Address
50
Name of Persons• Affiliation• Language• Field of activity• Biographical information
51
Name of Families• Name of the family [CORE]• Type of family [CORE]• Date associated with the family [CORE]• Place associated with the family [CORE if…]• Prominent member of the family [CORE
if…]• Hereditary title• Family history
52
Name of Corporate Bodies• Preferred name [CORE]• Location of conference, etc. [CORE]• Number of a conference, etc. [CORE]• Other designation [CORE if…]• Associated institution [CORE if…]
53
Name of Corporate Bodies• Date associated with the body [CORE
if…]• Language• Address• Field of activity• Corporate history
54
Name of a Place • Name of the place [CORE]• Identifier for the place [CORE]
But remember that Place Names as Jurisdictions follow RDA Chapter 11 Corporate Body instructions!
5555NAR access point is highlighted
Creating a NEW NAR
5656
Fixed fields, 040, 1XX, 670 fields input automatically
Creating a NEW NAR
5757
Creating a NEW NAR
58
Closing: Don’t Agonize!• The file is dynamic; any cataloger
with more information may improve the NAR in the future
• Be confident! You’re the expert, with the item in hand
59
Thank you!
Cooperation by all partners improves the authority and bibliographic databases!