RDA Test at LC Module 5: Relationships In Bibliographic Records and In Authority Records

RDA Test at LC: June Module 5 2 Core relationships not in this module Two related to naming the work in module 3:  Creator (RDA 19.2)  Other person, family, and corporate body associated with a work if used to name the work (RDA 19.3) Two not possible separately in our MARC context -- covered by naming the work or expression -- ignore as separate elements!  Work manifested (RDA 17.8)  Expression manifested (RDA 17.10)

RDA Test at LC: June Module 5 3 Other core relationships Contributors (ch. 20) Related works (ch. 25) Related expressions (ch. 26) Related manifestations (ch. 27) Related items (ch. 28) Related persons (ch. 30) Related corporate bodies (ch. 32)

RDA Test at LC: June Module 5 4 Contributor (RDA 20.2) Relationship between person, family, or corporate body associated with an expression Core for LC:  Illustrators of resources intended for children  Translators Cataloger’s judgment for others

RDA Test at LC: June Module 5 5 Relationship for contributors Give as authorized access point in MARC 7XX fields in bibliographic record  Identifier not used alone during RDA Test Relationship designators from RDA appendix I in subfield $e of 7XX field  Use “illustrator” when applicable  Others: cataloger’s judgment  Not a closed list  Do not include $e in NAR 1XX for contributor

RDA Test at LC: June Module 5 6 Example: contributor 100 1# $a Wood, Audrey $a The napping house / $c Audrey Wood ; illustrated by Don Wood # $a Wood, Don, $e illustrator. Notes: 1) Relationship designator “author” could be given for creator in 100 field. 2) 2nd statement of responsibility is not core; also, it isn’t needed to justify the 700 field.

RDA Test at LC: June Module 5 7 Example: contributor 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. Notes: 1) Relationship designators “author” and “translator” – cataloger’s judgment. 2) 2nd statement of responsibility is not core; also, it isn’t needed to justify the 700 field.

RDA Test at LC: June Module 5 8 Related work (RDA 25.1) Core for LC:  Whole-part relationships for works in a compilation  Standard serial relationships (“Continues,” “Continued by,” etc.) Cataloger’s judgment for others

RDA Test at LC: June Module 5 9 Relationship to related work Three methods (RDA 24.4):  Identifier: not used alone in RDA Test  Authorized access point  Description (structured or unstructured) Cataloger’s judgment to use relationship designators in RDA appendix J.2; MARC content designation gives some relationships

RDA Test at LC: June Module 5 10 Whole-part relationships If MARC 505 field contents note is given, no limit on number of works unless burdensome Cataloger’s judgment for total number of MARC 7XX analytical authorized access points if that is the method used to give the relationship Don’t need to justify the 7XX analytical access points by a 505 field

RDA Test at LC: June Module 5 11 Whole-part work example 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.

RDA Test at LC: June Module 5 12 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”

RDA Test at LC: June Module 5 13 Related expression (RDA 26.1) Core for LC:  Whole-part relationships for expressions in a compilation  Standard serial relationships Cataloger’s judgment for others

RDA Test at LC: June Module 5 14 Relationship to related expression Three methods (RDA 24.4):  Identifier: not used alone in RDA Test  Authorized access point  Description (structured or unstructured) Same guidelines about MARC 505 and 7XX fields for whole-part work relationships apply Cataloger’s judgment to use relationship designators in RDA appendix J.3; MARC content designation gives some relationships

RDA Test at LC: June Module 5 15 Whole-part expression example Authorized access points for the expressions: 100 1# $a Petterson, Per, $d $a Two Norwegian novels / $c Per Petterson $a Petterson, Per, $d $t Ut og stjæle hester. $l English $a Petterson, Per, $d $t Til Sibir. $l English. Could also include a contents note but not required to justify the access points; or, a contents note without the 700 fields would be possible # $a Out stealing horses -- To Siberia.

RDA Test at LC: June Module 5 16 Example: serial related expression Unstructured 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. 580 ## $a Issued also in Spanish under title: Revista de política y derecho ambientales en América Latina y el Caribe.

RDA Test at LC: June Module 5 17 Related expression (translation) - example 1 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.

RDA Test at LC: June Module 5 18 Related expression (translation) - example 2 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.

RDA Test at LC: June Module 5 19 Related expression (translation) - example 3 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”

RDA Test at LC: June Module 5 20 Related expression (translation) - example 4 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.

RDA Test at LC: June Module 5 21 Related manifestation (RDA 27.1) Two methods (RDA 24.4):  Identifier: not used alone in RDA Test  Description (structured or unstructured) Core for LC: Reproductions  Use a structured description in MARC 775 for regular-print reprints or MARC 776 for other reproductions Cataloger’s judgment for other relationships and for use of relationship designators in RDA appendix J.4

RDA Test at LC: June Module 5 22 Example: reproduction manifestation 100 1# $a Ringwalt, J. Luther $q (John Luther) $a Anecdotes of General Ulysses S. Grant. 260 ## $a Washington, D.C. : $b Library of Congress Preservation Microfilming Program, $c ## $a 1 microfilm reel (118 pages) ; $c 35 mm 776 0# $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 pages ; 18 cm $n Call number of original: E672.R58 $w (DLC)

RDA Test at LC: June Module 5 23 Related item (RDA 28.1) Core for LC:  Reproductions - same guidelines as for expressions  Special relationships for rare materials as warranted  “Bound withs” Two methods (RDA 24.4):  Identifier: not used alone in RDA Test  Description (structured or unstructured) Cataloger’s judgment for other relationships and for use of relationship designators in RDA appendix J.5

RDA Test at LC: June Module 5 24 Related person (RDA 30.1) May be relationship to another person or to family or to corporate body Core for LC: different identities Cataloger’s judgment for other relationships Recorded in authority data

RDA Test at LC: June Module 5 25 Relationship to related person Two methods (RDA 29.4):  Identifier: not used alone in RDA Test  Authorized access point Relationship designators in RDA appendix K  LC: do not use appendix K for different identities; follow LC policy instead  Other relationships: can give appendix K designator in subfield $i

RDA Test at LC: June Module 5 26 LC procedure: different identities LC policy for different identities:  2 identities = uncoded 500 fields in each NAR  3 or more identities: new DCM Z1 yellow page for the 663 field consolidates current information about use of the 663 field with $w nnnc in 500 fields (now in various LCRIs) 100 1# $a $a Snodgrass, Quintus Curtius, $d # $w nnnc $a Twain, Mark, $d ## $a For a listing of the names used by this author, search also under: $b Twain, Mark,

RDA Test at LC: June Module 5 27 LC procedure: different identities Authorized access point in authority records: 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,

RDA Test at LC: June Module 5 28 Related corporate body (RDA 32.1) May be relationship to another corporate body or to person or to family Core for LC: sequential relationships of corporate bodies  Only the immediately preceding and immediately succeeding bodies Cataloger’s judgment for other relationships

RDA Test at LC: June Module 5 29 Relationship to related body Two methods (RDA 29.4):  Identifier: not used alone in RDA Test  Authorized access point Relationship designators in appendix K  LC: do not use appendix K for earlier/later relationships; follow LC policy instead  Other relationships: can give appendix K designator in subfield $i Recorded in authority data

RDA Test at LC: June Module 5 30 Example: related corporate body Authorized access points in authority records: 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 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 Subfield $w codes indicate relationship: b = later; a = earlier.