Final Report of the PCC TG on Hybrid Integrating Resource Records

taupesalmonInternet and Web Development

Oct 21, 2013 (3 years and 9 months ago)

186 views


PCC Task Group on Hybrid Integrating Resource Records

Final report

Submitted: April 6, 2012

Revised: April 25, 2012













Task Group


George Prager (Chair, New York
University

Law School)

Valerie Bross (UCLA)

Renee Chin (
University

of Calif
ornia,

San Diego)

Les Hawkins (PCC Secretariat)

Laura Ramsey (OCLC)

Dale Swensen (Brigham Young
University

Law School)

Holly Tomren (Drexel
University
)

Margaretta Yarborough (PoCo liaison
,

UNC
-
Chapel Hill
)



2


Table of Contents


Background

................................
................................
................................
................................
...................

3

Summary of recommendations

................................
................................
................................
.....................

3

Section 1. Redescribing pre
-
RDA records using RDA

................................
................................
.................

4

Section
2. Enhancing pre
-
RDA records using RDA

................................
................................
.....................

6

Section 2.1 Straightforward enhancements

................................
................................
...............................

6

Section 2.2 Other enhancements (proceed with caution)

................................
................................
..........

7

Section 3. Special considerations when using RDA to enhance pre
-
RDA records

................................
......

8

Section 3.1 Overview

................................
................................
................................
................................

8

Section 3.2 Loose
-
leaf IRs (especially loose
-
leaf services)

................................
................................
......

8

Section 3.3 Non
-
textual IRs

................................
................................
................................
......................

9

Section 3.4 Provider
-
neutral IRs

................................
................................
................................
...............

9

Section 3.5 IRs related to resources in other forms of issuance (e.g., serial in print/IR online)

.............

10

Section 4. Table 1: Guidelines for creating a hybrid record from a pre
-
RDA record

................................
.

10

Section 5. Integrating resources: a cataloging manual

................................
................................
................

13

Section 5.1
Other general and miscellaneous changes needed in the IR manual

................................
....

17

Section 6: Appendices

................................
................................
................................
................................
.

28

Section 6.1 Appendix A: RDA implementation dependencies

................................
...............................

28

Section 6.2 Appendix B: Revision of PCC RDA Frequently Asked Questions

................................
.....

29




3


Background


The PCC Task Group on Hybrid Integrat
ing Resource Records was formed on January 17, 2012, and its
final charge was received on January 25, 2012
.
Its members included: George Prager (Chair, New York
Univ
ersity

Law School), Valerie Bross (UCLA), Lynne Branche Brown (Skyriver), Renee Chin
(Univ
ersity
of Calif
ornia,
San Diego), Les Hawkins (PCC Secretariat), Laura Ramsey (OCLC), Dale
Swensen (Brigham Young Univ
ersity

Law School), Holly Tomren (Drexel Univ
ersity
), and Marg
aretta
Yarborough (PoCo liaison,

UNC
-
Chapel Hill
)
.
Lynne needed to subseque
ntly withdraw from the
Task
Group
.

The group was charged to continue the work of an earlier Task Group, the PCC Task Group on Hybrid
Bibliographic Records, and to produce a guide or cue sheet that would

respond to the following questions:

o

In what situation
s would it be better to redescribe an integrating resource record according to
RDA rather than maintaining the record in a hybrid manner?


o

If there are situations where a pre
-
RDA record for an integrating resource does NOT need to be
redescribed, then:




W
hat maintenance on pre
-
RDA records can catalogers complete without concern
(because applying RDA instructions has the same effect as pre
-
RDA codes)?



What should catalogers trained to catalog using RDA watch out for when editing
integrating resource records

originally cataloged using a pre
-
RDA code?


o

Are there any special considerations needed when using RDA to maintain pre
-
RDA records for:



Loose
-
leaf IRs? (es
p.
l
oose
-
leaf services)



Non
-
textual IRs?



Provider
-
neutral IRs?



IRs related to resources in other
forms of issuance (e.g., serial in print/IR online)?



Other?


As time permitted, the Task Group was further charged to review
Integrating Resources:
A

Cataloging
Manual

(Appendix B of the BIBCO Participants’ Manual and Module 35 of the CONSER Cataloging
Manual), and to determine what sections of the manual would need to be reconsidered with regards to
RDA
.
Lastly, the Task Group was required to provide two appendices: A
ppendix A, RDA
implementation d
ependencies; and Appendix B, Revision [where needed] of PCC RDA Frequently Asked
Questions.

Summary of
r
ecommendations


Currently, we are in an “interim period
,
” as RDA will not be implemented officially by LC and PCC until
March 31, 2013
.
Most of the recommendations in this report are based on the nature of integrating
resources, not the current situation
.
Therefore, the Task Group believes that these recommendations will
4


also
be useful in the post
-
implementation period, n
ot just during the interim period
.
Shared databases are
likely to contain pre
-
RDA integrating resource records for an indefinite period, and many of these records
will need to be updated.

Updating records:
r
edescribing vs
.
e
nhancing

1.

Redescribing the resource in RDA is
nearly

always the best policy, whenever the latest iteration
of the resource is available
.
However, the final decision should be left up to the cataloger (or
institutional policy).

2.

Records should not be recoded as RDA (
040 $e rda) unless the resource
has been

completely
redescribed
, and all
elements in the record have been
verified

to be

in accordance with RDA.

3.

It is better not to redescribe the record in RDA, whenever the cataloger does not have access to
the most curr
ent iteration
.
This situation would normally only occur with updating loose
-
leaf
publications
.
Enhancing the record is a viable option in this case.

4.


A pre
-
RDA record may be enhanced in the same pre
-
RDA standard, or in RDA (thus creating a
hybrid record)
.

Enhance by
addition, not by

removing valid information
.
Adding more access
points is always an option
.

The goal is to contribute to the FRBR user tasks, not to tweak records
for purely stylistic purposes
.

Revising the Integrating Resources Manual


1.

The

IR manual should be reorganized along FRBR and RDA lines
.
A suggested

reorganization

is
outlined in
Section
5
. Integrating resources: a cataloging manual
.

2.

Throughout the manual,
RDA

terminology should replace
AACR2

terminology, and
RDA/LCPS
/PCC policy

references should replace AACR
2
/LCRI citations.

3.

An analysis of other recommended changes is given for each current chapter of the IR manual.


Section 1
.
Redescribing pre
-
RDA records using RDA


In what situations
would it be better to redescribe an integrating resource record according to RDA
rather than enhancing the record in a hybrid manner?

The Task Group recommends
taking
a liberal approach

towards redescribing a pre
-
RDA record in RDA
.
If the cataloger has ac
cess to the latest iteration of the resource, it is best if she/he redescribes the
resource
.
However, the final decision needs to be the cataloger’s (or dependent upon institutional policy)
.
We agree with the earlier Task Group that, if the decision is m
ade to redescribe, the redescription should
be a complete process, where all appropriate elements are evaluated in light of RDA (
p.
3

of their
report
)
.
Equally as important, the cataloger should
use

the most recent iteration of the resource (or its surrogate),
or at least an iteration of the resource no earlier than the one that has been used as the basis of the pre
-
RDA description
.
In some situations, t
he cataloger may not have easy access to a later iteration, or the
changes needed to redescribe may be so time
-
consuming that enhancement is a more practical option,
especially if the record has previously been updated only sporadically, if at all
.
While
redescription of a
pre
-
RDA record is clearly the preferred option, enhancement of the record is also helpful
.
Typical cases
5


would be enhancing the pre
-
RDA record with a new place of publication or publisher, additional ISBNs,
an additional author in the s
tatement of responsibility, or closing out the record
.

As one Task Group memb
er pointed out,

“With serials you worry that if you recatalog, you’re going to
lose some data from the AACR2 record when you create the RDA description because the AACR2 was
based

on the first or earlier issues and you only have later ones
.
The rules for transcribing that
information (with regard to fullness, abbreviations, etc.) may have changed so that you can
not

