This
document outlines the changes to MARC21 usage that the National Library of
Australia will make in order to accommodate resource descriptions created using
RDA for original cataloguing (for decisions about copy cataloguing refer to the
Internal Cataloguing Guidelines).
|
Date
|
Name
|
Revision
|
|
7 November 2012
|
Catherine Argus
|
Original document
|
|
30 January 2013
|
Jenny Stephens
|
Document TRIMMED
|
|
4 February 2013
|
Jenny Stephens
|
Update
|
|
12 March 2013
|
Jenny Stephens
|
Update to 040 field.
|
|
29 May 2013
|
Maxine Davis
|
Update 1XX, 336, 337, 338 & 7XX to remove references to MARC
codes in $4 and $b. Add reference to Internal Cataloguing Guidelines for
decisions re copy cataloguing.
|
|
20 October 2014
|
Maxine Davis
|
Update 33X, incl. exception for 338 $b usage for “other”
|
Bibliographic
records
Leader/18
- Cataloguing Form
Record "i" to indicate the presence of ISBD punctuation at subfield
boundaries.
040 –
Cataloguing Source
Record "rda" in $e subfield to indicate the use of the RDA rules for
description.
The $e subfield should sit before the $c or $d subfields.
040 ## $a
ANL $b eng $e rda
040 ## $a
ANL $b eng $e rda $d ANL
1XX–
Relationship between a name and the resource
Relationship designators should
be included in the 1XX field, where known, to express the specific nature of
the relationship between the person, family or corporate body and the work,
expression, manifestation or item.
Record relationship designators
in textual form in $e subfield.
Refer to RDA Appendix I for the
relevant list of relationship designators.
Multiple terms may be recorded if
appropriate.
100 1# $a Lawson, Henry, $d 1867-1922, $e author.
245 Title
Statement
$h GMD: This
subfield is no longer used as RDA replaces the general material designation
(GMD) and the class of materials concept with Content Type, Media Type, and
Carrier Type
260 -
Publication, Distribution, etc.
This field is no longer used. Use
the 264 field instead
264 - Production,
Publication, Distribution, Manufacture, and Copyright Notice
Correct use of first and second
indicators is essential.
For unpublished material, record
production statement.
For published material, record
information about publication, and distribution or manufacture when
appropriate, using separate 264 fields as required.
Always record copyright date if
it is available. A separate 264 field is required for this.
264 #1 $a Sydney : $b [publisher not identified],
$c 2012.
264 #2 $b ABC Books
264 #4 $ c ©2012
If both a publication and a
copyright date are recorded, 008/06 should be coded “t” (Publication date and
copyright date), Date 1 should contain the publication date, and Date 2 the
copyright date.
336
Content Type
Content Type relates to the fundamental
form of communication through which the work is expressed and the human sense
through which it is intended to be perceived.
Record type of content in textual
form in $a subfield.
Refer to RDA Chapter 6.9.1.3 for
the relevant list of the terms.
Record “rdacontent” as the
source code in $2 subfield.
Record as many as are applicable*
using separate 336 fields. *To be considered applicable by NLA additional
content types should comprise a substantial part of the resource’s content
(e.g. more than 20%).
For example if you are
cataloguing a resource with multiple types of content, e.g. a print volume
containing lots of illustrations or photographs, you will have multiple
336 fields, one for each type of content.
336 ## $a text $2 rdacontent
336 ## $a still image $2 rdacontent
However a
print volume with a single illustration or photograph would only require the
336 for “text”.
In the
case of multiple parts, the $3 subfield can be used to specify the particular
part of the resource to which the content type refers if they differ. The $3
subfield may be positioned in the string at either start (as per LC practice)
or end (see examples in MARC 21) but should be consistent within the same
record.
336 ## $3 book $a text $2 rdacontent
336 ## $3 CD $a spoken word $2 rdacontent
337 Media
Type
Media Type relates to the general
type of intermediation device required to view, play, run, etc., the content of
the resource.
Record type of media in textual
form in $a subfield.
Refer to RDA Chapter 3.2.1.3 for
the relevant list of the terms
Record “rdamedia” as the
source code in $2 subfield.
If you are cataloguing a resource
with multiple formats/parts, e.g. a print volume with a CD-ROM, you will have
multiple 337 fields, one for each type of media. The $3 subfield can be used to
specify the part of the resource to which the media type refers. The $3
subfield may be positioned in the string at either start (as per LC practice)
or end (see examples in MARC 21) but should be consistent within the same
record.
337 ## $a unmediated $2 rdamedia
337 ## $a computer $2 rdamedia
337 ## $3 book $a unmediated $2 rdamedia
337 ## $3 CD-ROM $a computer $2 rdamedia
338
Carrier Type
Carrier Type relates to the
format of the storage medium and housing of the carrier of the resource.
Record type of carrier in textual
form in $a subfield.
Refer to RDA Chapter 3.3.1.3 for
the relevant list of the terms
For carrier term “other” only,
include $b with corresponding code from Term and Code List for RDA Carrier Types, this will vary depending on the category of
carrier.
Record “rdacarrier” as the
source code in $2 subfield.
If you are cataloguing a resource
with multiple formats or parts, e.g. a print volume with a CD-ROM, you may have
multiple 338 fields for each part of resource if they have different carrier
types. The $3 subfield can be used to specify the part of the resource to which
the carrier type refers. The $3 subfield may be positioned in the string at either
start (as per LC practice) or end (see examples in MARC 21) but should be
consistent within the same record.
338 ## $a
computer disc $2 rdacarrier
338 ## $a
volume $2 rdacarrier
338 ## $3
book $a volume $2 rdacarrier
338 ## $3
CD $a computer disc $2 rdacarrier
338 ## $a other $b cz $2 rdacarrier
For USB
flash drives use carrier term “other” and code “cz” until JSC approves a more
appropriate term.
7XX–
Relationship between a name and the resource
Relationship designators should
be included in 7XX fields, where known, to express the specific nature of the
relationship between the person, family or corporate body and the work,
expression, manifestation or item.
Record relationship designators
in textual form in $e subfield.
Refer to RDA Appendix I for the
relevant list of relationship designators.
Multiple terms may be recorded if
appropriate.
700 1# $a Thompson, Keith, $e illustrator.
7XX–
Relationships between Works, Expressions, Manifestations and Items
The specific nature of the
relationship between a work, expression, manifestation or item and a related
work, expression, manifestation or item should be included in 7XX fields, if
considered important.
Record the relationship
information in $i subfield.
Refer to RDA Appendix J for the
relevant list of relationship designators.
700 1# $i Parody of (work) : $a Bryson, Bill. $t
Short history of nearly everything.
Authority
records
008/10
- Descriptive cataloging rules
Record "z" to
indicate the cataloguing rules used to formulate the 1XX heading.
040 –
Cataloguing Source
Record "rda" in $e subfield to indicate the use of the RDA rules for
description.
040 ## $a
ANL $b eng $e rda
The $e subfield should sit before the $c or $d subfields.
046–
Special Coded Dates
Date/s associated with the
person, family, corporate body, work or expression described in the authority
record should be recorded in the 046 field.
Date/s may also be recorded in
the heading in the 1XX field if required.
046 ## $f 1867 $g 1922
100 1# $a Lawson, Henry, $d 1867-1922
046 ## $s 1850 $t 1859
100 1# $a Bankart, G., $d active 1850-1859
Date/s should be recorded according
to ISO 8601 - Representations of Dates and Times where possible.
If the
date/s cannot be recorded according to ISO 8601, the EDTF scheme should be used and “edtf” recorded as the
source code in $2 subfield.
When there is probable or approximate date or
something a bit more uncertain, use EDTF date scheme (Extended Date/Time
Format).
So for a
probable date 1) use a question mark just as in the heading; 2) for an approximate date use a tilde after the date and 3) for dates
where you have a 2 possible dates then put them in brackets separated by a
comma with no space in the same 046 subfield AND MOST IMPORTANTLY when using
the edtf date scheme you must add $2 to the 046. Subfield $2 would then apply
to the entire field
|
RDA dates in ISO 8601
date scheme (no need to provide a source in $2)
|
||
|
Category
|
RDA presentation
|
ISO 8601 coding in 046
|
|
Single year
|
1964
|
1964
|
|
Year/Month
|
1964 June
|
1964-06 (A hyphen must be inserted between YYYY and MM when DD is
omitted)
|
|
Year/Month/Day
|
1964 June 27
|
19640627
|
|
Early A.D. date
|
65 A.D.
|
0065
|
|
B.C. date
|
361 B.C.
|
-0360 (note there is a difference of one because the B.C. system
has no year zero)
|
|
Century
|
20th century
|
19
|
|
RDA dates in EDTF date
scheme (provide ‘edtf’ in 046 $2)
|
||
|
Category
|
RDA presentation
|
EDTF coding in 046
|
|
Probable date
|
1816?
|
1816?
|
|
Approximate date
|
Approximately 931
|
0931~
|
|
Known to be one of two years
|
1666 or 1667
|
[1666,1667]
|
Attributes
of Persons, Families and Corporate Bodies
The following fields should only
be used to record information about persons, families and corporate bodies that
is gathered in the course of establishing the authorised heading.
The information may also be
recorded in the heading in the 1XX field if required.
- 368
- Other Attributes of a Person or Corporate Body: Any other attribute that serves to
characterize a person or corporate body or that may be needed for
differentiation from other persons or corporate bodies but cannot be
recorded in another field.
- 370
- Associated Place:
The town, city, province, state, and/or country associated with the
person, family or corporate body
- 371
– Address:
The address where the person or corporate body can be found or contacted.
- 372
- Field of Activity:
The field of endeavour or area of expertise in which the person or
corporate body is or was engaged.
- 373
- Associated Group:
Information about a group, institution, association, etc. with which the
person is or has been affiliated. Dates of affiliation may also be
recorded.
- 374
– Occupation:
Information about the profession or occupation in which the person works
or has worked. Dates of work in the profession or occupation may also be
recorded.
- 375
– Gender:
Information about the gender of the person. Dates of identification with a
specified gender may also be recorded.
- 376
- Family Information:
Information about the family, such as type of family, the name of a
prominent member of the family, and hereditary title.
- 377
- Associated Language:
The MARC language code/s and/or term/s associated with the person, family
or corporate body. This may include the language of the family or the
language that the person or corporate body uses for publication,
broadcasting, communication, etc.
- 378
- Fuller Form of Personal Name:
The fuller form of the name of the person, either to distinguish the
person from another person with the same name or when a part of the name
of the preferred name is represented only by an initial or abbreviation.
4XX and
5XX– Relationship between Persons, Families and Corporate Bodies
The relationship between a
person, family, or corporate body and a related person, family, or corporate
body may be recorded, if considered important.
Record the relationship
information in $i subfield.
Refer to RDA Appendix K for the
relevant list of relationship designators.
100 1# $ a Garrett, Peter, $d 1953-
510 2# $w r $i Group member : $a Midnight Oil
(Musical group)
Attributes
of Works and Expressions
The following fields should only
be used to record information about works and expressions that is gathered in
the course of establishing the authorised heading.
The information may also be
recorded in the heading in the 1XX field if required.
- 336
– Content Type:
The form of communication through which the work described is expressed
and the human sense through which it is intended to be perceived.
- 370
- Associated Place:
The town, city, province, state, and/or country associated with the work
or expression
- 377
- Associated Language:
The MARC language code/s and/or term/s in which the work is expressed.
- 380
– Form of Work:
The class or genre to which a work belongs.
- 381
- Other Distinguishing Characteristics of Work or Expression: Any characteristic that serves to
characterize a work or expression but cannot be recorded in another field.
- 382
– Medium of Performance:
The instrumental, vocal, and/or other medium of performance for which a
musical work was originally conceived or for which a musical expression is
written or performed.
- 383
- Numeric Designation of Musical Work: A serial number, opus number, or thematic
index number assigned to a musical work by the composer, publisher, or a
musicologist.
- 384
– Key:
The set of pitch relationships that establishes a single pitch class as a
tonal centre for a musical work or expression.
4XX and
5XX– Relationships between Works, Expressions, Manifestations and Items
The specific nature of the
relationship between a work, expression, manifestation or item and a related
work, expression, manifestation or item should be included in 4XX and 5XX
fields, if considered important.
Record the relationship
information in $i subfield.
Refer to RDA Appendix J for the
relevant list of relationship designators.
100 1# $ a Dickens, Charles, $d 1812-1870. $t
Oliver Twist
530 #0 $w r $i Adapted as a motion picture (work)
: $a Oliver! (Motion picture)