This report focuses on items of interest to the music library community. For more information about the meeting and for reports about activities mentioned below, please see the CC:DA web page at http://www.libraries.psu.edu/tas/jca/ccda/index.html. Presentation is more topical than chronological.
Reports
CC:DA Chair. The full report is at http://www.libraries.psu.edu/tas/jca/ccda/docs/chair40.pdf
. The Chair reviewed the votes taken by electronic mail since Annual 2007, and
asked for and received confirmation of the results. Most of the votes related to RDA (Resource Description and Access); some
authorized the JSC (Joint Steering Committee for Development of RDA) liaison,
John Attig, to make responses to RDA
drafts and issues on the CC:DA’s behalf.
Another vote resulted in a refusal to pass on to the JSC the PCC
proposal on making series transcription optional in serials cataloging. Of particular interest to the music community
was that authorizing a response to a background paper from the CILIP
representative to the JSC. This paper
considered the impact of proposed language in the Draft Principles of the IFLA Meetings of Experts on an
International Cataloguing Code (IME ICC) about uniform titles; it gives primacy
to the “commonly known title in the language and script of the catalogue when
one exists for the resource” in choosing a uniform title, as opposed to AACR2’s
emphasis on using the composer’s original title. The MLA Liaison and Kathy Glennan, JSC
member, contributed to
Library of Congress (Barbara Tillett, LC liaison to CC:DA). For a detailed report of LC
initiatives, visit: http://www.loc.gov/ala/mw-2008-update.html
Barbara Tillett reviewed highlights from her report. Issues of particular interest to the music community include:
Chatham addressed the LC Working Group on the Future
of Bibliographic Control’s recommendation that work on RDA be suspended by
stressing that the Committee of Principals is committed to the current
publication timetable. A vendor (Cognilore)
has been chosen for the RDA authoring software, and a demo may be ready by ALA
Annual, but definitely by IFLA in August. A non-live prototype should be available
within the next month or so. Chatham
mentioned some of the anticipated features—search history, a linked index, the
ability to bookmark, ability to export sections as PDFs for printing, a
portable “user profile,” options to view or hide examples, and links between
RDA and corresponding sections of AACR2.
This last feature was not universally embraced by committee members, who
were concerned about potential confusion and promoting resistance to
change.
Joint Steering Committee (John Attig, ALA Representative). John offered the
PowerPoint presentation prepared for the RDA Update Forum as a surrogate for
his report. That presentation is
available at http://www.collectionscanada.gc.ca/jsc/docs/jca-philadelphia-20080113.pdf. A companion report by Marjorie Bloss, RDA
Product Manager, is at http://www.collectionscanada.gc.ca/jsc/docs/mb-philadelphia-20080113.pdf.
JSC met in October 2007 in
The concept of “authority control” takes some
interesting turns in this environment, John pointed out. Currently, authority records record facts
(670 fields) and decisions (most everything else); in general, the facts are
not recorded as discrete data elements (in MARC, for example, all information
from a given source goes into 670 subfield b, regardless of what it
conveys). In RDA, the process starts
with recording facts, or attributes, with provision for differentiating data
elements being recorded (without requiring it), and then access points can be
decided on. Access points themselves are
not data elements. One implication for
this might be a change in the practice for undifferentiated names. Currently, one authority record can represent
multiple persons; each person is represented by 670 fields that present facts
about the person. The persons are all
accorded the same preferred access point; though some might also be represented
by variant access points, such distinctions are only apparent from viewing the
670 fields. In RDA, the emphasis on
identification could produce multiple authority records that have the same
preferred access point; by using an identifier to stand for the authority
record in other records, the differentiation can be made without the need to
produce a unique access point.
Some of the more significant outcomes of the October
meeting were 1) confirming changes to practice in formulating uniform titles
for portions of the Bible to make them somewhat less Christo-centric; 2)
considering treaties to be collaborations, allowing the preferred access point
for the treaty to include the preferred access point for the first-named
signatory; 3) moving forward with internationalization by replacing directions
to record elements in English with directions to record elements in the
cataloging agency’s preferred language; 4) identifying a change in mode of
issuance or media type as cause for preparing a new description for a resource;
5) accepting the current practice in AACR2 1.1B1 that directs the omission of
introductory words from transcriptions of the title proper.
John mentioned that the JSC had brought a discussion
paper to MARBI at this meeting to start the discussion on needed changes to
accommodate use of RDA with MARC21. At
the same time, the JSC is also encouraging looking ahead to a post-MARC
world. Publication is still scheduled for
2009.
The JSC has made the vast majority of the RDA
working documents publicly available at http://www.collectionscanada.ca/jsc/working1.html,
to provide context for the changes being incorporated into RDA.
The JSC will next meet in April, once again in Chicago.
CC:DA Task Force to Maintain
“Differences Between, Changes Within” (Kevin Randall).
This task force has now been discharged, and the revised document is
available as a free download from the ALCTS Web site (go to http://www.ala.org/ala/alctscontent/alctspubsbucket/webpublications/cataloging/newrecord/differences.cfm).
CC:DA Task Force on
Specialist Cataloging Manuals (Mark Scharff).
The Task Force was charged with producing a list of standards and
manuals that would be useful for specialist communities or for working with
specialized cataloging issues, and would have some usefulness in an RDA
environment. The list would not be
within the text of RDA, but provided a link in the online version. On the cusp of submitting a report and list,
the TF received input from the JSC that indicated a desire for a far less
focused, and much more dynamic, document than that described in the original
charge. The Task Force then spent more
energies on developing a structure for the existing resources, and some
guidance for extensibility. CC:DA
accepted the report with some amendments.
The Task Force will await feedback from JSC as to whether further work
is needed.
Task Force on CC:DA’s Internal and External
Communication (Laura Smart, and
including MLA members Jim Alberts and Matthew Wise). The TF is developing an
electronic contact list for external communication for specific areas (e.g.
CJK, maps, music). Planning for
migrating the CC:DA Web site to ALA continues.
The Task Force’s scope has extended to cover wikis and other such forms
of communication. Work is just about
done on setting up a CC:DA mailing list to which non-members could subscribe
for read-only access.
CC:DA Webmaster
(Patricia Hatch). Patricia was unable to
attend ALA, so the committee received a written report detailing progress
toward migrating the CC:DA Web site. She
recommended the appointment of a task force to assist with this formidable
undertaking.
ALA Representative to NISO (Cindy Hepfer). Cindy is new to this position, and is trying
to expand communication and input to NISO beyond areas within ALCTS. A number of standards proposals are in the pipeline
(preservation products, environmental conditions for exhibits, title pages for
conference publications, statistics harvesting, to name some), and CC:DA
members and liaisons will be asked to provide input as appropriate.
RDA Implementation Task
Force
(Cheri Folkner in lieu of Shawne Miksa).
Shawne has recently taken over as chair of the TF, and has to cope with
a dearth of documentation. Ideas have
been collected for a program for ALA Annual; more work is needed to secure a
program spot, including identifying the target audience—is it “high-level”
implementers (networks, systems, administrators) or catalogers?
CC:DA Discussion of RDA Drafts
John Attig led the group in
these discussions, which covered Sections 2-4 and 9 of RDA, at varying levels
of detail. While the draft had been
available for about a month, committee members were still working through its
463 pages. Some committee members found
the document ambiguous as to what sort of record would contain the data being
recorded. Few comments had been entered
in the CC:DA wiki.
Among general comments from
committee and audience members:
Among the statements on particular chapters and rules:
Other
CC:DA will meet three times
at ALA Annual in Anaheim, CA—Friday, June 27, 1:30-5:30; Saturday, June 28,
1:30-5:30; and Monday, June 30, 8:00-12:00.
Return
to the 2008 Documents Menu
Return
to BCC Historical Documents Menu
Return
to BCC Home Page
Last updated March 12, 2008