Presentation is loading. Please wait.

Presentation is loading. Please wait.

LC Training for RDA: Resource Description & Access Relationships in RDA -- in bibliographic records and in authority records Cooperative and Instructional.

Similar presentations


Presentation on theme: "LC Training for RDA: Resource Description & Access Relationships in RDA -- in bibliographic records and in authority records Cooperative and Instructional."— Presentation transcript:

1 LC Training for RDA: Resource Description & Access Relationships in RDA -- in bibliographic records and in authority records Cooperative and Instructional Programs Division Library of Congress Sept. 2012

2 2 Learning Objectives for Module 4 -- Relationships in RDA  Understand the basics of relationships in RDA  Determine the relationships that we will code here at UCSD  Express relationships correctly in bibliographic records

3 Outline for today 1. Introduction: Basics of relationships in RDA 2. Relationships between People and Resources 3. Relationships within Resources: works, expressions, manifestations, items 4. Relationships within People: persons, families and corporate bodies 3

4 4 Basics of relationships 1. What are relationships? 2. Why relationships? Expressing Relationships: Helps users find what they want!

5 5 Basics of relationships Entity – relationship – Entity “Name” is the creator of “Work” “Adolfo Tarango” is the creator of “Developing and Managing Electronic Journal Collections” “Work” is a commentary on “Work” “There is nothing like a Dane!” is a commentary on “Hamlet” “Corporate Name A” is the earlier name of “Corporate Name B” “Center for Music Experiment” is the earlier name of “Center for Computing and the Arts”

6 RDA Relationship Designator The term relationship designator refers to a designator that indicates the nature of the relationship between a resource and a person, family, or corporate body associated with that resource represented by an authorized access point and/or identifier. 6

7 7 Entities being related Relationships between: 1. Resources and associated persons, families, and corporate bodies [Shi Deng is the author of Glossary of Library and Information Science, English-Chinese, Chinese-English] 2. Resources (works, expressions, manifestations, items) [The Daily Guardian is the earlier name of the UCSD Guardian] 3. Persons, families, corporate bodies [Charles Lutwidge Dodgson also published under the identity Lewis Carroll]

8 RDA 18.2 Functional Objectives and Principles  The data recorded to reflect relationships … should enable the user to find all resources associated with a particular person, family, or corporate body.  … the data should reflect all significant relationships between a resource and persons, families, and corporate bodies associated with that resource. 8

9 9 Relationships in RDA  Chapters 18-22, Appendix I Resource and associated persons, families, corporate bodies  Chapters 24-28, Appendix J Between resources (works, expressions, manifestations, items)  Chapters 29-32, Appendix K Between persons, families, corporate bodies

10 10 [Screen image from the RDA Toolkit ( ) used by permission of the Co-Publishers for RDA (American Library Association, Canadian LibraryAssociation, and CILIP: Chartered Institute of Library and Information Professionals)]

11 11 Relationship designators  RDA appendices I, J, and K Not closed lists  If needed term is missing: Identify the needed term and use it in your bib record Notify your Unit Head Unit Head will follow PCC process to have term fast-tracked through the formal JSC process to be added to the appendix and the vocabulary

12 12 Methods to express relationships 1. Authorized access point 110 2# $a Society of Linguists, $e author 2. Structured description $i Also issued as: $t Health statistics 3. Unstructured description 500 ## $a Translation of the author’s novel Digital fortress

13 13 Designation of relationships in MARC bibliographic records $e of and $j of 111 and 711 $i of $i of 76X-78X linking entry fields MARC 21 coding (e.g., “continues”; “continued by”) MARC fields

14 14 Citing another resource: Authorized access points In MARC fields: Give the form represented by NAR* If there is no NAR, create one (NACO catalogers) * Exception: Do not use AACR2 NAR with “Polyglot” or more than one language in subfield $l for multiple expressions.

