Re: [RDA-L] If we don't adopt RDA immediately
110 RDA change: Spell out Dept. (This was in AACR2 but not applied.) Spell it out IF the corporate body spells it out. If the agency uses an abbreviation such as Dept. in its name, the authorized access point would still be established with the abbreviated form. 111 RDA change: Give full name of conference as on item, e.g., Annual ... Again, this is an oversimplification. Frequency is retained, but not number or year in the name. The change is not to use the full name in the preferred name for the conference, it's to retain frequency in the preferred name. 7XX analytics RDA adds |icontains (work), or |icontains (expression) before |a. This may confuse patrons, and create split files; consider not assigning and supression in display. Actually, these designators do not need to be used at all in MARC records, because the second indicator value of 2 in the 7XX MARC tag already conveys the information about the relationship. 245|c RDA change: may transcribe all authors, regardless of number, but may transcribe fewer followed by [and # others]. In the case of a compilation with supplied title, transcribe statements of responsibilities after titles in 505. Transcribe degrees, titles, Jr., Rev., the late, etc.; but not Dame nor Sir. I don't know why you say not Dame nor Sir. Statements of responsibility are transcribed as they appear. The instruction 2.4.1.4 says Transcribe a statement of responsibility in the form in which it appears on the source of information. And one of the examples given there is: by Sir Richard Acland 250 RDA change: transcribe rather than abbreviate, e.g., 250 |aSecond edition. Only use abbreviations if in the item. This result in the unacceptable to some double period after an abbreviation, e.g., ed.. What you say here is correct, but somewhere else I saw that you were going to convert the AACR2 2nd ed. to Second edition. This presumes that the resource says Second on it, when it may very well say 2nd. I wouldn't feel comfortable converting the ordinal number to its spelled out form. 260 RDA change: Transcribe all places of publication in repeating |a; transcribe full names of publishers. RDA moves needed jurisdiction to 500, as opposed to bracketed in 260|a. Only the first named place is required. Bracket adjacent element in the same field, e.g., 260 |a[S.l. :|b[s.n.],|c[2010?]. In MARC, there is no period at the end of the 260 field if it ends in a bracket. *RDA directs that the copyright sign be used, or copyright be spelled out, rather than c. Also the phonogram copyright symbol (P) is used rather than p. 300 Abbreviations such as p., v., ill., spelled out; cm without period considered a symbol, not an abbreviation; in. still allowed. The principle here is that measurements (in., min., rpm) will still be abbreviated. Metric symbols such as cm, m, km, etc. do not include a period after them unless the field ends in a period. 490|v RDA change: Transcribe as found rather than abbreviate, e.g., |vvolume ... Well not completely as found. All uppercase could be transcribed as all lowercase, for example. 600 RDA change: Includes all personal names, e.g., fictitious persons, God. It does not include RDA family names (which are coded as personal names). LC policy is that these may not be used as subjects, only as 100 and 700 access points. For subjects, LCSH policy is to use a more general/generic family name heading from the subject authority file. 700 RDA change: *May* trace all authors as opposed to only 2nd and 3rd, but only first, translator of poety, illustrator of children's material required. The |erelation designator was not assigned during the test period. It may not have been assigned by LC, but it certainly was used by other testers. ** * Adam L. Schiff * * Principal Cataloger* * University of Washington Libraries * * Box 352900 * * Seattle, WA 98195-2900 * * (206) 543-8409 * * (206) 685-8782 fax * * asch...@u.washington.edu * **
Re: [RDA-L] If we don't adopt RDA immediately
Steven Arakawa said:
RDA records in MARC format are largely compatible with AACR2 records;
it really isn't necessary to recatalog an RDA record to AACR2 at the
local level.
No matter how desirable it may seem to do so, the level of work
envolved if/when most of your derives are RDA prohibits editing all
RDA records to AACR2.
Once you've changed your local Bible/Korean headings (not a very large
part of most databases), all you *must* cope with is the absense of
GMDs in nonbook materials. Our plan is to export [338 : 336] (except
[volume : text]) as 245$h, until clients tell us they are prepared
to either display those two terms at end of title proper, or at head
of other data. After collaltion is too late.
If icons are used instead, they will probably be based in fixed
fields.
Changes should be automated, not done by hand. An exception might be
replacing those long phrases used rather than S.l., s.n., and
estimated dates in 300, for ISBD inclusions which do not eat up so
much display space, particularly on a hand held electronic device.
One hopes they will be few enough of those, it will not be too heavy a
copy cataloguing burden.
__ __ J. McRee (Mac) Elrod (m...@slc.bc.ca)
{__ | / Special Libraries Cataloguing HTTP://www.slc.bc.ca/
___} |__ \__
Re: [RDA-L] If we don't adopt RDA immediately
Here is a more detailed list of AACR2/RDA differences.
-
Most changes are to choice of entry, or to description, not form of
entry.
-
The few changes to form of entry:
100/600/700 RDA change: More frequent use of |c identifier such as
occupation to create unique heading.
100/600/700|d LC RDA practice: Use hyphen before death date, hyphen after
birth date, but no b., d,; active replaces AACR2 fl. and RDA
florished. The use of active is no longer limited to pre 20th
century authors.
100/110/700/710 RDA change: addition of |e relators, e.g., |eauthor.
(This affects bibliographic records, not authorities.) This however
was not done during the test period.
110 RDA change: Spell our Dept. (This was in AACR2 but not
applied.) Remove |k uniform title for treaty entries.
111 RDA change: Give full name of conference as on item, e.g.,
Annual ...
130 RDA change: |pO.T. and |pN.T. removed from between Bible
and |p name of the individual books. For the whole Old and New
Testaments, spelled out. Qur'an replaces koran.
For 240 see Descriptive changes ...
7XX analytics
RDA adds |icontains (work), or |icontains (expression) before |a.
This may confuse patrons, and create split files; consider not
assigning and supression in display.
-
Changes in choice of entry:
100 RDA change: entry under first author, regardless of number. Cf.
245|c.
110 RDA change: Treaties are entered under the first country
mentioned, regardless of number or alphabetical order; or in the case
of a treaty between one country and a group of countries, under
the one country.
-
Descriptive changes are more numerous:
040|beng or |bfre; RDA change: 040|erda. (LAC already uses 040|b language
of cataloguing).
240 Uniform title after 1XX
RDA change: Under AACR2 (25.9) one uses Selections as collective
title for three or more various works by someone; under RDA one uses
Works. Selections. This comes into play with *two* or more works.
The order of the pieces for the uniform title Short stories. Spanish.
Selections is explicitly described in AACR2 (25.11). In RDA there
seems to be no similar explicit instruction. it might be Short
stories. Selections. Spanish. Under RDA, only one language is
allowed in the |l of a uniform title--no dual languages with
ampersand, no Polyglot for three or more languages.
2XX
RDA change: Use square brackets only for information not found in the
item, regardless of source within the item.
RDA change: [sic], or bracketed additional letters, no longer used
after typos. Create 246 with corrected title spellings.
RDA change: No longer add defining word to ambiguous title, e.g.,
:|b[poems], :|b[proceedings{.
RDA change: Transcribe punctuation as found, e.g., ..., but add ISBD
punctuation.
245 |b
RDA change: Other title information not a core element.
245|h [gmd]
RDA change: no longer used. SEE 336-338 below.
245|c RDA change: may transcribe all authors, regardless of number,
but may transcribe fewer followed by [and # others]. In the case of a
compilation with supplied title, transcribe statements of
responsibilities after titles in 505. Transcribe degrees, titles,
Jr., Rev., the late, etc.; but not Dame nor Sir.
*There is no required correlation between authors transcribed in 245,
500, 505, 508, or 511 and traced authors, i.e. one may have untraced
authors in the description, and unjustified author added entries.*
RDA change: A noun phrase *associated* with the author is included in
|c, e.g., 245 10 |aBurr /|ca novel by Gore Vidal, but 245 10 |aBurr
:|b a novel /|cGore Vidal.
250 RDA change: transcribe rather than abbreviate, e.g., 250 |aSecond
edition. Only use abbreviations if in the item. This result in the
unacceptable to some double period after an abbreviation, e.g., ed..
260 RDA change: Transcribe all places of publication in repeating |a;
transcribe full names of publishers. RDA moves needed jurisdiction
to 500, as opposed to bracketed in 260|a.
Bracket adjacent element in the same field, e.g., 260 |a[S.l.
:|b[s.n.],|c[2010?].
Fuller use of 250|e(|f|g) for manufacturing place, body, and date may
be seen in RDA records. This practice is not new.
RDA change: In the absence of a publication year, do not substitute
copyright year; instead of |cc2010, use |c[2010], c2010.* In the
absence of date of publication, and date of distribution or manufacturer is
known, use that date following |c, manufacturing date in |g. Name of
manufacturer need not be given if publisher is known, but not doing so
creates a strange display.
*RDA directs that the copyright sign be used, or copyright be spelled
out, rather than c.
Re: [RDA-L] If we don't adopt RDA immediately
Kathleen Lamantia asked:
If my institution does not buy/adopt RDA immediately thereafter, will we st=
ill be able to do original cataloging?
In answer to a question concerning reprospective change to legacy
records, OCLC informed me that they will leave AACR2 records as they
are, and continue to accept AACR2 records, since they regularly have
new libraries join OCLC, which load their legacy records.
But purchasing the RDA Toolkit or print version is not required to do
RDA compatible records. I'm sending you SLC's RDA cheat sheet.
Our experience is that the cheat sheet is far easier to comprehend
than RDA.
Since the records you are preparing do not require the display of an
alternative to GMDs, and are not Bibles or treaties, the differences
are not great. Needing to spell our all abbreviations not found in
the item is the major change.
This is assuming you rarely have a geneology prepared by more than
three people, which with AACR2 would be entered under title. With
RDA, it would be entered under the first author mentioned, and all
authors may be listed in 256/$c and traced.
__ __ J. McRee (Mac) Elrod (m...@slc.bc.ca)
{__ | / Special Libraries Cataloguing HTTP://www.slc.bc.ca/
___} |__ \__
Re: [RDA-L] If we don't adopt RDA immediately
Hello
What worries me is the existing OCLC policy
*If a record created according to either AACR2 or RDA already exists in
WorldCat, please do NOT create a duplicate record according to the other
code. Such duplicates are not within the scope of the OCLC policy on
parallel records and OCLC staff will merge them if found.
*When performing copy cataloging, catalogers may LOCALLY edit records
created under any rules to another set of rules.
So for those who don't have their IT departments on board to change to
RDA, the burden of stripping and redoing OCLC records from RDA to AACR2
in their local catalog is on the burden of each non-implementing
cataloging staff. The same will occur for those converting to RDA when
there is an AACR2 record.
Once this is done on a revised locally there is no way to share the
revised record. Every cataloging department all over the country will be
repeating the work which doesn't make sense.
I do not see that OCLC is supporting the needs of either the AACR2 or
RDA partner libraries under their current policy. Whichever format gets
the record in first will have the record in AACR2 or RDA. First come,
first served isn't the way a partnership shared database should work.
Ida Z. daRoza
San Mateo County Library
-Original Message-
From: Resource Description and Access / Resource Description and Access
[mailto:RDA-L@LISTSERV.LAC-BAC.GC.CA] On Behalf Of J. McRee Elrod
Sent: Thursday, February 17, 2011 8:31 AM
To: RDA-L@LISTSERV.LAC-BAC.GC.CA
Subject: Re: [RDA-L] If we don't adopt RDA immediately
Kathleen Lamantia asked:
If my institution does not buy/adopt RDA immediately thereafter, will
we st=
ill be able to do original cataloging?
In answer to a question concerning reprospective change to legacy
records, OCLC informed me that they will leave AACR2 records as they
are, and continue to accept AACR2 records, since they regularly have
new libraries join OCLC, which load their legacy records.
But purchasing the RDA Toolkit or print version is not required to do
RDA compatible records. I'm sending you SLC's RDA cheat sheet.
Our experience is that the cheat sheet is far easier to comprehend
than RDA.
Since the records you are preparing do not require the display of an
alternative to GMDs, and are not Bibles or treaties, the differences
are not great. Needing to spell our all abbreviations not found in
the item is the major change.
This is assuming you rarely have a geneology prepared by more than
three people, which with AACR2 would be entered under title. With
RDA, it would be entered under the first author mentioned, and all
authors may be listed in 256/$c and traced.
__ __ J. McRee (Mac) Elrod (m...@slc.bc.ca)
{__ | / Special Libraries Cataloguing HTTP://www.slc.bc.ca/
___} |__ \__
Re: [RDA-L] If we don't adopt RDA immediately
John Hostage said:
Bracket adjacent element in the same field, e.g., 260 |a[S.l.
:|b[s.n.],|c[2010?].
RDA does not use these abbreviations.
No. But ISBD does. Those long screen eating phrases will be separately
bracketed as shown. This is also an ISBD provision.
__ __ J. McRee (Mac) Elrod (m...@slc.bc.ca)
{__ | / Special Libraries Cataloguing HTTP://www.slc.bc.ca/
___} |__ \__
