rda test train the trainer n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
RDA Test “Train the Trainer” PowerPoint Presentation
Download Presentation
RDA Test “Train the Trainer”

Loading in 2 Seconds...

play fullscreen
1 / 107

RDA Test “Train the Trainer” - PowerPoint PPT Presentation


  • 123 Views
  • Uploaded on

RDA Test “Train the Trainer”. Module 4: Identifying Works and Expressions [Content as of Mar. 31, 2010]. Bibliographic or authority data?. RDA does not prescribe if attributes about the work/expression and the access points are to be recorded as bibliographic data or authority data

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'RDA Test “Train the Trainer”' - MikeCarlo


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
rda test train the trainer

RDA Test “Train the Trainer”

Module 4: Identifying Works and Expressions

[Content as of Mar. 31, 2010]

bibliographic or authority data
Bibliographic or authority data?
  • RDA does not prescribe if attributes about the work/expression and the access points are to be recorded as bibliographic data or authority data
  • Agency decision related to implementation functionality, to analysis policy, etc.
    • For initial implementation, most often establish the access point with authority data
language and script
Language and script
  • Title for a work in the language and script in which it appears in the resource – RDA 5.4
    • Alternative: a transliterated form as a substitute for or in addition to the found form
  • Descriptive attributes for a work or expression in RDA chapter 7 in language and script preferred by the agency
  • Other attributes for a work or expression in RDA chapter 6 in language and script prescribed in instructions
title of an expression
Title of an expression?
  • No! -- Doesn’t exist in the FRBR/FRAD models
  • Instead, build the access point for an expression by adding identifying attributes to the access point for the work (RDA 5.5/5.6)
authorized access point for a manifestation
Authorized access point for a manifestation?
  • Not included in RDA yet
    • Will be added when the FRBR model is extended to subject entities because most often need to have such an access point for a subject relationship
yes create an authorized access point for a manifestation
Yes, create an authorized access point for a manifestation
  • However, at times do need an access point for a manifestation for non-subject reasons (e.g., for a monographic series issued in different carriers):
    • Build on the access point for the expression by adding a distinguishing characteristic

130 $a R&D studies (CD-ROM)

general guidelines for titles rda 6 2 1
General guidelines for titles (RDA 6.2.1)
  • Capitalization of title – see RDA appendix A.3
  • Numbers in title in found form
    • For parts of works, see RDA 6.2.2.9
  • Accents in title as found; optionally, can add
general guidelines for titles rda 6 2 11
General guidelines for titles (RDA 6.2.1)
  • Omit initial article unless accessed by that article
  • Do not give space between a period and an initial
  • If initials lacking periods have spaces, retain spaces
  • Abbreviations in title – see RDA appendix B.3
terminology
Terminology
  • Title of the work: “word, character, or group of words and/or characters by which a work is known”
  • Preferred title
    • For current implementations = the form of title used when constructing the authorized access point
  • Variant title
    • For current implementations = the form of title used when constructing a variant access point
sources of information
Sources of information
  • Sources for preferred title for work (6.2.2.2):
    • For a work created after 1500: from resources embodying the work (usually the first manifestation received) or reference sources
    • For a work created before 1501: from modern reference sources
sources of information1
Sources of information
  • If the evidence of modern reference sources is inconclusive for a work created before 1501, use (in this order of preference):

a) modern editions

b) early editions

c) manuscript copies

  • All other elements for works and expressions: any source
reminder changes in the resource
Reminder: changes in the resource
  • Some changes affect the identification of the work (RDA 6.1.3)
    • Related to some of the reasons for new descriptions (RDA 1.6) discussed in module 3
    • Depends upon basis of identification for the specific mode of issuance
elements covered in this module
Elements covered in this module
  • Works: Core and Core if …
  • Expressions: Core and Core if …
  • Other elements if change from AACR2
  • MARC 21 changes included in the above
  • Other MARC changes
preferred title for the work
Preferred title for the work
  • General instructions in RDA 6.2
  • Specific instructions:
    • parts (RDA 6.2.2)
    • compilations (RDA 6.2.2)
    • some musical works (RDA 6.14.2)
    • some legal works (RDA 6.19.2)
    • some religious works (RDA 6.23.2)
    • some official communications (RDA 6.26.2)