be sure
from what’s in the record exactly how it appeared on that
first issue that you now don’t have the chance to
examine
.
Thus your only choice is to base your new RDA description on the issues you have, which may
mean you have to delete data found in the original record that was based on the first issue
.
This is no
t so
much a problem though with integrating resources, since most of the description is based on the current
iteration
.
Although you might not have in hand the first issue of a serial, when you have a loose
-
leaf
publication to recatalog, it’s quite probab
le that it will be the most current iteration, and obviously
someone describing an online resource will be looking at the latest version
.
Details about earlier versions
are usually optional and relegated to notes, where rules for transcription are not so
rigid and exacting.”

Redescribing to RDA is definitely recommended in the following cases:

1.

As stated in the
earlier guide
, “If you cannot do what you need to do unless you re
-
describ
e, you
ought to re
-
describe” (
p.
3)
.
In general, we recommend re
describing

to RDA whenever the
cataloger judges that by doing so, user access to the resource would be enhanced by contributing
to the FRBR user tasks: find, identify, select, and obtain
.


2.

If

the necessary changes to a non
-
RDA record using a hybrid approach would render the record
unintelligible, or difficult to interpret, such as when a needed authorized access point would not
be valid under pre
-
RDA codes.

Examples:

a)

An integrating resource w
ith an authorized access point for the name of a family, such as
some genealogical blogs.

b)

An integrating resource with an authorized access point

for a
n animal or
a fictitious person

(e.g., a Miss Piggy website with Miss Piggy listed as the primary creator
).

c)

An integrating resource with an authorized access point for the name of a personal author
,
rather than the preferred title under AACR2’s “rule of three
,


and linking entries for related
resources
that
would be confusing and/or inconsistent if the resour
ce were not redescribed
.


When it is best NOT to redescribe in RDA:

Although not
required by

the

original charge,

the Task Group

felt it would

be helpful to mention
situations in which it is best not to redescribe a pre
-
RDA record in RDA:


a)

The pre
-
RDA
record already fulfills user tasks and accurately describes the resource
.



b)

The cataloger does not have access to the resource or an acceptable surrogate.


6


c)

The cataloger only has access to an iteration of the resource that is earlier than the one cited
in
the existing pre
-
RDA record.


In the

last two instances,

it is not possible to know if the pre
-
existing information in the record includes
AACR2
-
sanctioned abbreviations and other practices, or if it represents actual transcription, so the proper
RDA trans
cription is not possible (e.g., the chief source may have “2
nd

ed.” or “second edition” but both
would appear as “2
nd

ed.” on the AACR2 record)
.


Section 2
.
Enhancing pre
-
RDA records using RDA

Section 2.1 Straightforward enhancements


If there are situations where a pre
-
RDA record for an integrating resource does NOT need to be
redescribed, what enhancements on pre
-
RDA records can catalogers complete without concern
(because applying RDA instructions has the same effect as pre
-
RDA codes
)?

The following is a selective list of changes in a pre
-
RDA record that would be done in essentially the
same manner in AACR2 or RDA
.
Most of these changes would be handled the same way in all records,
regardless of mode of issuance.

Fixed length data
elements (006 and 008
)

P
hysical

description fixed fields (007
)

V
arious

numbers and codes (0XX
)

T
itle

proper (245
)

Former title (247)

V
ariant

titles (246
)

R
esponsible
bodies (except if the new responsible body is a family: MARC 21 field 100 3
#)

D
imensions

(300 $c
)

F
requency

(310) and former frequency (321
)

D
ates

of publication and/or sequential designation (362 1
#)

Notes

(5XX
)

S
ubject

and genre/form added access points (6XX
)

A
dditional

authorized access points (
7
XX
)

Linking entries (77X
-
78X)

S
eries

8
XX

acc
ess points (800
-
830
)

URLs (856
)

Non
-
Latin scripts

Closing

out records

For a more complete list of RDA elements that may be added to a pre
-
RDA record, refer to
Table 1:
Guidelines for creating a hybrid record from a pre
-
RDA record
.




7


Section 2.2

Other enhancements
(proceed with caution)


If there are situations where a pre
-
RDA record for an integrating resource does NOT need to be
redescribed, what should catalogers trained to catalog using RDA watch out for when editing
integratin
g resource records originally cataloged using a pre
-
RDA code?

The
goal is to enhance records to contribute to the FRBR user tasks, not tweak records for purely stylistic
reasons
.


This section offers guidance on what NOT to do, when editing a pre
-
RDA IR re
cord
.
For a
more complete list of RDA elements that may be added to a pre
-
RDA record, refer to
Table 1
.



Do not recode the record as “rda
,”

unless completely redescribing
.
Recoding the record as
RDA would involve adding
040

$e “rda


and changing Leader 18 “De
scriptive cataloging form”
to “i
.”



Do not remove anything that is valid in a pre
-
RDA record, unless the information given is
obsolete
.
Enhance by addition, not by taking valid information away.

Examples:

o

General materi
al designations

(245 $h)

o

Abbreviations
:
Do not remove
Latin abbreviations used in AACR2 ([s.n.], [s.l.], and
others), unless the field where the abbreviation occurs needs to be updated.
Do not
change

other
valid AACR2 abbreviations to the spelled out forms

that would be used in
RDA in most cases, such as edition statements, imprint statements, and physical
description fields
.

o

Bracketed information:

The RDA cataloger revising a pre
-
RDA IR

record

needs to be
mindful that AACR2 calls for brackets in many cas
es where they would not be used in
RDA
.
RDA
prescribes using

brackets

only
for

information supplied from sources other
than the resource itself
.
If you are not updating or enriching the data, the brackets should
not be removed
.

o

Capitalization:

If you a
re not replacing the data, do not alter the pre
-
existing
capitalization, if it is valid under pre
-
RDA practice.



Do not use an authorized access point (1XX) or choice of entry that would not be valid in
AACR2 records
.
Additional access points (246, 7XX) ma
y however be freely added
.

Examples:

o

AACR2 uses a “title main entry” for most resources with four or more authors (regardless
of whether it is a compilation or collaboration)
.
When only enhancing such a record, not
redescribing it, do not change the autho
rized access point from title proper to a personal
author, if the number of persons responsible for the work remains
at least four
.
(RDA
would use a preferred access point for the primary or first named author for most
collaborative works)
.

o

If
maintaining an AACR2 record for a genealogical blog, do not use an authorized access
point for a family name (100 3#).



Linking entries (76X
-
78X
)
:

When
linking

to a

pre
-
RDA record, the form in the linking entry
should also reflect pre
-
RDA convent
ions and

sh
ould not be updated to how RDA would cite the
related resource
.


8


Section 3
.
Special
considerations

when using RDA to enhance pre
-
RDA
records

Section 3.
1
Overview


If the cataloger chooses not to
redescribe

a pre
-
RDA record to RDA, she/he has two options: to maintain
a pre
-
RDA record in that pre
-
RDA standard, or to maintain it using RDA, thus creating a hybrid record
.
Hybrid records may contain both pre
-
RDA and RDA elements
.
The coexisting elements should
enhance
the record and not cause more confusion
.
To maintain/enhance pre
-
RDA records using RDA, do not
change or delete information that is valid or correct with regard to the most current iteration available
.
Obsolete information may be moved to note fi
elds or deleted
.


Adding RDA elements or sub
-
elements to enhance a pre
-
RDA record

The following new RDA elements may be added to any pre
-
RDA record: Relationship designators or
codes ($e, $4, or $i); Content, media, and carrier types (terms, codes, or bot
h: 336
-
338); Sound,
projection, video, and digital file characteristics (new 344
-
347 fields, when implemented by LC, PCC,
OCLC); Form of work (380), and
the new
dissertation subfields (502 $b
-
$o).

When updating descriptive information in any area of a pre
-
RDA record, it is permissible to follow RDA
conventions, including (but not limited to) the title and statement of responsibility elements

(245)
, edition
information

(250)
, imprint information (260, 264), carrier information (300), series statements (490),

and
notes (5XX)
.
Additional access points may be added as needed, if considered to be important for
identification and access
.
Prior to PCC Day 1 for RDA Authority Records (March 31, 2013), authorized
access points may be in AACR2 or RDA form, as long a
s the form exists in the
LC/NACO A
uthority
F
ile
.
On or a
fter this date, all authorized access points
on bibliographic records coded “pcc” must be
RDA, even if the bibliographic description follows a pre
-
RDA code.
.

The resource represented by a pre
-
RDA
record may be related to another resource or resources (e.g., a
new edition, a change in mode of issuance, physical format, etc.)
.
If the record for the related resource
has been created after RDA implementation, it should be cataloged according to RDA
.
In most cases,
related resources cataloged using different standards should not cause confusion for users
.
If a new
record is described in RDA, the old record can be retained as AACR2 or as
a

hybrid
.
The records may
include reciprocal linking entries
.
I
f the pre
-
RDA record has been linked to a related record that is
cataloged according to RDA, the form of the linking entry should follow RDA conventions
.
Conversely,
if the RDA record has been linked to a related pre
-
RDA record, the form of the linking en
try should be
faithful to the specific pre
-
RDA code.

For a more complete list of RDA elements that may be added to a pre
-
RDA record, refer to

Table 1
.


Section 3.
2 Loose
-
leaf IRs (especially loose
-
leaf services)


There are very
few special considerations needed when using RDA to maintain pre
-
RDA records for
updating loose
-
leafs
.
The rules for when to create a new bibliographic record (RDA/LCPS 1.6.3.3 and
AACR
2
/LCRI 21.3B) are the same
.

9


RDA (3.4.1.10) does not require the
addition of a statement of extent for incomplete textual resources, or
if the total extent is unknown
.

RDA 3.4.5.2 does allow the use of

1 volume (loose
-
leaf)


for a current
loose
-
leaf resource that is likely to remain in only one volume (e.g., BNA

s tax

management portfolios,
etc.)
.
RDA 3.4.5.19 is a comparable rule for multi
-
volume updating loose
-
leafs
.
In most cases, the
cataloger will not know the final number of volumes for an incomplete loose
-
leaf, and
will

likely omit the
300 $a (not core for inc
omplete textual resources), or use

volumes (loose
-
leaf)”
--
similar to what AACR2
2002 Revised requires for all incomplete loose
-
leafs
.
RDA cataloger
s

enhancing

AACR
2

record
s

for
updating loose
-
leaf
s

should keep in mind this slight difference in RDA and AA
CR
2

practice.


Section 3.
3 Non
-
textual IRs


Non
-
textual IRs are generally online websites or databases in which the content is primarily images
(Leader 06 “type of record” k), audio (type i/j), video (type g), maps (type e), music scores (type c),
computer

datasets (type m), or some combination thereof
.
These integrating resources are currently
coded in MARC 21 with at least one 006 and several 007s in order to capture their diverse material and
physical characteristics
.
This information may be complement
ed on any pre
-
RDA record by the addition
of the new RDA elements for content, media, and carrier type (MARC 21 336
-
338 fields)
.
Content type
var
ies

depending upon t
he code

in Leader
0
6, and more than one
code
might be applicable
.
Content,
media, and
carrier types may also change over time
.
As with other online websites or databases, in RDA
the carrier will be

online resource


and the media type will be

computer
.”


Pre
-
RDA records for online websites or databases generally lack

a statement of exten
t (300 $a), unless the
AACR2 9.5B3 option has been applied
.
If a statement of extent is lacking,
a

300

field

for

“1 online
resource


may be added to any pre
-
RDA record
.


Section 3.
4 Provider
-
neutral IRs


Although RDA prescribes the creation of

a
separate
record

for each manifestation
,
the PCC
recommends
applying the provider
-
neutral

approach where it is applicable to online IR databases
.

In the current cataloging environment, identification of online integrating resources can be problematic,
as evidenced b
y the number of duplicate or duplicative records
.
Duplicative records make it difficult to
consistently identify and thereby maintain
provider
-
neutral

IR records
.

Can RDA provide the framework needed to support and improve resource discovery of online
p
rovider
-
neutral

IRs to allow for more consistent maintenance of IR records? The purpose of maintaining and
enhancing records is to improve resource discovery
.
If a resulting enhanced
provider
-
neutral

pre
-
RDA
record description renders user access more di
fficult or confusing, catalogers may choose to redescribe a
pre
-
RDA record using RDA, rather than try to maintain it using RDA standards
.


10


Section 3.
5 IRs related to resources in other forms of issuance (e.g., serial in print/IR
online)


Pre
-
RDA records f
or IRs related to resources in other forms of issuance can be maintained as hybrid or
pre
-
RDA

records, or be converted to RDA
.
For more information, see
Loose
-
leaf IRs
,
Non
-
textual IRs
,
and

Provider
-
neutral IRs
.


Generally, link only between RDA
-
compatible records (e.g., AACR2, RDA, or hybrid)
.
For example, do
not link a latest entry print serial record to a hybrid
AACR2/RDA record
.
T
he latest entry print serial
record may be redescribed in RDA, and th
en linked to the related record(
s
)

if appropriate.


Section 4
.

Table 1:
Guidelines for creating a hybrid record from a pre
-
RDA
record


Enhancing pre
-
RDA
r
ecords

for
i
ntegrating
r
esources

When adapting pre
-
RDA copy from a national utility such as OCLC, you have three basic choices:

1)
L
eave the copy as it is, in its pre
-
RDA state
.

2)
A
dd some RDA elements without changing the whole record, thus creating a hybrid
.

3)
R
e
describe the resource to result in a record that is fully RDA
.


