That's pretty much how I see it too.  We have to work with what we've
got at present.  However even in MARC you can use $i to express a
relationship in an authorised access point


100 $a Tolkien, J.R.R.
245 $a The return of the king
700 $$i Sequel to$aTolkien, J.R.R. $tTwo towers

. - if your system supports it.  We are currently having some
difficulties with entering $i at the beginning of the 700 field in our
system and keeping it there...



________________________________

 	 	 Alan Danskin 
Metadata Standards Manager


The British Library
Bldg 25
Boston Spa
WETHERBY
West Yorkshire
LS23 7BQ

www.bl.uk

 	 	
T +44 (0) 1937 546669
Mob 07833401117
F +44 (0) 1937 546586
[log in to unmask]

________________________________

See how the British Library is transforming stored knowledge into smart
knowledge here


-----Original Message-----
From: Helen Doyle [mailto:[log in to unmask]] 
Sent: 25 October 2012 13:55
To: Danskin, Alan; [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