How to Submit a Revision Proposal to CC:DA

Printable PDF: How to Submit a Revision Proposal to CC:DA

Association for Library Collections & Technical Services
(A division of the American Library Association)
Cataloging and Metadata Management Section
Committee on Cataloging: Description and Access

How to Submit a Revision Proposal to CC:DA

Table of Contents
Who Can Submit a Revision Proposal?
What Types of Proposals Are Acceptable?
How Will Proposals Be Evaluated?
Preliminary Steps To Take in Submitting a Proposal
Formal Elements of a Revision Proposal
Forwarding the Proposal
What is the Timetable for Submitting a Revision Proposal?
Where Can I Find Examples of Revision Proposals?

RDA: Resource Description and Access is a set of guidelines and instructions on formulating data to support resource discovery. RDA provides a comprehensive set of guidelines and instructions covering all types of content and media.

RDA was developed and is maintained by the Joint Steering Committee for Development of RDA (JSC), which is responsible for making decisions regarding the content of RDA. This international group is made up of representatives from the American Library Association, the Australian Committee on Cataloguing, the British Library, the Canadian Committee on Cataloguing, the Chartered Institute of Library and Information Professionals, the German National Library, and the Library of Congress.

The JSC receives, discusses, and makes decisions on proposals received from one of the JSC constituencies or from non-JSC groups. Each JSC constituency is expected to respond to every proposal, and reaches decisions by consensus.
The Committee on Cataloging: Description and Access (CC:DA) is the body within the American Library Association (ALA) that is charged with initiating and developing proposals for the revision of RDA. Within the United States, all additions and changes to RDA (except those originating from the Library of Congress) must be channeled through this group.

Who Can Submit a Revision Proposal?
Anyone can submit a revision proposal to CC:DA by following the instructions detailed below. CC:DA welcomes input and suggestions for revision. At the same time, it should be noted that the revision process is a formal one that requires careful preparation and patience upon the part of the petitioner. The latter is particularly important because, although approved and endorsed by CC:DA, a proposal must usually pass through a lengthy review, revision, and subsequent review process before it is approved by the Joint Steering Committee for Development of RDA (JSC).

What Types of Proposals Are Acceptable?
The JSC accepts two types of proposals:

  1. Certain minor issues may be subject to a Fast Track procedure. This is designed to deal with issues that do not require extensive discussion or consultation by the JSC members. Examples include the addition of terms to the RDA vocabularies (including the relationship designators), the addition, deletion, or modification of examples, the correction of errors in the text (including typographical errors). Suggestions for Fast Track proposals should be directed to the ALA representative to the JSC, who will carry them forward to the JSC. (Correction of errors in the text can optionally be submitted using the “feedback” button in the RDA Toolkit.)
  2. Other proposals follow the more formal process described in this document.

CC:DA is open to considering revision proposals that range from small, isolated additions or changes to the text (e.g., the Committee submitted a proposal to change an RDA instruction and a related glossary definition to expand the scope of Artistic and/or Technical Credit to include sound recordings) to major changes of the code (e.g., addition of a new chapter or deletion of an instruction).

How Will Proposals Be Evaluated?
Whether minor or major revisions result, each proposal is carefully evaluated by the Committee and considered from several different angles. Although each area below might not be equally important for every proposal, the following list provides an overview of the factors and questions that the Committee routinely considers in its evaluation process.

  • The need for the revision: Is the current text confusing? Does the current text and/or examples lead to incorrect or inconsistent results, or does it cause access or identification problems for catalog users? Is there an inconsistency among similar or analogous instructions? Is an instruction in the wrong place? Does the proposal address a situation not covered? Is it appropriate to a general code?
  • The context: What are the underlying principles or issues? Are there analogous situations?
  • The correctness of the proposal: Does the proposal solve a problem without creating others? Is it in accordance with underlying principles? Is it clear and unambiguous? Is it consistent with other similar instructions?
  • The possible impact on other instructions: Would the proposed change necessitate other changes? Would examples need to be corrected? Would captions, indexes, tables of contents, etc., need to be changed?
  • The potential impact of the proposal: Would old cataloging need to be altered? Would the change simplify decisions? How often does the matter arise? Is access affected?

Preliminary Steps To Take in Submitting a Proposal
Given the complexity and time-consuming nature of the revision process, as well as the careful evaluation and close examination that each proposal will receive, it is advisable to undertake several preliminary steps before undertaking the preparation of a formal proposal:

  1. Discuss the concern with other catalogers in order to test the merits of your case and to establish the validity of the potential proposal in light of the evaluative criteria given above.
  2. Contact the Chair of CC:DA, one of the voting members of the Committee or one of the liaisons from a group (e.g., Music Library Association’s CC:DA representative) whose sphere of cataloging interest and activity might be closely allied with your concern. Discussion of the potential proposal with this expert might uncover other issues that need to be addressed, open up an avenue for discussion with other members of a particular cataloging community, or lead to taking an altogether different approach to the problem. Additionally, the Chair, the voting members, and the liaisons can be particularly helpful in guiding the process outlined below and in navigating the waters of CC:DA procedures.
  3. Consider consulting with the ALA representative to the JSC. It can be helpful to discuss preliminary ideas with someone familiar with the overall editorial and revision process.