15 15 Citing another resource: Linking entry fields In MARC fields:  Copy and paste what is in the existing record for that resource and adjust the subfield coding as appropriate

16 16 Designation of relationships in MARC authority records  In authority records, relationships are shown in: 500 $w and $w  Optional relationships can be added in 5XX $w r $i (more on this later)

17 17 Summary  You have been recording relationships in AACR2  There are some new concepts about relating entities in RDA  Relationships are recorded as authorized access points, notes, and linking fields  UCSD follows PCC practices

18 18 Persons/families/bodies and resources  Creators and others associated with works (ch. 19)  Contributors associated with expressions (ch. 20)  Manufacturers, publishers, distributors associated with manifestations (ch. 21)  Owners, annotator, autographer, etc. associated with items (ch. 22)

19 19 Creator relationships Persons/families/bodies related to works author compiler filmmaker interviewer programmer and others … (RDA Appendix I)

20 20 Creator relationships (con’t) LC catalogers will (according to LC- PCC PS 19.2): Give first creator with principal responsibility (1xx field) If multiple creators associated with the work are present, apply cataloger judgment to give more than the first (7xx fields)  UCSD catalogers will follow the same practice Also include specific $e with term from Appendix I in both 1xx and 7xx

21 21 Creator relationships in bibliographic records  Give as authorized access point in MARC 1XX field (and 7XX field if more than one creator or if “other” associated with work) in bibliographic record  Relationship designators from RDA appendix I.2 in subfield $e of 1XX and 7XX field Not a closed list Do not include $e in name authority record

22 22 Example Creator work relationship 110 $a Society of Linguists, $e author. 710 $a Linguists International, $e author. 100 $a Glass, Philip, $e composer. 110 $a Virginia, $e enacting jurisdiction.

23 23 Example Others associated with work Others associated with works (19.3): 710 $a U.S. Geology Society, $e issuing body. 710 $a ABC Institute, $e sponsoring body.

24 24 Contributor relationships Persons/families/bodies related to expressions Translators Editors of compilations Performers Illustrators Arrangers of music Compilers

25 25 Contributor relationships (cont.)  LC catalogers: Give the first illustrator of resources intended for children as an authorized access point in a MARC 7XX field in bibliographic record, and add the relationship designator $e illustrator  UCSD catalogers: Follow broader PCC practice, which strongly encourages coding the $e relationship designator for all contributors

26 26 Example 1: Contributor relationships 100 1# $a Wood, Audrey, $e author $a The napping house / $c Audrey Wood ; illustrated by Don Wood # $a Wood, Don, $e illustrator.

27 27 Example 2: Contributor relationships 100 1# $a Lindgren, Astrid, $d , $e author $a Pippi Långstrump. $l English $a Pippi Longstocking / $c Astrid Lindgren ; translated by Tiina Nunnally # $a Nunnally, Tiina, $d $e translator.

28 28 Example 3: Contributor relationships 245 $a Favorite American music / $c performed by the Baltimore Symphony Orchestra with Marin Alsop conducting $a $a Baltimore Symphony Orchestra, $e performer. 700 $a Alsop, Marin, $e conductor.* * Could have used the more general “$e performer” for Alsop.

29 Relationship Designators for Bibliographic Records -- Quiz RDA Bibliographic Record: 100 1# $a Mishima, Yukio, $d , $e author $a Shiosai. $l English $a The Sound of waves / $c Yukio Mishima; translated by Meredith Weatherby # $a Weatherby, Meredith, $e translator. Authority records: 100 1# $a Mishima, Yukio, $d $t Shiosai. $l English 100 1# $a Weatherby, Meredith 29

30 Open Metadata Registry metadataregistry.org 30

31 31

32 32 Relationships to manifestations Persons/families/bodies related to manifestations (RDA 21.0, Appendix I.4) Producers Publishers (e.g., broadcasters) Manufacturers (e.g., engravers, printers) Distributors (e.g., film distributor)