preferred title changes from aacr2
Preferred title: changes from AACR2
  • No longer routinely omit introductory phrases (e.g., “Here beginneth …”) and statements of responsibility
    • Preferred title based on first manifestation received
    • If later manifestations have different forms, determine the most common form of the preferred title -- it may not have such a phrase or statement
preferred title other changes from aacr2
Preferred title: Other changes from AACR2
  • “Selections” not used alone as the preferred title -- instead, “Works. Selections”
  • For simultaneous publications with different titles: choice based on first resource received
simultaneous publication different titles in same language
Simultaneous publication: different titles in same language
  • Choose the preferred title based on title of the resource first received (not the resource published in the home country)

U.K. volume received first: Walking in Britain

U.S. volume received later: Day walks in Britain

Preferred title = Walking in Britain

simultaneous publication different titles languages
Simultaneous publication: different titles/languages
  • No longer a priority order of languages – use title in resource first received

Serial published simultaneously in German and

English versions

German-language version received first

English-language version received later

Preferred title = title from German-language version

preferred titles parts of the bible
Preferred titles: parts of the Bible
  • Refer to the Old and New Testaments by their spelled-out forms (not “O.T.” and “N.T.”)
  • Omit the name of the testament in the preferred title for individual books or groups of books
bible examples
Bible examples

130 $a Bible. $p New Testament

not130 $a Bible. $p N.T.

130 $a Bible. $p Genesis

not130 $a Bible. $p O.T. $p Genesis

130 $a Bible. $p Gospels

not130 $a Bible. $p N.T. $p Gospels

entity related to work
Entity related to work
  • RDA 0.6.3 and RDA 6.27.1: when creating the authorized access point for the work, precede the preferred title for the work, if appropriate, by the authorized access point representing the person, family, or corporate body responsible for the work
chapter 19 entity responsible for a work
Chapter 19: entity responsible for a work
  • Sources (RDA 19.1.1):
    • Preferred sources of information (RDA 2.2.2)
    • Other statements appearing prominently in the resource
    • Information appearing only in the content
    • Other sources
creator
Creator
  • Creator = “person, family, or corporate body responsible for the creation of a work” = core element (RDA 19.2)
  • If more than one, only the creator having principal responsibility named first in resource is required
  • If more than one and principal responsibility not indicated, only the first-named creator is required
collaborative works
Collaborative works
  • For collaborative works, the creators may perform the same or different roles (RDA 19.2.1)
    • Choosing the first-named creator to name the work may mean that the result is not the same as applying the AACR2 rule due to the order of names on the source
example creators with principal responsibility
Example: creators with principal responsibility

100 $a Sweet, Martha.

245 $a … / $c by Martha Sweet and Linda

Bruce with contributions by Gus

Peterson and Marilee James.

*700 $a Bruce, Linda.

*700 $a Peterson, Gus.

*700 $a James, Marilee.

* number of access points for other creators: agency decision

example creators with no principal responsibility indicated
Example: creators with no principal responsibility indicated

100 $a Brown, Susan.

245 $a … / $c by Susan Brown, Melanie

Carlson, Stephen Lindell, Kevin Ott,

and Janet Wilson.

*700 $a Carlson, Melanie.

*700 $a Lindell, Stephen.

*700 $a Ott, Kevin.

*700 $a Wilson, Janet.

* number of access points for other creators: agency decision

corporate body as creator
Corporate body as creator
  • Categories of works given in RDA 19.1.1
  • Includes government and religious officials for some categories of works
  • Corporate body takes precedence over a first-named person or family as creator
compilation of works
Compilation of works
  • RDA: do not name the compilation by the first work in the compilation as AACR2 does in some situations, because doing so misidentifies the aggregate work
  • Can give authorized access points for each work/expression
  • If no collective title, alternative is to devise a title proper
preferred title for compilations of one person family body
Preferred title for compilations of one person, family, body
  • RDA 6.2.2.10
  • Categories:
    • Complete works = use “Works”
    • Complete works in a single form = use term chosen by cataloger
    • Other compilations of two or more works in same form or different forms = give preferred title for each work