Formal Elements of a Revision Proposal
The proposal should be sent in electronic form to facilitate distribution over the Committee’s electronic discussion list. This will speed up the process by allowing CC:DA to consider the proposal as soon as it is received. Proposals distributed to CC:DA are also posted on the CC:DA Web site.

Electronic copies must be in Microsoft Word (1997 version or higher).

The CC:DA Webmaster prepares documents for distribution to CC:DA and for posting on the CC:DA Web site. The Webmaster may be contacted for assistance in the mechanical and editorial details of preparing a proposal. The Webmaster may contact the proposer for corrections or clarifications; the proposer will have the opportunity to review the final version of the proposal.

The proposal should take the form of a dated memorandum addressed as shown below. Once received by the Chair of CC:DA, the proposal will be assigned a document number.
[Name], Chair, ALA/ALCTS/CaMMS Committee on Cataloging: Description and Access
[To be supplied]
[To be supplied]
Note: On the From: line, please include the name of the person submitting the proposal, followed by the constituent group he or she represents, if applicable. On the Subject: line, please include the following types of information if applicable to the proposal: the RDA instruction number; captioned words associated with the instruction; whether examples, footnotes or appendices are affected:

  • RDA, Reports of One CourtRDA 7.24, Artistic and/or Technical Credit
  • RDA 9.13, Affiliation
  • RDA &, Heads of State and Government
  • RDA, Places in Certain Federations
  • Change to GLOSSARY entry for Artistic and/or Technical Credit

The proposal should include a background statement that provides the context in which the revision should be considered. A thorough explanation of the problem(s) in RDA that will be remedied by the revision, an historical overview of the steps, discussions, events, etc. that have led to its creation, and citations to any related documents are appropriate for inclusion in this section of the proposal. As the organizational needs of the proposal dictate, the Rationale and Assessment of impact discussed below may also be included here.
Proposed revisions:

According to JSC policy, “There will be one proposal per document.” CC:DA interprets this to mean that all revisions in the proposal must be closely related, not that a separate proposal is required for each instruction affected by the revision. It is therefore common for proposals to include revisions to more than one instruction. Furthermore, these revisions may occur in different parts of RDA.

To assist CC:DA and the JSC in discussing the proposal, the specific changes being requested should be given as a numbered list, if possible. This not only draws attention to the specifics, but allows reference to each change by number.

To enhance the clarity and readability of the proposal, the text of the proposed changes should be given in two versions: one using markup to show the changes from the current text, and one showing a clean version of the proposed text. The current text of RDA should be copied from the RDA Toolkit and should retain the original typography.

The proposed revisions should be indicated as deletions or additions to the current text.

The markup should use strike-through to indicate deletions and double-underlining to indicate additions.

Rationale/Explanation for the proposed revisions:
Each proposal should contain a rationale or justification for the suggested revision, including a statement of the problem presented by the current instruction.

Assessment of the impact and survey of related instructions:
Finally, the proposal should include an assessment of the impact resulting from implementation of the revision(s), including the need to study and/or change other instructions within RDA.

Other considerations for inclusion in the proposal:
It may be useful to include surrogates or other ways of depicting resources to be cataloged that illustrate the instruction being addressed (e.g., a recent proposal from the Music Library Association that included surrogates of two CDs to show circumstances where the inability to use a source that presents a collective title as the preferred source leads to complications). It may also be advisable to include evidence of having considered the scope of the proposed change and to offer suggestions for broadening or narrowing that scope, if applicable. Finally, it may be helpful to mention other constituencies that have been consulted or made a part of the proposal-drafting process (e.g., consultation or coordination with OLAC, the Canadian Association of Music Libraries, etc.).

Forwarding the Proposal
The revision proposal should be forwarded to the Chair of CC:DA, either directly or through any voting or non-voting member of CC:DA. The roster of current CC:DA members is available on the CC:DA Web site.

What is the Timetable for Submitting a Revision Proposal?
While CC:DA will accept a revision proposal at any time, revision is a complicated and lengthy procedure, and the more complicated and longer the proposal, the more time will be required to consider it. For a proposal to be guaranteed to receive consideration at the next CC:DA meeting, the following minimal time should be allowed:

  • Revision proposals should be made available to the Chair of CC:DA one month prior to the next CC:DA meeting, which is scheduled during the ALA Annual Conference or Midwinter Meeting. The proposals will be made available to the CC:DA membership and posted on the CC:DA Web site one month prior to the next CC:DA meeting.
  • If the revision proposal is accepted by CC:DA, it is forwarded to the Joint Steering Committee for Development of RDA (JSC). JSC requires that revision proposals be transmitted to JSC at least three months prior to the next scheduled JSC meeting in order to be considered. This is to allow sufficient time for the other JSC members to consult their respective advisory bodies, for those advisory bodies to review the proposal and formulate their responses, and for the JSC member to transmit those responses to the other JSC members in a time frame that allows them to read the responses and be prepared to discuss both the original proposal and the responses at the next JSC meeting. [The date of the next JSC meeting is available on the JSC Web site, usually as the final item on the latest report of Outcomes of the … JSC Meeting. The JSC procedures for receiving and considering revision proposals are documented in JSC’s “Statement of Policy & Procedures.”]
  • Unless the revision proposal is either accepted or rejected by all the JSC constituents, there will likely be further revision and subsequent review by JSC. This process may take a year or more, depending on the complexity of the proposal and the number of revisions requested.

