USING THE - Home | Library of Congress



Library of Congress Training for

RDA: Resource Description & Access

RDA: Module 3 --

Identifying Expressions and Describing Content

Developed by

Tim Carlton

Cooperative and Instructional Programs Division

Library of Congress

September 2012

Library of Congress Training for RDA: Resource Description & Access

RDA: Module 3 --

Identifying Expressions and Describing Content

Course Summary

This course is one element in a comprehensive suite of training prepared for the Library of Congress implementation of “RDA: Resource Description & Access” as a new cataloging code. It is intended for any person who needs to learn and apply the new rules in the processing of material for the Library collection.

Learning Objectives

At the end of this course, participants will be able to:

• Describe the FRBR entity, “expression”

• Extract data from the appropriate sources

• Determine the basis for the authorized access point for an expression

• Supply additions to construct the access points for expressions

• Apply LC policies as stated in Library of Congress Policy Statements

• Construct variant access points for expressions according to LC policy

• Properly record expression data in MARC authority records

• Record attributes of works and expressions that are related to intellectual or artistic content

• Locate and record the proper relationship designators for creators and contributors

• Effectively connect related works, expressions, and manifestations

Training Methods:

Lecture, discussion, and exercises

Duration:

3 hours

Table of Contents

Unit 1: Elements for Expressions 1

“Expression” -- The FRBR Entity 1

Identifying the Expression 1

LC Decisions on … 1

Is This Data Recorded as Bibliographic Data or Authority Data? 1

How to Identify Expressions 1

Using Existing Name Authority Records 2

Contributors 2

Constructing the Authorized Access Point Representing an Expression 2

Additions to Authorized Access Points for Expressions 3

Content Type 3

Content Type Recorded in 336 Field 3

Date of Expression 4

Language of Expression 4

If One Expression … 4

If Two or More Expressions … 5

Other Distinguishing Characteristic of the Expression 6

Variant Access Points for Expressions 6

MARC Authority Fields for Expressions 7

For More Guidance 7

LCPS 6.27, “Constructing Access Points to Represent Works and Expressions” 7

“What LC-PCC RDA Catalogers Need to Know” 7

Additional Resources 7

Unit 2: Exercise on Expressions 9

Unit 3: Exercise on Creators and Contributors 11

Unit 4: Describing Content 13

Content Attributes that are Recorded in the 300 field 13

Duration 13

Recording Playing Time, Running Time, etc. 13

Illustrative Content 14

Recording Illustrative Content 14

A Key Change from AACR2 14

Colour Content 14

Recording Colour Content 14

General Guidelines on Describing Content 15

Attributes of Works 15

Nature of the Content 15

Coverage of the Content 15

Coordinates of Cartographic Content 15

Intended Audience 16

Dissertation or Thesis Information 16

Attributes of Expressions 17

Summarization of the Content 17

Language of the Content 17

Form of Notation 18

Script 18

Supplementary Content 18

Music Resources 19

Cartographic Resources 19

Unit 5: Exercise on Content 21

Appendix 1: Creators, Contributors, and Relationship Designators 23

Appendix 2: New Work? New Expression? New Manifestation? 25

Unit 1: Elements for Expressions

“Expression” -- The FRBR Entity

“Expression” is the way in which a work (the idea in the creator’s mind) is expressed. e.g.:

• through language (i.e., alpha-numeric characters)?

• through sound?

• through performance?

Identifying the Expression

Authorized access points are used in bibliographic records to identify the expression being cataloged; also in 6XX and 7XX fields to represent relationships to other expressions. Just as for Works, the forms of authorized access points for Expressions are prescribed according to the instructions in RDA Chapter 6.

Identifying the expression is a simple two-step process, similar to identifying the Work:

1. Name the work

2. Add expression-level identifying information

LC Decisions on …

Is This Data Recorded as Bibliographic Data or Authority Data?

• Always identify the expression by giving information in the bibliographic record; sometimes (per DCM Z1) also by making a title or name/title authority record

