I agree that putting RDA into MARC feels like putting it in a straight jacket, but that is what we're going to have to do until a replacement comes along. I did my examples in both templates, but found it useful to put it into MARC after I'd completed the RDA template because that is going to be the reality soon. However, I think that using MARC stops me thinking more theoretically about RDA because of MARC's limitations, and I can't decide if that's a good thing (taking a short term view) or a bad thing (looking forward to the future of RDA outside MARC).
Nicky Ransom
Data Quality Manager & Cataloguer
University for the Creative Arts
Farnham
________________________________________
From: CIG E-Forum [[log in to unmask]] on behalf of Jenny Wright [[log in to unmask]]
Sent: 25 October 2012 14:15
To: [log in to unmask]
Subject: Re: [CIG-E-FORUM] CIG-E-FORUM Digest - 25 Oct 2012 - Series
I agree with Helen that MARC is, in so many ways, just not adequate to
deal with RDA (and I've just seen Celine's comment come in on same).
However, I'm consoling myself that it allows us to take relatively baby
steps of change, since RDA in MARC is not so radically different from
AACR2 in MARC - and one day we can move to RDA in SUPERFORMAT, and we'll
all feel a lot more comfortable with RDA by then
Yours optimistically
Jenny Wright
Development Manager
Bibliographic Data Services Ltd.
-----Original Message-----
From: CIG E-Forum [mailto:[log in to unmask]] On Behalf Of Helen
Doyle
Sent: 25 October 2012 13:55
To: [log in to unmask]
Subject: Re: [CIG-E-FORUM] CIG-E-FORUM Digest - 25 Oct 2012 - Series
Musings over lunch:
I'm struck more and more by the fact that RDA thinks very differently
from the way in which MARC works. RDA feels like a huge bubble of
related information, which you can approach from almost any angle and
navigate around (very 3D), whilst MARC works in a much more rigid,
linear, prescribed fashion.
A bit like being given a recipe that allows you to bake every type of
cake under the sun, with options for fancy icing and jam, then finding
you have only a war-time ration to work with. (Maybe a tad extreme
there, but best I can come up with!).
We're trying to force RDA concepts into the strait-jacket that is MARC,
because there's currently no other choice. I really like ideas such as
"there may be other types of relationship between the specific volumes
of a series that you need to bring out", but MARC is too linear to
properly capture this. I want to link to everything possible in order to
show the user how much related stuff there is out there, but then I
remember I have to use MARC to encode it all and most of my ideas have
to go.
Anyway, just a thought.
HelenD.
Helen Doyle
Assistant Librarian
Royal Academy of Dance
36 Battersea Square
London
SW11 3RA
0207 326 8032
>>> "Danskin, Alan" <[log in to unmask]> 10/25/2012 12:04 pm >>>
Series
In RDA you can transcribe what is actually on the source in the series
statement. In RDA you can even use sources outside the resource see
2.12.2.2
However you can make a relationship to the series as a whole. In MARC
this is what we do when we use an 830. In RDA this is a whole-part
relationship and it obviates the need to relate directly to other membrs
of the series.
Of course, there may be other types of relationship between the specific
volumes of a series that you need to bring out, for example if there was
a sequential relationship between the resource being catalogued and
another volume in the series, but not reflected by the series numbering.
These relationsbips can be mande using authorised access points, if you
have enough information, or using structured or unstructured
descriptions.
Alan
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
|