CC:DA Task Forces ( -2016)

Task Force on Machine-Actionable Data Elements in RDA Chapter 3

Formed: March 14, 2011
Reconstituted: March 5, 2013
Chair: Lapka/Hillmann (originally Rolla, then Lapka)
Charge: interim report at Annual 2011, final report at Midwinter 2012
Charge after reconstitution: draft proposal and status update at Annual 2013, interim report at Midwinter 2014, draft discussion paper at Annual 2014; revised timeline: proposal at Annual 2015
Submitted: oral report (Annual 2011); oral report (Midwinter 2012); discussion paper (Annual 2012); interim report (Annual 2013); oral report (Midwinter 2014); oral report (Annual 2014); strawman proposal (Midwinter 2015); proposal (Annual 2015)

 

Task Force to Investigate Definitions of and Instructions for Accompanying Material in RDA: Charge and Roster

Formed: January 19, 2016
Chair: Elyssa Gould
Charge: Joint CC:DA/CCC discussion paper at Annual 2016
Submitted:

Chicago Manual of Style Task Force report

Final Report from the Task Force on the Chicago Manual of Style

The Task Force to Investigate Changes Affecting RDA in the Chicago Manual of Style, 16th edition, has submitted its final report.  Most of the recommendations involve minor editorial changes to RDA and related documentation.  One of the recommendations, however, involves a substantive change to RDA which would have a major impact on authorized access points.  I would like to suggest that CC:DA discuss and vote on this recommendation; the rest can be handled as Fast Track proposals.

The recommendation in question relates to CMOS 8.159, which deals with capitalization of hyphenated compounds.  In the 16th edition, this provision reads:

8.159 Hyphenated compounds in headline-style titles

The following rules apply to hyphenated terms appearing in a title capitalized in headline style. For reasons of consistency and editorial efficiency, Chicago no longer advises making exceptions to these rules for the rare awkward-looking result (though such niceties may occasionally be observed in display settings, as on the cover of a book). For rules of hyphenation, see 7.77–85.

1.   Always capitalize the first element.

2.   Capitalize any subsequent elements unless they are articles, prepositions, coordinating conjunctions (and, but, for, or, nor), or such modifiers as flat or sharp following musical key symbols.

3.   If the first element is merely a prefix or combining form that could not stand by itself as a word (anti, pre, etc.), do not capitalize the second element unless it is a proper noun or proper adjective.

4.   Capitalize the second element in a hyphenated spelled-out number (twenty-one or twenty-first, etc.) or hyphenated simple fraction (two-thirds in two-thirds majority). This departure from previous Chicago recommendations recognizes the functional equality of the numbers before and after the hyphen.
The Task Force proposes to revise RDA A.29 to conform to this provision (see p. 9 of the TF report); formerly in RDA, only the first word in such a compound was capitalized.

In addition to RDA A.29, this issue is also the basis for the following TF recommendations:

RDA 9.2.2.25
RDA 11.2.2.11
RDA 11.2.2.24.2
RDA 11.2.3.6
RDA 11.2.3.7 [two instances]
RDA 19.2.1.3 [2nd instance]
RDA A.11.4
RDA A.14 [2nd instance]
RDA A.16.2 [two instances]
RDA A.16.5
RDA A.17.6
RDA Glossary, Tonic Sol-fa

As Kathy Glennan reported at Midwinter, she asked Gary Strawn to look at the impact of this change on the NACO authority file.  He provided some statistics, but the bottom line was that instances needing to be changed would be difficult to identify by program and even more difficult to correct safely.

Given the impact of this recommendation and given that differences in capitalization are not taken into account by the NACO normalization rules, it seems questionable that this is a revision that CC:DA would wish to propose.  My understanding is that CMOS governs the text of RDA itself, but governs the results of applying RDA instructions only when there is no applicable RDA instruction.  In this case, the text of RDA A.29 applies, and need not conform to the provisions of CMOS.

Beyond this single issue, I propose (a) to communicate to the JSC Secretary the recommended revisions to the RDA Editor’s Guide; and (b) to make Fast Track proposals for the following TF recommendations:

RDA 1.1.2
RDA 1.1.3
RDA 2.20.10.3
RDA 6.2.2.4
RDA 6.30.2.2
RDA 8.12.1.3
RDA 19.2.1.3 [1st instance]
RDA A.10 [three instances]
RDA A.14 [1st instance]

For the sake of completeness, the TF recommended that no change be made in the following instructions:

RDA 7.17.3.3
RDA B.11
RDA H.1

Again, I suggest that CC:DA discuss and vote on the recommendation for RDA A.29 (and related instructions); if there is any disagreement with any of the other recommendations, these should be raised during the discussion.

John

Task Force on Place Names in RDA

CC:DA/TF/Place Names/1

March 5, 2013

Charge

The Task Force on the Recording of Place Names is charged with continuing CC:DA’s work in clarifying and suggesting revisions to RDA’s instructions on recording the names of places, with the ultimate goal of making these instructions conform to RDA’s goals of 1) creating an international standard and 2) presenting bibliographic information as machine-actionable data. With that in mind, the Task Force will explore, among other options:

  • Removing the requirement to record larger places from the instructions for recording preferred and variant forms of names;
  • Adding instructions for creating authorized and variant access points of places;
  • Creating separate instructions for an element called Name of Larger Place in chapter 16;
  • Alternately, creating a relationship element of Larger/Smaller Place.

The Task Force will submit an interim report at Midwinter 2014 and will deliver a final revision proposal at Annual 2014, to be submitted to the JSC for their Fall 2014 meeting.

Continue reading

Task Force to Investigate the instructions for recording relationships in RDA

June 10, 2012

Charge

The Task Force to Investigate the instructions for recording relationships in RDA is to consider the structure of elements for relationships and the instructions for recording relationships. It is then to draft instructions for recording structured descriptions of relationships, such as contents notes and accompanying material statements, taking into account the issues raised in the JSC Representative’s discussion paper on this topic (CC:DA/JSC Rep/JCA/2011/5: Descriptions of relationships (b)).

The task force should submit an interim report at Midwinter 2013 and a final report at Annual 2013.

Report

Task Force on recording relationships: Discussion paper, which includes both the interim report and an appendix with a straw man proposal by John Attig.

TF on Instructions for Recording Relationships: Final Report (May 2013)

Instructions for Recording Relationships: Discussion Paper (July 2013)

Discussion Paper: Instructions for Recording Structured Descriptions of Related Manifestations (December 2014)

Discussion Paper: Instructions for Describing Accompanying Material in RDA (December 2014)

Revision to 3.1.4, Resources Consisting of More than One Carrier Type (June 2015); Revision (July 2015)

Additional instructions in Chapter 27 for Structured Descriptions of the “Contained in” and “Container of” Relationships (June 2015); Revision (July 2015)
Continue reading