33 33 Relationships designators for persons/families/bodies associated with manifestations Few terms are listed in Appendix I.4 The terms: “producer,” “publisher,” “manufacturer,” “distributor” are separate elements (264 field) and thus are not given in subfield $e of 7XX field

34 34 Examples: Relationships to manifestations 264 #1 $a Bethesda : $b NIH, $c # $a National Institutes of Health (U.S.), $e broadcaster. 264 #1 $a St. Paul : $b West Publishing Company, $c # $a West Publishing Company.* * “Publisher” isn’t used as an RDA relationship designator because that relationship is an element (264 field).

35 35 Relationships to items Persons/families/bodies related to items (RDA 22.0, Appendix I.5) Owners Custodians Curators  LC: cataloger judgment  UCSD: Mostly for gifts and special collections. For now, continue to code as 790 field and use RDA relationship designator in $e

36 36 Examples: Relationships to items LC: 500 $a University Library's copy has ms. notes by author on endpapers. $5 IaH 700 $a Smiley, Jane, $e annotator UCSD: 590 $a UCSD copy has ms. notes by author on endpapers. 790 $a Smiley, Jane $e annotator

37 Examples: Relationships to items LC: 541 $c Gift; $a John Jefferson; $d $5 DLC 700 $a Jefferson, John, $e donor. UCSD: 790 $a Jefferson, John $e donor 37

38 38 Summary Work: o Code authorized access points for creators and include $e with term from Appendix I Expression: o Code authorized access points for contributors and include $e with term from Appendix I Manifestation: Unlikely to be needed; cataloger judgment Item: For local gifts and special collections

39 39 Relationships between resources Relationships between works, expressions, manifestations, and items  Relationships in bibliographic and/or authority records: Related works (ch. 25) Related expressions (ch. 26) Related manifestations (ch. 27) Related items (ch. 28)

40 40 Related works  RDA 25.1  Common work relationships: Whole-part, e.g.,  Works in a compilation  Chapters in a book Adaptations Supplements Sequential relationships (e.g., earlier and later serials)

41 41 Related works LC catalogers are only required to code (LCPS 25.1): Whole-part relationships for works in a compilation Sequential serial relationships PCC catalogers generally follow LC practice UCSD catalogers may use cataloger judgment to apply more broadly.

42 42 Whole-part relationships for compilations  LC: Give MARC 505 contents note unless contents indicated in another part of the description (e.g., in MARC 245 $a because no collective title present) or unless burdensome  LC: Give one MARC 7XX analytical authorized access point; cataloger judgment if additional 7XX fields for other works  Don’t give analytical authorized access points for some works: anthologies of poetry, conference proceedings, hymnals, journals, interviews, etc. – LCPS 25.1

43 43 Example: Whole-part work Authorized access points for the works: 100 1# $a Shakespeare, William, $d $a Hamlet ; $b King Lear / $c William Shakespeare. * $a Shakespeare, William, $d $t Hamlet. * $a Shakespeare, William, $d $t King Lear. * 2nd indicator in 700 indicates the relationship “Contains”

44 44 Example: serial related works Structured descriptions and three identifiers each: $a TCA journal $t Journal of professional counseling, practice, theory, & research $x $w (DLC) $w (OCoLC) $a Journal of professional counseling, practice, theory, & research $t TCA journal $x $w (DLC) $w (OCoLC) indicators 00 = relationship “Continued by” 780 indicators 00 = relationship “Continues”

45 45 Authority record, work relationship 046 ## $k # $a Chase, Mary, $d $t Harvey 380 ## $a Play 530 #0 $w r $i Adapted as a motion picture (work): $a Harvey (Motion picture) 670 ## $a Harvey, ## $a Wikipedia, Jan. 6, 2011 $b (Harvey; Pulitzer Prize-winning play by Mary Chase; premiered in 1944)

46 46 Related expressions  RDA 26.1  Common expression relationships: Whole-part (e.g., translations in a compilation) Revisions Editions Translations Language editions Abridgements