alternative for other compilations
Alternative for “Other compilations …”
  • Instead of or in addition to giving the preferred title for each work, use a conventional collective title, e.g.,:
    • Works. Selections
    • Posters. Selections
    • Orchestra music. Selections
compilation of two works by same creator
Compilation of two works by same creator

AACR2:

100 $a Miller, Arthur, $d 1915-2005

240 $aArchbishop’s ceiling

245 $a Two plays / $c Arthur Miller.

505 $a The Archbishop’s ceiling -- The

American clock.

700 $a Miller, Arthur, $d 1915-2005.

$t American clock.

compilation of two works by same creator1
Compilation of two works by same creator

RDA with alternative for conventional collective title:

100 $a Miller, Arthur, $d 1915-2005

240 $a Plays. $k Selections

245 $a Two plays / $c Arthur Miller.

505 $a The Archbishop’s ceiling -- The

American clock.

700 $a Miller, Arthur, $d 1915-2005.

$t Archbishop’s ceiling.

700 $a Miller, Arthur, $d 1915-2005.

$t American clock.

compilation of works by different creators
Compilation of works by different creators

AACR2:

100 $a Polk, Sharon.

240 $a Community band concerts

$a Community band concerts / $c Sharon

Polk. Fall harvest festivals / Terri Swanson.

$a Swanson, Terri. $t Fall harvest

festivals.

compilation of works by different creators1
Compilation of works by different creators

RDA without alternative for devised title:

$a Community band concerts / $c Sharon Polk.

Fall harvest festivals / Terri Swanson.

700 $a Polk, Sharon. $t Community band concerts.

700 $a Swanson, Terri. $t Fall harvest festivals.

compilation of works by different creators2
Compilation of works by different creators

RDA with alternative for devised title:

245 $a [Two United States Midwest memoirs]

505 $a Community band concerts / Sharon Polk

-- Fall harvest festivals / Terri Swanson.

700 $a Polk, Sharon. $t Community band concerts.

700 $a Swanson, Terri. $t Fall harvest festivals.

signatory to a treaty etc
Signatory to a treaty, etc.
  • RDA 6.22
  • Scope = “government or other party that has formally signed a treaty, etc., as an adherent to its terms and conditions”
  • In the form of the authorized access point (ch. 11)
signatory to a treaty etc1
Signatory to a treaty, etc.
  • Core:
    • first-named signatory as part of creating the authorized access point for the work (RDA 6.29.1.15+)
    • both signatories if the work is a bilateral treaty
      • 2nd signatory as part of authorized access point for the treaty (can also give separate access point for the 2nd signatory)
authorized access point for treaties
Authorized access point for treaties
  • First-named signatory regardless of number of signatories + preferred title (RDA 6.19.2.7-6.19.2.8)
    • Not based on English alphabetic order
    • Exception: if one party on one side and two or more on other side, use the single party even if not first-named
  • Additions to the access point: 6.29.1.33
bilateral treaty
Bilateral treaty

110 $a Barbados.

240 $a Treaties, etc. $g Finland $d

1989 June 15

245 $a Convention between Barbados and

Finland : $b for the avoidance of

double taxation with respect to

taxes on income.

*710 $a Finland.

* Agency decision if including separate

access point for party in 240 $g.

multilateral treaty
Multilateral treaty

110 $a Sweden.

240 $a Treaties, etc. $d 2009 May 28.

245 $a Treaty on import duties between

Sweden, Finland, Denmark, Norway,

and Iceland.

*710 $a Finland.

*710 $a Denmark.

*710 $a Norway.

*710 $a Iceland.

* Agency decision on number of additional access points.

other person family body
Other person, family, body
  • Other person, family, or corporate body associated with a work = core element ifused when creating the authorized access point for the work (RDA 6.27-6.31)
  • RDA 19.3
  • Scope = “a person, family, or corporate body associated with a work other than as a creator”
other person family body used in work s authorized access point
Other person, family, body used in work’s authorized access point
  • Won’t occur often
  • One example:
    • Jurisdiction governed by laws is not the jurisdiction enacting the laws (not the creator)
    • But RDA 6.29.1.2 says to construct the authorized access point for laws governing one jurisdiction by combining the authorized access point for the jurisdiction governed and the preferred title for the laws
