This is, at least as presented, a matter of markup. I'm not sure that
markup alone, or this markup in particular, solves the problem that
worries me the most, which is trying to get both display and access out
of one single set of data elements. I'm still unclear as to what we are
trying to accomplish, which should be decided before we determine HOW we
will accomplish it. Some people seem to be wanting to *describe* by
*transcribing*, others are concerned about *access*. Others have brought
up the problem of linking this title to the way that titles are treated
in authority records or in other products. Once the goals are determined
then there should be the possibility of creating one or more (and
hopefully more than one) solutions for coding those decisions. The
discussion seems to move directly into coding questions before goals are
clarified.
I also detect that some members of the list are unhappy with the
goals/decisions of RDA, which again is a topic apart from coding or
markup issues. What is the rationale for the RDA decision, and should
disagreement with that be the basis for formal comments to RDA?
kc
Jonathan Rochkind wrote:
This seems like a perfectly reasonable and good solution to me,
expressed clearly and well. I'm confused why the thread continues
after Adam's contribution, ignoring it, and discussing instead why
various other solutions are all unsatisfactory?
Jonathan
On Jun 29, 2007, at 4:11 PM, Adam L. Schiff wrote:
I think from our discussion on this matter is that RDA needs another
element to record what I will call the "linking word or term" in the
title. To have title proper and alternative title elements is not
enough,
because the linking word "or" and its equivalents in other
languages need
to be included in descriptions and it would be very complicated if not
impossible to have a machine supply the correct word in all cases.
Title proper: Twelfth night
Linking word or term: or
Alternative title: What you will
Title proper: Charles de Coster
Linking word or term: ou
Alternative title: La vie est un songe
Other title information: biographie
Once this linking word element were established, then the issue of
how to
encode the title in MARC could be resolved. Several different
possibilities have been discussed here, and the JSC will need to
evaluate
them and decide on which one to recommend, and on if any changes to
the
MARC format are needed to accommodate them. As Kevin points out, the
indexing of the MARC encoding could vary from system to system
based on
the needs of each individual agency, and depending on how the
system was
configured, various additional access points would or would not be
needed.
Adam
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Adam L. Schiff
Principal Cataloger
University of Washington Libraries
Box 352900
Seattle, WA 98195-2900
(206) 543-8409
(206) 685-8782 fax
[EMAIL PROTECTED]
http://faculty.washington.edu/~aschiff
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
-----------------------------------
Karen Coyle / Digital Library Consultant
[EMAIL PROTECTED] http://www.kcoyle.net
ph.: 510-540-7596 skype: kcoylenet
fx.: 510-848-3913
mo.: 510-435-8234
------------------------------------