• Authorized access points are used in other authority records as 5XX fields (relationships to other expressions) for treaties and in cases of cataloger judgment

How to Identify Expressions

• Per LCPS 0.6.3 (Core Elements for Works and Expressions), LC will identify expressions by adding an attribute to the authorized access point in only these situations:

o Music resources (RDA 6.28.3)

o Sacred scriptures (RDA 6.30.3)

o Translations and language editions (RDA 6.27.3)

• For other than these three categories, LC will identify the expressions by utilizing other fields in the bibliographic record.

o Content type

▪ 336 field

o Language

▪ 008/35-37

▪ 041 field

▪ 546 field

• Do not add another characteristic to differentiate one such expression from another. For example: do not differentiate one translation of Shakespeare’s Hamlet in French from another French translation; do not differentiate one arrangement of Berlioz’ Corsaire from another arrangement.

Using Existing Name Authority Records

• If there is already an AACR2 NAR, what you do depends on how many expressions are represented by that NAR (there are usually multiple language expressions).

o If only one, use the form in the NAR.

o If more than one, do not use that form in your bibliographic record 7XX field. Instead, give separate access points for each expression in the bibliographic record 7XX fields.

• If there is already an RDA NAR, use that form of the access point, even if it includes an additional expression attribute LC wouldn’t include; this action is consistent with the LC/PCC policy of using authorized access points in existing name authority records.

Contributors

Remember that those entities “contributing to the realization of a work through an expression” are called contributors -- not creators. The instructions for contributors are found in Chapter 20.

Examples of contributors are editors, translators, illustrators, arrangers of music, performers, writers of commentary, and others.

“Contributor” is a relationship of a Group 2 FRBR entity (Person, Family, or Corporate Body) to a Group 1 FRBR Entity (specifically, an Expression).

The discussion below concerns the addition of an access point to reflect this relationship -- not the transcription of the statement of responsibility attribute.

20.2.1.3 provides numerous examples, and LCPS 20.2.1.3 provides the core element instruction:

( Contributor (as a relationship) is a CORE ELEMENT for LC only for illustrators of resources for children. If multiple illustrators are present, apply cataloger judgment to give more than the first (we already saw, in RDA Chapter 2, that transcribing the first statement of responsibility relating to title proper is CORE).

RDA Appendix I.3.1 lists the relationship designators used for contributors.

Constructing the Authorized Access Point Representing an Expression

← Look at 6.27 to see how to construct the authorized access point for an expression:

• The basis is the authorized access point for the work

• Add one or more of the elements listed in 6.27.3

Example:

Goncourt, Edmond de, 1822–1896. Frères Zemganno. English

(Resource described: The Zemganno brothers / by Edmond de Goncourt. An English translation of a French novel)

Additions to Authorized Access Points for Expressions

Here are the four possible additions:

a) a term indicating content type (6.9)

b) the date of the expression (6.10)

c) a term indicating the language of the expression (6.11)

d) a term indicating another distinguishing characteristic of the expression (6.12)