identifier for the work
Identifier for the work
  • RDA 6.8
  • Scope: “a character string uniquely associated with a work, or with a surrogate for a work (e.g., an authority record) that serves to differentiate that work from other works”
  • Precede the identifier with indication of person or agency, etc., responsible for assigning the identifier
marc for identifier for a work
MARC for Identifier for a work
  • In access point in bibliographic records, record control number in MARC subfield $0 (Authority record control number)
  • In authority records:
    • a record control number in field 001, 010, etc.
    • other identifiers in field 024 with first indicator “7” (ensure that source of code has been added to MARC list cited in subfield $2)
core elements to distinguish
Core elements to distinguish
  • If elements are being recorded to distinguish one work from another or from the name of a person, family, or corporate body, record the elements:
    • either as additions to the authorized access point representing the work [RDA Test],
    • as separate elements, or
    • as both
  • In a “core context,” application would generally be as additions to the authorized access point
form of work
Form of work
  • RDA 6.3
  • Scope = class or genre to which a work belongs -- no controlled vocabulary
  • Core if needed to differentiate a work
marc for form of work
MARC for Form of work
  • Access point: added in parentheses to preferred title for the work (subfielding will vary)
  • 380 field: subfield $a

130 0# $a Ocean’s eleven (Motion picture)

380 ## $a Motion picture

date of work
Date of work
  • RDA 6.4
  • Scope: earliest date associated with a work
    • Date work was created, or
    • Date work was first published or released
  • Core if needed to differentiate a work
marc for date of work
MARC for Date of work
  • Access point: added to preferred title for the work (subfielding will vary)
  • 046field: subfields $k and $l

046 ## $k 2001

130 0# $a Ocean’s eleven (Motion picture : 2001)

380 ## $a Motion picture

046 ## $k 2005

110 2# $a Connecticut Commission on Children.

$t Annual report (2005)

place of origin of the work
Place of origin of the work
  • RDA 6.5
  • Scope: country or other territorial jurisdiction from which a work originated (includes local place)
  • In authorized access point form (RDA ch. 16)
  • Core if needed to differentiate a work
marc for place of origin of the work
MARC for Place of origin of the work
  • Access point: added to preferred title for the work (subfielding will vary)
  • 370 field: subfield $g

130 0# $a Advocate (Boise, Idaho)

370 ## $g Boise, Idaho

medium of performance
Medium of performance
  • RDA 6.15
  • Scope = “instrument, instruments, voice, voices, etc., for which a musical work was originally conceived”
  • Core: if title is not distinctive, give if applicable when creating the authorized access point (RDA 6.28.1.9)
  • Core if needed to differentiate a work with a distinctive title
medium of performance1
Medium of performance
  • No limitation on recording medium of performance (no longer AACR2 “rule of three”)
  • More possibilities for indeterminate medium of performance (RDA 6.15.1.13)
marc for medium
MARC for Medium …
  • Access point: in subfield $m as applicable
  • 382 field: subfield $a

100 1# $a Stravinsky, Igor, $d 1882-1971.

$t Symphonie de Psaumes

382 ## $a mixed voices $a orchestra

100 1# $a Beethoven, Ludwig van, $d 1770-

1827. $t Sonatas, $m piano, $n …

382 ## $a piano

numeric designation of a musical work
Numeric designation of a musical work
  • RDA 6.16
  • Scope = “a serial number, opus number, or thematic index number assigned to a musical work by the composer, publisher, or a musicologist”
  • Can give as many as available
  • Use abbreviations per appendix B.5.4
numeric designation of a musical work1
Numeric designation of a musical work
  • Core: if title is not distinctive, give if applicable when creating the authorized access point
  • Core if needed to differentiate a work with a distinctive title
marc for numeric designation of a musical work
MARC for Numeric designation of a musical work
  • Access point: subfield $n if applicable
  • 383 field: $a, $b, $c

100 1# $a Beethoven, Ludwig van, $d 1770-

1827. $t Sonatas, $m piano, $n no.