Redescribing vs.
c
reating a hybrid

Consider redescribing a record when:



The existing record is minimal or substandard and you want to create a
more complete or higher
level

record.




You need
to make extensive changes to an existing record because of changes in a new iteration
of the resource
.




Doing so will enhance discoverability and identification of the resource.




You are sufficiently trained in RDA to redescribe.

You may want to c
onsider
creating a hybrid record (i.e.
,

adding RDA elements to a pre
-
RDA record
without converting the entire record to RDA) when:



You want to add some RDA elements to a record, but lack the time, resources, or training to do a
complete redescription.


11




The informa
tion in the existing

record

is correct and complete, but you want to
enrich the record
with
RDA elements such as content/media/carrier, relationship designators, etc.




In your estimation, redescribing will do little to enhance the functionality of the reco
rd.

The table below is designed to provide guidance in editing, enhancing, or maintaining a pre
-
RDA record
when you want to add some RDA elements, but do

n
o
t want to redescribe. Hybrid records will remain
coded according to the standard under which they we
re originally created. In other words, fixed

field
values that label the record as AACR2, pre
-
AACR2, etc. will not be changed.


Table 1.
Guidelines for creating a hybrid record from a pre
-
RDA record


MARC

Element

Action

All fields




Do not remove or reformat information
in
fields
that are

correct.



Change information in existing fields as
needed to match the current iteration. New
information may be formatted according to
RDA if preferred, or formatted according to
the standards of the

existing record.



New fields may be add
ed

as needed and
formatted according to RDA or following
the standard of the existing record.

All fields
under
authority
control

Main and added entries,
uniform titles, series added
entries, subject access fields

Alw
ays match access points with forms
established in name and subject authority files,
recognizing that in some cases (for personal,
corporate or place names) these may be RDA
forms.

Leader/18


Descriptive cataloging form


Leave the value in this field as is
.

007

Physical description fixed field

If 007 is present and you add fields 336
-
338,
make sure the codes in the 007 agree with the
values you assign for content/media/carrier.


040

Cataloging Source

Do not add $e rda.

1XX/240

Main entry/Uniform title

(Prefer
r
ed entry/Preferred title)

Do

not change the choice of entry

if it would
not be
valid

under the pre
-
RDA code
.


See “All
fields under authority control” above.

245

Title
statement

D
o not remove a GMD
that is still
applicable to
the current
iteration
. See “All fields” above.

247

Former title

When replacing the title proper with a new
title, transfer the former title to 247 without
altering punctuation, capitalization, or form.

250

Edition statement

Change as needed to match the current
iteration.

See “All fields” above.

12


MARC

Element

Action

260

Publication, etc.

May add new publi
cation information

using an
additional 260 field or by
replacing

the
old

information for the
new

in the existing one.

If
adding a new 260 field, move $c (date) from
the existing field to the new one.

See “All
fields” above.

300

Physical description/extent

Retain pre
-
RDA abbreviations and Latin terms,
unless the description has changed.

See “All
fields” above.


You may

also opt to add a 300 field for
“1

online resource


if not already present.

336/337/338

Content, media, carrier types

Feel free to add these to any record.

You may
also
need to update

the
corresponding 007, 300,
and 516

fields
.

516

