UIUC RDA Local Policy
October 29, 2013
UIUC Library began implementing RDA cataloging standards on February 4, 2013. We continue
to comply with the current policy of conformity to LC-PCC policy statements,1 PCC guidelines,2
the OCLC RDA policy statement3 and CARLI recommendations.4 For serials, foreign language
materials, electronic resources, music, rare books and other special materials, follow the
cataloging policy from the corresponding cataloging organizations.
1. LC RDA Core elements
Follow LC RDA Core elements unless instructed to do otherwise below.
2. Duplicate records
Under OCLC policy, records can still be created using AACR2. OCLC also still allows
parallel records for different languages of cataloging. However, only one bibliographic
record per language is allowed for each manifestation of a title regardless of the different
descriptive rules. If AACR2 and RDA records in the same language are found, apply
“Best Record” rules. Use criteria such as which record has the highest level of
authentication (i.e., lc or pcc), which record has the most holdings or contains the most
information. If neither the AACR2 nor the RDA record matches the above criteria, select
the record input first.
3. Hybrid Records
Hybrid records refer to those bibliographic records which have RDA elements added to
non-RDA records. According to PCC Guidelines on Hybrid Bibliographic Records,
hybrid records should not be created in the following situations:
The pre-RDA record already fulfills user tasks and accurately describes the resource.
The cataloger does not have access to the resource or an acceptable surrogate.
Do not change a record to conform to different rules unless you have an item at hand and
the record is a minimal level record (encoding level is “K”)
1
The LC-PCC Policy Statement is available from the RDA Toolkit (within the Toolkit, click on the "Resources" tab)
http://www.loc.gov/aba/pcc/rda/RDA%20PCC%20Proposed%20Guidelines%20and%20Standards.html
3
http://www.oclc.org/rda/new-policy.en.html
4
http://www.carli.illinois.edu/products-services/i-share/cat/rda-resources
2
4. Relationship designators ($e or $j in 1xx and 7xx; $j for conference only )
Relationship designators are required locally although not included in LC RDA Core
elements. We use relator terms ($e or $j) but not relator codes ($4). According to the
PCC Relationship Designator guidelines, “It is recommended that PCC catalogers use
relationship designators from the RDA appendices unless they are cataloging according
to specialist community guidelines that prescribe an alternative source vocabulary.” Use
Appendix I in the RDA Toolkit for lists and guidelines on recording the person’s,
family’s or corporate body’s relationship to resources. Check the definition for each term
before using it. If you cannot find terms in RDA Appendix I, check Library of Congress
MARC Code List for Relators for MARC term sequence. If the RDA term is different than
the MARC term, prefer the RDA term. If needed terms or codes are lacking, provide the
more general term if it is sufficient. “If you cannot ascertain a more specific relationship,
assign the element term, e.g., Creator or Publisher. If the nature of the relationship cannot
be ascertained even at a general level, do not assign a relationship designator.” (PCC
Guidelines). For information about the reconciliation of terms, see MARC and RDA
Relators Reconciled. The relationship designator subfield is repeatable
5. Name Authority records (1xx and 7xx)
Catalogers creating RDA bibliographic records should use authorized forms of names
and titles established in existing AACR2 and RDA authority records. If no AACR2 or
RDA authority record exists or if the AACR2 authority record contains a 667 field
prohibiting use of the heading (i.e., with the note “This 1XX field cannot be used under
RDA…”), catalogers who do not have access to create authority records should establish
the headings following RDA standards and process the book. After the book is
processed, print out the bibliographic record and attach copies of title page, cover page,
barcode and related information, and place them on the NACO shelf located in CAM.
6. Statement of responsibility ($c in 245)
There is no limit on number of persons, families, corporate bodies included. It is not
necessary to justify the authorized access point for every listed creator. The choice is
based on cataloger’s judgment. The first-named or principle creator is always required. If
only the first-named entity is given, a summary is included to explain the omission (e.g.
[and twelve others]).
7. GMD (General Material Designation, “$h” in 245 field)
Do not add a GMD to RDA catalog records. A chart for mapping GMD to MARC values
is available at: http://special-cataloguing.com/misc/gmd_to_cmc_and_extent_20120330.pdf
Contact CAM for additional information.
8. Punctuation in edition statement
Transcribe an edition statement in the 250 field as it appears on the source of information.
If the edition statement ends in an abbreviation that includes a period (such as “ed.”), do
not add an additional period at the end of the field.
9. Publishing date and copyright date
If a single-part monograph contains only a publication date, record it in the 264 and fixed
fields. If it contains both a copyright date and a publication date, record both even if they
are the same. If an item lacks a publication date but one can be inferred from the
copyright date, record the publishing date in square brackets, and code Type of date
008/06 as “t” (see OCLC #811020012). These requirements do not apply to multipart
monographs, serials or integrating resources.
10. Dimensions for Serials ($c in 300)
For serials, we treat dimensions as required even though it is optional according to the
CONSER RDA standard.
11. Content type, media type, and carrier type (336, 337, 338)
Though LC does not use $b (code) in the fields, we follow OCLC’s RDA policy and
require use of $b in all three fields. Copy catalogers accept what exists in the record.
Original catalogers provide both code and term in subfield $b and subfield $2. You can
find terms in RDA section 6.9 (Content type), section 3.2.1.3 (Media type) or section
3.3.1.3 (Carrier type) in the RDA Toolkit. However we recommend using the LC list
because it provides both terms and codes. For accompanying material, 336, 337 and 338
are repeatable.
MARC 336 Content type http://www.loc.gov/standards/valuelist/rdacontent.html
MARC 337 Media type http://www.loc.gov/standards/valuelist/rdamedia.html
MARC 338 Carrier type http://www.loc.gov/standards/valuelist/rdacarrier.html
12. Compilations by more than one creator.
If there is a collective title, identify the compilation by its preferred title (RDA 6.27.1.4).
In other words, the title is the main entry and the creators are analytical entries in 700
fields. Give one MARC 7XX analytical authorized access point for the predominant or
first work when it represents a substantial part of the resource; use cataloger judgment if
additional 7XX fields are given for other works. Also 505 content notes are required for
each title.
If no collective title is available, do not devise a title to use as a preferred title in the
MARC 130 field to identify the compilation. Record each title in the 245 field and do not
give 505 content notes. If a preferred title is needed later (e.g., for a translation of the
compilation), see the LC-PCC PS Alternative at RDA 6.27.1.4
13. Other fields
Follow standards even if some MARC fields do not display in Voyager Classic. For
example, when using RDA rules, 264 field(s) should be used to record publication
information rather than the 260 field. Also, when recording the source of the description,
the 588 field should be used instead of a more general 500 note.
14. Different formats
For RDA cataloging examples of materials in different formats, refer to the RDA
examples in the RDA Toolkit or on the Library of Congress website.
For any questions about cataloging rules or local practice, contact the CAM RDA Task Force.