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.

Art NACO Pasadena 2013-04-29: Foundations

658 views

Published on

This material was prepared by the Program for Cooperative Cataloging and the Library of Congress.

Published in: Education
  • Be the first to comment

Art NACO Pasadena 2013-04-29: Foundations

  1. 1. NACO TrainingPrepared bythe Program for Cooperative CatalogingStanding Committee on Training
  2. 2. Learning Objectives (1)• At the end of the course, participants will beable to:– Consult and use MARC 21 Authority Format, LCGuidelines Supplement, and DCM Z1– Create and revise NARs according to RDA and theLC-PCC Policy Statements2Module 1. Foundations
  3. 3. Learning Objectives (2)• Apply content designation in accordancewith the MARC 21 Authority Format• Evaluate, update, and modify existingname authority records• Determine if a named entity isestablished through NACO or SACO• Understand NACO administrative details3Module 1. Foundations
  4. 4. Day 1: NACO Foundations• Authorities in a Shared Database• PCC NACO Principles and Parameters• Searching/BFM• Normalization• FRBR and FRAD• MARC 21 Authority Format4Module 1. Foundations
  5. 5. Day 2: Describing Personsand Describing Families• Persons: RDA Chapters 8 and 9• Families: RDA Chapters 8 and 10• Review LC-PCC PSs• Practicum and exercises5Module 1. Foundations
  6. 6. Day 3: Describing Corporate Bodies• RDA Chapters 8 and 11• Review LC-PCC PSs• Practicum and exercises6Module 1. Foundations
  7. 7. Day 4: Describing PlacesDescribing Works and Expressions• Places: RDA Chapters 12 and 16 (inconjunction with Chapter 11)• Works and Expressions: RDA Chapters 5 and 6(in conjunction with Chapters 8-11)• Review LC-PCC PSs• Practicum and exercises7Module 1. Foundations
  8. 8. Day 5: Making Changes to Existing NARsand NACO Administration• Changes to NARs (DCM Z1)• Review LC-PCC PSs & DCM Z1• Practicum and exercises• NACO administrative details8Module 1. Foundations
  9. 9. Day 1: NACO FoundationsThis module is designed to introduce NACOparticipants to:• The shared database environment• PCC NACO principles and parameters• MARC 21 Authority Format• LC Guidelines Supplement to MARC 21• DCM Z19Module 1. Foundations
  10. 10. NACO Principles:Authorities in a Shared Database10Module 1. Foundations
  11. 11. Standards in Card Catalogs“The Card Division” in the early 1900s 11Module 1. Foundations
  12. 12. Standards Today• We have moved away from limitations of cardcatalogs• LC is a member of PCC and must meet thesame standards as any NACO library12Module 1. Foundations
  13. 13. 13PCC Program OverviewNACOCONSERSACOBIBCOModule 1. Foundations
  14. 14. Name Authority Cooperative Program(NACO)• Over 785 NACO members–Full-level members–NACO funnel projects• Funnels may be based on geography,specialization (art, music), or language• NACO partners contribute nameauthority records to LC database viautilities14Module 1. Foundations
  15. 15. Exchanging Records• More standardization required• Local systems/utilities are different• Earlier MARC formats were diverse (US MARC,CanMARC, UK MARC)• MARC 21 is more universal15Module 1. Foundations
  16. 16. MARC 21 to BIBFRAME• Efforts are underway to transition from MARC21 to a new bibliographic framework• Collaborative process• Focus: translate the MARC 21 format to alinked data model– While retaining as much as possible the robustand beneficial aspects of MARC• Proposed model: BIBFRAME– http://bibframe.org/16Module 1. Foundations
  17. 17. 17Authority Record Creation and DistributionUtilitiesBritishLibraryLC/NACO AUTHORITY FILE (NAF)Utilities (such as OCLC and SkyRiver) and the British Librarycontribute authority records, which are then sent to LC.Each morning all contributed authority records, including LC’s,are redistributed to the BL, the utilities, and all CDS customers.Module 1. Foundations 17
  18. 18. High Value – Low EffortNACO’s goal:• To build a name authority file• For the greatest good of all• With the least amount of effort byparticipants18Module 1. Foundations
  19. 19. Dynamic File• The LC/NACO Authority File is a dynamic file,changing every 24 hours• Any record may be changed by another NACOparticipant for appropriate reasons19Module 1. Foundations
  20. 20. The Catalog Serves the UsersAccording to the Statement of InternationalCataloging Principles:• Controlled access points should be providedfor the authorized and variant forms of names• Controlled access points provide theconsistency needed for collocating thebibliographic records for sets of resources20Module 1. Foundations
  21. 21. NARs and the NAF• Name authority record (NAR) showsauthorized access point and variant accesspoints• LC/NACO Authority File (NAF) includes allNARs• Libraries choose levels of authority control• DCM Z1 Introduction describes LC’s policiesfor when to create a name authority record21Module 1. Foundations
  22. 22. Cataloger’s Judgment• Use judgment when applying manyinstructions• A different choice isn’t always an error, sorespect the judgment of your colleagues• Leave a correct, unique authorizedaccess point alone22Module 1. Foundations
  23. 23. Specific Practices• A practice may not apply equally to all parts ofNACO worke.g., Geographic names always requireresearch, but personal names seldom do23Module 1. Foundations
  24. 24. Focus on Work in Hand• Focus on records related to an item beingcataloged• NACO (including LC) catalogers arediscouraged from cruising the database to finderrors to report24Module 1. Foundations
  25. 25. Go To the Source• Ask the other library’s NACO contact if younotice problems in an authority record• NACO liaisons:http://www.loc.gov/aba/pcc/naco/pccliaisons.html25Module 1. Foundations
  26. 26. NACO Parameters• Documentation• Contribution guidelines—PCC• Changes to existing NARs• Cancellation of NARs• Bibliographic File Maintenance (BFM)• Searching (why, how, and when)• Normalization rules26Module 1. Foundations
  27. 27. NACO Parameter:Documentation• RDA Toolkit• LC-PCC PSs• MARC 21 Authority Format• LC Guidelines Supplement to the MARC21 Authority Format• Descriptive Cataloging Manual (DCM :Z1)27Module 1. Foundations
  28. 28. Use Both RDA and LC-PCC PSs• RDA gives the basic instructions• LC-PCC PSs give further explanations,additional applications, and examples• LC-PCC PSs tell which RDA options andalternatives to applyLC-PCC PSs take precedence over RDA28Module 1. Foundations
  29. 29. 2929MARC 21 Format : Cataloger’s DesktopModule 1. Foundations
  30. 30. LC Guidelines Supplementto MARC 21 Authority Format• Instructions for LC, NACO, SACO, series,subjects practices• Many have the statement “Do not use thisfield/subfield”30Module 1. Foundations
  31. 31. 31LC GuidelinesModule 1. Foundations
  32. 32. Descriptive Cataloging Manual(DCM Z1):Name and Series Authority Records• Instructions on handling NAR and SARpractices• LC & PCC practices where they differ• NACO normalization• Examples32Module 1. Foundations
  33. 33. 3333DCM Z1Module 1. Foundations
  34. 34. Tag Links: LC Guidelines and DCM Z1Links to additional documentation34Module 1. Foundations
  35. 35. LC Guidelines: 05335Module 1. Foundations
  36. 36. DCM Z1: 05336Module 1. Foundations
  37. 37. Other Documentation• Alphabetic List of Ambiguous Entities–DCM Z1: Headings for Ambiguous Entities–Subject Headings Manual (SHM) H 405• LC-ALA Romanization Tables• Policy announcements from PSD37Module 1. Foundations
  38. 38. 38Division of the World:Name vs. Subject fileIs the entity a name or a subject?Ambiguous EntitiesSHM H 405NameAuthorityFileSubjectAuthorityFileModule 1. Foundations
  39. 39. 3939Tabular Version of Z1 Appendixhttp://www.loc.gov/aba/pcc/saco/alpha405.htmlModule 1. Foundations
  40. 40. 40• http://www.loc.gov/catdir/cpso/roman.html40Romanization TablesModule 1. Foundations
  41. 41. PCC Home Page41http://www.loc.gov/aba/pcc/Module 1. Foundations
  42. 42. NACO Home Page42http://www.loc.gov/aba/pcc/naco/Module 1. Foundations
  43. 43. 43• PCC listserv(http://www.loc.gov/aba/pcc/discussion.html)• Cataloging and Acquisitions Home(http://www.loc.gov/aba/)43Source of Latest ChangesModule 1. Foundations
  44. 44. 44NACO Parameter :Contribution Guidelines for PCC• NACO libraries decide which NARs tocontribute• Series and music work or expressionNARs may be contributed only aftercompleting additional training• When creating certain types of NARs,other related NARs must be establishedModule 1. Foundations
  45. 45. 45For this NAR:1XX Parent body. $b Subordinate bodyAnother NAR is needed for:1XX Parent body1. Parent-SubordinateHierarchiesModule 1. Foundations
  46. 46. 1b. Parent-Subordinate HierarchiesFor this NAR:110 2 _ Universidad Complutensede Madrid. $b BibliotecaAnother NAR is needed for:110 2 _ Universidad Complutense deMadrid46Module 1. Foundations
  47. 47. 1c. Parent-SubordinateHierarchiesFor this NAR:1XX Parent body. $b Subordinate body. $bSubordinate bodyNARs are needed for:1XX Parent body.1XX Parent body. $b Subordinate body47Module 1. Foundations
  48. 48. 1d. Parent-Subordinate HierarchiesFor this NAR:110 2 _ Universidad Complutense de Madrid. $bColegio Mayor de San Pablo. $b Centro deEstudios UniversitariosNARs are needed for:110 2 _ Universidad Complutense de Madrid.110 2 _ Universidad Complutense de Madrid. $bColegio Mayor de San Pablo48Module 1. Foundations
  49. 49. 492. Bodies in Variant Access PointsFor this NAR:1XX Government agency (Jurisdiction)4XX Jurisdiction. $b GovernmentagencyAnother NAR is needed:1XX JurisdictionModule 1. Foundations
  50. 50. 502b. Bodies in Variant Access PointsFor this NAR:110 2 _ Centre on Environment for theHandicapped (London, England)410 1 _ London (England). $b Centre onEnvironment for the HandicappedAnother NAR is needed:151 _ _ London (England)Module 1. Foundations
  51. 51. 2c. Bodies in Variant Access PointsFor this NAR:110 1 _ British Columbia. $b SchoolFacilities Planning410 1 _ British Columbia. $b Ministry ofEducation. $b School FacilitiesPlanningAnother NAR is needed:110 1 _ British Columbia. $b Ministry ofEducation51Module 1. Foundations
  52. 52. 3. Related Entities (5XX)• In many cases, it is useful to create accesspoints for related entities (5XX)• Every entity in a 5XX must be established• Reciprocal access points for related entitiesare required in three situations:– Persons with different identities (pseudonyms)– Earlier and later forms of a corporate name– Heads of state52Module 1. Foundations
  53. 53. 533b. Related Entities (5XX)1XX Current name ofentity5XX Earlier name ofentity $w a1XX Earlier name ofentity5XX Current name ofentity $w bModule 1. Foundations
  54. 54. 543c. Related Entities (5XX)110 2 _ InternationalBusiness MachinesCorporation510 2 _ Computing-Tabulating-RecordingCompany $w aOR510 2_ $i Predecessor: $aComputing-Tabulating-Recording Company $w r110 2 _ Computing-Tabulating-RecordingCompany510 2 _ InternationalBusiness MachinesCorporation $w bOR510 2_ $i Successor: $aInternational BusinessMachines Corporation$w rModule 1. Foundations
  55. 55. 3d. Related Entities (5XX)• It is not always useful to make reciprocalaccess points for related entities100 1_ Kimball, Edward L., $d 1930-510 2_ $i Employer: $a University of Wisconsin$w r55Module 1. Foundations
  56. 56. 3e. Related Entities (5XX)100 1_ Lennon, John, $d 1940-1980510 2_ $i Group member of: $a Beatles $w r56Module 1. Foundations
  57. 57. 3f. Related Entities (5XX)• When not required, use judgment! When arereciprocal access points useful?110 2_ Beatles500 1_ $i Group member: $a Lennon, John, $d 1940-1980 $w r500 1_ $i Group member: $a McCartney, Paul $w r500 1_ $i Group member: $a Harrison, George, $d 1943-2001 $w r500 1_ $i Group member: $a Starr, Ringo $w r57Module 1. Foundations
  58. 58. 58Mandatory Match 5XX-1XX5XX MUSTmatch 1XX onanother NARin the sameauthority file110 2 _ Dallas/Fort WorthInternational Airport510 2 _ Dallas/Fort WorthRegional Airport $w a110 2 _ Dallas/Fort WorthRegional Airport510 2 _ Dallas/Fort WorthInternational Airport$w bModule 1. Foundations
  59. 59. 594. Creator/Work Access PointsFor this NAR:1XX Creator. $t WorkThis NAR is needed:1XX CreatorModule 1. Foundations
  60. 60. 604b. Creator/Work Access PointsFor this NAR:1XX Creator. $t Work. $lLanguageTwo NARs are needed:1XX Creator1XX Creator. $t WorkModule 1. Foundations
  61. 61. 614c. Creator/Work Access PointsFor this NAR:100 1 _ Le Guin, Ursula $d 1929 - $t Earthsea.$l ChineseTwo NARs are needed:100 1 _ Le Guin, Ursula, $d 1929-100 1_ Le Guin, Ursula, $d 1929- $t EarthseaModule 1. Foundations
  62. 62. 624d. Creator/Work Access PointsFor this NAR:1XX Creator. $t Work. $kSelectionsTwo NARs are needed:1XX Creator1XX Creator. $t WorkModule 1. Foundations
  63. 63. 634e. Creator/Work Access PointsFor this NAR:100 1 _ McDougall, Christopher, $d 1962- $tBorn to run. $k SelectionsTwo NARs are needed:100 1_ McDougall, Christopher, $d 1962-100 1_ McDougall, Christopher, $d 1962- $tBorn to runModule 1. Foundations
  64. 64. Place name or corporate body inqualifier• If a place name or a corporate body is used ina qualifier, it must be established110 2_ Galleria darte contemporanea (Turin,Italy)151 Turin (Italy)130 _0 Circular (New York State Museum)110 2_ New York State Museum64Must be established!Module 1. Foundations
  65. 65. 65NACO Parameter :Changes to existing NARsAll authorized access points in the NAFare eligible to be changedby all NACO participantsModule 1. Foundations
  66. 66. 66NACO Parameter :Deletion of NARs• Only LC catalogers can delete NARs in theNAF• NACO libraries notify LC to delete NARs• LC/NACO database is redistributed daily tothe utilitiesModule 1. Foundations
  67. 67. 67NACO Parameter :Bibliographic File Maintenance(BFM)LC bibliographic records (as distributed by CDS) mustremain in synch with the NAFNACO partners must notify LC when certaintypes of changes to NARs affect authorizedaccess points used on LC bibliographicrecordshttp://www.loc.gov/aba/pcc/naco/bfmguide.htmlModule 1. Foundations
  68. 68. BFM : Examples• BFM NOT required: changes to authorizedaccess points– e.g., revised authorized access point including adeath date– Reports are generated by bibliographic utilities• BFM required: new NAR is created for aperson previously on an undifferentiated NAR(and LC bib records are affected)68Module 1. Foundations
  69. 69. 69NACO Parameter :SearchingCatalogers keep the database clean bysearching for related records beforecontributing an authority record to theLC/NACO Authority FileModule 1. Foundations
  70. 70. 70Why Search? (1)To prevent duplicate NARs• Authorized access point for entity alreadyestablished?• OCLC de-dupe detection and validationprograms need to be run• Report deletions to Cooperative ProgramsSectionModule 1. Foundations
  71. 71. 71Why Search? (2)• To avoid conflict in authorized access pointsand variant access points– Information on normalization rules coming up• To gather information from existingbibliographic recordsModule 1. Foundations
  72. 72. Why Search? (3)• To identify existing records that may need to beevaluated and re-coded for RDA– Presence of 667 note:THIS 1XX FIELD CANNOT BE USED UNDER RDA UNTIL THISRECORD HAS BEEN REVIEWED AND/OR UPDATED• To identify and re-code an existing RDA-acceptableAACR2 NAR to RDA• More information: Summary of ProgrammaticChanges to the LC/NACO Authority Filehttp://www.loc.gov/aba/rda/pdf/lcnaf_rdaphase.pdf72Module 1. Foundations
  73. 73. 73Why search? (4)• To identify bibliographic records that willneed BFM• To revise an existing NAR Personal name changes Corporate earlier-later Other revisionsModule 1. Foundations
  74. 74. 74Searching : How?• Search bibliographic and authority files• Maybe even subject headings inbibliographic and authority records• Search more than one form, e.g.:Fowler, Esther MillerFowler, E.Miller, E.Miller, EstherMiller, E. Anne• Search both the authorized access pointand the variant access pointsModule 1. Foundations
  75. 75. 75Module 1. Foundations
  76. 76. 76Module 1. Foundations
  77. 77. Searching : When?• Don’t leave authority records in the save filetoo long• Search again if 24 hours pass to: Avoid conflicts Avoid duplicates77Remember:24 Hour Rule to Avoid DuplicateAccess PointsModule 1. Foundations
  78. 78. NACO Normalization• Normalization is the conversion of a text stringto a normalized form• Text strings that normalize to the same formare considered to be duplicates and must bedifferentiated from each other• The goal of normalization is to ensure thateach authorized access point is unique78Module 1. Foundations
  79. 79. Normalization: Documentation• DCM Z1: Introduction79Module 1. Foundations
  80. 80. Normalization: Documentation• Linked from NACO Documentation & Updates80Module 1. Foundations
  81. 81. Impact of Normalization• Until early in 2013, “non-unique” or“undifferentiated” personal name NARswere sometimes created due tonormalization• Beginning in January 2013, NACOcatalogers were asked to avoid creatingnew undifferentiated personal nameauthority records (or adding to existingones)81Module 1. Foundations
  82. 82. 82NACO Normalization• OCLC and SkyRiver run databasesagainst a computer program usingNACO Normalization rules• Error reports on duplicates and conflictscome to LC– Coop catalogers handle themModule 1. Foundations
  83. 83. 83What happens in the Normalizationprocess?• All letters are converted to uppercase• Modified letters are converted tounmodified letters• All diacritics are removedModule 1. Foundations
  84. 84. 84What happens in the Normalizationprocess?• Most punctuation is removed.– Exceptions: first comma in subfield a; hyphenin birth and death dates• Subfield delimiters and subfield codesare retained and considered• The contents of 1XX, 4XX, and 5XXfields are comparedModule 1. Foundations
  85. 85. 85Tags Are Not Compared• MARC 21 tags are NOT consideredwhen the computer compares accesspoints for uniqueness–Subfield codes ARE considered• Different MARC tags (100, 110, 111,151, 130) do not make an authorizedaccess point uniqueModule 1. Foundations
  86. 86. 86What happens to the symbols?• Deleted with no space remaining:[ ] ′• Replaced by a blank space:@ ? / () = “ , -• Unchanged:- & + # bapostrophequotation markmusical sharpmusical flatComma after first onein birth/death datesexcept inbirth/death datesModule 1. Foundations
  87. 87. 87What is Compared?Line of characters that are part of thetagged field (character “string”)100 1 _ Le Bret, $c Monsieur $q (Alexis-Jean), $d1693-1772?NORMALIZES AS: LE BRET, $c MONSIEUR $q ALEXISJEAN $d 1693-1772Module 1. Foundations
  88. 88. 88Normalized Authorized Access Point• Normalized form:151 _ _ ILE DE MONTREAL QUEBEC• Catalog form:151 _ _ Île-de-Montréal (Québec)Module 1. Foundations
  89. 89. 89Conflicts and DuplicatesModule 1. Foundations
  90. 90. 90What is a conflict?Normalized match between•1XX vs. 1XXs•4XX vs. 1XXs & 5XXs•4XX vs. 4XX in same recordBut•5XX must normalize to 1XXs•4XX to 4XX is fine in different recordsModule 1. Foundations
  91. 91. 911XX DuplicatesA 1XX may NOTnormalize to thesame string asanother 1XX100 1 _ Smith-Jones, Barb100 1 _ Smith Jones, Barb(This is a duplicate)Module 1. Foundations
  92. 92. 921XX-4XX ConflictA 4XX may NOTnormalize to thesame string as a1XX or 5XX100 1 _ O’Brien, John400 1 _ O’Brien, Jack100 1 _ O’Brien, Jack400 1 _ O’Brien, J.(Jack)(This is a conflict)Module 1. Foundations
  93. 93. 93Conflict Within a RecordA 4XX may NOTnormalize to thesame string asanother string inthe same NAR110 2 _ Winston-SalemSunrise HikingClub410 2 _ Winston-SalemHiking Club410 2 _ Winston/SalemHiking Club(This is a conflict)Module 1. Foundations
  94. 94. 94No Conflict Between RecordsA 4XX MAYnormalize to thesame string as a4XX in anotherNAR100 1 _ Potter, Harold400 1 _ Potter, Harry100 1 _ Potter, Henry400 1 _ Potter, Harry(No conflicts here!)Module 1. Foundations
  95. 95. 95Normalization ExercisesLook at each record and decide ifany of the variant access pointswould normalize to the authorizedaccess pointModule 1. Foundations
  96. 96. 96Exercise 1151 _ _ Tbilisi (Georgia)451 _ _ Tiflis (Georgia)451 _ _ Tbilisi (Georgia)451 _ _ Tiflis $w nnaa451 _ _ Tbilisi (Georgian S.S.R.) $w nne451 _ _ Tblisi (Georgia)Delete this referenceModule 1. Foundations
  97. 97. 97Exercise 2110 2 _ Ballard-Carlisle Historical &Genealogical Society410 2 _ Ballard-Carlisle Historical andGenealogical Society410 2 _ Ballard-Carlisle Historical-Genealogical SocietyAll OK!Module 1. Foundations
  98. 98. 98Exercise 3110 1 _ United States. $b Office of theUnder Secretary of Defense,Acquisition410 1 _ United States. $b Office of theUnder Secretary of Defense forAcquisition410 1 _ United States. $b Under Secretaryof Defense, Acquisition410 1 _ United States. $b Office of theUnder Secretary of Defense(Acquisition)Delete this referenceModule 1. Foundations
  99. 99. 99100 1 _ Torrealba Ramos, Isabela400 1 _ Torrealba-Ramos, Isabela400 1 _ Ramos, Isabela TorrealbaExercise 4Deletethis 4XXModule 1. Foundations
  100. 100. 100Exercise 5100 1 _ Morel, Jean-Luc400 1 _ Morel, J.-L. $q (Jean-Luc)400 1 _ Morel, Jean LucDeleteModule 1. Foundations
  101. 101. FRBRText available in print or at:http://www.ifla.org/en/publications/functional-requirements-for-bibliographic-recordsModule 1. Foundations 101
  102. 102. FRAD & FRSADText available in print.http://www.ifla.org/publications/ifla-series-on-bibliographic-control-34FRSAD Final Report:http://www.ifla.org/files/assets/classification-and-indexing/functional-requirements-for-subject-authority-data/frsad-final-report.pdfModule 1. Foundations 102
  103. 103. FRBR• A conceptual model of the bibliographicuniverse• Based on the entity-relationship modeldeveloped for databases103 Module 1. Foundations
  104. 104. Entity-Relationship Model• Entity: Something that can be distinctlyidentified.• Relationship: An association between two ormore entities.• Attribute: A characteristic that may identifyinstances of entities or relationships.Module 1. Foundations 104
  105. 105. Entity-Relationship Diagramming• Entities• Relationships• AttributesRelationshipEntityAttributeModule 1. Foundations 105
  106. 106. Entity-Relationship DiagrammingEntity 1Entity 2RelationshipAttribute 1Attribute 2Attribute 1Attribute 2Module 1. Foundations 106
  107. 107. FRBR DiagrammingWorkExpressionManifestationItemis realized throughis embodied inis exemplified byModule 1. Foundations 107
  108. 108. FRBR Diagramming• cb1 Kelmscott Pressis the producer of →← has a producerom1 the 1891 publication of Poems by the Way byWilliam Morrisom2 the 1892 publication of The Recuyell of the Historyesof Troye by Raoul Lefevre.om3 the 1896 publication of The Works of GeoffreyChaucerModule 1. Foundations 108
  109. 109. FRBR Entities• Group 1: The products of intellectual or artistic endeavor.Sometimes called “the primary entities.”– Work: a distinct intellectual or artistic creation– Expression: the intellectual or artistic realization of a workin some form (e.g. alpha-numeric, musical notation)– Manifestation: the physical embodiment of an expression(e.g. a print publication)– Item: a copy of a manifestation109 Module 1. Foundations
  110. 110. FRBR Entities• Group 1 (“Primary entities”)– Work– Expression– Manifestation– ItemGone with thewindGerman translation ofGone with the windOriginal English text ofGone with the wind1936 publication byMacmillan1937 publication ofGerman translation byBertelsmann2006 publication byScribner1 of five Library copies of 1936publication (barcode 31197011774061)Library copy of 2006 publication(barcode 31197226590575)Library copy of 1937 publication(barcode 31197222656115)Module 1. Foundations 110
  111. 111. FRBR Relationships (Group 1)WorkExpressionManifestationItemrealized throughembodied inexemplified byModule 1. Foundations 111
  112. 112. FRBR RelationshipsWork: Gone with thewind (Novel)Work: Gone with thewind (Movie)Work-to-work relationshipsDerivative relationshipWork: Gone with the wind onfilm: a complete referenceDescriptiverelationshipsWork: Vanity fair and Gone with thewind: a critical comparisonWork: Vanity Fairderived fromdescribed bydescribed bydescribed byModule 1. Foundations 112
  113. 113. FRBR/FRAD Entities• Group 2: entities responsible for Group 1entities–Person–Family–Corporate body113 Module 1. Foundations
  114. 114. FRBR Entities• Group 2– Person– Corporate body– FamilyMargaretMitchellClaudeDebussyGeorge W.BushBritish Library Ikea A/SJin (Dynasty : 265-420)Peale (Family : Peale,Norman Vincent, 1898-1993)Yan (Family :China)Yan (Family :Philippines)Module 1. Foundations 114
  115. 115. FRBR Relationships (Gps 1-2)Work: Gone with the windPerson: Martin Beheim-SchwarzbachPerson: Margaret MitchellExpression: 1st GermanexpressionExpression: 1st EnglishExpressionrealized throughtranslated byhas atranslationcreatedbyModule 1. Foundations 115
  116. 116. FRBR Entities• Group 3: entities that can be subjects ofworks–Any group 1 or group 2 entity, and–Concept–Object–Event–Place116 Module 1. Foundations
  117. 117. FRBR Entities• Group 3 (subjects)– All entities in Groups 1 and 2+– Concept– Object– Event– PlaceStone ageFrenchlanguageGranite HorsesVesuvius (Italy)—Eruption, 79Olympic Games (29th : 2008 : Beijing,China)Salt Lake City(Utah)Biscay, Bay of (France and Spain)Module 1. Foundations 117
  118. 118. FRBR Group 3 Relationshipshas a subjectWork: Gonewith the windPerson: MargaretMitchellcreated byConcept: Georgia—History—Civil War, 1861-1865—FictionPerson: OHara, Scarlett —FictionConcept: Historical fictionConcept: War storieshas a genreModule 1. Foundations 118
  119. 119. FRBR/RDA Attributes• FRBR, a model, defines attributes, but doesnot tell us how to record the data• RDA, a cataloging code, defines attributes anddoes tell us how to record the dataModule 1. Foundations 119
  120. 120. Attributes ofPerson in RDAModule 1. Foundations 120
  121. 121. Person Entity AttributesPerson (Margaret Mitchell)Preferred name: Mitchell, MargaretVariant name: Marsh, John Robert, Mrs.Date of birth: 1900 November 8Date of death: 1949 August 16Gender: femalePlace of birth: Atlanta, Ga.Language of the person: EnglishFuller form of (fore)name: Margaret MunnerlynModule 1. Foundations 121
  122. 122. Person Entity Attributes (MARC)046 $f 19001108 $g 19490816100 1_ Mitchell, Margaret, $d 1900-1949400 1_ Marsh, John Robert, $c Mrs., $d 1900-1949370 Atlanta, Ga.375 female377 eng378 $q Margaret MunnerlynModule 1. Foundations 122
  123. 123. Attributes ofWork in RDAModule 1. Foundations 123
  124. 124. Work Entity AttributesWork (Gone with the wind)Preferred title: Gone with the windForm of work: NovelDate of work: 1936History of the work: Romantic novel first published inMay 1936; it won the Pulitzer Prize in 1937.Summarization of the content: Scarlett O’Hara, thespoiled daughter of a well-to-do plantation owner, mustovercome the challenges facing the South during andafter the Civil WarModule 1. Foundations 124
  125. 125. Work Entity Attributes(Current MARC Practice)046 $k 1936100 1_ … . $t Gone with the wind380 Novel678 Romantic novel first published in May 1936; it won thePulitzer Prize in 1937.Module 1. Foundations 125
  126. 126. Entity-Relationship LinkingModule 1. Foundations 126Work: Gone with the windPerson: Margaret Mitchellcreatedby
  127. 127. Linking in MARCAuthority Record for the Work Entity046 $k 1936100 1_ Mitchell, Margaret, $d 1900-1949. $t Gone with the wind380 Novel678 Romantic novel first published in May 1936; it won the Pulitzer Prize in1937.Authority record for the Person Entity046 $f 19001108 $g 19490816100 1_ Mitchell, Margaret, $d 1900-1949400 1_ Marsh, John Robert, $c Mrs., $d 1900-1949370 Atlanta, Ga.375 female377 engModule 1. Foundations 127Mitchell, Margaret, $d 1900-1949
  128. 128. FRBR/FRAD User Tasks• Find• Identify• Select• Obtain• Contextualize• JustifyModule 1. Foundations 128
  129. 129. The MARC Authority FormatIn NACO practice descriptions of persons,families, corporate bodies, works, andexpressions are created in the MARC AuthorityFormat.Module 1. Foundations 129
  130. 130. MARC Authority Structure• Fields– Fields are divisions of the record– Tag• 3-digit number naming the field– Indicators• Two characters giving handling instructions for the field– Subfields• Division of the field into different types of dataModule 1. Foundations 130
  131. 131. MARC Authority Structure• 0XX – control fields, standard numbers, etc.• 1XX – the authorized access point (only oneallowed)• 3XX – where most of the RDA entity attributesare recorded• 4XX – variant access points• 5XX – links to related entities• 6XX – notes and series treatmentModule 1. Foundations 131
  132. 132. MARC Authority Structure• X00 – Persons and Families• Also works or expressions with a person or family as creator• X10 – Corporate bodies• Also works or expressions with a corporate body as creator• X11 – Meetings, events, expeditions, etc.• Also works or expressions with a meeting (etc.) as creator• X30 – Works or expressions without an explicitcreator• X51 – Geographic entitiesModule 1. Foundations 132
  133. 133. MARC Authority Structure• Combining the previous two slides:– 100 = authorized access point for a person– 410 = variant access point for a corporate body– 511 = link to a related meeting (etc.)– 430 = variant access point (lacking an explicitcreator) for a work or expression– 151 = authorized access point for a geographicentityModule 1. Foundations 133
  134. 134. 00X : Control Fields• 008/09 (OCLC Auth/Ref) – “Kind of Record”– a = “established heading”– b and c = “reference record”• NACO catalogers will almost always code this“a”Module 1. Foundations 134
  135. 135. Module 1. Foundations 135
  136. 136. 00X : Control Fields• 008/10 (OCLC Rules) – “Descriptive CatalogingRules”– a-d = earlier rules, including AACR2– z = “other”• Use “z”Module 1. Foundations 136
  137. 137. Module 1. Foundations 137
  138. 138. Module 1. Foundations 138
  139. 139. Module 1. Foundations 139
  140. 140. 00X : Control Fields• 008/12 (OCLC Series) – “Type of series”– a = Monographic series– b = Multipart item– c = Series-like phrase– n = Not applicable• 008/13 (OCLC Ser num) – “Numbered or unnumbered series”– a = Numbered– b = Unnumbered– c = Numbering varies– n = Not applicable• 008/16 (OCLC Ser use) – “Heading use – series added entry”– a = Appropriate– b = Not appropriateModule 1. Foundations 140
  141. 141. Module 1. Foundations 141
  142. 142. 00X : Control Fields• 008/14 (OCLC Name use) – “Heading use –main or added entry” (1XX/7XX in bib record)– a = Appropriate– b = Not appropriate• 008/15 (OCLC Subj use) – “Heading use –subject added entry” (6XX in bib record)– a = Appropriate– b = Not appropriateModule 1. Foundations 142
  143. 143. Module 1. Foundations 143
  144. 144. 00X : Control Fields• 008/29 (OCLC Ref status) – “Referenceevaluation”– a = 4XX or 5XX fields present in the record– b = Includes 4XX fields that are not “evaluated”– n = no 4XX or 5XX fields present in the record• Because guidelines for evaluation of non-Roman script references have not yet beenestablished, use “b” if non-Latin script 4XXfields are presentModule 1. Foundations 144
  145. 145. Module 1. Foundations 145
  146. 146. 00X : Control Fields• 008/32 (OCLC Name) – “Undifferentiatedpersonal name”– a = Differentiated personal name– b = Undifferentiated personal name– n = Not applicableModule 1. Foundations 146
  147. 147. Module 1. Foundations 147
  148. 148. Module 1. Foundations 148
  149. 149. 00X : Control Fields• 008/33 (OCLC Auth status) – “Level ofestablishment”– a = Fully established– c = ProvisionalModule 1. Foundations 149
  150. 150. Module 1. Foundations 150
  151. 151. Module 1. Foundations 151
  152. 152. 00X : Control Fields• 008/39 (OCLC Source) – “Cataloging source”– blank = National bibliographic agency– c = Cooperative cataloging program• Most NACO catalogers will code this “c”Module 1. Foundations 152
  153. 153. Module 1. Foundations 153
  154. 154. Module 1. Foundations 154
  155. 155. Module 1. Foundations 155
  156. 156. Module 1. Foundations 156
  157. 157. 01X-09X : Code Fields• 010 – Library of Congress Control Number– added automatically in OCLC• 040 – Cataloging source– Always include “$e rda” immediately after “$beng.”Module 1. Foundations 157
  158. 158. Module 1. Foundations 158
  159. 159. 01X-09X : Code Fields• 046 – Special Coded Dates– $f Birth date– $g Death date– $k Beginning creation date– $l Ending creation date– $s Start period– $t End period– $2 Source of date schemeModule 1. Foundations 159
  160. 160. 01X-09X : Code Fields• 046 – Special Coded DatesGenerally follow ISO 8601 format:yy (century): 20[the first two digits of the year, i.e., 21st century]yyyy (year alone): 2012yyyy-mm (year and month): 2012-01yyyymmdd (year, month, and day): 20120113Module 1. Foundations 160
  161. 161. 01X-09X : Code Fields• 046 – Special Coded DatesDates below 1000: The “thousands” and the “hundreds”digits should always be represented• 0951 = 951 A.D.• 01 = 2nd century A.D.• 00 = 1st century A.D.BC dates:• Precede with a minus sign• Subtract one year because there was no year zeroo -0046 = 47 B.C.o -00 = 1st century B.C.Module 1. Foundations 161
  162. 162. 01X-09X : Code Fields• 046 – Special Coded Dates– ISO 8601 can’t handle more complex situations. Use EDTF(Extended date/time format) standard instead– See http://www.loc.gov/standards/datetime/– When using EDTF always include $2 edtf in the field-0035? $2 edtf probably 36 BC1957~ $2 edtf approximately 1957[1930,1931] $2 edtf either 1930 or 1931197u $2 edtf between 1970 and 1979Module 1. Foundations 162
  163. 163. Module 1. Foundations 163
  164. 164. 1XX: Authorized Access Point• 100 1_ = Person with surname• 100 0_ = Person without surname• 100 3_ = Family• 110 1_ = Corporate body (jurisdiction)• 110 2_ = Corporate body (non-jurisdiction)• 111 2_ = Meeting (etc.)• 130 = Work/Expression with no explicit creator• 151 = Geographical entityModule 1. Foundations 164
  165. 165. 1XX: Authorized Access Point• At a minimum, includes the preferred name ofthe entity• May also include cataloger-added elements,such as dates, qualifiersModule 1. Foundations 165
  166. 166. Module 1. Foundations 166
  167. 167. 3XX: RDA Elements• 370 – Associated Place– $a – Place of birth– $b – Place of death– $c – Associated country– $e – Place of residence/headquarters– $f – Other associated place– $g – Place of origin of work– $s – Start period– $t – End period– $2 – Source of termModule 1. Foundations 167
  168. 168. Recording the Place Attribute• The form of the place name is governed byRDA Chapter 16.• Authorized access points for jurisdictionalplace names are generally formed as inAACR2, e.g. “Paris (France)” However:• 16.2.2.4. “If the place name is being used torecord ... a place associated with [an entity] ...precede the name of the larger place by acomma.” -- e.g. “Paris, France”Module 4. Describing persons 168
  169. 169. Recording the Place Attribute• Abbreviations. 9.8-11 all say: “Abbreviate the namesof countries, states, provinces, territories, etc., asinstructed in appendix B (B.11), as applicable.”• So when recording this attribute use, e.g., “U.S.”, not“United States”• Omit terms of jurisdiction or other designationsRussia not Russia (Federation)Korea not Korea (South)Buenos Aires, Argentina not Buenos Aires, Argentina (Province)Prussia not Prussia (Duchy)Prussia not Prussia (Kingdom)Module 4. Describing persons 169
  170. 170. Exercise:Recording the Place Attribute• These RDA forms are all found in the authorityfile. What form would you use to record theattribute?London (England) Mexico City (Mexico)Austin (Tex.) Ontario (Calif.)Arizona District of ColumbiaUnited States Auckland (N.Z.)France Puerto RicoModule 4. Describing persons 170
  171. 171. Recording the Place Attribute370 $a London, England [birthplace]370 $b Mexico City, Mexico [death place]370 $e Austin, Tex. [place of headquarters]370 $f Ontario, Calif. [other associated place]370 $a Ariz. [birthplace]370 $b D.C. [death place]370 $b U.S. [death place]370 $a Auckland, N.Z. $b P.R. $c France[birthplace, death place, associated country]Module 4. Describing persons 171
  172. 172. Recording the Place Attribute: LCSHPlace names can also be drawn from LCSH. If so, record themexactly as found and include $2 lcsh.370 Cache Valley (Utah and Idaho) $2 lcsh [birthplace]370 $b Pompeii (Extinct city) $2 lcsh [death place]370 $e Tahoe, Lake (Calif. and Nev.) $2 lcsh [place of residence]Do not mix NACO AF terms and LCSH terms in the same 370field. If you need to use both, record them in separate fields.370 Long Island (N.Y.) $2 lcsh [birthplace]370 $e New York, N.Y. [place of residence]Module 4. Describing persons 172
  173. 173. Module 1. Foundations 173
  174. 174. 3XX: RDA Elements• 377 – Associated language– $a Language code– $b Language term– $2 Source of code (do not use in NACO)• NACO: Use the MARC language codehttp://www.loc.gov/marc/languages/langhome.html377 eng• Do not record a language term unless the code is acollective code377 nic $l AbidjiModule 1. Foundations 174
  175. 175. Module 1. Foundations 175
  176. 176. 4XX: Variant Access Point• 400 1_ = Person with surname• 400 0_ = Person without surname• 400 3_ = Family• 410 1_ = Corporate body (jurisdiction)• 410 2_ = Corporate body (non-jurisdiction)• 411 2_ = Meeting (etc.)• 430 = Work/Expression with no explicit creator• 451 = Geographical entityModule 1. Foundations 176
  177. 177. 4XX: Variant Access Point• At a minimum, includes a variant name of theentity• May also include cataloger-added elements,such as dates, qualifiers. This is optional inRDA• In NACO practice, variant access points mayconflict with other variant access points. Theymay not conflict with any authorized accesspoint.Module 1. Foundations 177
  178. 178. Module 1. Foundations 178
  179. 179. 5XX : Links to Related Entities• 500 1_ = Person with surname• 500 0_ = Person without surname• 500 3_ = Family• 510 1_ = Corporate body (jurisdiction)• 510 2_ = Corporate body (non-jurisdiction)• 511 2_ = Meeting (etc.)• 530 = Work/Expression with no explicit creator• 551 = Geographical entityModule 1. Foundations 179
  180. 180. 5XX : Links to Related Entities• The link is created by recording the exact form of theauthorized access point of another entity• An authority record for the other entity must exist• A corresponding link may or may not exist in theother record• Because there are many different kinds of possiblerelationships, the use of relationship designators tospecify the nature of the relationship is encouragedModule 1. Foundations 180
  181. 181. 5XX : Links to Related EntitiesRelationship Designators• Record the designator in subfield $i, before theauthorized access point• Include subfield $w r• Capitalize the designator and follow with a colon511 2_ $i Group member of: $a Lewis and Clark Expedition$d (1804-1806) $w r[related entity to the person named Meriwether Lewis]Module 1. Foundations 181
  182. 182. 5XX : Links to Related EntitiesRelationship Designators• Designators for relationships between persons/families/corporate bodies and other persons/families/corporatebodies are drawn from RDA Appendix K• Designators for relationships between works/expressionsand other works/expressions are drawn from RDAAppendix J• Designators for relationships between persons/families/corporate bodies and works/expressions are drawn fromRDA Appendix I or the MARC relator terms listModule 1. Foundations 182
  183. 183. Module 1. Foundations 183
  184. 184. Module 1. Foundations 184
  185. 185. Module 1. Foundations 185
  186. 186. Module 1. Foundations 186
  187. 187. Module 1. Foundations 187
  188. 188. Module 1. Foundations 188
  189. 189. Module 1. Foundations 189
  190. 190. Module 1. Foundations 190
  191. 191. 6XX: Notes• 667: Cataloguer’s note (RDA 5.9, 8.13)• Intended for other catalogers, not for thepublic• Free text, no required format, although thereare some commonly used phrasesModule 1. Foundations 191
  192. 192. Module 1. Foundations 192
  193. 193. 6XX: Notes• 670: Source consulted (RDA 5.8, 8.12)• Records sources of information used to record otherelements in the description• Use one 670 per source• In NACO practice the first is generally the resourcebeing cataloged when the authority record is firstcreated• Suggested format:670 Title proper, date: $b location within source (datafound)Module 1. Foundations 193
  194. 194. Module 1. Foundations 194
  195. 195. Module 1. Foundations 195
  196. 196. 6XX: Notes• Alternately, 3XX $u / $v can be used to record theSource Consulted element. However:• In PCC practice, information used to create the authorizedaccess point (1XX) or variant access points (4XX) must berecorded in 670(s).• $v may be used alone; $u must always be preceded by $v100 1_ Pratchett, Terry370 Beaconsfield, England $e Salisbury, England $vContemporary authors online, August 22, 2002 $v Wikipedia,July 27, 2012Module 1. Foundations 196
  197. 197. 6XX: Notes• 675 – Source data not found– Citation for a consulted source in which noinformation is found related in any manner to theentity represented by the authority record orrelated entities– Use with discretion – it is not necessary to citeevery source you searched. Use as a time saver forothers by citing sources you think other catalogersmight attempt to searchModule 1. Foundations 197
  198. 198. 6XX: Notes• 675 – Source data not found– Not repeatable– Only subfield $a available– Repeat subfield $a for each source– Separate each subfield $a by a semicolon675 $a GNIS, 2 February 2013; $a TheColumbia gazetteer of the world, 1998Module 1. Foundations 198
  199. 199. Module 1. Foundations 199
  200. 200. 6XX: Notes• 675 – Source data not found– Exceptionally, if data is not found in the resourcebeing cataloged, record in the first 670 as usual(do not use 675)– Record “name not given,” “title not given,” etc., insubfield $bModule 1. Foundations 200
  201. 201. Module 1. Foundations 201
  202. 202. 6XX: Notes• 678 – Biographical or Historical Data (RDA 6.7,9.17, 10.8, 11.11)– Record a brief statement about the person, family,corporate body, or work. This is entirely free text,in your own words, based on all the sources youhave consulted– Intended to be read by the public– Recommended format• *Entity’s name in direct order+ (*dates if available+)was/is a … *describe the entity+Module 1. Foundations 202
  203. 203. Module 1. Foundations 203
  204. 204. Module 1. Foundations 204
  205. 205. Module 1. Foundations 205

×