Type of Computer Fil
e or Data
Note

W
hen changing this field
, you may also need to
update the corresponding 007, 300, and 516
fields
.

588

Source of Description Note


Make sure this matches the version you have in
hand.

Modify as needed.

6XX

Subject
access fields


Add new entries as needed, but generally do
not remove existing ones.

See “All fields
under authority control” above.

7XX

Added entries/Analytical added
entries (Access points)

Add new entries as needed, but generally do
not remove existing ones.

See “A
ll fields
under authority control” above.

76X
-
78X

Linking entries

Recognize that data in linking entries reflect
information as it appears in corresponding
records for these entities, which may not be in
the same standard as the record at hand.

Do
not mo
dify this information if it is correct as is.

General

Relationship designators

Feel free to add approved RDA relationship
designators to any access points if desired.

General

Non
-
Latin scripts

Feel free to add parallel fields in non
-
Latin
scripts per PCC guidelines.




13


Section
5
.
Integrating
resources: a cataloging manual


With the impending implementation of RDA, most PCC documentation will need to be reorganized along
FRBR and RDA lines
.
The Task Group agreed that the IR manual would also need to be reorganized and
suggested

the following restructur
ing,

which has been outlined on the two tables below
.
T
able
2

displays
the proposed arrangement of the new

IR manual

by its new section numbers
, and
Table
3

displays the
same content arranged by the section numbers of the current IR manual
.
The proposed new sections are
referred to as “RDA IR.1
,”

etc
.
The Task Group also discussed changes
needed in each section of the IR
manual
.
The summaries of these changes are arranged by the section numbers of the current IR manual

below
.

Table
2

Proposed a
rrangement



Current
a
rrangement of 2011 Revision

RDA IR: Introduction

Introduction

RDA IR:
Objectives

Objectives

RDA IR: References

References

RDA IR: Definition of terms

Definition of terms

RDA IR.1 What is an integrating resource?


Current IR.1 What is an integrating resource?

RDA IR.2 Identifying manifestations and items

(RDA Chapter 2)


Current IR.3
-
IR.9; also pa
rts of current IR.10

RDA IR.2.1 Basis of identification of the
resource & Sources of information (RDA 2.1
-
2.2)

Current IR.3

Sources of information

RDA IR.2.2 Title and statement of responsibility

(RDA 2.3
-
2.4)

Current IR.4 Title and statement of responsibility
area


RDA IR.2.3 Edition statement (RDA

2.5)

Current IR.5 Edition area

RDA IR.2.4 Production, publication,
distribution

(RDA 2.7
-
2.11)

Current IR.7 Publication, distribution, etc., area
manufacture stat
ements and copyright date

RDA IR.2.5 Series statement (RDA 2.12)

Series access points would be covered as part of
RDA IR.7, or, exceptionally, included here.

Current IR.9

Series statements and series access
points




14


Proposed a
rrangement



Current
a
rrangement of 2011 Revision

RDA IR.2.6 Note (RDA 2.20, etc.)

Notes are covered in various parts of RDA,
depending upon what FRBR entity they relate to.

Current IR.10
Notes and electronic location and
access

RDA IR.3 Describing carriers (RDA Chapter 3)


The information given in IR.6 can be moved here,
and the subsec
tion entitled
,

Digital file
characteristics. This chapter should include new
sections on RDA media and carrier terms and
codes.


Current IR.8

Physical description area,

and current
IR.6

Type and extent

of resource area


RDA IR.4 Providing acquisition and

access
information (RDA Chapter 4)

Brief new sections might be added, based on other
topics covered in
RDA Chapter 4
.

Current IR.10
.21 Electronic location and access


RDA IR.5 Identifying works and expressions
(RDA Chapter 6)

This section of the new manu
al should fo
cus
especially on RDA 6.27
-
6.30

Constructing access
points for works and expressions. It should also
include a section on content type terms and codes
(RDA 6.9), unless a special chapter is added to the
manual to cover RDA’s content, media, an
d carrier
terms and codes.

Closest current IR counterparts: IR.12 Determining
main and added entries, and IR.13 Uniform titles


RDA IR.6 Describing content (RDA Chapter 7)

Several sections in current IR.10 Notes and
electronic location and access would be

covered
here, such as IR.10.15 Audience, and IR.10.18
Summary.

New sections could be added to for some of the
characteristics given in other sections of RDA
Chapter 7, such as RDA 7.18 Sound content.

No exact counterpart in the current IR manual.

15


Proposed a
rrangement



Current
a
rrangement of 2011 Revision

RDA IR.
7 Recording relationships between
w
orks,
e
xpressions,
m
anifestations
, and

i
tems

(WEMI) (RDA
Chapters
24
-
28)

A discussion should be included for relationship
designators (cf. RDA Appendix J). RDA IR.7
would include a section on authori
zed access points
for series (
RDA 25
.1.1.3
).
A
s an alternative,

a
ll
aspects of series, not just series statements, could
be covered in RDA IR 2.5.

Current IR.11 R
elationships to other resources

RDA IR.8 Recording relationships between
Group II FRBR entities (RDA
Chapters
29
-
32)

These relationships will generally be expressed in
name authority records
.

A brief section on these
relationships could optionally be included in the
manual, since relationships in general are such an
important part of RDA.

Not in current IR manual
.

RDA IR.9 Fixed field coding

Current IR.14

Fixed field coding

RDA IR.10 Subject analysis and classification
(FRBR Group III relationships; subjects not yet
in RDA; placeholder
C
hapters 33
-
37)
.


I
nclude
a
lso

a
brief
section on
genre/form
.


Current
IR.15

Subject analysis and classification

RDA IR.11 How many bibliographic records?
(RDA/LCPS 1.6.3)

Current IR.16

How many bibliographic records?

RDA IR.12 Provider
-
neutral record for
electronic integrating resources

Current IR.2

Provider
-
neutral record for electronic
integrating resources

RDA IR.13 Full record examples

Current IR.17
Publication, distribution, etc. area





16


Table
3

Current a
rrangement of 2011 Revision

Proposed
a
rrangement



Introduction

RDA IR: Introduction

Objectives

RDA IR: Objectives

References

RDA IR: References

Definition of t
erms

RDA IR: Definitions of terms

Current IR.1 What is an integrating resource?

RDA IR.1 What is an integrating resource?


Current IR.2

Provider
-
neutral record for
electronic
integrating resources

RDA IR.12 Provider
-
neutral record for electronic
integrating resources

Current IR.3

Sources of information

RDA IR.2 Identifying manifestations and items


RDA IR.2.1 Basis of identification of the resource
& Sources of information
(RDA 2.1
-
2.2)

Current IR.4 Title and statement of
responsibility area

RDA IR.2.2 Title and statement of responsibility

(RDA 2.3
-
2.4)

Current IR.5 Edition area

RDA IR.2.3 Edition statement (RDA

2.5)

Current IR.6

Type and extent of resource area

RDA
IR.3 Descri
bing carriers (RDA Chapter 3)


Current IR.7 Publication, distribution, etc., area
manufacture statements and copyright date

RDA IR.2.4 Production, publication, distribution

(RDA 2.7
-
2.11)

Current IR.8

Physical description area

RDA IR.3 Descri
bing carriers (RDA Chapter 3)


Current IR.9

Series statements and series access
points

RDA IR.2.5 Series statement (RDA 2.12)

RDA IR.7 Recording relationships between works,
expressions, manifestations, and items
(WEMI)
(RDA
Chapters
24
-
28)

Current
IR.10

Notes and electronic location and
access

RDA IR.2.6 Note (RDA 2.20, etc.)

RDA IR.4 Providing acquisition and access
information (RDA Chapter 4)

Current IR.11

Relationships to other resources

RDA IR.7 Recording relationships between
w
orks,
e
xpression
s,
m
anifestations, and
i
tems (WEMI)
17


Current a
rrangement of 2011 Revision

Proposed
a
rrangement



(RDA
Chapters
24
-
28)

Current

IR.12

Determining main and added
entries

RDA IR.5 Identifying works and expressions
(RDA Chapter 6)

Current

IR.13 Uniform titles

RDA IR.5 Identifying works and expressions
(RDA Chapter 6)


Current IR.14

Fixed field coding

RDA IR.9 Fixed field coding

Current IR.15

