Add Bookmark

Please click in the document at the location of desired bookmark.

Find URL

Please click in the document at the location for the desired URL.

Warning

Content displayed is Filtered. Hits in filtered content are not currently visible in the document as displayed. To view all hits, select the Full view from the View Text menu.

LC-PCC PS for 25.1
RELATED WORK
CORE ELEMENT FOR LC
Related work is a core element for LC for compilations.
LC practice: Give a MARC 505 contents note unless the contents are indicated in another part of the description (e.g., in MARC 245 $a because no collective title is present). There is no limit on the number of works in the contents note unless burdensome. For compilations of works, give an analytical authorized access point for the predominant or first work in the compilation when it represents a substantial part of the resource. Disregard contributions such as a preface or introductory chapter. Generally, do not apply this core element to anthologies of poetry, hymnals, conference proceedings, journals, collections of interviews or letters, and similar resources.
Related work is also a core element for LC for serial relationships such as “Continuation of,” “Continued by,” etc.; generally, give these as reciprocal relationships.
PCC practice: Give complete contents in a MARC 505 contents note unless considered burdensome or unless the contents are indicated in another part of the description (e.g., in MARC 245 $a because no collective title is present). For compilations of works, give an analytical authorized access point for the predominant or first work in the compilation when it represents a substantial part of the resource. Optionally, give analytical authorized access points for works other than the predominant or first work, if considered important for access. Disregard contributions such as a preface or introductory chapter. Generally, it is not necessary to give contents notes for anthologies of poetry, hymnals, conference proceedings, journals, collections of interviews or letters, chapters of multivolume monographs cataloged as monographic sets and similar resources.
PCC practice: For rare materials, citation notes and references to published descriptions are encouraged. Record in the form prescribed by Standard Citation Forms for Rare Materials Cataloging.
[2017-03]
LC-PCC PS for 25.1.1.3
RECORDING RELATIONSHIP TO RELATED WORK
Formal Contents Notes (Structured Descriptions)
LC practice/PCC practice: Create a formal contents note as follows:
1.
Use the appropriate value in indicator 1 of MARC field 505 (Formatted Contents Note) to indicate the character of the note, e.g., "Contents:"; "Incomplete contents:"; "Partial contents:".
2.
Record the title proper that appears in the source that provides the best identification; however, if the title appears on the title page, normally use the title page title; generally give other title information only when the title proper would be meaningless without it or when it would greatly enhance keyword searching.
3.
When the contents listed have different statements of responsibility, generally record a first statement of responsibility for each title proper recorded in the contents note.
4.
Generally omit prefatory and similar matter of little importance.
5.
For publications in one volume:
a)
Omit chapter and section numbering.
b)
Use a space-dash-space to separate the components.
6.
For publications in two or more volumes:
a)
Give the volume designation that is found on the resource; separate the volume designation from the title by a period-space.
b)
If the number of physical volumes differs from the number of bibliographic volumes, include the number of physical volumes within parentheses after the title (or after the title and statement of responsibility).
c)
Separate each volume with a space-dash-space; if the set is incomplete, put the space-dash-space before each title (other than the first) that is being recorded and leave four spaces for the missing volume; if two or more titles are being transcribed for one volume, apply the punctuation conventions from ISBD such that the titles by the same person, body, etc., are separated by a space-semicolon-space and titles by different persons, bodies, etc., are separated by a period-space.
d)
When some of the volumes in a multipart publication have their own titles and some of the volumes do not, and it is decided to make a formal contents note, use the statement "[without special title]" to represent the untitled volumes.
LC practice: Follow the guidelines stated above modified as follows:
1.
For LC original cataloging, encode contents information at the MARC 21 basic level (MARC field 505 second indicator = #) and do not use subfields $g, $r, or $t.
2.
Give tables of contents in e-CIP records according to the guidelines in DCM D8.9; note that the limitation stated in 2. immediately above does not apply in the case of e-CIP records.
3.
When the cataloger has created a single bibliographic record that covers a number of ephemeral publications, follow DCM C18.8 or DCM C14.
4.
If the volumes are of different editions (see Policy Statement 2.5.1.6.1), include within parentheses edition statements and dates of publication, distribution, etc., after the title (or title and statement of responsibility).
Serials
LC practice/PCC practice: For serials, prefer using MARC 7XX subfield $i or specifically-defined MARC tags (e.g., MARC fields 780 and 785 for sequential relationships) rather than MARC 5XX fields for recording relationships to related works. Relationships that would be coded in MARC fields 773, 774, or 787 are not required. Give reciprocal relationships when appropriate.
Authorized Access Points for Component Parts of Compilations of Laws (Comprehensive Description)
LC practice/PCC practice: If a comprehensive description for a compilation includes a part or parts noted in either the MARC 245 field or in MARC 500 fields and a separate description is not made for the part(s), give an authorized access point for the following types of component part(s): the component part is a type that is not normally associated with the compilation; the component part has a numbering system separate from that of the compilation. Do not, however, give access points for the following: pocket supplements, separately issued supplements, replacement volumes, and indexes. If more than three different component parts are mentioned, generally do not give access points for any of them.
 
 
 
EXAMPLE
 
110 1#$a District of Columbia.
240 10$a District of Columbia Code (2001)
245 10$a LEXIS District of Columbia Code annotated.
500 ##$a Kept up to date by pocket parts, replacement volumes, advance annotation service, and advance legislative service.
730 02$a Advance annotation service to LEXIS District of Columbia code.
Annotation service prepared by the publisher
 
110 1#$a Nevada.
240 10$a Nevada Revised Statutes (1957)
245 10$a Nevada Revised Statutes annotated ...
500 ##$a Includes an unnumbered volume with title: Court rules annotated.
No access point for the volume of court rules because such a part is a regular feature of compiled statutes of U.S. states
 
 
 
Authorized Access Points for Component Parts of Compilations of Laws (Analytical Description)
LC practice/PCC practice: If an analytical description is prepared for a component part of a compilation, make a note on the comprehensive description about the component part. In the description for the component part, make a note showing the relationship to the comprehensive entry and give an authorized access point for the compilation.
 
 
 
EXAMPLE
Comprehensive description
110 1#$a Georgia.
240 10$a Official Code of Georgia Annotated (1981)
245 10$a Official code of Georgia Annotated ...
500 ##$a Kept up to date by pocket supplements, replacement volumes, and Advance annotation service.
No access point is included for the separately numbered component part Advance annotation service if it is cataloged separately
Analytical description
245 00$a Official Code of Georgia Annotated. $p Advance annotation service / $c prepared by the editorial staff of the publisher.
500 ##$a Updates the annotations of the Official Code of Georgia Annotated.
710 1#$a Georgia. $t Official Code of Georgia Annotated (1981)
 
 
 
Follow the same practice when a single publication is related to several successive editions of a compilation (e.g., an annotation service updating several successive biennial codes). Note that an edition of the comprehensive work is not specifically identified.
 
 
 
EXAMPLE
Comprehensive description
110 1#$a Montana.
240 10$a Montana Code Annotated (1979)
245 10$a Montana Code Annotated ...
264 #1$a Helena, Mont. : $b Montana Legislative Council, $c 1979-1980.
500 ##$a Annotations updated between editions by Montana Code Annotated. Annotations.
Analytical description
245 00$a Montana Code Annotated. $p Annotations.
264 #1$a Helena, Mont. : $b Montana Legislative Council, $c [1980]-
500 ##$a Annotates the most recent edition of Montana Code Annotated.
710 1#$a Montana. $t Montana Code Annotated.
 
 
 
[2017-07]