Thursday, April 25, 2013
May: Programmatic Changes to the LC/NACO Authority File for RDA
Date: May 8, 2013
All webinars are one hour in length and begin at 11am Pacific, noon Mountain, 1pm Central, and 2pm Eastern time.
This hour-long webinar covers the changes to the LC/NACO authority file related to RDA. The phased approach to changes adopted by the PCC will be discused, such as records with the 667 update notice added during Phase 1, as well as records updated as part of Phase 2 of Changes to the LC/NACO Authority File. Changes to the LC/NACO authority file came from the work of two PCC task forces, most recently the PCC Acceptable Headings Implementation Task Group.
This session is part of a two-webinar series that included CONSER RDA Core Elements for Serials on February 13.
Who should attend? Those who contribute to or use the LC/NACO Authority File
Presenter: Dave Reser has been a senior cataloging policy specialist in the Policy & Standards Division of the Library of Congress for the last 15 years, and held positions as a cataloger and cooperative cataloging specialist prior to that. He currently serves as the editor of the Library of Congress-Program for Cooperative Cataloging Policy Statements, and has served as the LC representative to the Joint Steering Committee for Development of RDA since December 2012.
Single Webinar Registration Fees: $39 ALCTS Member; $49 Non-member; $39 International; $99 Group (a group of people that will watch it together).
Check the ALCTS Web site for discount pricing for the entire webinar series.
For additional information and access to registrations links, please go to the following website:
ALCTS webinars are recorded and registrants receive a link to the recording shortly following the live event.
For questions about registration, contact ALA Registration by calling 1-800-545-2433 and press 5 or email email@example.com. For all other questions or comments related to the webinars, contact Julie Reese, ALCTS Events Manager at 1-800-545-2433, ext. 5034 or firstname.lastname@example.org.