Module 5: MARC Encoding of Persons and Corporate Bodies

advertisement
MARC Encoding of
Persons/Corporate
Bodies; Changes in the
LC/PCC Authority File
046 and 3XX Fields










046
368
370
371
372
373
374
375
377
378
Special coded dates (R)
Other attributes of P-CB (R)
Associated place (R)
Address (R)
Field of activity (R)
Associated group (R)
Occupation (R)
Gender (R)
Associated language (R)
Fuller form of personal name (NR)
See http://www.loc.gov/marc/authority/ecadhome.html for
complete information about these fields.
2
James/Kuhagen for VLA -- Feb. 5, 2013
Other MARC Changes for Use
in NARs
Specific for RDA:

008/10 = z

value "z" (Other) for use in 008/10 for RDA
o 040 (Cataloging source) subfield $e = rda
Added for RDA, but can be found in
AACR2 NARs:

4XX-5XX – “r” in $i or $4


3
value used in control subfield $w position 0
Subfield $i – Relationship information – Use
phrase or term from Appendix J or K of RDA
James/Kuhagen for VLA -- Feb. 5, 2013
New MARC 21 Fields –
Overview





4
Only 2 fields have defined indicators – in all of
the other fields the indicators are undefined
(blank)
All except for 046 and 378 have subfields $a or
$b
Most have subfield $2 (Source) defined
Most have subfields $0 (Record control number)
and $4 (Relator code) defined but these are
not routinely used
Most have subfields $6 (Linkage) and $8 (Field
link and sequence number) defined but these
are not used in the LC/NAF
James/Kuhagen for VLA -- Feb. 5, 2013
New MARC 21 Fields –
LC/NAF Procedures






5
Best practices given in DCM Z1
All are optional
Provide in numerical order by MARC 21 field
Repeatable subfields may be repeated in the
same field
If a source subfield ($2) or date parameters
($s or $t) are needed, repeat the field
670s must be provided to support information
used as part of a 1XX or 4XX
James/Kuhagen for VLA -- Feb. 5, 2013
New MARC Fields in NARs
Note that AACR2 coded authority records
may have some of these fields
008/10
040
WaU
046
100 1
370
372
373
375
400 1
510 2
6
c
$a DLC $b eng $c DLC $d PPi-MA $d DJBF $d DLC $d
$f 19400707
$a Starr, Ringo
$a Liverpool, England
$a Rock music $2 lcsh
$a Beatles $2 naf $s 1962 $t 1970
$a male
$a Starkey, Richard
$ w r $i Group member of: $a Beatles
James/Kuhagen for VLA -- Feb. 5, 2013
What makes a NAR RDA?


Many AACR2 headings have had 046 and
3XX fields added either by Phase 1 (see
slides 15-20) programmatically or by
catalogers
To be RDA, a NAR must have



7
008/10=z and
$e rda
Remember a NAR may be coded “rda” and
not be correct....so watch out for typos!
James/Kuhagen for VLA -- Feb. 5, 2013
Changes in the LC/PCC
Authority File
Background

During RDA Test, catalogers could make new
RDA name authority records (NARs) and add
7XX forms to existing AACR2 NARs

Example:
100 1 $a Barkley, Charles, $d 1963700 14 $a Barkley, Charles $q (Charles Wade),
$d 1963-

9
After the decision was made to adopt RDA,
several PCC Task Groups were formed,
including one for “acceptable headings”
James/Kuhagen for VLA -- Feb. 5, 2013
Acceptable Headings Task
Group

PCC Task Group on AACR2 & RDA and
Acceptable Headings Categories (2011;
Phil Schreur)


Made recommendations on what
constituted “acceptable” for RDA and
suggestions on how to convert the
authority file
How to resolve competing issues?
• Minimizing unnecessary changes
• Converting a working file being maintained
by both AACR2 and RDA catalogers
10
James/Kuhagen for VLA -- Feb. 5, 2013
3 Categories of Records

Authority records that are already
“acceptable for use” under RDA (over 95%;
7.6 million)




11
Identical, or
Differences based on information available
at the time of cataloging (not cataloging
rules)
Authority records are probably not
acceptable under RDA or need a human
decision (approximately 350,000)
Authority records that could be made RDA
compatible by an automated process
(approximately 350,000)
James/Kuhagen for VLA -- Feb. 5, 2013
Acceptable (Dates of a person)



AACR2 heading established without a date of
birth/death, but date(s) subsequently recorded
in 670
Optional addition in AACR2 and RDA unless
conflict
Example:

Existing AACR2 heading:
• Pliny, $c the Elder

Possible RDA reformulation:
• Pliny, $c the Elder, $d 23-79

12
Cataloger can recode heading to RDA and
record dates in 046
James/Kuhagen for VLA -- Feb. 5, 2013
Acceptable (Fuller form of
name)



AACR2 heading established without a fuller
form of name
AACR2 was more restrictive than RDA about
when it was added optionally
Example:

Existing AACR2 heading:
• Presley, Elvis, $d 1937-1977

Possible RDA reformulation:
• Presley, Elvis $q (Elvis Aron), $d 1937-1977

13
Cataloger can recode the heading to RDA and
record the fuller form of name in 378 $q
James/Kuhagen for VLA -- Feb. 5, 2013
But what about the other
categories?

PCC Acceptable Headings Implementation
Task Group (2012; Gary Strawn)


Detailed specifications of the categories and
recommended changes
Designed strategy for:
• How many records to update
• When/how/where to update the records; 5 scenarios
proposed

14
Also discussed recoding all acceptable
headings as RDA, but that was deferred
James/Kuhagen for VLA -- Feb. 5, 2013
The Plan
15

