[DCRB-L] Fwd: AACR2 and MARC
Deborah J. Leslie
dcrb-l@lib.byu.edu
Thu, 16 Jan 2003 14:46:45 -0500
This is a multi-part message in MIME format.
------_=_NextPart_001_01C2BD98.001FEFF4
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I completely agree that examples in DCRM should be encoded in MARC. =
--DJL
-----Original Message-----
From: Jane Gillis [mailto:jane.gillis@yale.edu]=20
Sent: Thursday, January 16, 2003 11:59 AM
To: dcrb-l@lib.byu.edu
Subject: [DCRB-L] Fwd: AACR2 and MARC
I am forwarding this message from Autocat because Gordon Pew makes an =
excellent point on why examples in AACR2 (and other codes, I would add) =
need to be in the MARC format. I think this has been discussed in Bib =
Standards. I hope we take this advice in formulating the DCRM chapters.
Jane
Date: Thu, 16 Jan 2003 10:37:06 -0600
Reply-To: AUTOCAT <AUTOCAT@LISTSERV.BUFFALO.EDU>,
Gordon Pew <gpew@law.harvard.edu>
Sender: AUTOCAT <AUTOCAT@LISTSERV.BUFFALO.EDU>
From: Gordon Pew <gpew@law.harvard.edu>
Subject: AACR2 and MARC
To: AUTOCAT@LISTSERV.BUFFALO.EDU
X-YaleITSMailFilter: Version 1.0c (attachment(s) not renamed)
In replying to the thread about how to record a reprint date, Mac Elrod
commented, "Some decade I hope we will have the examples in AACR2 given
with MARC coding". I couldn't agree more. It has often been noted on
this list that AACR2 is a cataloging code that is supposed to be
communications-format neutral. It is designed to serve catalogers who =
use
every kind of carrier from typed-up cards to integrated library systems:
and, as presently constituted, it is for use by libraries employing
USMARC, UKMARC, CANMARC, Australian MARC (or their successors), and
probably others.
Increasingly, however, national standards are moving toward =
harmonization,
and non-Anglo-American schemes are being studied for harmonization as =
well
(e.g., the German RAK, IIRC). Increasingly, also, technology has =
allowed
the automation of some of the smallest libraries. These developments
argue for the admission by the code-writers that the great majority of
libraries interpret AACR2 through the MARC format. There are some =
things
in AACR2 that I find very cumbersome to place within the MARC format.
One of the latest developments, the accommodation of earlier and current
imprints for looseleafs and other integrating resources, is a case in
point. In AACR2, the provision of this information is made by notes: in
the MARC format, the information is carried (or will be) in repeating =
260
fields. In AACR2, 2002 revision, this is explained in 12.4 et seq., =
where
one is instructed to use notes for earlier publishing information. You
must know the MARC format in order to know that you should enter earlier
place and publisher in a second 260 field: and your automated system may
or may not generate a note in the bibliographic record. If it doesn't,
you must add one manually.
If "they" won't take the steps necessary to make the correlation between
AACR2 and the MARC format, perhaps it is time for someone else to create =
a
work that will provide this vital service for catalogers -- especially =
in
a time when professional catalogers seem, literally, to be a dying =
breed.
(And don't even get me started on the complications caused by the =
LCRIs!)
Gordon Pew
Head of Copy Cataloging and Database Management
Harvard Law School Library
164 Langdell Hall
1545 Massachusetts Avenue
Cambridge, Mass. 02138
gpew@law.harvard.edu
(617) 495-4487=20
Jane Gillis | Rare Book Cataloger| Sterling Memorial Library
Yale University | New Haven CT 06520
(203)432-8383 (voice) | (203)432-7231 (fax) | jane.gillis@yale.edu
------_=_NextPart_001_01C2BD98.001FEFF4
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>Message</TITLE>
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D750134619-16012003><FONT face=3DGeorgia =
color=3D#000080>I=20
completely agree that examples in DCRM should be encoded in MARC.=20
--DJL</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> Jane =
Gillis=20
[mailto:jane.gillis@yale.edu] <BR><B>Sent:</B> Thursday, January 16, =
2003=20
11:59 AM<BR><B>To:</B> dcrb-l@lib.byu.edu<BR><B>Subject:</B> [DCRB-L] =
Fwd:=20
AACR2 and MARC<BR><BR></FONT></DIV><FONT size=3D3>I am forwarding this =
message=20
from Autocat because Gordon Pew makes an excellent point on why =
examples in=20
AACR2 (and other codes, I would add) need to be in the MARC =
format. I=20
think this has been discussed in Bib Standards. I hope we take =
this=20
advice in formulating the DCRM chapters.<BR><BR>Jane<BR><BR><BR>
<BLOCKQUOTE class=3Dcite cite=3D""=20
type=3D"cite">Date: =
Thu, 16=20
Jan 2003 10:37:06 -0600<BR>Reply-To: AUTOCAT=20
<AUTOCAT@LISTSERV.BUFFALO.EDU>,<BR> Gordon Pew=20
<gpew@law.harvard.edu><BR>Sender: AUTOCAT=20
<AUTOCAT@LISTSERV.BUFFALO.EDU><BR>From: Gordon Pew=20
<gpew@law.harvard.edu><BR>Subject: AACR2 and MARC<BR>To:=20
AUTOCAT@LISTSERV.BUFFALO.EDU<BR>X-YaleITSMailFilter: Version 1.0c=20
(attachment(s) not renamed)<BR><BR>In replying to the thread about =
how to=20
record a reprint date, Mac Elrod<BR>commented, "Some decade I hope =
we will=20
have the examples in AACR2 given<BR>with MARC coding". I =
couldn't=20
agree more. It has often been noted on<BR>this list that AACR2 =
is a=20
cataloging code that is supposed to be<BR>communications-format=20
neutral. It is designed to serve catalogers who use<BR>every =
kind of=20
carrier from typed-up cards to integrated library systems:<BR>and, =
as=20
presently constituted, it is for use by libraries =
employing<BR>USMARC,=20
UKMARC, CANMARC, Australian MARC (or their successors), =
and<BR>probably=20
others.<BR><BR>Increasingly, however, national standards are moving =
toward=20
harmonization,<BR>and non-Anglo-American schemes are being studied =
for=20
harmonization as well<BR>(e.g., the German RAK, IIRC). =
Increasingly,=20
also, technology has allowed<BR>the automation of some of the =
smallest=20
libraries. These developments<BR>argue for the admission by =
the=20
code-writers that the great majority of<BR>libraries interpret AACR2 =
through=20
the MARC format. There are some things<BR>in AACR2 that I find =
very=20
cumbersome to place within the MARC format.<BR>One of the latest=20
developments, the accommodation of earlier and current<BR>imprints =
for=20
looseleafs and other integrating resources, is a case =
in<BR>point. In=20
AACR2, the provision of this information is made by notes: in<BR>the =
MARC=20
format, the information is carried (or will be) in repeating=20
260<BR>fields. In AACR2, 2002 revision, this is explained in =
12.4 et=20
seq., where<BR>one is instructed to use notes for earlier publishing =
information. You<BR>must know the MARC format in order to know =
that=20
you should enter earlier<BR>place and publisher in a second 260 =
field: and=20
your automated system may<BR>or may not generate a note in the =
bibliographic=20
record. If it doesn't,<BR>you must add one manually.<BR><BR>If =
"they"=20
won't take the steps necessary to make the correlation =
between<BR>AACR2 and=20
the MARC format, perhaps it is time for someone else to create =
a<BR>work=20
that will provide this vital service for catalogers -- especially =
in<BR>a=20
time when professional catalogers seem, literally, to be a dying=20
breed.<BR>(And don't even get me started on the complications caused =
by the=20
LCRIs!)<BR><BR>Gordon Pew<BR>Head of Copy Cataloging and Database=20
Management<BR>Harvard Law School Library<BR>164 Langdell =
Hall<BR>1545=20
Massachusetts Avenue<BR>Cambridge, Mass.=20
02138<BR>gpew@law.harvard.edu<BR>(617) 495-4487 =
</BLOCKQUOTE><X-SIGSEP>
<P></X-SIGSEP>Jane Gillis | Rare Book Cataloger| Sterling =
Memorial=20
Library<BR>Yale University | New Haven CT 06520<BR>(203)432-8383 =
(voice)=20
| (203)432-7231 (fax) |=20
jane.gillis@yale.edu<BR></FONT></P></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C2BD98.001FEFF4--