Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

RDA State of the Union


Published on

Presentation by John Baga and Bob Wolverton delivered to Mississippi Library Association's Technical Services Roundtable, April 19, 2013.

Published in: Education, Technology
  • Login to see the comments

RDA State of the Union

  1. 1. RDA “State of the Union”John Baga, Monographic Catalogerjbaga@library.msstate.eduBob Wolverton, Database Maintenance/Authority
  2. 2. • 2005: Began as AACR3• 2005: Renamed Resource Description andAccess and integrated principles of FRBR• 2008: Draft of RDA published• 2010: RDA Toolkit published in June• 2013: RDA officially implemented by LC
  3. 3. • Post March 31, 2013– All new authority records must be established andcoded according to RDA– National libraries are contributing only RDAbibliographic records
  4. 4. • LC/PCC Implementation Phase 2– March 27: 372,000 authority records have beenchanged to incorporate abbreviation substitutionslike ca., fl., d., b., Dept., etc.• April 8: Similar automated changes began forassociated headings in bibliographic records– Other changes include:• Bible headings, violoncello changed to cello, anduniform titles with “Selections” changed to “Works.Selections”
  5. 5. • OCLC Policy: still accepting AACR2 bibliographicrecords, but– Do not create duplicate records (one in RDA, another inAACR2) for the same resource– Never revert an RDA record to AACR2• Do it locally if you wish– Do not remove GMDs• [sound recording], [videorecording], [electronic resource]• Mix of AACR2 and RDA records will increase• Hybrid records will exist (RDA and AACR2elements on a single record)
  6. 6. • Cataloging community is drafting bestpractices
  7. 7. • Post April 2013: Online access to AACR2 viaRDA Toolkit subscription– Cataloger’s Desktop no longer provides accesswithout a subscription to the RDA Toolkit…• RDA Toolkit is still being edited for readability• Some examples are misleading and even wrong“The more I get into it, the more it seems like kabbalahor a plot outline from Tolkien, or at worst, the InternalRevenue Code.”—Aaron Kuperman, Library of Congress.
  8. 8. • Has not effected user experience yet…?– Many RDA fields are not yet indexed or displayingin OPACs– AACR2 records will outnumber RDA records in ourlocal catalogs for a while
  9. 9. Save the Date• March 31, 2016: OCLC’s day 1 for removingGMDs from all existing bibliographic records• Post 2016: MARC Replacement via LC’sBibliographic Framework (BibFrame)
  10. 10. Bad News• RDA will be a hassle initially– Retraining is costly and time consuming– RDA Toolkit is expensive and difficult to use– More time spent on authority work and originalcataloging– Inconsistency with legacy data– Benefits of RDA will not be seen until more OPACssupport FRBR
  11. 11. Good News• RDA is not so bad– Mainly cosmetic changes– Spelling out abbreviations should help patrons– Enhances authority records with more information,and reduces undifferentiated name headings– FRBR should improve access and OPACfunctionality– First stage in a progression towards linked data• Interconnected data on the Semantic Web, i.e. the wayWikipedia works
  12. 12. New MARC Fields for Authorities• 046 – Special Coded Dates• 370 – Associated Place• 371 – Address• 372 – Field of Activity• 373 – Affiliation• 374 – Occupation• 375 – Gender• 376 – Family Information• 377 – Associated Language• 378 – Fuller Form of Personal Name• 380 – Form of Work• 678 – Biographical or Historical Data
  13. 13. Authority Records• More relationships established– 110 2# $a Rolling Stones500 1# $i Group member: $a Mick Jagger• Distinguishing attributes to authority records– Fields of activity and occupations• 372 Political science $2 lcsh• 374 Journalists $2 lcsh– Usage of qualifiers• 100 1# Smith, John $c (Historian)
  14. 14. Authority Records Cont.• Avoid a split file– Any expression (name-title) record should be codedRDA if it is based on an RDA name authority record• LC Policy: When editing existing authorityrecords, NACO cataloger should evaluate andrecode it as RDA• PCC Policy: Unless correcting a conflict, do notchange an existing heading by adding orremoving a fuller form of name
  15. 15. This is not RDA 101• FRBR• Theory• All new MARC fields• Every change in RDA
  16. 16. New Ways of Thinking• Information taken from anywhere on the source– Brackets only used for outside sources, e.g. websites• Transcribe what you see on the piece– Even abbreviations!– Typos without [sic] or [i.e.]• More cataloger’s judgment– Many decisions are optional
  17. 17. • Latin abbreviations are goneAACR2 RDAS.l. (Sine loco) [Place of publication not identified]s.n. (sine nomine) [publisher not identified][et al.] [and others]ca. (circa) approximately[sic]
  18. 18. AACR2 RDAp. pagesv. volumes1 v. (unpaged) unnumbered pagescol. ill. color illustrationsb&w black and whitePub. Co. Publishing CompanyDept. DepartmentJan. JanuaryN.J. New Jerseybk. book2nd rev. ed. Second revised edition[18--?] [between 1800 and 1899?]cm cmin. in.
  19. 19. Transcribe What You See 245 10 CHANGING NORMS IN GLOBALIZATION 245 10 $a Letters From an Athiest246 1# $i Title should read: $a Letters from an atheist 245 10 $a ArChiTecTs GoNe WiLd!LC is sticking with AACR2 capitalization rulesOne librarian’s concern: “The title is the first thing auser looks at in the catalog and when they start seeingsome in all caps, some with spelling mistakes, etc., thisreally does make us look bad.”
  20. 20. New TerminologyAACR2 RDAChief source of information Preferred sourceHeading Access pointControlled heading Authorized Access Point (AAP)Main entry Preferred access pointAuthor CreatorEditor/translator ContributorArea of description Element??? Attributes??? Entities??? Manifestations
  21. 21. New MARC Fields (33X)• 336 – Content Type• 337 – Media Type• 338 – Carrier TypeBook336 ## $a text $2 rdacontent337 ## $a unmediated $2 rdamedia338 ## $a volume $2 rdacarrierDVD (AACR2) DVD (RDA)$h [videorecording] 336 ## $a two-dimensional moving image $b tdi $2rdacontent337 ## $a video $b v $2 rdamedia338 ## $a videodisc $b vd $2 rdacarrier
  22. 22. New MARC Fields Cont.• 344 – Sound characteristics• 346 – Video characteristics• 347 – Digital file characteristicsDigital file characteristics347 ## $a video file $b Blu-Ray $2 rda347 ## $a text file $b PDF $2 rdaSound characteristics344 ## $a digital $g stereo $2 rda344 ## $a digital $g surround $h Dolby Digital 5.1 $2 rdaVideo characteristics346 ## $a VHS $b NTSC $2 rda
  23. 23. New MARC Fields for Music• 382 – Medium of performance• 383 – Numeric Designation of a Musical Work• 384 – KeyBeethoven’s “Moonlight” Sonata100 1# $a Beethoven, Ludwig van, $d 1770-1827. $t Sonatas,$m piano, $n no. 14, op. 27, no. 2, $r C# minor382 ## $a piano383 ## $a no. 14, $b op. 27, no. 2384 ## $a C# minor
  24. 24. Production, Publication, Distributor,Manufacturer, Copyright Date• 264 replaces the 260– Used for all new original RDA records– 260 in RDA records may be changed to 264– 260/264 may co-exist in AACR2 and RDA recordsPublication, Distributor, and Copyright Date264 #1 $a Syracuse, New York : $b [publisher not identified], $c 2010.264 #2 $a [Place of distribution not identified] : $b Elect Distributors, $c 2012.264 #4 $c ©2009
  25. 25. Published MaterialsPublication 264 #1 $a Syracuse, New York : $b [publishernot identified], $c 2010.Distributor 264 #2 $a [Place of distribution notidentified] : $b Elect Distributors, $c 2012.Manufacture 264 #3 $a Starkville, Miss. : $b Redwood, $c[date of manufacture not identified]Copyrightdate264 #4 $c ©2009Unpublished MaterialsProduction 264 #0 $a [Starkville, Mississippi?] : $b[producer not identified], $c [1980?]
  26. 26. 264 “Cascading Vortex of Horror”Chain of 264s when publisher not identified264 #1 $a Jackson, Miss. : $b [publisher not identified], $c [date of publication notidentified]264 #2 $a [Place of distribution not identified] : $b [distributor not identified], $c[date of distribution not identified]264 #3 $a [Place of manufacture not identified] : $b [name of manufacturer notidentified], $c [date of manufacture not identified]264 #4 $c ℗2002
  27. 27. Other MARC Changes• 250 is repeatable:• Some “Extent” terms have changed:• 7XX $i – Relationship designationAACR2 RDA300 ## $a 1 sound disc 300 ## $a 1 audio disc300 ## $a 1 CD-ROM 300 ## $a 1 computer discEdition Statement250 ## First edition.250 ## Special edition.Relationship designation700 1# $i Parody of (work) $a Carroll, Lewis, $d 1832-1898. $t Alice’s adventures in Wonderland700 1# $i Translation of: $a Mitchell, Margaret, $d 1900-1949. $t Gone with the wind• 502 has subfields:Thesis Note502 ## $b Ph.D $c Yale University $d 2013.
  28. 28. Interesting…• Fictitious characters may now have nameheadings and be authors– 100 #0 $a Darth Vader (Fictitious character)
  29. 29. Relationship Designators• Known as relator codes in AACR2, e.g. $e ill.• RDA puts more emphasis on utilizing these– But they are optional• The “role” a person or corporate body playsRelationship Designators710 2# $a Miramax Home Entertainment (Firm), $e production company.700 1# $a Gorey, Edward, $d 1925-2000, $e illustrator.700 1# $a Eastwood, Clint, $d 1930- $e film producer, $e film director, $e actor.
  30. 30. Identifying an RDA Record• 040 $e rda• 336/337/338• Absence of abbreviations and Latin terms• Desc coded as i
  31. 31. Follow cm with a period only if490 follows immediately after.“One wonders if RDA would havebeen adversely affected ifsomeone sequestered the entireJoint Steering Committee on theday they came up with thisrule?”—Aaron Kuperman,Library of Congress
  32. 32. Converting Records: LC/PCCLC Policy: Do not apply RDA “rules”, likechoice of entry, to AACR2 records unlessrecoding the record as RDA– Do not touch existing 130, 240, 7XXPCC Policy: Any AACR2 records youupgrade should be recoded to RDA
  33. 33. Converting Records: OCLC• OCLC Policy: AACR2 monographic records canbe converted to RDA only if the cataloger hasthe original resource in hand• OCLC will perform a global “hybridization” ofAACR2 records to include RDA elements e.g.spelled out abbreviations, 33X, etc.
  34. 34. Enhancing• In the meantime, you may enhance AACR2 records toinclude the following:– Add more names to the statement of responsibility and asaccess points– Convert 260 to 264, or add additional 264 if needed– Change Latin abbreviations to their RDA equivalent, e.g.“S.l.” to [Place of publication not identified]– Spell out non-transcribed abbreviations, e.g. illustrations– Add 33X fields– Add relationship designators, e.g. $e author• Refer to PCC’s Guidelines for Enhancing & Editing non-RDA Monograph Records
  35. 35. Stay tuned for theRDA Implementation Panel!
  36. 36. RDA ImplementationJohn Baga, Monographic Catalogerjbaga@library.msstate.eduBob Wolverton, Database Maintenance/Authority
  37. 37. Do I have to use RDA?• Almost all new records createdby LC are RDA• LC’s National Authority File isintegrating RDA– OCLC will not accept new AACR2authority records• OCLC still accepts AACR2bibliographic records
  38. 38. Implementation Strategies• Create an RDA implementation plan now– Can you actually afford it?– When will you start cataloging with RDA?Decide on your Day 1.– Will you do any retrospective cataloging?– What is important to your patrons andstakeholders?• GMD?– Who needs to be trained?
  39. 39. Systems• Can your ILS handle RDA records?• Talk with your systems administrator or ILSvendor• Do the new MARC fields display?• What fields should you index?• Create a test server for your ILS and OPAC
  40. 40. OPAC• Retain GMD?– How will the 33X co-exist with GMDs?• Do the 336/337/338 fields display in your catalog?– Which 33X to display is being debated by the community– Display in brief or full record views?• What other libraries think about the 33X:– Do not make sense to the user– Some are indexing these– Some are hiding them from public display– Others suggest indexing/displaying 336 and 338, but notthe 337
  41. 41. 337 Media Type
  42. 42. Copy Cataloging• Accept RDA copy as-is?– If accepting RDA records, train copy catalogers tomake local edits correctly.• Convert AACR2 records to RDA in your localcatalog?– Change AACR2 headings to be RDA compliant?– Add relationship designators?– Delete 33X fields?– Put GMDs back in?
  43. 43. General Cataloging• Begin examining RDA’s Core Elements(required data in bibliographic records)• Plan your training– What does it mean for your backlog?– Set a timeline and goal– Use the latest resources– Where to begin?
  44. 44. Original Cataloging• Create a policy about which optional RDAelements will be used in your cataloging– Will you simply follow the LC-PCC PolicyStatements (new version of LCRIs)?• Assign relationship designators?– 100 $a Smith, John. $e author– 100 $a Wilson, Sam. $e composer
  45. 45. Implementation Tips• Train your copy catalogers right now to understand RDAchanges– Create a simple cheat sheet– Copy Cataloging New Monographs: Fields to Check• Draft a list of local policy decisions and documentation• Inform your technical and public staff what they’ll noticeimmediately:– No GMD– Fewer abbreviations– 33X fields– 7XX relationship designators– Some changes to headings
  46. 46. Implementation Tips• Coordinate and communicate with alldepartments• Show library staff sample records• Get feedback from staff and administrators
  47. 47. RDA Implementation at MSU• Subscribed to the RDA Toolkit in summer 2012• Completed RDA NACO authority training in late 2012– Training webinars took a week– Submitted authority records at our own pace to LC/PCCreviewers– Granted independence in creating RDA authority recordsNovember 2012• Currently undergoing RDA NACO series training– Training webinars took three hours– Review process may take several weeks• Bibliographic training planned for late 2013
  48. 48. RDA Implementation at MSU• MSU catalogers closely follow RDA-L, PCC-L,OCLC-CAT, and AUTOCAT• Keep technical services staff informed• Specify what new fields and MARC changesshould be addressed to systems• Systems created a test server for our ILS andOPAC so we can experiment with RDA records
  49. 49. RDA Implementation at MSU• Some deliberations– Implications for consortium libraries– Keep the GMD or not?• Training copy catalogers• Formal presentation to public services staffand soliciting their feedback• Our ILS (Sirsi) will load an RDA update in theFall
  50. 50. Suggested Implementation Plan1) Train your copy catalogers to recognize RDA records2) Make sure your ILS can handle RDA fields3) Create test records in your system4) Decide on what RDA fields should display5) Review LC and PCC RDA documentation6) Make local policy decisions7) Train original catalogers to use RDA Toolkit8) Complete the NACO training webinars (only if you wish to contributeauthority records)9) Complete LC’s RDA bibliographic training webinars10) Meet with your staff regularly11) Make a presentation to your library about RDA12) Monitor PCC website (or PCC-L) and OCLC-CAT for latest updates13) Endure Enjoy RDA
  51. 51. Training Resources• Terminology– AACR2 Terminology vs. RDA Terminology– Glossary of RDA and FRBR Terminology• Implementation– PCC’s Post RDA Implementation Guidelines andStandards– Building an RDA Implementation Strategy for yourLibrary (University of Chicago)• Cataloging– RDA Record Examples– Changes From AACR2 to RDA
  52. 52. Webinars• Bibliographic – LC RDA Training• Authority - NACO RDA Bridge Training• Series – NACO RDA Series Bridge Training• Various formats – ALCTS Webinars• Serials – CONSER training
  53. 53. New Publications• Look for these at your nearest bookstore
  54. 54. Free Online Resources• FRBR– What is FRBR? A Conceptual Model for the Bibliographic Universe -• AACR2 Compared with RDA– AACR2 Terminology vs. RDA Terminology -– AACR2 to RDA for audiovisual catalogers -– Changes from AACR2 to RDA -– RDA Changes from AACR2 in MARC Tag Order -• RDA Cataloging by Format– Electronic Resources -– Music scores/sound recordings -– Videorecordings -• RDA Implementation– Building an RDA Implementation Strategy for your Library (University of Chicago) -– RDA Training and Implementation at University of Waterloo -– Implementation and Coding Practices at Carnegie Library of Pittsburgh -• RDA MARC Fields– RDA in MARC Bibliographic Data -– RDA in MARC: Summary of Additions -– RDA Content-Media-Carrier Values for Various Types of Resources -• RDA Test Libraries Resources– University of Chicago -– North Carolina State University -• RDA Webinars– ALCTS -– PCC RDA Training -• RDA Record Examples– CD-ROMs/DVD-ROMs -– Videos -• Official Documentation and LC/PCC/OCLC Policies– LC’s RDA Website -– RDA Core Elements -– OCLC RDA Policy Statement -– PCC Guidelines for the 264 Field -– PCC Post RDA Implementation Guidelines and Standards -– RDA and PCC -– PCC’s Guidelines for Enhancing & Editing non-RDA Monograph Records -– RDA Toolkit -