Hi all, I'm writing some marc record display code, and I have a question
about the 'right' way to display LCSH headings.
LCSH headings are typically displayed with -- between components. But
looking at the MARC, it looks like the -- punctuation isn't actually
in the MARC field. (A rare
Only for certain subfields:
Dash (-) that precedes a subdivision in an extended 600 subject
heading is not carried in the MARC record. It may be system generated
as a display constant associated with the content of subfield $v, $x,
$y, and $z.
From
Thanks! So $v, $x, $y, and $z should always get a -- before them --
that's sufficient logic to do it 'right'? I guess an LCSH 6xx always
needs an $a first, so I don't need to worry about if a $v or $x happens
to come first, and shouldn't get a preceding --.
Should I do this only for 6xx
Hey, and it occurs to me, in an HTML display, it might be better to use
an actual em-dash than the traditional two hyphens too? Since the LC
documentation just talks about dash -- two hyphens is how you
approximate an em-dash in ascii of course, but we're not living in ascii
anymore!
Tod
Using -- before subfields $v, $x, $y, and $z should work well for
all the standard MARC 6XX fields.
The only exception might be in any locally-defined fields 690-699.
Keith
On Wed, Sep 23, 2009 at 10:19 AM, Jonathan Rochkind rochk...@jhu.edu wrote:
Thanks! So $v, $x, $y, and $z should always
On Sep 23, 2009, at 9:19 AM, Jonathan Rochkind wrote:
Thanks! So $v, $x, $y, and $z should always get a -- before them
-- that's sufficient logic to do it 'right'? I guess an LCSH 6xx
always needs an $a first, so I don't need to worry about if a $v or
$x happens to come first, and
With your help, I have discovered I can do what I need to using MarcEdit.
MarcEdit is native to the Windows environment, which is what I am using.
Interestingly, it sits on Yaz, which sits on z39.50. MarcEdit has an API that
can be addressed by VBscript or .NET. I have downloaded the client and
Hi everybody,
Apologies for the crossposting.
I wanted to let people know that Ruby MARC 0.3.0 was just released as
a gem. This version addresses the biggest complaint about Ruby MARC,
which was the fact that it could only parse MARCXML with REXML, Ruby's
native XML parser (which, if you've
Nice work Ross! Users of rubymarc might like to see the performance
enhancements that motivated you to do the nokogiri integration:
http://paste.lisp.org/display/87529
!!!
//Ed
On Wed, Sep 23, 2009 at 10:51 PM, Ross Singer rossfsin...@gmail.com wrote:
Hi everybody,
Apologies for the
