Music Information Retrieval: Overview and Current Trends 2008
RDA for music cataloguers
1. RDA for Music Cataloguers
Written by Charlotte Stretton,
Cataloguing Team Leader, National Library of New Zealand
for New Zealand IAML Conference, November 2010
Presented by Chris Todd
2. Structure
AACR2
Part I - Description
Part II - Headings,
Uniform titles,
References
RDA
Attributes (of entities)
Relationships (between
entities)
3. Finding rules
AACR2
Start by identifying the
type of resource
RDA
Start by identifying the
data element
title (of music score) attribute (2.3)
title (of compact disc) attribute (2.3)
title (of MP3 file) attribute (2.3)
music score music (chapt 5)
compact disc sound recordings
(chapt 6)
MP3 music? sound? electronic? …
(chapt. 5?, 6? 9?)
PROBLEM!
4. RDA
Structure based on FRBR model (Works
Expressions Manifestations Items … )
Supports user needs and user tasks (Find
Identify Select Obtain)
Covers authority and bibliographic data
Record independent units of data (machine
readable, not just human readable)
5. RDA’s main changes
Core and “Core if” elements (no more levels
of description)
Take what you see (fewer abbreviations, no
more “rule of 3”)
Content, Media & Carrier types (no more
GMD)
Expanded sources of information
6. Take what you see
‘transcribe’ really does mean transcribe
In addition: few abbreviations: pages, not p.; colour, not col.;
illustrations, not ill.
Why change?
helps to accurately identify the item in hand
allows the use of other sources of data
(e.g. scanned or publisher supplied)
On resource In catalogue record
Volume 3 Volume 3
Vol. 3 Vol. 3
accompanied accompanied
7. Three new data elements
Content type (Core)
Media type (Optional)
Carrier type (Core)
Recorded as terms or codes
RDA covers content not presentation or display
Why change?
Clearer identification of format
8. GMD vs Content & Carrier
AACR2
General Material
Designation (GMD)
e.g.
[sound recording]
[music]
RDA
Content type & carrier type
e.g.
Content type: performed music
Carrier type: audio disc
Content type: notated music
Carrier type: volume
9. Sources of information
1.Identify the boundaries of the resource
Includes storage medium and housing (where
integral to resource)
Includes accompanying material for
comprehensive descriptions
2. Choose preferred source of information
includes permanent labels on resources
excludes labels on accompanying material
10. Sources of information 2
If information comes from outside the resource
itself it should be marked “either by means of
a note or by some other means (e.g. through
coding or the use of square brackets)” 2.2.4
The benefit:
Square brackets always mean the information
comes from outside the resource.
Makes identification easier.
11. Music rule changes
Editions (include musical presentation
statement)
Definitions (score, chorus score, vocal
score)
New elements in authority data
(medium of performance, numeric
designation, key)
12. Edition statement
• Scope extended to include
– Musical presentation statements
– Statements of responsibility indicating arrangement or
version e.g.“vocal score …”
• 2.5.2.1 “In case of doubt ... consider the
presence of ... a statement indicating …
– (g) A particular voice range or format for notated
music
as evidence that such a statement is a
designation of edition”
13. Changes in definitions of
scores
Score: Graphical, symbolic, or word-
based musical notation representing the
sounds of all the parts of an ensemble or
a work for solo performer or
electronic media
miniature score, use study score
short score & close score included with
condensed score
14. New attributes for works and
expressions
Data used to create headings for works
and expressions is now recorded
New elements specific to records for
musical works
Medium of performance
Numeric designation of a musical work
Key
15. New attributes for works and
expressions, example
Authorised access point for the work
Beethoven, Ludwig van, 1770-1827. Sonatas,
piano, no. 14, op. 27, no. 2, C# minor
Data elements in the authority record for
the work
Medium of performance piano
Numeric designation no. 14, op. 27, no. 2
Key C# minor
17. Adaptations of musical works
RDA rules not based on resource type
– Scope for definition of adaptations includes
notated music and performed music
“a) arrangements described as freely transcribed, based on, etc.,
and other arrangements incorporating new material
b) paraphrases of various works or of the general style of another
composer
c) arrangements in which the harmony or musical style of the
original has been changed
d) performances of musical works involving substantial creative
responsibility for adaptation, improvisation, etc., on the part of
the performer or performers
e) any other distinct alteration of another musical work” RDA
6.28.1.5.1
18. Librettos & Cadenzas
• Both treated as related works
• No option to enter librettos under
composer, now entered under author of
libretto
21. What I need to know now
• RDA test report available June 2011
• LC’s implementation decision to be
announced at ALA June 2011 (at earliest)
• Partner libraries implementation decisions
announced July – Sept 2011?
• Implementation period? 2nd
quarter 2012?
Timeline
22. MARC changes for RDA
Summarised
http://www.loc.gov/marc/RDAinMARC29.html
040 $e rda
336-338 for Content, carrier & media types
more fields with $e and $4 for relator terms &
codes
extra options in some fixed fields (e.g. 008/20
Format of music now has h – chorus score; i
– condensed score; j – performer-conductor
part)
23. RDA in New Zealand
Toolkit access available through EPIC
http://epic.org.nz/the-databases/all-
databases/rda
NLNZ cataloguers reviewing core
elements, options, alternatives & LC
policy statements
To be posted on DescribeNZ
24. Sources for RDA
Describe NZ
http://www.describe.org.nz/
Australian Committee on Cataloguing
RDA page
http://www.nla.gov.au/lis/stndrds/grps/a
coc/rda.html
RDA http://www.rda-jsc.org/
RDA Toolkit http://www.rdatoolkit.org/
Each set of rules has two main sections, but the basis for these sections is very different. AACR2 is based on the type of resource, whereas RDA is based on the type of data.
Reason for differences in structure is because based on FRBR
Major change from AACR2 is the focus on the value of the data to the user. Rules throughout RDA identify the objectives e.g. “Data recorded to reflect relationships to persons … associated with a resource should enable the user to find all resources associated with a particular person … “ Rule 18.2
The user tasks are part of the FRBR model
The attributes are attributes of works, etc. and attributes of persons families and corporate bodies
The relationships are relationships between works and persons etc. as well as relationships between resources e.g. libretto of an opera
Discrete data elements are very important. If the data is explicit, it can be manipulated for indexing and display. RDA is not a display standard
Core elements cover sufficient information to identify a resource. The core if elements apply only in certain circumstances e.g. Date of distribution is a core element if the date of publication is not identified.
If you are following any of the cataloguing lists you might think that abandoning abbreviations and copying directly mean that the cataloguing sky has fallen!
These 3 elements replace the General Material Designation. They are new fields in MARC and can be recorded as either terms or codes. Because RDA is a content standard but not a display standard there is nothing in RDA to suggest how these data elements should be presented. They could be text or symbols or icons or not displayed at all. The important thing is that the data is there.
This means that all statements that indicate a particular version of a score are treated as edition statements. Previously for scores the treatment would depend on the presentation of the information. Sometimes there would be a musical presentation statement, sometimes an edition statement and sometimes a statement of responsibility.
Major change – all notated music is a score or part – no more pages or volumes of music – affects extent elements
Minor change – one term changed to another term
3. Major-ish change – short and close scores are now treated as types of condensed scores. Condensed score (aacr2) = score giving only principal parts on minimum no. of staves, organised by instrumental sections. Close score = score giving all parts on minimum no. of staves. Short score = sketch by composer for ensemble work – gives main features only. Simplifies the categories
These elements are already well-known components of uniform titles for musical works. The difference with RDA is that they are distinct data elements in the record that describes the work as well as appearing in the heading
The access point is the same as the RDA version of this access point. The difference here is that the 3 elements below can now be recorded in the authority record. The MARC format has been updated to include fields for these 3 elements in bibliographic and authority records.
In AACR2 there are rules for adaptations of musical works and quite separately there are rules for sound recordings that consider the role of the performer. RDA brings these together. Category d) in the slide relates to the rules for main entry of sound recordings and the other rules are under main entry rules for printed music.
These records have been taken from the RDA test records on OCLC. The test participants are required to create both AACR2 and RDA versions of the records
This record is in LC’s online catalogue, but I have tweaked it slightly to show the relationship designators which are part of RDA. Note that the form of notation is always recorded. This is a change from AACR2 and is a reflection of the idea that in RDA we don’t assume a norm that people (& machines) are just supposed to know.
Partner libraries are NLA, Libraries and Archives Canada and the British Library.
These changes will need to be implemented in your library system. How this is done varies between systems and between libraries – in some places the tag tables and indexes are changed by systems staff within libraries, in other cases the system vendor does the updating centrally
We are going through the RDA rules and looking at the core elements. We are also examining the LC policy statements for RDA (which are included as links in the RDA toolkit) and drafting our responses to these. So far we are generally in agreement with the LC choices, however we may end up with some variations around dual language materials. We have also been looking at the rules that includes phrases such as “If it is considered important” and trying to tease out situations where we (NLNZ) would consider it important to add the particular data element. We have found this to be very useful, but also very time-consuming, so the extension of the timeline will make this task easier for us.
NLNZ has been posting on the DescribeNZ wiki. Because the Australians are represented on the JSC for the development of RDA they do get information a little ahead of the rest of us so this is a good site to follow as well. They’ve just updated their webpage and it’s got some good information.