Subject analysis and
classification

RDA IR.10 Subject analysis and classification

(FRBR Group III relationships;
subjects not yet in
RDA
; placeholder Chapters 33
-
37).

Current
IR.16

How many bibliographic
records?

RDA IR.11 How many bibliographic records?
(RDA/LCPS 1.6.3)

Current IR.17

Full record examples

RDA IR.13 Full record examples



Section 5.1
Other
general and miscellaneous changes needed in

the IR
m
anual

1.

Throughout
the manual, AACR2 terminology should be replaced by RDA terminology:


Heading


to

Authorized access point
,”


Author, composer, etc.


to
“C
reator
,”


Main entry


to

Preferred title + authorized access point for creator if appropriate
,
” and related changes
of this
kind.

2.

AACR2 rule numbers and references to Library of Congress Rule Interpretations (LCRIs) should
be changed to RDA instruction numbers and references to Library of Congress Policy Statements
(LCPSs).

3.

FRBR and FRAD terminology and concepts

should
be introduced throughout, where appropriate
.
FRBR terms that currently appear in the IR manual need to be examined, to ensure that

they have
been correctly used (for instance, sometimes


work


is used in a general, non
-
FRBR sense)
.

4.

Elimination of AACR2 ab
breviations, fields, and subfields, etc., from full and partial record
examples, if they are not appropriate under RDA (e.g., 245 $h GMD, unless the example is
comparing AACR2 to RDA practice).

5.

MARC 21 changes due to new elements in the MARC 21 format
.
Fu
ll and partial record
examples will need to be updated to include new MARC 21 fields where appropriate, such as
18


336
-
338 and

380
.
Fields 264 and 344
-
347 will also be included if implemented
by

the
time the
IR manual undergoes its next revision
.

6.

If the IR m
anual is reorganized along FRBR and RDA lines, then references to other sections of
the IR manual will need to be updated, once the new chapters are in place
.


Introduction

This section will need to be brought up to date, with some information on RDA imple
mentation and
the use of LCPSs.

Definition of terms used in this module

At the very least, “Digital file characteristics” and “Online resource” (both defined in RDA) should
be added to the list of terms here
.
Other terms such as the FRBR entities, authori
zed access point,
variant access point, content, media and carrier terms, could either be added here, or there could be a
reference to the RDA glossary, which defines all these terms
.

Objectives

This section is fine as is
.

References

The links need to be

rechecked, and the “date viewed” information updated
.
Citations should be
added for RDA, the RDA
T
oolkit, LCPSs, the CLW webpage, and possibly some citations added for
a few major sites on linked data and the Semantic Web.

IR.1 What is an integrating
resource
?

Proposed reorganization
:
RDA IR.1

What is an integrating resource?

RDA does not refer to

continuing resources,


only

serial


and

integrating resource,


or more
generally,

resource


(which refers to the manifestation)
.
But the definition of
an integrating resource
is basically the same:


A resource that is added to or changed by means of updates that do not remain discrete but are
integrated into the whole
.
An integrating resource may be tangible (e.g., a loose
-
leaf manual that
is updated by

means of replacement pages) or intangible (e.g., a Web site that is updated either
continuously or on a cyclical basis).


References to AACR2 should be revised:

p.
11: There is an AACR2 representation of mode of issuance but it is a useful visual aid, an
d
should be retained
.

19


p.
21

..
.

if considered to be important or required by AACR2.



This note could be rephrased
as: “… if considered to be important.” No notes or access points relating to an earlier
iteration of the resource are core in RDA.

The exam
ples are still relevant
.
It would be
help
ful

to add some examples of more unusual types of
IRs such as updating PDFs and updating handbooks
.


IR.2 P
rovider
-
neutral record for electronic integrating resources

Pr
oposed reorganization
: RDA IR.12
Provider
-
neutral record for electronic integrating resources
.

Few wholesale changes are needed to this chapter:

IR.2.1

Scope: The scope remains the same
.
The manual should note that the basic RDA
approach is to have a separate record for each manifestatio
n
.
However, until further notice,
the PCC will continue to apply the
provider
-
neutral

approach where it is applicable to online
IR databases
.
Include information about the new

040 code “pn”

when it
has been
implemented
.

IR.2.2
Guidelines for
r
ecord
creation and record consolidation: provider
-
neutral record
:
The
reference to LCRI 25.5B would need to be changed to RDA/LCPS 6.27.1.9
.
No change is
needed in the section
,

“Record consolidation and deleting duplicates.”

A
provider
-
neutral

RDA record exampl
e should be added.


IR.3 Sources of information

Proposed reorganization
: This chapter should be part of
RDA IR.2

Identifying manifestations and
items
as

the first section
,

RDA IR2.1 Basis of identification of the resource & Sources of information
(RDA 2.1
-
2.2).

IR.3.1.1

Basis of description: This section will probably not need to be changed much
.
The
general guidelines in RDA 2.2.2
-
2.2.4 should be followed, with special emphasis on RDA
2.1.2.4 (Basis
for identification of the resource: integrating resource
),
RDA
2.1.3.4
(Analytical
description: integrating resource
), and
RDA
2.20.13.4 (Iteration
used as the basis
for the identification of an integrating resource
)
.

IR.3.1.2

Chief source
of information: RDA 2.2.2 uses the phrase

Preferred source of
information


rather than

Chief source of information
.”


Preferred sources of information for
print IRs would generally follow RDA 2.2.2.2; online IRs: RDA 2.2.2.4
.
Brackets are only
needed if information is taken from outside the resource itself for the
elements and sub
-
elements enumerated under RDA 2.2.4
.

AACR2 is less restrictive than RDA concerning the
chief or prefer
r
ed source of
title
information for an online IR. AACR2 prefers

formally
presented evidence such as title screens, home pages, etc., and
encoded metadata
, but the
cataloger can select the best presentation of title information from any of these sources. RDA
2.2.4 is more restrictive

and prefers

embedded metadata in textual form that contains a title
(e.g., metadata embedded in an MP3 audio
file
, if available. The title presentation there
20


would take precedence over title
s

appearing in any other part of a home page, even though
the
se

other

title

pre
sent
ations may be preferable in the judgment of the cataloger
)
.

IR.4 Title and statement of
responsibility area


Proposed reorganization
: This section
sh
ould be subsumed into RDA IR.2 Identifying
manifestations and items
,

as

RDA IR 2.2

Title and statement of responsibility
.

RDA 2.3 covers Titles

and

RDA 2.4 covers Statements of r
esponsibility.

IR.4.1
Overview: CONSER
Standard Re
cord (CSR) practices
.
This section may need to be
revised, if CSR practices change under RDA
.
Per
RDA 2.4
,

for all modes of issuance
,

only
the first statement of responsibility is
a

core
element
.

IR.4.2

Title proper: The exception for serials and IRs preferring full form over acronym or
initialism is maintained
.
(IR.4.2.4; RDA 2.3.2.5)

IR.4.3

General material designation: This section could either be deleted, or it could be noted
that GMDs are not used
in RDA, but have been replaced by content, media, and carrier type
terms and codes, with a reference to the appropriate section or sections where these are
discussed in RDA.

IR.4.4

Parallel titles: Treatment of parallel titles proper is the same under RDA
as under
AACR2
.
However
,

RDA 2.3.3.2 allows parallel titles to be taken from any
where

in the
resource, unlike AACR2 12.1D1 (referring back to 1.1D1), which directs that parallel titles
be taken from the chief source of information
.

IR.4.5

Other title info
rmation (RDA

2.3.4):
Recommended

first sentence
for

this section:
“Other title information is not core in RDA.”


RDA does not follow the AACR2 practice
(AACR2 12.1E1c) of supplying other title information when the title proper consists solely of
the name o
f a corporate body, etc
.
Therefore, the example
included in this section

should be
removed from the IR manual or
revised

as an
illustration of an
AACR2 practice
that is
not

valid

in RDA.

IR.4.6

Statement of responsibility:
Per
RDA 2.4
,

for all modes of
issuance
,

only the first
statement of responsibility is
a

core
element
.
Instructions for changing statements of
responsibility seem to be the same under RDA 2.4.1.10.3 as in AACR2.

Areas such as Recording c
hanges to other titl
e information (RDA
2.3.4.7.3), Recording
c
hanges
in