( The elements are not required; they are added if needed to differentiate. Nor are they listed here in priority order; choose the most useful element(s).

Content Type

( Look at instruction 6.9

( Content type is a CORE ELEMENT when needed to differentiate an expression.

(Note that content type is labeled CORE in the Toolkit; but that relates to its use in the specifically coded 336 field. When considering whether to use it in an authorized access point for an expression, it is recorded only if needed to break a conflict -- although in practice another expression attribute is often used instead, so it seldom comes into play).

Content type is “a categorization reflecting the 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 as images, content type also reflects the number of spatial dimensions in which the content is intended to be perceived and the presence or absence of movement.

Take information on content type from any source.

Record a term or terms from the controlled vocabulary listed in Table 6.1 within RDA 6.9.1.3. You can record as many terms as are applicable to the resource being described. If none of the listed terms apply to the resource being described, record “other.” If the content type cannot be readily ascertained, record “unspecified.”

The content type -- if used -- is recorded in $h of the access point.

Content Type Recorded in 336 Field

LC catalogers will also record content type in MARC field 336 in bibliographic records.

This data can be easily recorded using ILS templates (for new records) and macros (for updating existing records). You are free to add additional 336 fields if appropriate. If there are multiple components of a resource (e.g., a book and a CD) and the term does not apply to all components, you may optionally use $3 to indicate what the term applies to (but this is not required).

LC policies for content type are the same as for media and carrier types discussed in Module 2.

( The PowerPoint presentation illustrates some examples of content type in 336 fields.

Date of Expression

( Look at instruction 6.10

LCPS 6.27.3 reiterates that LC adds an expression attribute only in the following situations:

• Music resources

• Sacred scriptures

• Translations and language editions

( You are no longer required to add a date for compilations whose preferred title is a collective title beginning with “Works.” This is a change from AACR2/LCRI practice!

You may take information for date of expression from any source

If you use the date of expression, the date of the earliest manifestation embodying the expression may be treated as the date of expression.

( If you find NARs which include the Date of Expression, you may continue to use that form. But do not create such a NAR or add the element to an existing NAR.

Language of Expression

( Look at instruction 6.11

( Language is a CORE ELEMENT when needed to differentiate an expression.

Take information on language of expression from any source.

The language of expression is recorded in $l of the access point. Use term(s) from the MARC Code List for Languages.

When determining whether you need to add a language attribute, determine whether you have …

• one expression in more than one language (for example, Tolstoy’s War and Peace, which included both Russian and French text in the original) or,

• two or more expressions

If One Expression …

• If the manifestation has only one expression in one language, give subfield $l only if the expression is a translation.

Example:

Brunhoff, Jean de, 1899-1937. Babar en famille. English

• If the manifestation has only one expression in more than one language, do not give subfield $l unless it is a translation.

Made-up example:

Tolstoy, Leo, graf, 1828-1910. Voĭna i mir.

(Resource described: a manifestation titled “Voĭna i mir L.N. Tolstogo”)

If Two or More Expressions …

← If the manifestation is a compilation of the original and one translation of the same work, record an analytical authorized access point for the original expression (without the $l for the language), and record a separate analytical authorized access point for the translation (with the $l for the language)

Example:

100 1# $a Macken, JoAnn Early, $d 1953-

245 10 $a Mail carrier = $b El cartero / $c JoAnn Early Macken.

700 12 $a Macken, JoAnn Early, $d 1953- $t Mail carrier.

700 12 $a Macken, JoAnn Early, $d 1953- $t Mail carrier. $l Spanish.

← If the compilation contains the original expression and more than one translation, give analytical authorized access points for the original expression (without the $l for the language) and at least one translation (with the $l for the language); giving additional analytical access points is cataloger judgment.

Other Language Situations

• If the manifestation is a compilation of two or more expressions of the same work in different languages, and the original expression is not present, record at least one of the expressions in an analytical authorized access point, with subfield $l for the language.

• If the manifestation is a compilation of two or more expressions of the same work in different languages, and you cannot determine the original, do the following:

o For the purpose of choosing the preferred title, choose the title proper named first on the preferred source of information as the preferred title of the work (i.e., treat the first as if it is the original edition)

o For the purpose of providing analytical a.a.p.’s, treat the manifestation as if you have a compilation of the original and more than one translation:

← Provide an analytical a.a.p. for the expression designated as the original, without subfield $l for the language

← Provide an analytical a.a.p. for at least one more expression, with subfield $l for the language

Example:

245 00 $a Diplôme international de l'OIV en management du secteur de la vigne et du vin : $b OIV MSc in wine management = International diploma of the OIV in management of the vine and wine sector = Internationales Diplom der OIV im Fachberich Management im Weinbausektor = Diploma internazionale dell'OIV in getion del settore della vigna e del vino = Diploma internacional de la OIV de management del sector la viña y el vino.

730 02 $a Diplôme international de l'OIV en management du secteur de la vigne et du vin.

730 02 $a Diplôme international de l'OIV en management du secteur de la vigne et du vin. $l English.

No Longer Use …

Two important changes have occurred from AACR2:

• Do not use “Polyglot” in subfield $l

• Do not record in one subfield multiple languages (e.g., “French & English”). Instead, provide specific information about all the languages of each expression.

Other Distinguishing Characteristic of the Expression

( Look at instruction 6.12

( Other Distinguishing Characteristic is a CORE ELEMENT when needed to differentiate an expression.

Other Distinguishing Characteristic is “a characteristic other than content type, language of expression, or date of expression that serves to differentiate an expression.”

Take information on other distinguishing characteristic from any source.

In addition to the general instruction, there are specific instructions for musical works (6.18), legal works (6.21), and religious works (6.25).

The other distinguishing characteristic is generally recorded at the end of the last subfield. However, some characteristics have their own subfields in access points, such as subfield $o for musical expressions and subfield $s for versions of the Bible (etc.).

Variant Access Points for Expressions

Variant access points for expressions -- that is to say, cross-references on Name Authority Records -- are not core elements in RDA.

LC policy is to apply cataloger judgment to determine if a variant access point is important for a user to be able to find or identify the expression.

If a variant access point for an expression is recorded, it may be one of the following:

• based on a variant title of the work associated with a particular expression

Example:

100 0# $a Hartmann, $c von Aue, $d active 12th century. $t Works. $l English.

400 0# $a Hartmann, $c von Aue, $d active 12th century. $t Arthurian romances, tales, and lyric poetry

670 ## $a Hartmann, von Aue. Arthurian romances, tales, and lyric poetry, [2001]

or

• a form with a variant of the addition in the authorized access point.

Example:

100 0# $a Theodore bar Konai, 8th/9th century. Liber scholiorum (Urmiah version)

400 0# $a Theodore bar Konai, 8th/9th century. Liber scholiorum (Ourmia version)

670 ## $a ………

MARC Authority Fields for Expressions

Apply cataloger judgment when deciding whether to include these fields in any name authority records made for expressions:

• 046: Special coded dates

• 336: Content type

For More Guidance

LCPS 6.27, “Constructing Access Points to Represent Works and Expressions”

Here are some highlights of this important Policy Statement which covers, among other issues, “Authority Records in the LC/NACO Authority File”:

• Catalogers creating RDA bibliographic records will use authorized forms established in existing AACR2 and RDA authority records. As a result, some bibliographic records may contain a mix of authorized headings created according to AACR2 and RDA.

• If no AACR2 or RDA authority record exists, catalogers will create RDA authority records. The resulting authorized access points will be used as needed in both RDA and AACR2 bibliographical records.

• Exception: Do not create ‘hybrid’ AACR2/RDA authorized access points in establishing new headings or in making additions to existing headings. Follow one cataloging code or the other in establishing authorized access points. Catalogers making additions to AACR2 headings or making new headings based on existing AACR2 records (e.g., name/title) will use AACR2 rules and appropriate LCRIs. Catalogers making additions to RDA headings or making new headings based on existing RDA records (e.g., name/title) will use RDA instructions.

• LC practice: Do not add 7XX fields for RDA forms to AACR2 records or 7XX fields for AACR2 forms to RDA records (this was done during the RDA test and you may see them in NARs; simply ignore these 7XX fields)

“What LC-PCC RDA Catalogers Need to Know”

This interim document summarizes the programmatic changes that will be made to the LC/NACO Authority File, and provides guidance regarding “What an RDA cataloger should do.” It can be found at:

Additional Resources

There are several additional resources you can consult for information and examples about these new fields. These are the same resources that were referred to when we discussed Works, so they are only listed here, without further elaboration.

← Refresher Training R-Documents R-5 and R-6

← Training Examples Folder at

← NetDev MARC page

Unit 2: Exercise on Expressions

First, let’s look at an example of a name authority record with expression data:

( Look at document R-6 in your pack of “refresher documents”

Example 14 is an example of an authority record for an expression.

Now, work with your colleague to complete:

• Exercise #6 Identifying Expressions

We will go over this exercise together in a few minutes.

Unit 3: Exercise on Creators and Contributors

Work with your colleague to complete:

• Exercise #7 Creators and Contributors

We will go over this exercise together in a few minutes.

Unit 4: Describing Content

This Unit provides general instructions on recording the attributes of works and expressions associated with the intellectual or artistic content of a resource. The elements include those that users typically rely on when selecting a resource to meet their requirements relating to content.

The “Content” elements delineated in RDA are of two types: attributes of the Work, and attributes of the Expression.

Content Attributes that are Recorded in the 300 field

But first, we will cover three content attributes that are recorded in the MARC 300 field (remember that the 300 field is a mix of carrier and content). Because these elements are related to content, they are covered in RDA Chapter 7, not Chapter 3.

Duration

( Duration is a CORE ELEMENT for LC

Duration is the playing time, running time, etc., of the content of a resource. Duration also includes performance time for a resource containing notated music or notated movement.

← Look at instruction 7.22

This data is recorded in MARC field 300 $a

Sources: Take information on duration from any source.

Recording Playing Time, Running Time, etc.

If the resource has a playing time, running time, etc., record it as follows. Abbreviating terms for units of time as instructed in appendix B.

• If the total playing time, running time, etc., is stated on the resource, record the time stated.

Example:

(2 hr., 15 min.)

• If the total playing time, running time, etc., is not stated on the resource but is readily ascertainable, record it.

Example:

(30 min.)

• If the total playing time, running time, etc., is neither stated on the resource nor readily ascertainable, record an approximate time preceded by approximately.

Example:

(approximately 90 min.)

• If the total playing time, running time, etc., cannot be approximated, omit it.

Other instructions under 7.22 address performance time, duration of individual parts, and resources containing both sound and/or moving images and text.

Illustrative Content

( Illustrative content is a CORE ELEMENT for LC for resources intended for children.

This data is recorded in MARC 008/18 as applicable and field 300 $b

Sources: Take information on illustrative content from any source.

Recording Illustrative Content

If the resource contains illustrative content, record “illustration” or “illustrations”, as appropriate. Tables containing only words and/or numbers are not considered as illustrative content. Disregard illustrated title pages, etc., and minor illustrations.

( Look at LCPS 7.15.1.3 for the alternative

“Generally do not record the type of illustrative content in place of

or in addition to the term ‘illustration’ or ‘illustrations.’ ”

A Key Change from AACR2

Do not use abbreviations!

• “color” (not “col.”)

• “sound” (not “sd.”)

• “silent” (not “si.”)

• “illustrations” (not “ill.”)

Colour Content

← Look at instruction 7.17

This data is recorded in MARC field 300 $b

Sources: Use evidence presented by the resource itself as the basis for recording the presence of color content. If desired, take additional evidence from any source.

Recording Colour Content

If the content of the resource is in colors other than black and white or shades of grey, record the presence of color using an appropriate term. Disregard colored matter outside the actual content of the resource (e.g., the border of a map).

( Look at LCPS 7.17.1.3

LC practice: Use the spelling “color” when recording that term.

Examples:

color (illustrations are in color)

some color (10 maps, some of which are in color)

chiefly color (illustrations, most of which are in color)

General Guidelines on Describing Content

These attributes are delineated in RDA Chapter 7, “Describing Content.”

Sources: Take information used to describe content from the resource itself. In certain cases the information may be taken from sources outside the resource.

Attributes of Works

Nature of the Content

The nature of the content is the specific character of the primary content of a resource.

← Look at instruction 7.2

This data is recorded in MARC 008/24 as applicable, and field 500

Record the nature of the content if it is considered to be important for identification or selection.

Examples:

Singspiel in two acts

Spreadsheet, with word processing and graphic capabilities

Coverage of the Content

The coverage of the content is the chronological or geographic coverage of the content of a resource.

← Look at instruction 7.3

This data is recorded in MARC field 500

Record the coverage of the content if it is considered to be important for identification or selection.

Examples:

Based on 1981 statistics

Shows all of western Europe and some of eastern Europe

Coordinates of Cartographic Content

( Longitude and Latitude is a CORE ELEMENT for LC. Because this element is recorded only by cartographic catalogers, we will not cover it in this course. If you need to catalog cartographic resources, consult the instructions in RDA 7.4.

Intended Audience

( Intended audience is a CORE ELEMENT for LC for resources intended for children

Intended audience is the class of user for which the content of a resource is intended, or for whom the content is considered suitable, as defined by age group, educational level, type of disability, or other categorization.

← Look at instruction 7.7

This data is recorded in MARC 008/22 as applicable, and field 521

Record the intended audience if the information is stated on the resource or is readily available from another source and is considered to be important for identification or selection.

Examples:

For children aged 7-9

For remedial reading programs

Dissertation or Thesis Information

( Dissertation or thesis information is a CORE ELEMENT for LC

Dissertation or thesis information is information relating to a work presented as part of the formal requirements for an academic degree.

← Look at instruction 7.9

This data is recorded in MARC 008/24 as applicable; and field 502 or 500

← Look at LCPS 7.9.1.3

• Record the sub-elements related to dissertation or thesis information in the appropriate subfields of MARC field 502, without AACR2-style punctuation.

Example:

502 ## $b Ph.D. $c University of Toronto $d 1974

• Do not routinely restructure pre-RDA style dissertation or thesis information in existing records.

Example:

502 ## $a Thesis (Ph.D.) – University of Toronto, 1974

(AACR2-style note, using $a only; do not restructure)

• If the resource lacks a formal thesis statement containing information related to the sub-elements, state its origin as a thesis in a general note in MARC field 500.

Example:

500 ## $a Revision of the author’s thesis

( Because LC catalogers rarely catalog original theses or dissertations, you will rarely record a 502 field; usually, you will construct a 500 field (see the last bullet above).

Attributes of Expressions

Summarization of the Content

( Summarization of the content is a CORE ELEMENT for LC for fiction intended for children.

A summarization of the content is an abstract, summary, synopsis, etc., of the content.

← Look at instruction 7.10

This data is recorded in MARC fields 520 and 856

Provide a brief summary of the content if it is considered to be important for identification or selection (e.g., for audiovisual resources or for resources designed for use by persons with disabilities) and sufficient information is not provided in another part of the description.

← Look at LCPS 7.10.1.3:

• Bibliographic records issued by the Library of Congress may include summaries, reviews, and abstracts from various sources, both internal and external.

• This LCPS provides guidance on the use of MARC fields 520 (Summary, Etc.) or 856 (Electronic Location and Access)

Language of the Content

( Language of the content is a CORE ELEMENT for LC

Language of the content is a language used to express the content of a resource.

← Look at instruction 7.12

This data is recorded in MARC fields 041 and 546

Sources: Take information on the language of the content from any source.

Record details of the language or languages used to express the content of the resource if they are considered to be important for identification or selection.

← Look at LCPS 7.12.1.3

• In addition to recording the language of the primary content, also record the languages of other content (summaries, tables of contents, etc.) if it will assist identification and selection.

Examples:

041 ## $a fre $a eng $a ita

546 ## $a Articles chiefly in French; one article each in English and Italian.

• When naming a language in a note, base the name on the form found in the current edition of MARC Code List for Languages

Form of Notation

( Form of notation is a CORE ELEMENT for LC for some scripts and for form of musical notation.

Form of notation is a set of characters and/or symbols used to express the content of a resource.

This data is recorded in MARC field 546

Script

Script is a set of characters and/or symbols used to express the written language content.

← Look at instruction 7.13.2

Sources: Take information on the script from any source.

Record the script or scripts using one or more of the terms listed in ISO 15924,” Codes for the representation of names of scripts,” ().

Examples:

Devanagari

Armenian

Cyrillic

(Resource written in both scripts)

Use the English-language names of scripts. Generally do not include the parenthetical information found in the list when recording the script name.

If a resource is in a language that is commonly written in more than one script, name both the language and the script.

Example:

546 ## $a Serbian $b Latin

Supplementary Content

( Supplementary content is a CORE ELEMENT for LC for indexes and bibliographies in monographs.

Supplementary content is content designed to supplement the primary content of a resource (e.g., an index, a bibliography, an appendix).

← Look at instruction 7.16

This data is recorded in MARC fields 500 and 504

Sources: Take information on supplementary content from any source.

Record the nature of supplementary content (i.e., its type, extent, location within the resource, etc.) if it is considered important for identification or selection.

← LCPS 7.16.1.3 provides extensive guidance on recording supplementary content

• Routinely consider the following as being important for selection: bibliographies and bibliographical references, discographies, filmographies, indexes, appendices, errata slips that are not printed as part of the publication.

• Give pagination or foliation unless the sections are scattered through the resource.

• If a publication contains bibliographical citations in any form, generally use the following note:

504 ## $a Includes bibliographical references.

• If there is a single bibliography, add the foliation/pagination to the note.

504 ## $a Includes bibliographical references (pages 310-325).

• If the publication contains an index to its own contents, use one of the following:

500 ## $a Includes index.

• The bibliography note and the index note may be combined.

504 ## $a Includes bibliographical references and index.

Music Resources

There are three LC Core elements for music resources. They are merely listed here with the appropriate RDA instruction number.

• Form of musical notation 7.13.3

• Format of notated music 7.20

• Medium of performance of musical content 7.21

Cartographic Resources

There are four LC Core elements for cartographic resources. They are merely listed here with the appropriate RDA instruction number.

• Horizontal scale 7.25.3

• Vertical scale 7.25.4

• Additional scale information 7.25.5

• Projection of cartographic content 7.26

Unit 5: Exercise on Content

Work with your colleague to complete:

• Exercise #8 Describing Content

We will go over this exercise together in a few minutes.

Appendix 1: Creators, Contributors, and Relationship Designators

The term “relationship designator” refers to a designator that indicates the nature of the relationship between a work or expression and a person, family, or corporate body associated with that work or expression, represented by an authorized access point. Relationship designators indicate the function performed by the person, family, or corporate body.

RDA Appendix I provides general guidelines on using relationship designators and lists relationship designators used for each specific type of relationship. Appendix I is structured in accordance with the structure of Chapters 19 and 20, and this structure will help you understand the difference between those entities that are involved at the work level (i.e., creators, other entities responsible for a work, covered in Chapter 19), and those entities that are involved at the expression level (i.e., contributors, covered in Chapter 20).

To develop a sense of expertise, follow along with the instructor to briefly review some of the terms in the three sections described below:

I.2. Relationship Designators for Persons, Families, and Corporate Bodies Associated with a Work

• I.2.1. Relationship Designators for Creators

• I.2.2. Relationship Designators for Other Persons, Families, or Corporate Bodies Associated with a Work

I.3. Relationship Designators for Persons, Families, and Corporate Bodies Associated with an Expression

• I.3.1. Relationship Designators for Contributors

Be sure to read the ‘scope’ of a designator to ensure that you are using it in the intended sense; do not use a “work” designator with an “expression” access point. For example, there is a difference between “compiler” (I.2.1) and “editor of compilation” (I.3.1).

( LC practice: Remember that LC policy is to always provide an authorized access point in the bibliographic record for an illustrator in all cases of resources intended for children. In these cases, the designator “illustrator” is also required in MARC 7XX subfield $e.

( In other cases, the use of relationship designators is optional. You are encouraged to utilize them if, in your judgment, it assists in the user tasks of “find,” “identify,” “select,” “obtain.” But you should neither agonize nor spend a lot of time making these decisions. Providing the access points themselves is more useful, and adding relationship designators may in many cases not enhance the record significantly. If you use them, use them correctly.

Appendix 2: New Work? New Expression? New Manifestation?

An important determination in RDA -- and one which results in a major change from AACR2 -- is whether a revised edition requires a “Uniform Title” to connect it to the earlier edition.

To fully understand this, you have to think in terms of the FRBR concepts of “Work” and “Expression”; try to forget the pre-RDA conception of a ‘work’ as ‘this thing I am cataloging’ (remember, that is a ‘manifestation’). Keep in mind the graphic representation we saw of the continuum from original work, to new expression, to new work.

This appendix provides examples of some common situations in monographic cataloging relating to revised editions and works published under different titles without revision. The next training module, “Relationships,” provides instruction on how to related revised editions and new manifestations. More detailed guidance on revised editions can be found in the “RDA Special Topics” presentation found at:

***

One purpose of the authorized access point for the work is to relate all expressions of that same work. If the title proper has changed 1) from one expression to another or 2) from one manifestation of the work to another, they need to be connected with what MARC calls a “uniform title” (“UT” -- a 240 field, or a 130 for a work without a creator).

* The following examples may not be RDA in every aspect, but are used to illustrate the situations.*

What constitutes a new work?

• A different creator (not an additional creator)

• A very different scope of content even if the title proper/preferred title is the same.

These would not be connected with a UT, because the works are not the same.

What constitutes a new expression or manifestation of the same work?

A. New title proper, but the work has not been revised

o new manifestation

o UT field for original preferred title -- same as AACR2

Original:

100 $a Smith, Lacey Baldwin, $d 1922-

245 $a A Tudor tragedy : $b the life and times of Catherine Howard.

260 $a [New York] : $b Pantheon Books, $c [1961]

Later title (no indication of revision):

100 $a Smith, Lacey Baldwin, $d 1922-

240 $a Tudor tragedy

245 $a Catherine Howard / $c Lacey Baldwin Smith.

260 $a Stroud Gloucestershire : $b Amberley, $c [2010], ©2010.

500 $a Originally published under title: A Tudor tragedy.

B. Same title proper, and the work has been revised

o new expression

o no UT field -- same as AACR2 (expressions collocate through 100/245)

Original:

100 $a Harwood, Gregory W.

245 $a Giuseppe Verdi : $b a guide to research / $c Gregory Harwood.

260 $a New York : $b Garland Pub., $c 1998.

Revision:

100 $a Harwood, Gregory W.

245 $a Giuseppe Verdi : $b a research and information guide / $c Gregory W. Harwood.

250 $a Second edition.

260 $a New York, NY ; $a Abingdon, Oxon : $b Routledge, $c 2012.

C. New title proper, and the work has been revised

o new expression

o UT field for original preferred title -- change from AACR2 (related work a.e.)

Example A:

Original:

100 $a Monson, Craig.

245 $a Disembodied voices : $b music and culture in an early modern Italian convent /

$c Craig A. Monson.

260 $a Berkeley : $b University of California Press, $c 1995.

Revision:

100 $a Monson, Craig.

240 $a Disembodied voices

245 $a Divas in the convent : $b nuns, music, and defiance in seventeenth-century Italy /

$c Craig A. Monson.

260 $a Chicago : $b University of Chicago Press, $c 2012.

500 $a Revision of the author’s Disembodied voices.

Example B:

Original:

245 $a Contemporary art and multicultural education / $c edited by Susan Cahan and

Zoya Kucor.

260 $a New York : $b New Museum of Contemporary Art : $b Routledge, $c 1996.

Revision:

130 $a Contemporary art and multicultural education

245 $a Rethinking Contemporary Art and Multicultural Education / $c The New

Museum of Contemporary Art.

250 $a Fully revised second edition.

260 $a New York, NY : $b Routledge, $c 2011.[pic][pic][pic]

-----------------------

This training material has been created for a primary audience of Library of Congress staff. Other audiences are welcome to utilize it as they see fit. However, it should be understood th[?]"#EFGIJKLXYZt‹Œ??’“”—÷ëßÐÁ¸÷®¥™?‡~?‡rh®^K^Ah›?­hHu@5?aJ%jh2Ì5?U[pic]aJmHnHtHu[pic]h›?­hø[pic]í5?aJh›?­h¥zat it reflects policies for LC staff, and should not necessarily be interpreted to either prohibit or require specific practices for persons external to LC.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download