14, op. 27, no. 2 …

382 ## $a piano

383 ## $a no. 14, $b op. 27, no. 2

slide60
Key
  • RDA 6.17
  • Scope = “the set of pitch relationships that establishes the tonal centre, or principal tonal centre, of a musical work. Key is designated by its pitch name and its mode, when it is major or minor”
  • No longer dependent upon time period of the work
slide61
Key
  • Core: if title is not distinctive, give if applicable when creating the authorized access point
  • Core if needed to differentiate a work with a distinctive title
marc for key
MARC for Key
  • Access point: subfield $r if applicable
  • 384 field: subfield $a

100 1# $a Beethoven, Ludwig van, $d 1770-

1827. $t Sonatas, $m piano, $n no.

14, op. 27, no. 2, $r C# minor

382 ## $a piano

383 ## $a no. 14, $b op. 27, no. 2

384 ## $a C# minor

other distinguishing characteristic of the work
Other distinguishing characteristic of the work
  • RDA 6.6
  • Scope = “a characteristic other than form of work, date of work, or place of origin of the work that serves to differentiate a work from another work or from the name of a person, family, or corporate body”
  • Core if needed to differentiate …
marc for other distinguishing characteristic of the work
MARC for Other distinguishing characteristic of the work
  • Access point: added to the preferred title for the work (subfielding will vary)
  • 381 field: subfield $a

130 #0 $a Research paper (South African

Law Commission)

381 ## $a South African Law Commission

content type
Content type
  • RDA 6.9
  • Scope: “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.”
content type controlled vocabulary
Content type controlled vocabulary
  • Use one or more of the terms in RDA 6.9.1.3
    • Alternative: predominant or most substantial content
  • One of the three elements developed with ONIX community to replace the GMD
    • Can be included in templates with other elements
marc for content type
MARC for Content type
  • Access point: in subfield $h

100 1# $a Brunhoff, Jean de, $d 1899-1937.

$t Babar en famille. $h Spoken word

marc for content type1
MARC for Content type
  • MARC field 336
    • $a: content type term
    • $2: if term in $a is from RDA 6.9, give “marccontent”
    • $3: content type materials specified - give if appropriate
    • can repeat field or can repeat subfield $a if all terms are from vocabulary in subfield $2
marc 336 examples
MARC 336 examples

Book:

300 $a 123 pages, 28 unnumbered pages

336 $a text $2 marccontent

338 $a volume $2 marccarrier

Music CD:

300 $a 1 audio disc

336 $a performed music $2 marccontent

338 $a audio disc $2 marccarrier

marc 336 examples1
MARC 336 examples

DVD:

300 $a 1 DVD

336 $a two-dimensional moving image $2 marccontent

338 $a video disc $2 marccarrier

Online PDF:

300 $a 1 online resource (39 pages)

336 $a text $2 marccontent

338 $a online resource $2 marccarrier

marc 336 examples2
MARC 336 examples

Score:

300 $a 1 vocal score (xii, 300 pages)

336 $a notated music $2 marccontent

338 $a volume $2 marccarrier

Map:

300 $a 1 map

336 $a cartographic image $2 marccontent

338 $a sheet $2 marccarrier

marc 336 example
MARC 336 example

Website (with maps, text, and photographs):

300 $a 1 online resource

336 $a text $2 marccontent

336 $a cartographic image $2 marccontent

336 $a still image $2 marccontent

338 $a online resource $2 marccarrier

Or repeat subfield $a:

336 $a text $a cartographic image $a still image

$2 marccontent

language of expression
Language of expression
  • RDA 6.11
  • Scope = language in which a work is expressed
  • Use term(s) from the MARC 21 list of languages
  • Is a core element although some instructions in first release of RDA say it is a “Core if” element
language of expression1
Language of expression
  • Careful: distinguish between
    • one expression in more than one language and
    • a resource with two or more expressions of the same work, each in different language(s)
marc for language of expression
MARC for Language of expression
  • Access point: subfield $l (not repeatable)
  • No separate authority field for this element
  • In bibliographic records: use 041 and/or 546

041 1# $a eng $h fre