parallel other title information (RDA 2.3.5.4.3)
,

V
ariant title (RDA 2.3.6.1)
,

and
E
arlier title proper (RDA 2.3.7) are optionally covered by notes, as they are in AACR2.


IR.5 Edition area

Proposed reorganization
: RDA IR 2
.3 Edition statement.

IR.5.1. Overview
:
IR.5.1
instructs catalogers
not

to

transcribe parallel statements for edition
information appearing in multiple languages
.
This prohibition is based on LC/PCC policy, not
AACR2 (LCRI 12.2B3)
.
RDA guidelines call
for

transcription of the edition statement as it
21


appears on the source of information.

RDA 2.5.3.3
further
specifies,

Record parallel
designations of edition applying the basic instructions on recording edition

statements given
under 2.5.1.

If there is
more than one parallel designation of edition, record the statements in the
order indicated by the sequence, layout, or typography of the statements on the source or sources
of information.


Currently, there is no LCPS either contravening or supporting th
is
.

IR.5.2

Updating loose
-
leafs: The example given here should be changed (unclear if “4
th

ed.” is an
actual transcription as RDA requires, or represents several AACR2 conventions).

IR.5.3

Electronic resources: In the first example, it would be better not
to abbreviate the names of
the months in the 588 note, as this seems to be against the spirit of RDA (notwithstanding that
there is at least one example in RDA where the months of the year have been abbreviated)
.
In the
second example, the GMD should be r
emoved from the 245, and the 250 should
indicate
“edition”

instead of “ed.”



IR.6 Type and extent of resource area

Proposed reorganization
: RDA IR
.3

D
escribing carriers

(
subsection
:

Digital file characteristics
)
.

“Type and extent of resource area” has no
exact equivalent in RDA
.
Digital file characteristics (RDA
3.19) include file type, encoding format, file size, resolution, etc
.
LCPS 3.19 defines this as an LC
core element for cartographic resources, but it is not otherwise
required
.
MARC 21 has recen
tly
approved a new bibliographic field for digital file characteristics, 347, which has not yet been
implemented by LC, PCC, and OCLC.

Extent (RDA 3.4) is a core element if the resource is complete, or the total extent is known
.
Unlike
AACR2, RDA requires

it for remote access electronic resources as well as direct access resources
.
RDA 3.4.1.7.5 specifies instances where file type and number might be included in a statement of
extent
.

Appropriate MARC 21 fields for recording this data are the same
.
Thoug
h
not

used in more recent
AACR2 records due to the elimination of the Type and
extent of resource area
in 2004,

the 256 field
is still
valid
and is given in RDA Appendix D.2.1 as a place for field type, size, and extent
.
The
information may also be given
in the 300 field as part of the statement of extent or in the 516 field as
a note.


IR.7 Publication, distribution, etc., area

Proposed reorganization
: RDA IR2.4

Production, publication, distribution
.

An important RDA concept that is missing from IR.7 is the cascading status of
publication,
distribution, manufacture, and copyright
data as core elements
.
Elements in any of these categories
can be core or not depending on whether

its

corresponding elemen
ts
are present
in any of the higher
categories

(e.g., place of distribution is core only if no place of publication is given)
.
Also, some
data, whether known or just probable, must be given in 260 subfields $a and $b, such as

$a [Place of
publication not

identified
]
,”

etc
.

However, if the date(s) of publication cannot be approximated, no
date is recorded (RDA 2.8.6.5 applies to multipart monographs, serials, and integrating resources)
.

22


The cataloger should refer to the general instructions in RDA 2.8
-
2.1
1
.

Production


(RDA 2.7)
doesn

t apply to integrating resources in AACR2 or RDA
.

MARC 21

recently
introduced

a new 264 field, though it has not yet been im
plemented by LC, PCC,
or OCLC
.
Once

implemented,
the field will be included in
re
vised examples in

the IR manual.


IR.8 Physical description area


Proposed reorganization
: RDA IR.3

Describing carriers.

Also move IR.6 Type and extent of
resource area into the same section, and rename i
t “Digital file characteristics
.”

In AACR2, some

elements
(
such as
illustrations, color, and sound
)

are
considered a part of the physical description area

whereas in
RDA
, these same elements are

part of describing the content, which is an attribute of the
work and/or expression entities (RDA Chapter 7)
.
This will be cove
red in the
new
chapter,

RDA IR.6

Describing content
.

The

physical description area for IRs
will be

covered
mostly under


Describing carriers,


which is an
attribute of manifestations and items in RDA
.
Much of what is found in IR.8 can be carried over once
the general modifications already identified for all parts are made,
including new

RDA terminology,
abbreviations spelled out, new RDA rule citations, etc
.

IR.8.2

Updating loose
-
leafs: This section sho
uld be updated in light of RDA 3.4.1.10,
RDA
3.4.5.2, and
RDA
3.4.5.19 (
previously
discussed in
Section 3.2

Loose
-
leafs
)
.


IR.8.2.2

Electronic resources: The instruction for remote online resources (RDA 3.4) is
the
only major change
.
A statement of extent for these resources is now required
.
Current
CONSER St
andard
R
ecord policy requires a statement of extent (300 $a) only for tangible
resources
.

New bibliographic fields have recently been added to the MARC 21 format, but not yet implemented
by LC, PCC, or OCLC: 344
-
347, for
s
ound, projection, video, and digital file characteristics
.
Once
these fields are implemented,
they should be included in

so
me of
the
examples.


IR.9 Series statements and series access poin
ts

Proposed reorganization
: RDA IR.2.5 Series statement
.
Series access points (8XX fields) should be
covered in a section of RDA IR.7 Recording relationships between
w
ork
s
,
e
xpression
s
,
m
ani
festation
s
, and
i
tem
s

(WEMI)
.
Exceptionally, both series statements and series access points can
be treated in the same chapter, with a reference from RDA IR.7
.

This chapter does not require any changes aside from the general changes described in

Section 5.
1

Other general and miscellaneous changes needed in the IR manual
.

The RDA/LCPS treatment of series statements and authorized access points for series
is

generally the
same for all resources, regardless of mode of issuance.

The most relevant instructions are RDA/LCPS 2.12 Series statement,
R
DA/LCPS 24.6 Numbering of
part
, and RDA 25.1.1.3 Referencing related works.

23


The addition of one or two examples of se
ries statements and authorized series access points for
numbered series would be helpful.

Due to MARC 21 changes, examples can now include a series statement (490 field) with two $x, one
for the ISSN of main series, and one for the ISSN of subseries
.
Exam
ples can also include the ISSN
in 8XX series fields.


IR.10 Notes and electronic location and access

Proposed reorganization
: RDA IR2.6 Note
.
Not all notes describe the manifestation
. Notes relating
to content
would be covered in RDA IR.6. If it seems better to cover all notes in
the same chapter or
sub
-
chapter, then all notes c
an

be discussed in RDA IR 2.6

or moved to a separate chapter, outside
of RDA IR2 entirely.


Notes are main
ly covered under RDA 2.20, but

are also included in RDA
C
hapter 2, RDA
C
hapter 7,
and other chapters
.

IR10.1

Overview:
N
otes are not
a
core

element

in RDA.

IR.10.1.3

Order of
5XX notes (RDA D.1.1 Order of e
lements)

IR.10.2

Frequency of updates (RDA 2.14 Freq
uency and RDA 2.20.12 Note o
n f
requency)

IR.10.3

Language of text (RDA 7.12 Language of
content, RDA 6.11 Language of
e
xpression)

IR.10.4:

Source of title proper (See RDA 2.20.2.3 Title Source)
.
Note the optional omission
if there is only a single title and the title is on the
resource itself (although LC practice is not
to exercise this option)
.
Make a clear reference here to RDA 2.20.13 Note on
issue, part, or
iteration used as the basis for identification of the resource
, as well as to RDA 2.20.13.5 Date
of
viewing of an onl
ine resource
, and give examples of combined notes.

IR.10.5

Titles other than title proper (RDA 2.20.2.4 Title
v
ariations,
inaccuracies, and
deletions
)
.
IR.10 should only cover notes (5XX) about title variations
. I
nstructions for
constructing
the
246
fiel
d

