everything you need to know about

EVERYTHING YOU

NEED TO KNOW ABOUT Authority Control and RDA

La Donna Riddle Weber

Cataloging Librarian and Trainer

February 26, 2014

Purdue University Libraries

The Bible

• O.T and N.T. are dropped if specific books are

named

• AARC2 25.18A …. RDA 6.23.2.9, 6.30.22

• Bible. O.T. Ruth becomes Bible. Ruth

• Bible. N.T. Jude becomes Bible. Jude

• Bible. N.T. Gospels becomes Bible. Gospels

• If no specific book names use:

• Bible. Old Testament

• Bible. New Testament

Koran

• Koran becomes Qur’an

• And not just this scripture but any …

• RDA 6.23.2.5

• “Choose as the preferred title … the title by which it is most

commonly identified in reference sources in the language preferred

by the agency creating the data that deal with the religious group …

to which the scripture belongs.”

• Part of the move away from U.S. / Christianity-centric

rules and interpretations

• Again … has been changed in the NAF but local catalogs

need to be updated.

Some other tweaks

Dump the Dept.

• RDA changes Dept. to

Department

• This affects subject,

name, and series

authorities

What does that

mean??

• fl. (for flourished) in name

authorities changed to

“active”

• ca. (for circa) in

authorities changed to

“approximately

• These changes called for a major clean up in the NAF • To avoid split files, Library of Congress and

OCLC made global changes to these headings when RDA was adopted

• In March 2013 Library of Congress upgraded about 400,000 authority records making this change

• AND associated bibliographic records changed

• Took about thirteen days … 30,000 per day!!

Fictional entities

• I knew Geronimo Stilton wrote those books!!

• Fictional entities can be considered creators

• Code as person

• Families too, BTW

• RDA chapter 10

(Fictitious character)

• Now you see it, now you don’t

• 9.19.1.2 instructs to add it whether or not there is a

conflict. This contradicts the fact that it is not a core

element at 9.6

• The British Library has made another JSC proposal to

address this contradiction and it will be discussed at the

JSC meeting in DC in November 2013. ...

Name Authorities

• Titles and terms associated with surnames can now be

used

• AACR2 22.15C, 22.19B – don’t use Jr., Sr., III …

• GONE! Now we use them … most of the time …

• RDA 9.2.2.9.5

• Birth and death dates

• Option to add even when not needed to break conflict

• LC-PCC PS for 9.19.1.3: New Authority Records

LC practice/PCC practice for Optional addition: Add a date of birth

and/or date of death to new authority records, even if not needed to

distinguish between access points.

3xx fields • 3XX fields contain additional information about

characteristics of the heading entities in fields 100-185.

• All new 2009 through 2013

• Only 378 and 384 are not repeatable

• 336 – CONTENT TYPE The form of communication

through which a work is expressed. Field 336 information

enables expression of content types from various lists

when the authority is for a title or name/title

• 336 ## $a two-dimensional moving image $b tdi $2 rdacontent

• 336 ## $b prm $2 rdacontent

• 336 ## $a text $2 rdacontent $3 liner notes

368 Other Attributes of Person or

Corporate Body (R)

• Any attribute that serves to characterize a person or

corporate body or that may be needed for differentiation

from other persons or corporate bodies and for which

separate content designation is not already defined.

• For a person: Can include designations of the title of a

person or other attributes.

• For a corporate body: Can include designations indicating

the type of corporate body or jurisdiction, or other

attributes.

368 ## $a Television station

368 ## $a Firm

368 ## $b County

368 ## $b Village

368 ## $c Holiness

368 ## $c Seventh Day

368 ## $c Spirit

368 ## $c Saint

368 ## $d Princess

Content designator history

• Field 370 - Associated Place [NEW, 2009] 9.10

• Field 371 - Address [NEW, 2009]

• Field 372 - Field of Activity [NEW, 2009] 9.15

• Field 373 - Associated Group [RENAMED, 2011] Prior to

2011 was named "Affiliation“ 9.13

• Field 374 - Occupation [NEW, 2009] 9.16

• Field 375 - Gender [NEW, 2009] 9.7

• Field 376 - Family Information [NEW, 2009] 10.3, 10.6

• Field 377 - Associated Language [NEW, 2009] 9.14

• Field 378 - Fuller Form of Personal Name [NEW, 2011]

9.5

378

• Field 378 - Fuller Form of Personal Name [NEW, 2011]

• $q in pre-RDA records

• “grandfathered” in – leave if already in the record

• RDA / NACO uses field for conflict breaking

• LC-PCC PS for 9.19.1.4 [Fuller form of name]: New

Authority Records

• LC practice for Optional addition: Do not apply.

• PCC practice for Optional addition: Decision on application of the

optional addition is pending.

EXAMPLE 1

AACR2: 100 1 $a Bailey, R. Y. $q (Richmond Young), $d b. 1893

RDA: 100 1 $a Bailey, R. Y., $d 1893- 400 1 $a Bailey, R. Y. $q (Richmond Young), $d b. 1893 $w nnea

a) Use of abbreviation “b.” in subfield $d not valid under RDA

b) Subfield $q removed because subfield $d was being changed— Subfield $q not needed since there is no conflict

c) Make a see reference for the old valid form of heading, 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

Example 2

AACR2:

100 1 $a Walter, David, ‡d 1948-

RDA:

100 1 $a Walter, David, ‡d 1948-2012

400 1 $a Walter, David, ‡d 1948- $w nne

a) Date of death added and record recoded to RDA

b) Reference is valid under RDA

Example 3

AACR2:

100 1 $a Ryan, Robert S. $q (Robert Samuel), $d 1925-

RDA:



a) Normalizes to the same form as 1XX

b) Note that subfield $q retained at the time of recoding

in this case since no other changes are being made to

the 1XX

Example 4

AACR2:

100 1 $a Smith, John, $c pianist

RDA:

100 1 $a Smith, John $c (Pianist)

400 1 $a Smith, John, $c pianist

a) Normalizes to the same form as 1XX

• Field 380 - Form of Work [NEW, 2010]

• Field 381 - Other Distinguishing Characteristics of Work

or Expression [NEW, 2010]

• Field 382 - Medium of Performance [NEW, 2010]

• Field 383 - Numeric Designation of Musical Work [NEW,

2010]

• Field 384 - Key [NEW, 2010]

• Field 385 - Audience Characteristics [NEW, 2013]

• Field 386 - Creator/Contributor Characteristics [NEW,

2013]

Examples of Authority Records

• http://www.rdatoolkit.org/sites/default/files/examples_of_rd

a_authority_records_041113.pdf

http://www.rdatoolkit.org/sites/default/files/examples_of_rda_authority_records_041113.pdf



Problems to watch for

• 667 |aTHIS 1XX FIELD CANNOT BE USED UNDER

RDA UNTIL THIS RECORD HAS BEEN REVIEWED

AND/OR UPDATED

This is aimed at BIBCO/NACO/SACO libraries who

have the power to upgrade records

• Deleted authorities with “status” d

These remain in the authority file

|

FAST

• What will you do?? Keep? Or Delete?

• You can change your loading profiles so that FAST

headings automatically get removed as you load them.

(What do you do with 2nd indicator 1-7).

• You can change your authority maintenance options to

ignore FAST headings in bib records. Whether and how

you could do either of these depends on your ILS.

• If deleted or suppressed, you need not worry about

verification and would not clutter up the authority file.

VIAF

•Virtual International Authority File

•Transitioning from shared-governance

to VIAF Council with OCLC having

primary maintenance responsibility

•Now an OCLC service

•http://viaf.org/

http://viaf.org/

everything you need to know about

Documents