100 1# $a Brunhoff, Jean de, $d 1899-1937.

240 1# $a Babar en famille. $l English

546 ## $a English translation of the author’s original French work

no longer using polyglot
No longer using “Polyglot”
  • Does not help user search and identify specific languages; so:
    • If separate expressions, name each expression separately
    • If multiple languages in one expression, list each language
example multiple languages in one expression
Example: Multiple languages in one expression

$l Ancient Greek & Latin

[a Greek text with Latin translation and notes]

$l Hindi & English

[a Hindi motion picture with English subtitles]

$l Arabic, English, German & Hebrew

[conference proceedings with each paper in one of

four languages]

example multiple language expressions
Example: Multiple language expressions
  • 245 $a Antigo Testamento Poliglota : $b
  • Hebraico, Grego, Português, Inglês.
  • $a Text in Greek, Hebrew, Portuguese, and
  • English in columns on facing pages.
  • 730 $a Bible. $p Old Testament. $l Hebrew …
  • 730 $a Bible. $p Old Testament. $l Greek …
  • 730 $a Bible. $p Old Testament. $l Portuguese …
  • 730 $a Bible. $p Old Testament. $l English …

[AACR2:130 0# $a Bible. $p O.T $l Polyglot …]

identifier for the expression
Identifier for the expression
  • RDA 6.13
  • Scope = “a character string uniquely associated with an expression, or with a surrogate for an expression (e.g., an authority record), that serves to differentiate that expression from other expressions”
  • Precede the identifier with indication of person or agency, etc., responsible for assigning the identifier
marc for identifier for an expression
MARC for Identifier for an expression
  • In access point in bibliographic records, record control number in MARC subfield $0 (Authority record control number)
  • In authority records:
    • a record control number in field 001, 010, etc.
    • other identifiers in field 024 with first indicator “7” (ensure that source of code has been added to MARC list cited in subfield $2)
scale for cartographic resources
Scale for cartographic resources
  • Core elements from chapter 7’s attributes of expression
    • Horizontal scale of cartographic content (RDA 7.25.3)
    • Vertical scale of cartographic content (RDA 7.25.4)
  • See Training document #3 for other non-core elements in chapter 7
horizontal scale of cartographic content
Horizontal scale of cartographic content
  • RDA 7.25.3
  • Scope = “the ratio of horizontal distances in the cartographic content of a resource to the actual distances they represent”
  • Sources expanded to any source -- so no square brackets:
  • Basic instructions in 7.25.1; no abbreviations
vertical scale of cartographic content
Vertical scale of cartographic content
  • RDA 7.25.4
  • Scope = “the scale of elevation or vertical dimension of the cartographic content of a resource”
  • Source: any source within the resource
marc for horizontal vertical scale
MARC for Horizontal/Vertical scale …
  • 255 field (bibliographic format): add “Scale” or “Vertical scale”

255 $a Scale 1:63,360.

255 $a Scale 1:6,336,000. Vertical

scale 1:192,000.

255 $a Scale approximately 1:220,000.

date of expression
Date of expression
  • RDA 6.10
  • Scope = “earliest date associated with an expression”
    • May use date of the earliest manifestation embodying the expression
  • Core if needed to differentiate an expression of a work from another expression of the same work
marc for date of expression
MARC for Date of expression
  • Access point: in subfield $f
  • 046 field: subfields $k and $l

046 ## $k 2000

100 1# $a Wilde, Oscar, $d 1854-1900.

$t Works. $f 2000

other distinguishing characteristic of the expression
Other distinguishing characteristic of the expression
  • General instruction: RDA 6.12
  • Specific instructions:
    • musical works (RDA 6.18)
    • religious works (RDA 6.23)
    • selections/excerpts from a larger work (RDA 6.12.1.4)
other distinguishing characteristic of the expression1
Other distinguishing characteristic of the expression
  • Scope = “a characteristic other than content type, language of expression, or date of expression that serves to differentiate an expression from another expression of the same work”
  • Core if needed to differentiate an expression of a work from another expression of the same work
marc for other distinguishing expression
MARC for Other distinguishing … expression
  • Access point: added to the authorized access point for the work
  • Some characteristics have their own subfields in access point:
    • subfield $k for “Selections”
    • subfield $o for musical works (e.g., “arranged”)
    • subfield $s for versions of the Bible, etc.
marc for other distinguishing expression1
MARC for Other distinguishing … expression
  • 381 field: subfield $a

130 #0 $a Nutcracker (Choreographic work :

Baryshnikov)