(RDA 2.3.6, etc.) would be more appropriate in IR.4 (Proposed
RDA IR2.2 Title and
statement of responsibility
).

IR.10.6

Changes in title proper (RDA 2.3; particularly 2.3.2.12.3 Integrating resources)
.
Confine this section to notes and move the discussi
on on IR title changes to RDA IR.2.2 Title
and
s
tatement of responsibility
.

IR.10.7

Parallel titles and changes to parallel titles (RDA 2.3; particularly
RDA
2.3.3.5.3

Integrating resources)

IR.10.8
Other title information and changes in other title inform
ation (RDA 2.20.2.5: Other
information relating to a title
; RDA 2.3, particularly

RDA

2.3.4.7.3 Integrating resources)

24


IR.10.9
Statements of responsibility or issuing bodies and changes in that information (RDA
2.20.3 Note on
statement of responsibility
; p
articularly
RDA
2.20.3.6.3 Integrating resources)

IR.10.10

Edition statement (RDA 2.20.4 Note on
edition statement
; particularly
RDA
2.20.4.5.3 Integrating resources)

IR.10.11

Dates of production (RDA 2.7.6.5),
publication (
RDA

2.8.6.5), distribution (
RDA
2.9.6.5), and manufacture

(
RDA
2.10.6.5) for
multipart monographs, serials, and integrating
resources
.
Provide an explanation on t
he distinction between these date types in RDA
and

AACR2
.
D
ates of production
are seldom

relevant for an IR
.

RDA 2.20.10 N
ote on
copyright d
ate
,

and RDA 2
.11.1 Copyright d
ate
,

can be discussed here as well.

IR.10.12

Publication, distribution, etc., information: see
RDA
2.20.6 Note on
production
statement
(particularly
RDA 2.20
.6.4.3 Integrating resources),
RDA 2.20
.7 Note on
publication statement
(particularly
RDA 2.20
.7.5.3 Integrating resources),
RDA 2.20
.8 Note
on
distribution statement
(particularly
RDA 2.20
.8.4.3 Integrating resources),
RDA 2.20
.9
Note on
manufacture statement
(particularly
RDA 2.20
.9.4.3 Integrating reso
urces)
.
The
distinction between production, publication, distribution, and manufacture are different
in

AACR2.

IR.10.13

Physi
cal description (RDA Chapter 3 D
escribing carriers, RDA Chapter 7
D
escribing content)

IR.10.14

Accompanyi
ng material (RDA Chapter
25 R
elated works)

IR.10.15

Audience (RDA 7.7 Intende
d a
udience)

IR.10.16

Other formats (RDA 27.1 Related
m
anifestation)

IR.10.17

In
dexes (RDA 7.16 Supplementary c
ontent)

IR.10.18

Summary (
RDA 7.10 Summarization of the c
ontent)

IR.10.19

Description based on (RDA 2.20.13
)
: Note on
issue, part, or iteration used as the
basis for identification of the resource
; particularly
RDA
2.20.13.4 Iteration
used as the basis
for the identification of an integrating resource
and
RDA
2.20.13.5 Date of
viewing of an
online resource
)

IR.10.20

Type of computer file or data (RDA 3.1
9.2 File t
ype, as well as possibly
RDA
3.19.3 Encoding format and
RDA
3.19.4 File size)

IR.10.21

Electronic location and access
:

In RDA
,


The scope [of electronic location and
access] has been limited to the location of the resource.



Refer to RDA 4.6 for
the
URI (856
$u)
.
Suggested location in IR manual: RDA IR.4

Providing acquisition and access
information
.


25


IR.11 Relationships to other resources


Proposed reorganization
:
RDA IR.7 Recording relatio
nships between entities:
w
orks,
e
xpression
s
,
m
anifestations, and
i
tem
s
.

General
c
hanges:

As further enumerated under

Section 5.1
, AACR2 terminology needs to be
changed to RDA terminology, and
FRBR concepts need to be incorporated throughout the chapter
.
References to AACR2 rules and LCRIs need to be changed to references to RDA instructions and
LCPSs.

IR.11.1

Overview: This section should enumerate the four methods
outlined by

RDA for
recordin
g

relationships (RDA 24.4.1
-
24.4.3)
. Also, provide

basic information about
relationship designators (
RDA
24.5, Appendix J for WEMI relationships)
.

Added entries: Unlike AACR2,
supplying

authorized access points in RDA for related
works/expressions is opti
onal in all cases
.
The actual situations listed in IR.11.1 can remain
in the manual.

Linking entries: This section is fine for now
.
It is unknown at this point whether LC/PCC
will adopt requirements or best practices on
the

use of
l
inking entries, rather

than/instead of
the other methods enumerated for expressing relationships given in RDA 24.4.

IR.11.2

Fields for l
inking entries: The last paragraph on use of 787 fields should be expanded
to encourage the use of $i
, to give more precise information on the

nature of the relationship
(when available).

Chart: This chart needs to be redone, referencing FRBR categories and using FRBR and RDA
terminology
.

IR.11.3

Form of note in linking entry field: RDA instructions call for the differentiation of
preferred acce
ss points for two works with the same preferred title
.
Ensure that
the
reference
to CSR practice is still valid (non
-
creation of

uniform titles


in selected cases).

Examples:

1st two examples for use of 780/785 are for 2 different expressions for the
same work
.
It would be useful to add another set of examples for two
successive
editions of related
works
that also have a

780/785 relationship
.


IR.12 Determining main and added entries


Proposed reorganization:

This chapter along with IR.13 should be co
mbined into RDA IR.5
Identifying works and expressions.

The content here is basically fine
.
The changes described in
Section 5.1

need to be made here.


26


IR.13 Uniform titles


Proposed reorganization:

This chapter along with IR.12
should

be combined into
RDA

IR.5
Identifying works and expressions.

The changes described in

Section 5.1

also need to be made here.

IR.13.1
: CSR practice
.
It is unknown at this time wheth
er CSR practice will change, as it is
fundamentally at odds with RDA in not requiring differentiating “uniform titles” in many cases.

IR.13.2
: RDA (and also LC practice) require
s

that the authorized access points for all works and
expressions be differentiated from each other
.
The guidelines for qualifiers (chiefly RDA/LCPS
6.27.1.9) are for the most part carried over from LCRI 25.5B.


IR.14 Fixed field coding


Proposed reorganiz
ation
: RDA IR.9

Fixed field coding
.
The Task Group as a whole doesn’t have
strong preferences where this information should be integrated into a
n

RDA version of the IR manual
.
But it seems best to retain it in a separate chapter, since fixed field coding

covers several aspects of
bibliographic resources and all the WEMI entities
.
A
dd

“see also


references

from other chapters to
the fixed field information in this chapter
.

There are no changes needed for 006/008 fixed length data elements coding
.
Add a n
ew section for
Desc 008/18 (i.e., a=AACR2, i=rda)
.

The 007 physical description field is closely correlated with
the RDA
core
fields 336
-
338 (content,
media,
and carrier

type)
.

Record examples here could include 336
-
338 fields and/or references could
be
made between the section on 007 coding and the section in the new RDA IR.3 on describing
carriers, as well as RDA IR.6 on describing content (which presumably would have a section on
content types)
.

Some examples may need updating
.
CSR examples in light o
f RDA will need to be reassessed (e.g.,
IR.14.7 008 Dates).


IR.15 Subj
ect analysis and classification

Proposed reorganization
: RDA IR.10

Subject analysis and classification
.

The manual could include these guidelines from RDA 0.6.7

Recording
subject
relationships

:


When recording relationships between a work and an entity that is the subject of that work,
include as a minimum at least one subject relationship element. When using an access point to
represent the subject entity, the access point may be

formulated using either the preferred name,
title, or term for the entity, or a classification number representing the entity. Formulate the
access point representing the subject entity following the standards for subject access points and
classification
numbers used by the agency creating the data
.”

27


However, RDA Chapter 23
(
General guidelines on recording the subject of a work, and related
C
hapters 33
-
37
)

ha
s

not yet been released
.
No substantive changes need to be made to the IR section
on subjects at t
his time.

IR.15.3.1:

This section on form subdivisions and genre/form terms seems fine as well.


IR.16 How many bibliographic records
?


Proposed reorganization
: RDA IR.11

How many bibliographic records?

The changes in

Section 5.1

will need to be made here.

