On March 29, 2013 the Library of Congress’ Policy and Standards Division (PSD) announced a project to update LCSH headings affected by RDA Phase 2 (those headings that are printed in LCSH but established in the name authority file). The project has been completed and the final batch of revised records was distributed through the MARC Distribution Service on Tuesday, April 23rd. The list of subject authority records that were revised is available at Library of Congress Completes Revisions to LCSH Prompted by RDA Phase 2 (PDF, 188 KB)
Personal, corporate, and conference names, as well as titles and geographic headings, were examined as part of the project. Revisions were made to:
- Headings, references and notes
- Phrase headings and subdivisions that are based on titles (e.g., Food in the Koran; Future life—Koranic teaching)
- Headings for temporary exhibition buildings, which are qualified by the name of the exhibition (e.g., Cyclebowl (Expo 2000, 2000, Hannover, Germany))
Excluded from the project were the revisions to headings for treaties, which have been postponed until the issues under discussion in the Program for Cooperative Cataloging have been resolved.
PSD is now accepting proposals to modify LCSH headings to bring them into alignment with the authorized RDA form of heading. It is possible that some affected headings have been missed. In addition, name headings that were not programmatically changed as part of Phase 2 may be revised in the coming months and years. Any time an authorized name heading is revised, a proposal should also be made to revise the name heading printed in LCSH, including cases in which the name heading is used as a qualifier or in some other way in an LCSH authority record.
At this time, PSD is not planning to revise those LC subject headings that include abbreviations that are not permitted in RDA, which chiefly appear in a subfield $y (e.g., Egypt—History—Early Dynastic Period, ca. 3100-ca. 2686 B.C.). Proposals to make revisions of that sort will not be accepted.
Questions or comments may be directed to email@example.com