Punctuation in the Enhanced 505

Its perhaps a bit late in the 'MARC day' to be writing about punctuation in the 505 field. So this page will mainly consist of some examples from DLC records, illustrating just how complex the punctuation in this field can be. The general idea is that the titles in the 505 can be punctuated very much like the titles in the 245, yet in the 505, subfield $t is repeated in lieu of using all the different subfields available in the 245 ($b–with its three different punctuations, $n, $p).

Note: All of the examples below have been taken verbatim from DLC records; the only change we have made is to truncate some of the excerpts, once we have illustrated the salient point.

Titles without s/r1):

505 00$tMask of the Ronin --$tSurvivor --$tUke --$tDeadly dance --$tGhostwarrior.

Titles and s/r:

505 00$tExpanding our boundaries /$rRichard Stursberg --$tForeword /$rAdrienne 
Clarkson --$tIntroduction /$rMaria von Finckenstein --$tCelebrating with George 
Pitseolak /$rAnn Meekitjuk Hanson -- Fifty years of thinking it over.

Another type of responsibility

Subfield $r indicates 'responsibility', but punctuation can be used to indicate differeing types of responsibility. When creators of a work are entered in 505 $r, the punctuation is a '/' (forward slash), as in the preceding example; but when performers of a work are entered in subfield $r, they are given in parens:

505 00$tTell me everything$r(SPIT Orchestra ; Brad Lubman, conductor)
 --$tEarly that summer$r(Lark Quartet) --$tArsenal of democracy$r(Orkest de 
Volharding ; Jurjen Hempel, conductor) --$tFour Marys$r(Cassatt String Quartet).

Common uses for subfield $g

  1. to indicate track times in a recording
  2. to indicate part numbers
  3. to indicate non-filing articles
505 00$tEternity's sunrise$g(10:54) --$tSong of the angel$g(4:49) --$tPetra : 
a ritual dream$g(10:29) --$tSappho : lyrical fragments$g(14:31) --$tFuneral 
canticle$g(23:54).
505 00$g1.$tLead us not into temptation --$g2.$tHeaven tonight --$g3.$tIt 
used to matter --$g4.$tRun with the big dogs --$g5.$tDon't call it love --$g6.
$tShootin' out streetlights --$g7.$tLove is bigger --$g8.$tThoroughfare.
505 00$gThe$tstarlighter --$tHit the road to dreamland --$gThe$tmoon is made of 
gold --$tPajamas --$gThe$tinch worm --$tMemphis in June --$tWarm valley --$tHere 
I'll stay --$gThe$twaters of March --$tSomewhere over the rainbow.

Subfield $g is useful to mark text in the 505 that should be hidden from indexing. All of the above uses of subfield $g can be conceivably combined in a single 505, and if we look hard enough, we can find one:

505 80$gCD 2.$tCantata no. 140,$tZion hor̈t die Wac̈hter /$rBach$g(4:46) --$tTe 
Deum in D,$tPleni sunt coeli et terra /$rCharpentier$g(2:23) --
...
$tGloria,$tLaudamus te /$rPoulenc$g(2:57) --$tChichester psalms /$rBernstein
$g(3:51) --$gThe$tlamb /$rTavener$g(3:12) --$tAgnus dei /$rBarber$g(7:46).

A more Interesting example

This example illustrates:

  • the use of subfield $g to hide articles from indexing
  • the use of an '=' in subfield $t to indicate a parallel title
505 00$gLes$tfrancs juges =$gDie$tFemerichter$g(12:28) --$tWaverley$g(10:24)
 --$gLe$tRoi Lear =$tKing Lear =$tKönig Lear$g(15:57) --$gLe$tcarnival romain =
$tRoman carnival =$tRömischer Karneval$g(9:29) --$tBéatrice et Bénédict$g(8:06)
 --$gLe $tcorsaire =$gThe$tcorsair =$gDer$tKorsar$g(8:44) --$tBenvenuto 
Cellini$g(10:07).

MARC Report and the 505

As far as MARC Report goes, we think the 505 field catchecks added in version 235 will catch quite alot of problems–although, as 505's can be quite lengthy, you may need to check the field-in-hand a bit closer to see exactly what the problem is. We have 'tuned' down the catcheck a lot, to make it less likely that some of the variant punctuation practices used in the 505 will trigger a false hit. If you do notice a condition that is triggering a message erroneously, please let us know.

We have tested these 505 punctuation catchecks on thousands of DLC records. The amount of basic errors they are catching is substantial. If you are following the typical cataloging practice, you will find these catchecks invaluable. If you find them a problem, please use the instructions here to turn off the cataloging check (these instructions can in fact be used to turn off any cataloging check).

An example of a problematic 505

The 505 is a rich data field for keyword indexing. But browse indexing the 505? well, its a bit over the edge, in our view. All the same, it might be done, and if so, excessive use of subfield $t in this regard might cause a false punctuation error message. For example, MARC Report is (somewhat) aware of this situation, and so will not flag the following sequence as an error:

505 00$tCanon in D /$rJohann Pachelbel --$tFur Elise$t(Ode to joy) /$rLudwig van 
Beethoven --$tSonata in C major$t(Mozart's lullaby) /$rWolfgang Amadeus Mozart 
--$tOn the beautiful blue Danube /$rJohann Strauss ... 

However, something like the following will trick the program:

$tSonata in C minor /$rDomenico Scarlatti --$tLargo /$rGeorge Frederick 
Handel --$tMinuet$t(Organ fugue in G minor)$t(Little fugue) /$rJohann Sebastian 
Bach. 

MARC Report will object to the second consecutive parenthetical $t in the work by JS Bach and display the brief message:

505: Item punct. should be ' --'. 
1) 's/r': statement of responsibility
235/505.txt · Last modified: 2013/04/27 09:09 (external edit)
Back to top
CC Attribution-Noncommercial-Share Alike 3.0 Unported
Driven by DokuWiki Recent changes RSS feed