Where Can I Find Examples of Revision Proposals?
All RDA revision proposals are posted on the JSC website. Check here for examples of recent proposals, paying particular attention to the ALA proposals.

Revised by CC:DA: June 4, 2012

Posted in CC:DA Documents, Proposals | Tagged , , | Leave a comment

Interim report: Task Force on Sources of Information

CC:DA/TF/ Sources of Information/3

Interim report: Task Force on Sources of Information


Posted in Task Forces, Working docs | Tagged , , | Leave a comment

Interim report: Task Force on Relationship Designators in RDA Appendix K

CC:DA/TF/Relationship Designators in RDA Appendix K/3

Interim report: Task Force on Relationship Designators in RDA Appendix K

Posted in Task Forces, Working docs | Tagged , , | Leave a comment

Report: Task Force to Investigate Changes Affecting RDA in the Chicago Manual of Style, 16th edition

CC:DA/TF/ Investigate Changes Affecting RDA in the Chicago Manual of Style, 16th edition/3

Report: Task Force to Investigate Changes Affecting RDA in the Chicago Manual of Style, 16th edition


Posted in Task Forces, Working docs | Tagged , , | Leave a comment

Revision of RDA 3.19.3 for video encoding formats and introduction of new instruction for optical disc characteristics


Revision of RDA 3.19.3 for video encoding formats and introduction of new instruction for optical disc characteristics

Posted in Proposals, Working docs | Tagged , , , , | Leave a comment

CC:DA Procedures

CC:DA/Pro/14/2012 June 1

CC:DA Procedures 2012

Posted in About CC:DA, CC:DA Documents | Tagged , | Leave a comment

RDA Worldwide at ALA Annual in Anaheim


The ALCTS International Relations Committee, the ALCTS CaMMS RDA Conference Forums and Programs Task Force, and the ALCTS CaMMS Committee on Cataloging: Description and Access (CC:DA) invite you to RDA Worldwide. This panel discussion will be given at ALA Annual, on Sunday, June 24, 2012, from 1:30-3:30 pm, in Room 304AB, Anaheim Convention Center.

Resource Description and Access (RDA), the new guidelines for library cataloging and metadata creation, is intended for use in an international context. RDA is also very much a work in progress. To what extent has RDA succeeded in going beyond AACR2’s Anglo-American context? How is implementation now proceeding in different world regions, and what are the potential impacts on developments in the United States? This panel discussion will present multiple perspectives on these unfolding questions.

The panel will feature four speakers. Troy Linker, Publisher, ALA Digital Reference, will serve as responder. The panel will be moderated by David Miller, ALCTS IRC Chair.

  1. Christine Frodl, Head of Cataloguing Standards, German National Library (Deutsche Nationalbibliothek), will give an overview of German cataloguing traditions, the pre-RDA situation in Germany and preparations for RDA. The German National Library plans to implement RDA in 2013, following the timelines of the Library of Congress and other national libraries represented on the Joint Steering Committee. Her talk will also focus on issues of the translation of RDA into German, and on activities of EURIG, the European RDA Interest Group.
  2. Ageo García, Latin American Librarian, Tulane University, will speak on RDA and Latin America: Transitions, Preparations, and Perspectives. Many countries in Latin America have been using AACR2 and MARC21 to build their catalogs. The region is determined to prepare for and embrace the challenges presented by the conceptual, functional and technological changes of the digital environment. There is an array of preparations in the area to implement RDA, including the translation of RDA into Spanish.
  3. Chris (Christine) Todd, Team Leader, Cataloguing Team 1, National Library of New Zealand, will describe the New Zealand cataloguing context, then discuss the National Library’s preparations for RDA to date, as well as the Library’s plans now that implementation decisions have been made. She will also identify some aspects of RDA that National Library cataloguers have raised concerns about.
  4. Lee Kai, Cataloger, Capital Library of China, Beijing, and MLIS student, School of Information Studies, Syracuse University. This presentation will provide a basic understanding about the Chinese cataloging community in which RDA will be implemented, focusing on the two of the most influential library consortia in China, the National Library of China and China Academic Library and Information System (CALIS). The current development of RDA in China will be presented, especially in terms of research, staff training, and catalogers’ and system librarians’ responses to the new code.


Posted in Interesting, helpful, Presentations | Tagged , | Leave a comment