IR.16.1
: The situations requiring new bibliographic records should refer to RDA 1.6.3 and
AACR2 rules replaced by corresponding RDA and LCPS instructions
.
The examples in this
section will require slight modification
.

IR.16.2
:

The text from LCRI 12.0 (first two paragraphs of IR.16.2) should be removed and/or
replaced with the slightly different text in LCPS 0.0 under:
Determining number of records:
l
oose
-
leaf services
.
The remainder of that section applies.

The text
of the LCPS is very similar to the LCRI, but there has been one significant change in
policy, which requires a change in IR.16.2.1
.
Pamphlets/paperbacks, 2nd paragraph, last
sentence
.
LCPS 0.0 allows the cataloger to include a note and authorized access
point in the
bibliographic record for the pamphlet/paperback indicating a relationship to the service
.

IR.16.3.1
: Last paragraph
:


OCLC Online Data Quality Control Section


is now

OCLC
Quality Control Section.


The duplicate record form is now called

WorldCat and Authority
Record Quality Control Request


and can now be found here:
https://www.oclc.org/forms/record
-
quality.en.html

The current link no longer works.

IR.16.3.2
: Selecting re
cord
s

to retain remains the same with the exception of

choose the
record that most adheres most closely to AACR2
.


IR.16.3.3
: No changes
.


IR.17 Full record examples


Proposed reorganization
: RDA IR.13

Full record examples.

The Task Group recommends
providing full record examples of AACR2/RDA hybrid records and
new record examples cataloged using RDA guidelines only
.
One or two AACR2
-
only records can
also be included
.
The variety of records will be useful for identification and highlighting core
ele
ments
.
The current full record examples can be edited to illustrate AACR2/RDA hybrids
.




28


Section 6:
Appendices

Section 6.1
Appendix A: RDA
implementation dependencies


The recommendations and practices in the report do not suggest changes to be made to R
DA or to LC
policies.

1.

Revision of Integrating Resources Manual (BIBCO Participants


Manual Appendix A/CONSER
Cataloging Manual Module 35) to include RDA
-
related concepts

a.

Steps needed:
Section 5

of this report suggests both general changes and section
-
by
-
section changes to be considered, in order to address RDA concepts

i.

Constitute a Task Group to revise the Manual; charge the Task Group and
establish a deadline for completion

ii.

Submit the completed

draft manual to the Standing Committee

iii.

Submit the draft manual to the PCC Steering Committee for approval for review

iv.

Distribute the draft for comment to CONSER and BIBCO communities

v.

Revise the draft as necessary

vi.

Post the final version to the PCC Web site

and

include it in CONSER
and

BIBCO documentation, as well as Cataloger

s Desktop

vii.

Format the Manual
with hyperlinks

t
hat refer t
o the RDA Toolkit
; also i
nclude

a
link to the Manual o
n

the Resources tab of the RDA Toolkit

b.

Responsibility: The PCC Standing
Committee on Standards is responsible for initiating a
task group to review the Manual

c.

Time frame: If volunteers could be found, a task group could be initiated after the reports
of the “Decisions Needed” groups have been accepted in June.

Considering how

recently
the Manual has been revised, though, and the focus on basic training in the fall 2012 and
winter 2013, a more reasonable time frame for revision might be spring/summer 2013.

d.

Other dependencies: Additional changes related to integrating resources
may emerge
from discussion of the reports of PCC “Decision
s

Needed” task groups and from
revisions proposed to the JSC


2.

Revision of the SCCTP Integrating Resources Workshop

a.

Steps needed:

i.

Constitute a Task Group to revise the Manual; charge the Task Group
and establish a
deadline for completion

ii.

Determine whether to reconsider the general organization/purpose of the sessions or to
revise for RDA
-
related changes.

If the latter, then…

iii.

Identify types of changes needed.

A process similar to that used by this T
G should be
followed, to identify categories of changes to apply to the SCCTP workshop.

Categories
should include:

a)

Use of RDA, FRBR, FRAD terminology (where appropriate)

b)

Review of examples for abbreviations, fiel
ds, and subfields (e.g., 245 $h)

c)

Instructio
n and examples for new fields (e.g., 336
-
338)

29


iv.

Screen
-
by
-
screen, f
ield
-
by
-
field review of sessions 3, 4, 5, and 6.

Discussion in sessions
4
-
5 of how to modify pre
-
RDA copy

v.

Submit the completed draft manual to the Standing Committee on Training

vi.

Submit the
draft manual to the PCC Steering Committee for approval for review

vii.

Revise the draft as necessary

viii.

Post the final version to the CLW Web site/SCCTP Trainers’ Web site and schedule
train
-
the
-
trainers sessions

b.

Responsibility: The PCC Standing Committee on Trai
ning is responsible for initiating a task
group to review the workshop

c.

Time frame: To call for volunteers either at the May 2013 Operations Committee
M
eeting or
at the 2013 ALA Annual Meeting.

Work to be completed by fall 2013

d.

Other dependencies:

i.

Deliver
y of RDA training for PCC members and the review for NACO work should be
completed before the SCCTP workshops can be revised, to avoid overload

ii.

Review of the IR Manual should be completed before the SCCTP workshop is revised


Section 6.2
Appendix B:
Revision of PCC RDA Frequently Asked Questions


The Task Group suggests

revisions to the following FAQs:

3.
1
In a hybrid record as described in 2.5 above, won’t it be difficult to code the correct
“descriptive cataloging rules?”

The
Final report

[PDF: 406 KB; 36 p.] of the
PCC TG on Hybrid Bibliographic Records

provides
guidelines for catalogers who wish to add a l
imited set of

newly defined MARC 21 fields and
codes to existing or new AACR2 records during the transition from AACR2 to RDA.

The
practice is limited to 336, 337, 338, and relationship designators.


The guidelines aim to strike a
balance between allowing

catalogers to make use of the new fields in both AACR2 and RDA
records and the need to maintain record integrity and identification of the descriptive rules used to
create the record.

For integrating resource records, the Final Report of the PCC TG on Hy
brid
Integrating Resource Records may also be consulted.

3.2

How will we know when a record crosses the line from AACR2 to RDA?



The guidelines provided in the
Final report

[PDF: 40
6 KB; 36 p.] of the
PCC TG on Hybrid
Bibliographic Records

place limits on the new MARC 21 fields that can be added to an existing
AACR2 record.

The coding of the descriptive cataloging
rules will identify the record as AACR2
or RDA.


For integrating resource records, the Final Report of the PCC TG on Hybrid
Integrating Resource Records may also be consulted.

3.3

Can RDA elements, such as 33X fields, be added now to existing PCC AACR2
bibliographic records?

The
Final report

[PDF: 406 KB; 36 p.] of the
PCC TG on Hybrid Bibliographic Records

provides
guidelines for adding new MARC 21 fields (i.e., 336, 337, 338, and relationship designators) to
AACR2 bibliographic records as long as the bibliographic integrity/identity is not
affected.

Once
30


the guidelines are posted on the PCC website
,

33X fields may be added to existing PCC AACR2
bibliographic records.


For integrating resource records, the Final Report of the PCC TG on
Hybrid Integrating Resource Records may also be consulte
d.

3.4 Should AACR2 PCC records be re
-
cataloged to RDA?

During this interim period, the PCC recommends that AACR2 PCC records generally not be re
-
cataloged to RDA.

The PCC endorses the exceptions detailed in OCLC’s RDA policy statement.

The Final report [
PDF: 406 KB; 36 p.] of the PCC TG on Hybrid Bibliographic Records also
supports generally not recataloging AACR2 records to RDA.

The group’s recommendations
provide the option to redescribe a non
-
PCC AACR2 record to RDA when first authenticating the
recor
d as PCC.

In these cases, the record should be completely converted to RDA and labeled as
RDA in both the Leader/18 (DESC) and 040 $e to make clear the integrity of the record.

However, fo
r integrating resource records,
the Final Report of the PCC TG on
Hybrid
Integrating Resource Records recommends redescribing to RDA whenever the latest iteration of
the resource is available.

To

follow
up
,

the RDA Post
-
Implementation Guidelines TG has been formed to develop best
practices to be followed after RDA implem
entation and protocols for machine or batch editing to
accomplish addition or deletion of elements on a large scale.