I've been thinking about this issue because it is an interesting way for Catalogers, Data Analysts and Librarians to look at the issue. This also plays into
the Cataloging thinking of "transcribing a title" and the interesting new feature(s) of RDA. Let me remind you that I'm doing this on the cuff, so some things
are not presented "pretty" or necessarily logical--I'm thinking aloud.
So we have this MARC record structure. As I have been mentioning before, it is possible to expand the structure. For the sake of this discussion, let's assume
we were to expand the Indicators from 2 to 3. The new indicators has definitions of:
0 This is textual data [transcribed]
1 This is content data [transcribed]
2 This is textual data [non-transcribed]
3 This is content data [non-transcribed]
4 This is transcribed data (textual and content)
5 This is non-transcribed data (as it appears on a title page or on the item textual and content)
... maybe more.
1. Transcription Solution:
So you could then define a 245 in two ways:
245 104 The adventures of Huckelberry Finn / $c Samuel Clemens.
245 005 The ADVENTURES of HUCKELBERRY FINN /$c samuel CLEMENS <== Appears on the t.p.
Noticed that I actually used indicator position 1 to indicate indexing (printing or not printing on the card). Now the ILS vendor has to make it possible when two 245s are present to make sure these indicators work correctly or you will either have duplicate entries. (And filing can be a problem if the ILS does not normalize the character string when indexing and gives different weighting to upper case letters and lower case letters.
2. Content vs. textual.
300 ##0 $a xii, 543 p. : $b ill., maps ; $c 28 cm.
300 ##1 $a xii $a 543 $ap. $bill $b maps $c 28 cm.
You can now teach the display to see the second 300 hundred as content data and the computer knows roman numerals from non roman.
3. Example with Imprint statement
260 ##0 [New York, N.Y.] : $b Moonshine Press, $c c1990.
260 ##2 NEW YORK :$b MoonSHINE, <==appears on t.p., but no date until you turn to t.p. verso.
260 ##1 New York, New York : $b The Moonshine Press, $c 1990, $g 2008
Do you see where I'm going with this. We are able to record data in a variety of ways and let the machine manipulate it as needed. The subfield codes can more or less stay the same, but we still may need to expand on this area.
William F. Maag Library
Youngstown State University
[log in to unmask]
""For he is the Kwisatz Haderach..."