Tuesday, October 30, 2012

Second Opportunity for Introducing RDA - A Workshop with Chris Oliver!

Second Opportunity for Introducing RDA - A Workshop with Chris Oliver!

<<<<<---------->>>>>

RDA Blog : RDA Blog is a blog on Resource Description and Access (RDA), a new library cataloging standard that provides instructions and guidelines on formulating data for resource description and discovery, organized based on the Functional Requirements for Bibliographic Records (FRBR), intended for use by libraries and other cultural organizations replacing Anglo-American Cataloging Rules (AACR2). This blog lists description and links to resources on Resource Description & Access (RDA). It is an attempt to bring together at one place all the useful and important information, rules, references, news, and links on Resource Description and AccessFRBRFRADFRSADMARC standardsAACR2BIBFRAME, and other items related to current developments and trends in library cataloging practice.

RDA Blog History: RDA Blog was created by Salman Haider, a Cataloging & Metadata Librarian Blogger & Online Social Media Expert from India. RDA Blog embarked on its journey to provide useful information to Resource Description and Access (RDA) in August 2011. It received good response from librarians, catalogers, and library professionals from all around the world. It is interesting to note that the first hundred thousand pageviews to RDA Blog came in 3 years, but it took just 8 months to reach another hundred thousand pageviews. At present it is viewed at a rate of fifteen to twenty thousand times per month. RDA Blog is widely followed in social media.

See also:

Thanks all for your love, suggestions, testimonials, likes, +1, tweets and shares ....

See also related posts in following RDA Blog Categories (Labels):

Tuesday, October 16, 2012

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)

Changes in LC-PCC Policy Statements in the October 2012 release of the RDA Toolkit

Friday, October 12, 2012

LCPS is now LC-PCC PS

(source: Library of Congress Website 10/2/12)

The Library of Congress and the Program for Cooperative Cataloging are pleased to announce a title change of the "Library of Congress Policy Statements" to "Library of Congress-Program for Cooperative Cataloging Policy Statements" (LC-PCC PSs) effective with the October 2012 release of the RDA Toolkit. The new title reflects the ongoing collaboration of LC and PCC in adopting a single set of policy statements, with clear labels indicating any differences in application. Adding "PCC Practice" statements has already begun, and will be ongoing until completed; developing new policy statements, negotiating changes to existing statements, etc., will be an ongoing activity shared by LC and PCC.
Current Library of Congress-Program for Cooperative Cataloging Policy Statements (LC-PCC PSs) are freely available as part of the RDA Toolkit. Go to Access the RDA Toolkit External Link and click on the "Resources" tab; a license to the Toolkit is not required. This allows fast and easy access through a single source to the most current policy information. Copies of LC-LCC PSs are also available in Cataloger's Desktop.