DCM Z1 Update

-
DCM Z1 Update:

1) The update includes agreements between PCC and LC with regard to "best practices" in the new MARC fields for authority records.

Note especially the information on the use of subfields $u and $v; the full text on the use of $u and $v is supplied only in the 046 section, but it is referenced in each of the fields where these subfields may be used.

Here is an excerpt from that 046 section on the use of subfields $u and $v -- NACO catalogers please take note:

The following represents PCC practice on recording sources of information in $u and $v in fields where they are defined, and/or in field 670:

1. 670s must be used to support information used as part of a heading in 1XX and 4XX.

2. For 046, 37X, 381:

a. use of $v is optional if the same information/source is already cited in the 670

b. use $v if the information/source is not cited in a 670

c. use of $u is optional, and should always be preceded by $v.

2) Catalogers are instructed to no longer supply Content Type information in the 336 field of authority records, pending the outcome of report/recommendations from the PCC Access Point for Expressions Task Group. Please see the 336 section.

3) Very exciting: New information on 4XX references in the 4XX section. Here is an excerpt:

Best practice guidelines for RDA:

• Record variants found in the manifestation being cataloged:

° Use cataloger's judgment;

° No limitation on the number or form of references

• Establish additional headings needed to support elements used in 4XX references (e.g. parent body associated with subordinate body being established)

•  Trace a former heading as a cross-reference in all cases, unless the former heading was egregiously incorrect

•  Use the established form of components in 4XX references, except for non-Latin script references

•  If a form found on the manifestation being cataloged includes a variant form of a component of a 4XX reference, that form may be used in its entirety as an additional 4XX reference, provided that it is not divided into its component parts through the use of subfields.

4) The recently announced MARC change in field 368 is not reflected in the DCM Z1 update, but will be changed with the next update; however, please do not use the newly defined subfields in 368 until LC-PCC announces that these are ready for use.

(Source: By Paul Frank through PCC LIST)

Comments

Post a Comment

RDA Blog is DISCONTINUED

RDA Blog is discontinued. Visit below link for updated information on RDA:

Resource Description and Access (RDA)


Popular posts from this blog

Date of Publication Distribution Copyright in RDA & MARC 21 Field 264 Examples

-
Image
Date of Publication, Distribution, and Copyright in Resource Description and Access (RDA) Cataloging Rules  & MARC 264 Examples Table of Contents: Core Element How Date of Publication is defined Where the Rules are for Date of Publication in RDA What are the Sources of Information for Date of Publication in RDA How is Date of Publication Transcribed / Recorded in Resource Description and Access (RDA) Dates of the Non-Gregorian or Julian Calendar; Dates in the Form of Chronogram RDA Examples What to do if the date on the resource is incorrect Multipart Monographs, Serials, and Integrating Resources Date of Publication not Identified in a Single-Part Resource RDA Cataloging Examples of Dates Supplying Dates (Date of Publication Not Identified in the Resource) Importance of Supplying Probable Place and Date of Publication Examples of Supplying Publication Data Other RDA Examples of Dates Date of Distribution Where the Rules are for Date of Distribution in RDA
Read more

RDA -- INTRODUCTION BACKGROUND AND HISTORY

-
Resource Description and Access ( RDA ) is a standard for cataloguing that provides instructions and guidelines on formulating data for resource description and discovery. Intended for use by libraries and other cultural organizations such as museums and archives, RDA is the successor to the Anglo-American Cataloguing Rules, Second Edition (AACR2), the current cataloging standard set for English language libraries. RDA was initially released in June 2010. In March 2012, the Library of Congress announced it will have fully implemented RDA cataloging by March 31, 2013. Several other national libraries including the British Library, Library and Archives Canada, National Library of Australia, and Deutsche Nationalbibliothek also planned to implement RDA in 2013. Background RDA emerged from the International Conference on the Principles & Future Development of AACR held in Toronto in 1997. It was quickly realised that substantial revision of AACR2 was required, which
Read more

Title and Statement of Responsibility in RDA with MARC 21 Examples

-
Image
Contents: Title Proper         Title Proper Transcription Parallel Title Proper Other Title Information Variant Titles Earlier Title Proper and Later Title Proper Statement of Responsibility        “Rule of Three” -- Change from AACR2!           More Than One Statement of Responsibility <<<<<---------->>>>> Title Proper Ø          Title proper is a CORE ELEMENT Title proper is the chief name of a resource.  It is the focus for identifying the preferred source of information.  An alternative title is treated as part of the title proper.  The title proper excludes any parallel titles proper, other title information, and parallel other title information.  This data is recorded in MARC field 245 $a $n $p P          Look at instruction 2.3.2 Sources :           If the information does not appear on a source forming part of the resource itself, take it from one of the following sources (in order of preference
Read more