Phase 1: mark all records that are
known to be (or likely to be)
incompatible with RDA, unless they are
a candidate for a Phase 2 change

Phase 2: make ‘mechanical’ changes
to any record that meets specific criteria
James/Kuhagen for VLA -- Feb. 5, 2013
Phase 1 Headings

Consist of three types:



pre-AACR2 records (008/10=a or b)
AACR2-compatible records (008/10=d)
Known conditions that make it likely the
record should be reviewed by a human
before re-coding to RDA or reformulating

EXCEPTION:

If the record is also a candidate for
mechanical changes in Phase 2, it was not
considered under Phase 1
436,943 records in Phase 1

16
James/Kuhagen for VLA -- Feb. 5, 2013
Phase 1 Headings (cont.)

667 field added to NARs July 30August 20, 2012:
THIS 1XX FIELD CANNOT BE USED
UNDER RDA UNTIL THIS RECORD
HAS BEEN REVIEWED AND/OR
UPDATED
Heading still OK for AACR2 records if
008/10=c
 May be OK for RDA too, or may need
to be changed

17
James/Kuhagen for VLA -- Feb. 5, 2013
Phase 1 Enhancements

Since the record was being updated anyway
(667), a few supplementary fields were added
to the record when the information was readily
accessible to the program




18
046 field for dates of a person
378 field for fuller form of name of a person
382 (medium of performance), 383 (numeric
designation), and 384 (key) added for musical
works
Note these fields do not make the NARs RDA
records—only 008 and 040 coding do that
James/Kuhagen for VLA -- Feb. 5, 2013
Phase 1 “Known Conditions”

Conference headings


“Polyglot” and ampersand in $l




Many $c terms okay but not enough hits to be
excluded by program, e.g., “$c da Vinci”
Some $c terms like “$c Ph. D.” not allowed in RDA
Treaties
Music


19
Use multiple access points for each expression in
RDA
Some personal names with $c


Frequency words like “annual” omitted in AACR2
but not RDA
$s with “libretto” or “text”
$m certain medium of performance records
James/Kuhagen for VLA -- Feb. 5, 2013
Phase 1 “Known Conditions” –
Examples

Conference headings:



Polyglot and ampersand in $l



Virgil. $t Aeneis. $l Polyglot
Virgil. $t Aeneis. $l English & Latin
Some personal names with $c


20
European Dairy Conference $d (1987 : $c
London, England)
Law of the Sea Institute. $b Conference
Ignatius, $c of Loyola, Saint, $d 1491-1556
Wayne, E. J. $q (Edward Johnson), $c Sir, $d
1902-
James/Kuhagen for VLA -- Feb. 5, 2013
Phase 2 Headings

Primary purpose: update and convert (when
possible) records that have certain predictable
characteristics that are susceptible to machine
manipulation


21
Reduces the number of records that catalogers
have to change individually
Primary difference: unlike phase 1, 1XX,
4XX, and 5XX fields will actually be changed
in phase 2; references will be added for
former forms (when applicable); RDA 7XXs
will be removed
James/Kuhagen for VLA -- Feb. 5, 2013
Phase 2 Headings (cont.)

Around 400,000 authority records to be
updated!
30,000 records updated per day (March
2013)
 Distributed weekly to CDS customers
 Bibliographic records containing
headings will also be updated

22
James/Kuhagen for VLA -- Feb. 5, 2013
Major Changes in Phase 2
Expanding/replacing certain
abbreviations
 Major changes for some sacred
scriptures (Bible, Koran)
 Change from violoncello to cello
 Conversion of some X00 $c
 Selections as a conventional
collective title

23
James/Kuhagen for VLA -- Feb. 5, 2013
Phase 2 Changes –
Examples

Some abbreviations will be spelled out





Sacred Scriptures




24
AACR2: Miles, Linda, $d 1947 Jan. 3RDA: Miles, Linda, $d 1947 January 3AACR2: United States. $b Dept. of Labor
RDA: United States. $b Department of Labor
AACR2: Bible. $p O.T. $p Genesis
RDA: Bible. $p Genesis
AACR2: Koran
RDA: Qur’an
James/Kuhagen for VLA -- Feb. 5, 2013
Phase 2 Changes –
Examples (cont.)

Conversion of some X00 $c
Terms that are professions in $c
 AACR2: Blow, Jane, $c pianist
 RDA: Blow, Jane $c (Pianist)


“Selections” to “Works. Selections”
AACR2: Virgil. Selections
 RDA Virgil. Works. Selections

Note that “$k Selections” after the preferred title for a work (e.g.,
Iliad. Selections, Poems. Selections) will not change)
25
James/Kuhagen for VLA -- Feb. 5, 2013
More Information

Summary of Programmatic Changes to the
LC/NACO Authority File: What LC-PCC
Catalogers Need to Know


PCC Acceptable Headings Implementation
Task Group details and background
documents

26
http://www.loc.gov/aba/rda/pdf/lcnaf_rdapha
se.pdf
http://files.library.northwestern.edu/public/pc
cahitg/
James/Kuhagen for VLA -- Feb. 5, 2013
Conclusion
Policies change as we get closer to
implementation so don’t forget to...
 Check PCC page for interim guidelines



Check OCLC’s RDA page

27
http://www.loc.gov/aba/pcc/rda/RDA%2
0Interim%20Policies%20and%20Best%
20Practices.html
http://www.oclc.org/rda/about.htm
James/Kuhagen for VLA -- Feb. 5, 2013
Questions?
28
James/Kuhagen for VLA -- Feb. 5, 2013
Download