-
Recent posts
- CC:DA Task Force to Review Chinese Rare Book Cataloging Guidelines
- Library of Congress Report, 2019 Midwinter Meeting
- PCC Report for CC:DA at ALA Midwinter, Seattle, January 26, 2019
- Chair’s Report on CC:DA Motions and Other Actions, July-December 2018
- Minutes of the meeting held at the 2018 ALA Midwinter Meeting in New Orleans, Louisiana June 23 and 25, 2018 Draft
Recent comments
- Kathy Glennan on Expanding RDA 6.29.1.3, Laws Governing More Than One Jurisdiction
- Amanda Ros on Adding Controlled Vocabulary to RDA 3.19.6, Regional Encoding, and to the Glossary
- Amanda Ros on Adding Controlled Vocabulary to RDA 3.19.6, Regional Encoding, and to the Glossary
- Amanda Ros on Adding Controlled Vocabulary to RDA 3.19.6, Regional Encoding, and to the Glossary
- Amanda Ros on Adding Controlled Vocabulary to RDA 3.19.6, Regional Encoding, and to the Glossary
Archives
Comment policy
Only current CC:DA members and liaisons are authorized to comment on posts. Others who wish to contribute to CC:DA's discussions are invited to provide input by contacting the Chair, a member of the Committee, or their appropriate liaison.
New CC:DA members and liaisons will be assigned an account for the CC:DA Blog during the month of their initial appointment. For assistance with an account contact the CC:DA Webmaster.
All first-time comments on this site are moderated. We ask that all comments be relevant to the post to which they are directed and maintain professional courtesy.
All categories
Tag cloud
agenda ALA2012 ALA2013 ALA2014 ALA2015 ALA2016 ALA proposal Annual 2012 Annual 2013 Annual 2014 Annual 2015 Behrens British Library Canadian Committee on Cataloguing Chair's report corporate bodies Dunsire European Regional Representative Glennan Iseminger JSC JSC rep Lapka Leonard Library of Congress McGrath Midwinter 2012 Midwinter 2013 Midwinter 2014 Midwinter 2016 minutes music Music Working Group (JSC) Myers OLAC PCC Rendall Reser response Robare Rolla roster RSC Shrader SnyderLinks
Comment received from Mark Scharff, Washington University in St. Louis:
In trying to alleviate confusion over what the statement “score and x parts” says about the physical disposition of the manifestation, the proposal goes too far in the other direction. This is an anomalous situation, to be sure; it appears to be the only RDA extent statement that uses the word “and” as a link to connect two entities that are physically integrated. If the two entities are uncoupled and no single notated-music term will be adequate to describe the volume, then “x pages” would be the only choice. This is not a user-friendly solution, however; notwithstanding icons or facets or search limits, users still expect to see a term assuring them that they have retrieved a description of notated music if that’s what they want. Perhaps a better solution is to take a cue from 3.4.2.3 and 3.4.4.3 and add “in 1 volume” to the existing formulation. The note at 3.21.2.5 can then be retained for details about the physical disposition of things, e.g. what pages of the resource constitute the parts.
Comment posted on behalf of the Machine Actionable Data Task Force:
The Machine Actionable Data Task Force agrees with the comments made by Mark Scharff (who serves as resident music expert on our group).
In RDA, extent for notated music generally employs the pattern: [Extent of Expression] ([Extent of Carrier]). As Mark notes, the extent of the expression is an important part of this composite statement. It serves a vital role in the user task of identification, so it shouldn’t be relegated to a note.
Currently, the Extent of Expression element does not formally exist in RDA, but our TF will propose its addition. It remains conceivable that extent for resources comprised of notated music would – in catalog displays – retain the syntax: [Extent of Expression] ([Extent of Carrier]).
We agree with the solutions proposed by Mark. For the 2nd exception in 3.4.3.2, we suggest adding “in 1 volume” for clarification.
1 score and 3 parts in 1 volume (19 pages)
[or perhaps]
1 score and 3 parts (in 1 volume (19 pages))
We suggest employing the note at 3.21.2.5 to indicate the location of content units within the carrier:
Parts printed on pages 11-19.
I agree with Mark and the MADTF that this proposed revision goes in the wrong direction.
While I rather like the outcome suggested by the TF (adding “in 1 volume”), that isn’t compatible with RDA 3.21.2.8 (Number of Bibliographic Volumes Differing from Number of Physical Volumes), or with its ISBD equivalent (5.1.2). I also can’t figure out how to concisely write instructions that would generate the outcome suggested by the TF.
This leads me to question how the “score and one part” situation really differs from a textual work with extensive illustrations (say, 57 pages of text and 24 leaves of plates). In the latter situation, we’d give: 57 pages, 24 leaves of plates. Why aren’t we trying to do the same thing with these “score and parts” anomalies? That might look something like:
1 score (10 pages), 3 parts (pages 11-19)
or possibly
1 score, 3 parts (19 pages)
or the even the current practice of
1 score and 3 parts (19 pages)
Then 3.21.2.5 could be applied to make a note about being in a single physical unit (or perhaps, a single physical volume?), if considered important for identification or selection.
The situation with 4 parts bound together I think has to be:
4 parts – per 3.4.3
4 parts in 1 volume — per 3.21.2.5, if revised along the lines of what’s in this proposal.
It seems that it would be prudent to minimize the changes to Chapter 3 until the MADTF makes its proposal addressing extent of expression.
A shorter-term approach to the immediate problem would be to remove the 1st conditional clause in 3.21.2.5. The Music WG’s assessment that this is phrased as if the “exception” in 3.4.3.2 is an “alternative” is spot-on. I would also support the addition of the reference from 3.4.3.2 to 3.21.2.5.
If the JSC wants to pursue incorporating instructions for published-together parts, as suggested by the WG, then the word “of” should be inserted before “multiple parts” in the name of the exception and wherever else it is paired with the “score and one or more parts” clause.
So, the exception would be titled:
Resource consisting of a score and one or more parts or of multiple parts in a single physical unit.
I also think the JSC should decide throughout RDA if the term should be
“physical units”
or
“physical volumes”
They must mean the same thing — at least I hope they do!
What I recommend:
1. Accept only the new paragraph proposed for the 2nd exception at 3.4.3.2, revised as follows to better follow RDA language [rewording suggestions welcomed]:
Make a note to explain the extent, if considered important for identification or selection (see 3.21.2.5).
2. Change the heading for 3.21.2.5 to:
Score and One or More Parts, or Multiple Parts in a Single Physical Unit
Otherwise, accept the WG’s proposed changes for this instruction.