47 47 Related expressions Like work relationships, LC limits their requirements for relationships between expressions (LC PS 26.1): Whole-part relationships for expressions in a compilation (same policy as for works) Sequential serial relationships

48 48 Example 1: Whole-part expression Authorized access points for the expressions: 100 1# $a Petterson, Per, $d $a Two Norwegian novels / $c Per Petterson # $a Out stealing horses -- To Siberia $a Petterson, Per, $d $t Ut og stjæle hester. $l English $a Petterson, Per, $d $t Til Sibir. $l English $a Out stealing horses $a To Siberia.

49 49 Example 2: serial related expression Structured description for other language edition: 130 0# $a Revista de política y derecho ambientales en América Latina y el Caribe. $l English $a Journal of environmental policy and law in Latin America and the Caribbean $i Issued also in Spanish under title: $t Revista de política y derecho ambientales en América Latina y el Caribe.

50 50 Example 3: Related expression - translation Authorized access point: 100 1# $a Brown, Dan, $d $a Digital fortress. $l French $a Forteresse digitale # $i Translation of: $a Brown, Dan, $d $t Digital fortress.

51 Example 4: Related expression - translation Structured description in 500 field: 100 1# $a Brown, Dan, $d $a Digital fortress. $l French $a Forteresse digitale. 500 ## $a Translation of: Digital fortress / Dan Brown. -- 1st ed. -- New York : St. Martin’s Press, pages ; 22 cm.

52 52 Example 5: Related expression - translation Structured description in 765 field: 100 1# $a Brown, Dan, $d $a Digital fortress. $l French $a Forteresse digitale. *765 0# $a Brown, Dan, $t Digital fortress $b 1st ed. $d New York : St. Martin’s Press, 1998 $h 371 pages ; 22 cm $w (DLC) * 2nd indicator “blank” = “Translation of”

53 53 Example 6: Related expression - translation Unstructured description in 500 field: 100 1# $a Brown, Dan, $d $a Digital fortress. $l French $a Forteresse digitale. 500 ## $a Translation of the author’s novel Digital fortress.

54 54 Related manifestations Common manifestation relationships: Reproductions Different formats for same expression (e.g., print vs. CD; print vs. PDF, print vs. online) Special issues  Required for reproductions; see LC- PCC PS 27.1

55 55 Recording related manifestations  Structured or unstructured description: Linking entry fields: 775 or 776 5XX Not by an authorized access point  LC: cataloger judgment to use relationship designators in RDA appendix J.4 in subfield $i if MARC content designation does not give relationship

56 56 Example: Related manifestations $a Health statistics for elementary -school children. 264 #1 $a Baltimore : $b Johns Hopkins University, $c ## $a volumes ; $c 27 cm $i Also issued as: $t Health statistics for elementary-school children $d Baltimore : Johns Hopkins University, $h CD-ROMs : 4 3/4 in.

57 57 Reproductions: LC core  LC: Generally, give information about the original in a linking field: MARC 775 field if same carrier 776 field if different carrier  Use information as is from the record for the original If detailed information is not available, give a bibliographic history note in a MARC 500 field

58 58 Reproductions: LC core (con’t)  If a reproduction is a compilation, generally do not give MARC 775 or 776 linking fields for each work/expression in the compilation, and do not give bibliographic history notes for each work/expression in the compilation

59 59 Example: Reproduction 100 1# $a Ringwalt, J. Luther $q (John Luther) $a Anecdotes of General Ulysses S. Grant. 264 #1 $a Washington, D.C. : $b Library of Congress Preservation Microfilming Program, $c ## $a 1 microfilm reel (118 pages) ; $c 35 mm $i Reproduction of (manifestation): $a Ringwalt, J. Luther (John Luther) $t Anecdotes of General Ulysses S. Grant $d Philadelphia : J.B. Lippincott Company, 1886 $h 118 p. ; 18 cm. $n Call number of original: E672.R58 $w (DLC) Structured description including an identifier:

60 60 Related items  RDA 28.1  Common item relationships Reproduction of a specific copy “Bound with” Item added to copy of manifestation in a special collection  Relationships that apply only to a single copy of the manifestation -- so, usually local information

61 61 Related item  LC catalogers are required to code related item relationships for: Reproductions Special relationships for rare materials as warranted “Bound withs”

62 62 Recording Related items RDA 28.1 Structured or unstructured description: Linking entry fields: 7XX 5XX Not by an authorized access point  Cataloger judgment to use relationship designators in RDA appendix J.5 in subfield $i if MARC content designation does not give relationship

63 63 Examples: Related items 501 $i Bound with: $a ___________. $5 DLC 775 $i Reprint of (item): $t Hiking in Unicoi State Park $d Helen, GA : RST Publishers, 1955 $h 22 p. : ill. ; 19 cm.

64 64 Summary Related resources LC core: o Works and Expressions: Whole part compilations Serial sequential relationships  Manifestations: Reproductions  Items: “Bound withs” Reproductions

65 65  Entities in relationships: Group 2  Relationships in authority records: Related persons (ch. 30) Related families (ch. 31) Related corporate bodies (ch. 32) Relationships between persons, families, and corporate bodies

66 66  LC catalogers focus on: Different identities for persons Immediately preceding/succeeding corporate bodies Relationships between persons, families, and corporate bodies

67 67 LC policy for different identities  2 identities: use a 500 field in each NAR  3 or more identities: use a 663 field with $w nnnc in 500 fields (see DCM Z1 yellow page)

68 68 Example: 2 identities 100 1# $a King, Stephen 500 1# $a Bachman, Richard 100 1# $a Bachman, Richard 500 1# $a King, Stephen

69 69 Examples: 3+ different identities 100 1# $a Twain, Mark, $d # $w nnnc $a Clemens, Samuel, $d # $w nnnc $a Snodgrass, Quintus Curtius, $d ## $a For works of this author written under other names, search also under $b Clemens, Samuel Langhorne, , $b Snodgrass, Quintus Curtius, # $a Clemens, Samuel, $d # $w nnnc $a Twain, Mark, $d ## $a For a listing of the names used by this author, search also under: $b Twain, Mark, Authorized access point in authority records:

70 70 Example: related corporate bodies Giving specific relationship in $w: 110 2# $a Library of Congress. $b Policy and Standards Division 510 2# $w a $a Library of Congress. $b Cataloging Policy and Support Office 110 2# $a Library of Congress. $b Cataloging Policy and Support Office 510 2# $w b $a Library of Congress. $b Policy and Standards Division

71 71 Other relationships  LC instructs its catalogers on giving other relationships in name authority records: Cataloger judgment to give relationship designator from RDA appendix K in subfield $i to identify specific relationship Need value “r” in subfield $w if using subfield $i

72 72 Examples: person related to corporate body or family 100 1# $a Garr, Arnold K # $w r $i Employer: $a Brigham Young University 100 1# $a Carroll, Charles N. $q (Charles Nagus), $d # $w r $i Descendants: $a Carroll (Family : $g Carroll, Charles N. (Charles Negus), )

73 M M EXAMPLE

74 74 Summary LC catalogers will code relationships in authority records for: Different identities for persons Immediately preceding/succeeding non-conference corporate bodies

75 75 Summary Module 4: Relationships  “Relate” is the second main goal of RDA (the first is identify)  Relationships can be shown within and between FRBR Group 1 (work, expression, manifestation, item) and Group 2 (person, family, corporate body) entities  Relationship designators in Appendices I, J, K

76 76 Module 4: Relationships in RDA Questions?


Download ppt "LC Training for RDA: Resource Description & Access Relationships in RDA -- in bibliographic records and in authority records Cooperative and Instructional."

Similar presentations


Ads by Google