380 ## $a Choreographic work

381 ## $a Baryshnikov

more other expression
More Other … expression

100 1# $a Dickens, Charles, $d 1812-1870.

$t Oliver Twist. $k Selections

381 ## $a Selections

046 ## $k 2004

130 #0 $a Bible. $l English. $s Authorized.

$f 2004

381 ## $a Authorized

primary relationships1
Primary relationships
  • RDA 17.4
  • Scope = “relationships between a work, expression, manifestation, and item that are inherent in the FRBR definitions”
  • Two relationships are core elements:
    • Work manifested
    • Expression manifested
conventions primary relationships
Conventions: primary relationships
  • RDA 17.4.2
  • Three conventions:
    • identifier [decision by the coordinating committee not to use this convention during the RDA Test]
    • authorized access point for the work or expression
    • composite description
work manifested
Work manifested
  • RDA 17.8
  • Scope = a work embodied in a manifestation
  • If more than one work is embodied in the manifestation, only the predominant or first-named work manifested is required
expression manifested
Expression manifested
  • RDA 17.10
  • Scope = an expression embodied in a manifestation
  • Core if more than one expression of a work
  • If more than one expression embodied in the manifestation, only the predominant or first-named expression manifested is required
relationships authorized access points
Relationships: authorized access points
  • These two relationships represented now in MARC records by the authorized access points for the work(s) and expression(s)
    • Not always a separate access point for the work
  • Some elements needed to identify works and expressions may not be part of the authorized access point -- must rely on other content in the records (e.g., 250 field)
relationships composite descriptions
Relationships: composite descriptions
  • Combination of one or more elements identifying the work and/or expression with the description of the manifestation
    • Essentially the MARC bibliographic record created today containing attributes of work, expression, and manifestation
other changes from aacr2
Other changes from AACR2

1) Can give language of expression for a motion

picture with subtitles (RDA 6.12.1.4)

2) Don’t abbreviate months used in preferred titles

for treaties (no abbreviations for months in

appendix B)

3) When using the name of a translator to identify a

version of the Bible and there are more than two,

use “and others” rather than “et. al.” (RDA

6.25.1.4)

other changes from aacr21
Other changes from AACR2

4) A theological creed, confession of faith, etc.,

does not need to be accepted by one or more

denominational bodies (RDA 6.30.1.4)

5) Possible to have a person as creator for some

sacred scriptures (RDA 6.30.1.2)

6) Use “manuscript” rather than abbreviation

“ms.” (RDA 6.30.4)

other changes from aacr22
Other changes from AACR2

7) No limit on number of authorized access points

for collections of works by different persons,

families, or corporate bodies

8) Appendix I has designators for relationships

between a resource and persons, families, and

corporate bodies associated with that resource

9) Librettos not treated as musical works

other changes from aacr23
Other changes from AACR2

10) Variant access point for librettos: authorized

access point for the musical work plus Libretto,

Text, etc. (RDA 6.27.4.2)

11) Variant access point for cadenzas: authorized

access point for the related work plus Cadenza

(RDA 6.28.4.2)

12) Not abbreviating “arranged,” “accompaniment,”

and “unaccompanied” when added to access point

for musical works

marc coding changes for rda authority records
MARC coding changes for RDA authority records
  • 008/10: value “z” (Other)
  • 040 $a ___ $b ___ $c ___ $e rda
marc authority 670 field
MARC Authority 670 field
  • If no separate MARC field for an RDA element, generally give information in 670 field
  • Agency decision for repeating in 670 field any element already recorded in a separate MARC field
    • Many of new MARC fields include “source” subfields
more information on authority format new fields
More information on authority format new fields
  • LC Network Development and MARC Standards Office site:
  • Training document #5 for LC’s proposed practice for the RDA Test

http://www.loc.gov/marc/authority/ecadhome.html