Docstoc

MARC 21 Changes for RDA

Document Sample
MARC 21 Changes for RDA Powered By Docstoc
					RDA, MARC 21, and Access Points

     Presented at Casalini Libri
               March 22, 2011



           George A. Prager
      New York University Law School Library
         pragerg@exchange.law.nyu.edu




                                               1
                         Outline
• 1. RDA-related Changes to MARC 21
   – 1.1 Introduction
   – 1.2 Bibliographic Format
   – 1.3 Authority Format
   – 1.4 Future RDA-Related MARC 21 Changes

•   2. Personal Name Headings
•   3. Family Name Headings
•   4. Corporate Name Headings
•   5. Preferred Titles for Works and Expressions
•   6. Further Resources
                                                    2
              1.1 Introduction

• RDA alignment with FRBR and FRAD
  conceptual models
• RDA also a metadata element set
• Three relational database models underlie the
  FRBR model; RDA needs to support all three
• Scenario 2 implementation (linked bibliographic
  and authority records) for initial release of RDA




                                                      3
                     1.1 Introduction

• RDA/MARC Working Group (RMWG)
  – Established in March 2008 under auspices of
    British Library, Library and Archives Canada,
    and the Library of Congress
  – Submitted discussion papers and proposals at
    all MARBI* meetings, beginning in June 2008

  *MARBI    stands for ―Machine-Readable Bibliographic Information‖; it is an
    interdivisional committee of the American Library Association (ALA),
    ALCTS (Association for Library Collections and Technical Services);
    LITA (Library and Information Technology Association; and RUSA
    (Reference and User Services Association).

                                                                                4
             1.1 Introduction

• Basic principles given in MARC Proposal No.
  2008-05/1 (issued June 2008)
   – Lays the groundwork for the other RMWG
     discussion papers and proposals

• Mapping of RDA to MARC 21
  – Completely clean mapping is not possible for
    all RDA elements, due to different levels of
    granularity between the two


                                                   5
                  1.1 Introduction

• When are new MARC fields and subfields necessary,
  and when do differences in granularity between
  MARC and RDA not require format changes?
   – Increased parsing of data at point of data entry
     usually leads to increased cataloging and systems’
     implementation costs, so it must be balanced against
     user needs

   – Discussion Paper No. 2008-DP05/4: Items not
     requiring MARC 21 format changes for RDA (June
     12, 2008)


                                                            6
1.2 Bibliographic Format: Leader and
                 00X
  • Leader/18 Descriptive cataloging form
     – ―i‖ (contains ISBD punctuation) or ―blank‖
       (does not contain ISBD punctuation)
         • LC and most other U.S. libraries have used
           code ―i‖ during the RDA test and evaluation
           period

  • 007 Physical Description Fixed Field
     – Some new codes have been added, such as:
      007/01 ―e‖: computer disc cartridge
                                                    7
   008 Fixed-Length Data Elements

• New codes added here as well, primarily
  in 008/23 & 008/29 for Form of item

  – ―o‖ online
  – ―q‖ direct electronic




                                            8
       040 Cataloging Source

• $b language of cataloging (NR)
  – If English, use:
  – $b eng


• $e description conventions (R)
  – $e rda
  – Additional code/s may be applicable

  – 040 ## $a NNU-L $b eng $c NNU-L $e rda
                                             9
              336-338
   Content, Media, and Carrier Types

• Replacement of 245 $h General material
  designation by three new variable fields:

  – 336 Content type (RDA 6.9)
  – 337 Media type (RDA 3.2)
  – 338 Carrier type (RDA 3.3)



                                              10
              336-338
  Content, Media, and Carrier Types
• All three fields are repeatable
• All three terms can use the codes: other, or
  unspecified
• RDA term in $a and/or RDA code in $b
• Both subfields may be repeated if more than one
  type is appropriate, and terms or codes are from
  the same vocabulary
• Source term is given in $2
• Materials specified may be given in $3
                                                11
           336 Content Type (R)
• Used for identifying works and expressions
• RDA core element
• Previously only indicated in Bibliographic
  LDR/06 ―Type of record‖

• $a Content type term (R)
   – Use term from RDA 6.9.1
• $b Content type code (R)
• $2 Content type source (NR)
   – Use ―rdacontent‖


                                               12
           336 Content Type (R)

• Definition of “Content type” (RDA 6.9.1.1):
  ―Content type is a categorization reflecting the
  fundamental form of communication in which the
  content is expressed and the human sense
  through which it is intended to be perceived. For
  content expressed in the form of an image or
  images, content type also reflects the number of
  spatial dimensions in which the content is
  intended to be perceived and the perceived
  presence or absence of movement.‖
                                                  13
               336 Content Type (R)
Some common content types:
• 336 $a text                   336 $a notated music
use for printed text            use for score
• 336 $a still image            336 $a computer program
use for photograph               use for applications software
• 336 $a performed music
use for performances of music
• 336 $a two-dimensional moving image
use for motion picture
• 336 $a cartographic image
use for two dimensional map
• 336 $a spoken word
use for recorded speech

                                                                 14
            337 Media Type (R)

• Not a RDA core element
• Previously only indicated in Bibliographic 07/01
  ―Specific material designation‖
• $a Media type term (R)
   – Use term from RDA 3.2.1
• $b Media type code (R)
• $2 Media type source (NR)
   – Use ―rdamedia‖

                                                     15
                  337 Media Type (R)
• Definition of Media type (RDA 3.2.1.1):
―Media type is a categorization reflecting the general type of
   intermediation device required to view, play, run, etc., the content of
   a resource.‖
Some common media types:
337 $a unmediated
(content designed to be perceived directly though the human senses
   without devices
337 $a computer (media accessed remotely and directly)
337 $a video (media used with videocassette players, DVDs, etc.)
337 $a projected (media used to project both two and three
   dimensional images)
337 $a microform


                                                                         16
           338 Carrier Type (R)

• RDA core element
• Previously only indicated in field 007/01‖Specific
  material designation‖
• $a Carrier type term (R)
   – Use term from RDA 3.3.1.3
• $b Carrier type code (R)
• $2 Carrier type source (NR)
   – Use ―rdacarrier‖

                                                  17
          338 Carrier Type (R)

• Definition of carrier type (RDA 3.3.1):
―Carrier type is a categorization reflecting
  the format of the storage medium and
  housing of a carrier in combination with
  the type of intermediation device required
  to view, play, run, etc., the content of a
  resource.‖


                                               18
          338 Carrier Type (R)

• Some common carrier types (often
  matching or similar to what’s in 300
  $a):
• Volume, audiocassette, videocassette,
  computer disc, online resource, microform
  reel, microfiche, film reel



                                          19
               336-338
   Content, Media, and Carrier Types
Printed book:
 245 10 $a Cataloging legal literature

  336 ## $a text $b txt $2 rdacontent

 337 ## $a unmediated $b n $2 rdamedia

 338 ## $a volume $b nc $2 rdacarrier

                                         20
               336-338
   Content, Media, and Carrier Types
Online resource with text and audio:

 245 04 $a The Oyez Project : $b U.S. Supreme
 Court media.

 336 ## $a text $b txt $a spoken word $b spw $2
 rdacontent

 337 ## $a computer $b c $2 rdamedia

 338 ## $a online resource $b cr $2 rdacarrier   21
      100-111, 700-711 $e, $j & $4
     Relator Term and Relator Code
  Relator term (RDA 18.5)
• $e (100-110 and 700-710) (R)
• $j (111 and 711) (R)
   – Optionally, use RDA appendix I terms to express
      possible relationships between a resource and
      persons, families, and corporate bodies

   $4 Relator code (R)
   – Or use a code or codes from the MARC Code List for
     Relators (available at:
     http://www.loc.gov/marc/relators/)

                                                       22
 100-111, 700-711, $e, $j & $4
Relator Term and Relator Code
100 1# $a Sacher, Johan, $e author.

245 10 $a Sacher on torts / $c Johan Sacher ;
illustrated by Yvonne Sacher ; edited and
translated by Gregor Schwartzbrot.

700 1# $a Sacher, Yvonne, $e illustrator.

700 1# $a Schwartzbrot, Gregor, $e editor, $e
translator.
                                            23
        380-384 (R); 490 $x ISSN
• 380-384 (see Authority Format)

• 490 $x ISSN made repeatable

  – ISSN of subseries must be recorded, if it
    appears in the resource (RDA 2.12.16.3)

  – Optional omission:
    Record only ISSN of subseries, and omit the
    ISSN of the main series
                                                  24
                502 Dissertation Note (R)
Enhanced 502 Dissertation note (RDA 7.9)*
New subfields for RDA sub-elements:

• $b Degree type (NR)
• $c Name of the granting institution (NR)
• $d Year degree granted (NR)
• $g Miscellaneous information (R)
• $o Dissertation identifier (R)
502 ## $b LL.M. $c New York University Law
  School $d 2010
*The entire dissertation note may still be recorded in one $a

                                                                25
       518 (R) & 033 (R)
 Date/Time & Place of an Event
New subfields added to 033 and 518 (all are
 repeatable):

033 $p Place of event (controlled or uncontrolled)
    $2 Source of term (for $p only)

518 $d Date of event (controlled or uncontrolled)
    $o Other event information
    $p Place of event (controlled or uncontrolled)
    $2 Source of term (for $p only)

                                                26
                 518 & 033
        Date/Time & Place of an Event


• 518 $a may still be used for entire contents of
  note

518 ## $o Broadcast $p Colorado Convention
  Center, Room 601-603, Denver, Colo. $d 2010
  July 12, 4:00-5:15 pm. EST



                                                    27
  700-730 $i Relationship Information

• Relationships between resource described in
  700-730 field and resource described in the
  1xx/245 field (RDA 24.5)
• Give RDA Appendix J term (resource to
  resource)

• Use $i as first subfield (newly defined for these
  fields)


                                                      28
700-730 $i Relationship Information

100 1# $a Beard, Henry.

245 10 $a Bored of the rings.

700 1# $i parody of (work) $a Tolkien, J. R.
  R. $q (John Ronald Reuel), $d 1892-1973.
  $t Lord of the rings.

                                           29
       76X-78X $i & $4 Relationship
     Information & Relationship Code
• Relationship designators and codes for relationships
  between resource described in 76X-78X field and
  resource described in 1XX/245 field

• $i Relationship information (R)
   – Give RDA Appendix J term
   – Use $i as first subfield
   787 08 $i reproduction of (manifestation) $a Verdi, Giuseppe, $d
     1813-1901. $t Otello. $d Milan: Ricordi, c1913
• $4 Relationship code (R)(newly defined in 76X-78X
  fields)
                                                                      30
           1.3 Authority Format

• New codes and fields

• 008/10 Descriptive cataloging rules
   – Use ―z‖ other

• 040 $e (R) Description conventions
   – Use ―rda‖



                                        31
       1.3 Authority Format: 336 (R)
               Content Type
• Used only in title or name/title authority records

• Subfields and usage similar to usage in
  Bibliographic Format

   – $a Content type term (R)
   – $b Content type code(R)
   – $2 Source (NR): use ―rdacontent‖
   – $3 Materials specified (NR)

                                                       32
   1.3 Authority Format: 046, 370-384
• RDA (0.6.3) allows certain elements to be recorded
  either as part of access point for the entity, as separate
  identifying elements, or both
• New fields and subfields ―contain additional information
  about characteristics of heading entities in fields 100-
  185‖
• Fields 046, 370-383 are repeatable (only 384 is not)
• Source of information for 046, 370-377:
   – Give in $v, $u, or in 670 field
• ―$0‖, Authority record control number or standard
  identifier, such as an International standard name
  identifier (ISNI), is valid for most of these fields, as well
  as the 5XX and 7XX authority fields, but this subfield will
  not be used in NACO records until it can be supplied
  automatically.*                                               33
      1.3 Authority Format: 046 (R)
          Special Coded Dates
• Applicable for persons, families, corporate
  bodies, works, or expressions
   – $f Birth date (NR) $g Death date (NR)
   – $k Beginning or single date created (NR)
   – $l Ending date created (NR)

  – $s Start period (NR) $t End period (NR)
  – $u Uniform resource identifier (R)
  – $v Source of information (R)
  – $2 Source of date scheme (NR)               34
     1.3 Authority Format: 046
       Special Coded Dates

100 1# $a Black, Henry Campbell, $d 1860-
 1927
046 ## $f 1860 $g 1927

110 2# $a American Association of Law
  Libraries
046 ## $s 1906
(founded in 1906)
                                            35
  1.3 Authority Format: 370-377

370 Associated place
371 Address
372 Field of activity
373 Affiliation
374 Occupation
375 Gender
376 Family information
377 Associated language

                                  36
        1.3 Authority Format: 370 (R)
              Associated Place
• $a Place of birth (NR) $b Place of death (NR)
  $c Associated country (R)
• $e Place of residence/headquarters (R)
• $f Other associated place (R)
• $g Place of origin of work (R)
• $s Start period (NR)    $t End period (NR)
• $u Uniform resource identifier (R)
• $v Source of information (R)
• $2 Source of term (NR)
                                              37
           1.3 Authority Format: 370
               Associated Place
• RDA core element when needed to distinguish
  two persons, corporate bodies, families, works,
  or expressions with the same name or title
100 1# $a Smit, Hans
370 ## $a Amsterdam, The Netherlands
(born in Amsterdam, The Netherlands)

130 #0 $a Insurance law journal (Chicago, Ill.)
370 ## $g Chicago, Ill.
(place of publication: Chicago, Ill.)

                                                    38
 1.3 Authority Format: 371 (R) and 373 (R)
          Address and Affiliation
• 371 Address (RDA 9.12.1.1 & 11.8.1.1)
   – Expands upon information given in field 370
   – Modeled on Bibliographic field 270: Address
• 373 Affiliation (RDA 9.13.1.1)
   – $a Affiliation (R)
   – $s Start period (NR) $t End period (NR)
   – $u Uniform resource locator (R)
   – $v Source of information (R)
   – $2 Source of term (NR)
                                                   39
     1.3 Authority Format: 371 and 373
          Address and Affiliation
100 1# $a Smit, Hans

371 ## $a Columbia University School of Law, 435
  West 116 Street $b New York $c NY $e 10027
  $u http://www.law.columbia.edu/fac/Hans_Smit

373 ## $a Columbia University. School of Law $2
  naf $s 1960 $u
  http://www.law.columbia.edu/fac/Hans_Smit

                                                  40
 1.3 Authority Format: 372 (R) and 374 (R)
       Field of Activity & Occupation
• 372 Field of Activity (RDA 9.15.1.1)
• 374 Occupation (RDA 9.16.1.1)
   – Both fields required for a person whose name
     consists of a phrase or appellation not
     conveying idea of a person
   – Also required for other persons, when needed
     for differentiation
   – 372 $a rare book collector
   – 374 $a catalog librarian $2 dot $s 1981
                                                41
      1.3 Authority Format: 375-377
•   375 Gender (R) (RDA 9.7)
100 1# $a Smit, Hans
 375 ## $a male

•   376 Family Information (R)(RDA 10.3, 10.6,10 .7)
100 3# $a Yan (Family : China)
370 ## $c China
376 ## $a Family

•   377 Associated Language (R) (RDA 9.14.1.1, RDA
    11.7.1)
110 2# $a Canadian Bar Association
377 ## $a eng $a fre

                                                       42
      1.3 Authority Format: 380 (R)
              Form of Work
• Class or genre to which work belongs. Helps to
  distinguish one work from another work with
  same name

• RDA core element when needed to differentiate
  two works (RDA 6.3)

• No controlled list of terms in RDA


                                                   43
          1.3 Authority Format: 380
                Form of Work
• May use uncontrolled term or term from
  controlled list in $a Form of work

• $2 Source of term (if using controlled term)
   – Code from Subject Heading and Term Source
     Codes

130 #0 $a Street legal (Television program)
380 ## $a Television program
                                              44
      1.3 Authority Format: 381-384

• 381 (R) Other distinguishing characteristic of the
  work/ … of the expression (RDA 6.6 & 6.12)
130 #0 $a Research report (South African Law
  Commission
381 ## $a South African Law Commission

• 382 Medium of performance (R) (RDA 6.15)
• 383 Numeric designation of a musical work (R) (RDA
  6.16)
• 384 Key (NR) (RDA 6.17)

                                                       45
      1.3 Authority Format: 400-430
           See From Tracings

• 400-411 Relator term $e
• 400-430 Relationship information $i
• 400-430 Relationship code $4 (defined in
  2009)

• LC did not use any of these subfields during the
  RDA test

                                                 46
      1.3 Authority Format: 500-530*
         See Also From Tracings
• $i Relationship information (R)
   – Use subfield $i for relationships other than
     earlier/later or pseudonym
   – Give RDA appendix J term (resource to resource) or
     Appendix K term (name to name)
   – Use $w/0 ―r‖ (defined in 2009)

• $4 Relationship code (R) (defined in 2009)
       LC did not use code during the RDA test
   *Examples in MARC 21 authority format

                                                          47
        1.3 Authority Format: 7XX
         Heading Linking Entries
• Adding RDA Form of Heading to AACR2
  Authority Record (RDA test and evaluation
  periods):
   – Keep AACR2 form in 1XX field of record
   – Keep record coded as AACR2
   – Add RDA form in 7XX field (whether the
     same, or different than, the AACR2 form)
      • Use second indicator ―7‖
      • Use ―$2 rda‖
                                                48
        1.3 Authority Format: 7XX
         Heading Linking Entries
100 1# $a Zimbalist, Efrem, $d 1923-
700 14 $a Zimbalist, Efrem, $c Jr., $d 1923- $2 rda

• Adding AACR2 Form of Heading to RDA
  Authority Record (RDA Test Period):
  – Keep RDA Form in 1XX field
  – Keep record coded as RDA
  – Add AACR2 form in 7XX field (whether the
    same, or different than, the RDA form)
  – Use 1st indicator ―1‖ and 2nd indicator ―4‖   49
1.4 Future RDA-Related MARC 21 Changes

• At the January 2011 MARBI meetings held
  during the American Library Association
  Conference, several discussion papers
  were presented concerning RDA-related
  changes to MARC 21. These papers will
  be brought back as proposals in June
  2011, and will most likely result in further
  changes to the MARC 21 formats

                                             50
1.4 Future RDA-Related MARC 21 Changes

• 1. New fields or subfields for publication,
  distribution, production, and manufacture
  statements, and copyright (RDA 2.7-2.11),
  one of the following options is likely:
  – Add a 2nd indicator to field 260 for function of
    statement. Use 2nd indicator ―blank‖ for legacy data
  – Define new fields (264, 266, 267-268), keep field 260
    for legacy data
  – In either case, a new field or subfield would be
    defined for copyright date
  Further information: Discussion Paper No. 2011-DP01
    (available at: http://www.loc.gov/marc/marbi/2011/2011-dp01.html)

                                                                        51
1.4 Future RDA-Related MARC 21 Changes

• 2. Language of expression (RDA 6.11) two options:
options:
   – Field 041 may be defined in Authority format
   – Field 377 (Associated language) may have its definition
     broadened to include Language of the expression


• 3. Associated institution (RDA 11.5):
  A core element for conferences in many cases, and
  sometimes for other corporate bodies
   – Field 373 (Affiliation, RDA 9.13) could be broadened, possibly a
     new subfield



                                                                    52
1.4 Future RDA-Related MARC 21 Changes

 • 4. Fuller form of name (RDA 9.5)
    • Core element when needed to distinguish a person from another
      person with the same name
    • Subfield $q would continue to be used in access points
    • Field 378 has been suggested.
 • 5. Type of jurisdiction (RDA 11.7.15 and 11.13.1.6)
    • Added to the name of a government other than a city or town when
      needed to differentiate between access points for two or more
      governments with the same name
    Example: Preferred name: Cork (Ireland : County)
    Type of jurisdiction added as an element: County
    • Field 334 has been suggested

 Further information on nos. 2-5: Discussion paper No. 2011-DP02
   (http://www.loc.gov/marc/marbi/2011/2011-dp02.html)
                                                                      53
1.4 Future RDA-Related MARC 21 Changes

• 6. Identifying work, expression, and
  manifestation records in the MARC 21
  Bibliographic, Authority, and Holdings
  Formats
   – Field 883 (Entity type) proposed for all 3
     formats
   – $a for Primary entity type term (work,
     expression, manifestation, or item)
   – $b for Primary entity type code (―w‖ work, etc.)
   More information: Discussion Paper No. 2011-
     DP03
   (available at: http://www.loc.gov/marc/marbi/2011/2011-dp03.html)

                                                                       54
1.4 Future RDA-Related MARC 21 Changes

• 7. Adding MARC fields or subfields for each of the carrier
  attributes listed in RDA Chapter 3; likely fields:

   – Field 340 Physical Medium; new subfields would be added for
     RDA elements Generation, Layout, Font, etc.
   – Field 344 Sound Characteristics (New)
   – Field 345 Projection Characteristics of Motion Picture Film (New)
   – Field 346 Video Characteristics (New)
   – Field 347 Digital File Characteristics (New)

   More information: Discussion Paper No. 2011-DP04
    (available at: http://www.loc.gov/marc/marbi/2011/2011-dp04.html)




                                                                        55
        2. Personal Name Headings
• Major changes in RDA:
  a. Personal names now include fictitious entities
  (RDA 9.0)
  May be represented by authorized access points, if they
  are presented in resource as having some kind of
  responsibility for work

100 0# $a Cowardly Lion.
245 10 $a What REALLY goes on in the land of OZ / $c
  as recounted by the Cowardly Lion.




                                                        56
       2. Personal Name Headings

• b. Variant spellings in Preferred name (RDA
  9.2.2.5.4)
   – Choose the form found on the first resource
     received
• c. Individuals with more than one identity
  (RDA 9.2.2.8)
   – May now choose the name associated with
     each identity as the preferred name for that
     identity (unlike AACR2, no longer limited to
     contemporary persons)

                                                    57
       2. Personal Name Headings

• d. Words, etc., indicating relationship
  following surnames (RDA 9.2.2.9.5)
       • Words or numerals indicating relationships
         with the preferred name are always
         included in the heading (in AACR2, they
         were only included after surnames in order
         to break conflicts)
        100 1# $a Saur, Karl-Otto, $c Jr.
     (In Portuguese, such words are treated as
     part of the surname)
                                                  58
      2. Personal Name Headings
e. Date associated with the person (RDA 9.3):
RDA has three date elements: Date of birth, Date of death, and
   Period of activity of the person

Dates for the Period of activity of the person are added if birth and
  death dates are both unknown
  AACR2 (22.17 & LCRI) didn’t use ―dates of activity‖ for 20th
  century persons, RDA has no date restrictions, LCPS 9.19.1.5:
  LC adds dates of activity only if needed to break a conflict
RDA allows only the abbreviations in Appendix B.
―B.C.‖ and ―A.D.‖ are the only abbreviations allowed with personal
  names



                                                                    59
    2. Personal Name Headings

e. Date associated with the person (cont.):
―century‖ is used, not ―cent.‖
―b.‖ and ―d.‖ are not used, LC catalogers will
  use a hyphen after the date of birth, and a
  hyphen before the date of death (LCPS
  9.3.3.3)
―active‖ is used by LC, to replace the
  abbreviation ―fl.‖
―approximately‖ is used, not ―ca.‖

                                                 60
        2. Personal Name Headings

• f. Fuller form of name (RDA 9.5)
•    RDA allows a part of the name not represented in the
  preferred name ($a) to be added in all cases—not just
  when there is a conflict (as is the case in AACR2)
• LC practice is to always give the fuller form of name if
  known
• Statement of responsibility: George Prager
   – AACR2 form: 100 1# $a Prager, George, $d 1952-
   – RDA form: 100 1# $a Prager, George $q (George
      Allen), $d 1952-

                                                         61
       2. Personal Name Headings

• g. Persons known by a surname only (RDA
  9.2.2.9.2)
  Words or phrases associated with the name are
  treated as an integral part of the name (included
  in $a), not treated as additions to the name ($c):
  AACR2: 100 1# $a Seuss, $c Dr.
  RDA: 100 1# $a Seuss, Dr.



                                                   62
       2. Personal Name Headings

• h. Conflict resolution: additions to access
  points representing names (RDA 9.19.1.3-
  9.19.1.7)
   – 1st choice: Date of birth and/or death
   – 2nd choice: Fuller form of name, including
     elements not included in the $a (LCRI 22.17-
     20 gives this as the 4th of 5th choices, before
     making the heading undifferentiated:
     Example: 100 1# $a Clapper, John $q (John
     Samuel)

                                                   63
     2. Personal Name Headings
– 3rd choice: Period of activity of the person
  LCRI 22.17-20 allows ―flourished‖ and ―century‖ dates
  as the 6th and 7th choices to break conflicts, but only
  for persons living before the 20th century

– 4th choice: Term indicating profession or
  occupation of a person (9.16, 9.19.1.6)
   100 1# $a Galdi, Giovanni $c (Cataloger)
   • AACR2 would not allow this addition for a 20th or
     21th century person; LCRI 22.19 makes an
     exception for musicians



                                                         64
         2. Personal Name Headings
• 5th choice: Field of activity of the person (RDA 9.15,
  9.19.1.7)
Defined in RDA as: ―A field of endeavour, area of expertise,
  etc., in which a person is engaged or was engaged.‖
  100 1# $a Prager, George $c (Mountain climber)
  100 1# $a Cordola, Antonio $c (Violinist)
Additions to names not permitted in RDA:
   – Titles of position or office (―Rev.‖, ―Professor of law‖,
     ―Dr.‖)
   – Initials of academic degrees (―Ph. D.‖, ―J.D.‖)
   – Initials denoting membership in an organization

                                                            65
     2. Personal Name Headings
RDA does not include these attributes, as they are not
 included in FRAD. However, academic degrees and
 similar information can be given in a 670 field of the
 authority record, if desired

Undifferentiated names should be rare in RDA, because
 it allows qualification of all personal names (both pre-
 and post 19th century) by dates of activity for a
 person, terms indicating profession or occupation of a
 person, and terms indicating field of activity of a
 person



                                                          66
         3. Family Name Headings

• ―Families‖ not covered in AACR2. In RDA, they
  may be used as creators, etc.
• Useful for archival and genealogical collections

• Families defined in RDA (8.1.2):
―Two or more persons related by birth, marriage,
  adoption, civil union, or similar legal status, or
  who otherwise present themselves as a family‖



                                                       67
          3. Family Name Headings

   • Choosing the Preferred Name for the Family
     (10.2.2.3):
―Choose the name by which the family is commonly known
  … The name chosen may be the surname (or
  equivalent) used by members of the family, the name of
  a royal house or dynasty, or the name of a clan, etc.‖
   • Record the type of family: family, clan, royal house,
     dynasty (RDA core element 10.3)
   • Record significant dates associated the family (RDA
     core element 10.4)


                                                         68
      3. Family Name Headings

• Record a place associated with the family
  (RDA 10.5; core element if needed to
  distinguish from another family)
   • RDA option (10.10.1.4) to add this element
     if the addition assists in the identification of
     the family (LC applies)
• Record a prominent member or members of
  the family (RDA 10.6; core element if
  needed to distinguish the family from another

                                                    69
      3. Family Name Headings

– RDA option (10.10.1.5) to add this element if
  the addition assists in the identification of the
  family (LC applies)
100 3# $a Medici (Royal house : $g Medici,
  Lorenzo de’, 1449-1492)
Other RDA elements for family: Hereditary title
  (10.7), Family history (10.8), and Identifier
  (10.9, Core element)


                                                      70
               3. Family Name Headings
• LCPS for 10.0:
• Apply this chapter for distinctive family entities needed
  they are needed as creators
• Continue current subject cataloging practice for general
  family groupings (Subject Cataloging Manual H 1631)
• Separate authority records will exist in the LC/NACO file
  and the LCSH file*
• LC/NACO family records should include 667 note: This
  heading is not valid as a subject. Use a family name
  heading from LCSH
• *RDA access point in bibliographic record: 100 3# $a Smythe (Family : $d 1745-1995
    : $c Providence, R.I.)
•   Subject heading in bibliographic record: 600 30 $a Smith family



                                                                                  71
      4. Corporate Name Headings
• There are not so many changes for corporate
  names in RDA. We will discuss only the most
  significant:
• a. Variant spellings (RDA 11.2.2.5.1)
  RDA: Chose the form found in the first resource
  received (LCPS continues practice of using form
  resulting from official change in spelling)
   AACR2 (24.2C): Uses the form resulting from
  official change in spelling; if this doesn’t apply,
  then the most commonly found spelling in items
  issued by the body

                                                    72
      4. Corporate Name Headings

• b. “Department” vs. “Dept.”:
RDA will spell out ―Department‖, when it appears
  spelled out in the source for a corporate name.
  This is not a change from AACR2, but from the
  LCRIs which used the abbreviation ―Dept.‖
RDA: 110 1# $a Nebraska. $b Department of the
  Environment
LCRI: 110 1# $a Nebraska. $b Dept. of the
  Environment

                                                    73
    4. Corporate Name Headings

• c. Conference names (RDA 11.13.1.8)
  – Same instructions for conferences, exhibitions, fairs,
    festivals (AACR2 had different rules: 24.7 & 24.8)
  – Terms of frequency kept in conference names
    (AACR2 would leave them out):
  – RDA: 111 2# $a Biennial Symposium on
    Active Control of Vibration and Noise
  – AACR2: 111 2# $a Symposium on Active
    Control of Vibration and Noise

                                                             74
      4. Corporate Name Headings

• c. Conference names (cont.):
• AACR2 authority record (following LCRI 24.7B):
  No number, date, or place used for ongoing
  conference
• RDA authority record: Use all appropriate
  qualifiers for numbered conference (qualification
  for post-test period if being cataloged as a
  monograph)


                                                  75
      4. Corporate Name Headings
• c. Conference names (cont.)
  – Dates are omitted from name of exhibition, fair, or
    festival:
  RDA: Schweizerische Grönland-Expedition
  AACR2: Schweizerische Grönland-Expedition 1912/13
  – Location of conference (11.3.2)
  RDA: Unlimited number of locations can be given; each
    location is separated from the other by a semicolon
    (Appendix E 1.2.4)
  AACR2: If conference held in more than two places, use
    first place, followed by ―etc.‖
  – RDA: For an online conference, use ―Online‖

                                                      76
      5. Preferred Titles for Works and
                 Expressions
• RDA has made a few changes, mostly (I think)
  for the better. We’ll touch upon the most
  important ones:
• a. Parts of the Bible
   RDA (6.23.2.9): spells out ―Old Testament‖ and
  ―New Testament‖;
   AACR2: uses ―O.T.‖ and ―N.T.‖



                                                    77
      5. Preferred Titles for Works and
                 Expressions
a. Parts of the Bible (cont.)
RDA: leaves out the names of the Testaments in
  headings for the individual books or several
  books
 AACR2: includes names of Testaments in
  headings for individual books or several books
 RDA: 130 #0 $a Bible. $p Leviticus
 AACR2: 130 #0 $a Bible. $p Old Testament. $p
  Leviticus

                                                   78
      5. Preferred Titles for Works and
                 Expressions
  b. Collective uniform titles:
RDA (6.2.2.10): ―Works. Selections‖
AACR2 (25.9): ―Selections‖
  c. Bilingual and multilingual compilations of
 expressions of the same work
RDA (6.27.3), unlike AACR2 (25.5C), does not
 combine two or more names of languages, or
 use ―Polyglot‖ in $l of access points


                                                  79
       5. Preferred Titles for Works and
                  Expressions
Example: An English and Italian edition of Buzzati’s:
  Deserto dei tartari
RDA bibliographic record:
700 1# $a Buzzati, Dino, $d 1906-1972. $t Deserto dei
  tartari. $l English
700 1# $a Buzzati, Dino, $d 1906-1972. $t Deserto dei
  tartari. $l Italian
AACR2 bibliographic record:
100 1# $a Buzzati, Dino, $d 1906-1972.
240 10 $a Deserto dei tartari. $l English & Italian


                                                        80
      5. Preferred Titles for Works and
                 Expressions
• d. Librettos
• RDA (6.27.4.2) does not treat as musical work;
  enters independently:
RDA heading and reference on authority record:
100 1# $a Piave, Francesco Maria, $d 1810–1876.
  $t Ernani. $l Spanish
400 1# $a Verdi, Giuseppe, $d 1813–1901. $t
  Ernani. $p Libretto. $l Spanish


                                               81
              6. Further Resources
• Coyle, Karen. RDA Vocabularies for a Twenty-First
  Century Data Environment. Chicago, Ill. : American
  Library Association, 2010 (Library technology reports ; v.
  46, no. 2 Feb./Mar. 2010)
• Danskin, Alan. A Long and Winding Road: RDA from
  Principles to Practice; http://www.rda-
  jsc.org/docs/A_long_and_winding_road_format_150310.
  pdf (last updated March 16, 2010)
• EURIG-JSC seminar on RDA: "RDA in Europe: making it
  happen!" Aug. 8, 2010
  http://www.slainte.org.uk/eurig/meetings.htm
• Hart, Amy. The RDA Primer: a Guide for the Occasional
  Cataloger. Santa Barbara, Calif. : Linworth, 2010. ISBN:
  9781586833480 (also available as an e-book)
                                                          82
            6. Further Resources

• Joint Steering Committee for Development of
  RDA http://www.rda-jsc.org/rda.html (list of links)
• Kuhagen, Judith A. RDA Essentials. Connecticut
  Library Association. Nov. 4, 2010.
  http://www.rda-
  jsc.org/docs/ConnLA_Tech_6nov2010.ppt#413,
  142,Inform your library’s users
• LC documentation for the RDA … test
  http://www.loc.gov/catdir/cpso/RDAtest/rdatest.h
  tml (list of links)

                                                    83
           6. Further Resources

• Maxwell, Robert L. Introduction to RDA. Utah
  Library Association, May 14, 2010;
  http://www.rda-
  jsc.org/docs/RDA_part_1_201005.pdf
• Maxwell, Robert L. RDA in Depth: Differences
  Between RDA and AACR2. Utah Library
  Association, May 14, 2010; http://www.rda-
  jsc.org/docs/RDA_part_2_201005.pdf
• McCallum, Sally. RDA in MARC;
  http://www.loc.gov/marc/RDAinMARC29.html
  (last updated Jan. 5, 2011)
                                                 84
            6. Further Resources

• Oliver, Chris. Introducing RDA: a Guide to the
  Basics. Chicago : American Library Association,
  2010. ISBN 9780838935941
• RDA and OCLC
  http://www.oclc.org/rda/about.htm (list of links)




                                                  85
           6. Further Resources

• RDA and PCC
  http://www.loc.gov/catdir/pcc/RDA-PCC.html (list
  of links)
• Schiff, Adam L. Changes from AACR2 to RDA: a
  Comparison of Examples; http://www.rda-
  jsc.org/docs/BCLAPresentationWithNotes.pdf
  (last updated Apr. 22, 2010?)
• Tillett, Barbara B. RDA Changes from AACR2
  for Texts; http://www.rda-
  jsc.org/rdapresentations.html (last updated Jan.
  12, 2010?)
                                                86
Thank you.



             87