LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  May 2011

CODE4LIB May 2011

Subject:

Re: is this valid marc ?

From:

"Doran, Michael D" <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Thu, 19 May 2011 14:32:04 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (148 lines)

Hi Jonathan,

> To me, "control character" means ASCII less than 20.

Pre-Unicode, "control character" was defined by hex 00-1F ("C0") for a 7-bit character set plus hex 80-9F ("C1") for an 8-bit character set.

> But, two, Michael, are you the doran in this?
> http://rocky.uta.edu/doran/charsets/marc8default.html

Yes.

> You might want to remove CR, LF, and the other disallowed control
> characters from your own published list of MARC8 characters!

The ones in bold are the allowed characters.  Note that the MARC definition of the control character is different from the ASCII definition.  The charts on that site are dynamically generated (from the URDU database http://rocky.uta.edu/doran/urdu/search.cgi) which is why I chose to distinguish with bold, rather than not show the other control character positions.

-- Michael

> -----Original Message-----
> From: Jonathan Rochkind [mailto:[log in to unmask]]
> Sent: Thursday, May 19, 2011 2:23 PM
> To: Code for Libraries
> Cc: Doran, Michael D
> Subject: Re: [CODE4LIB] is this valid marc ?
> 
> Thanks Michael. So one weird thing is that at least some of those
> characters "specifically designated as control characters" aren't
> ordinarily what everyone else considers "control characters".  To me,
> "control character" means ASCII less than 20. Which the last four
> aren't. So now it's unclear what the "prohibted" (by not being
> mentioned) control characters are, since I don't know what MARC
> considers a 'control character' exactly.
> 
> But I'm really just picking nits to demonstrate the impenetrability of
> MARC specs.  I believe you all (especially Terry) that CR and LF aren't
> allowed.
> 
> But, two, Michael, are you the doran in this?
> http://rocky.uta.edu/doran/charsets/marc8default.html
> 
> You might want to remove CR, LF, and the other disallowed control
> characters from your own published list of MARC8 characters!
> 
> On 5/19/2011 3:16 PM, Doran, Michael D wrote:
> >> Is it really true that newline characters are not allowed in a marc
> >> value?
> > Yes.
> >
> >    CONTROL FUNCTION CODES [1]
> >
> >    Eight characters are specifically designated as control characters for
> MARC 21 use:
> >
> >    - escape character, 1B(hex) in MARC-8 and Unicode encoding
> >    - subfield delimiter, 1F(hex) in MARC-8 and Unicode encoding
> >    - field terminator, 1E(hex) in MARC-8 and Unicode encoding
> >    - record terminator, 1D(hex) in MARC-8 and Unicode encoding
> >    - non-sorting character(s) begin, 88(hex) in MARC-8 and 98(hex) in
> Unicode encoding
> >    - non-sorting character(s) end, 89(hex) in MARC-8 and 9C(hex) in Unicode
> encoding
> >    - joiner, 8D(hex) in MARC-8 and 200D (hex) in Unicode encoding
> >    - nonjoiner, 8E(hex) in MARC-8 and 200C (hex) in Unicode encoding.
> >
> > [1]
> http://www.loc.gov/marc/specifications/specchargeneral.html#controlfunction
> >
> > -- Michael
> >
> > # Michael Doran, Systems Librarian
> > # University of Texas at Arlington
> > # 817-272-5326 office
> > # 817-688-1926 mobile
> > # [log in to unmask]
> > # http://rocky.uta.edu/doran/
> >
> >
> >
> >
> >
> >
> >> -----Original Message-----
> >> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
> >> Jonathan Rochkind
> >> Sent: Thursday, May 19, 2011 1:27 PM
> >> To: [log in to unmask]
> >> Subject: Re: [CODE4LIB] is this valid marc ?
> >>
> >> Is it really true that newline characters are not allowed in a marc
> >> value?  I thought they were, not with any special meaning, just as
> >> ordinary data.  If they're not, that's useful to know, so I don't put
> >> any there!
> >>
> >> I'd ask for a reference to the standard that says this, but I suspect
> >> it's going to be some impenetrable implication of a side effect of an
> >> subtle adjective either way.
> >>
> >> On 5/19/2011 2:19 PM, Karen Coyle wrote:
> >>> Quoting Andreas Orphanides<[log in to unmask]>:
> >>>
> >>>> Anyway, I think having these two parts of the same URL data on
> >>>> separate lines is definitely Not Right, but I am not sure if it adds
> >>>> up to invalid MARC.
> >>> Exactly. The CR and LF characters are NOT defined as valid in the MARC
> >>> character set and should not be used. In fact, in MARC there is no
> >>> concept of "lines", only variable length strings (usually up to 9999
> >>> char).
> >>>
> >>> kc
> >>>
> >>>> -dre.
> >>>>
> >>>> [1] http://www.loc.gov/marc/bibliographic/bd856.html
> >>>> [2] I am not a cataloger. Don't hurt me.
> >>>> [3] I am not an expert on MARC ingest or on ruby-marc. I could be wrong.
> >>>>
> >>>> On 5/19/2011 12:37 PM, James Lecard wrote:
> >>>>> I'm using ruby-marc ruby parser (v.0.4.2) to parse some marc files I
> >>>>> get
> >>>>> from a partner.
> >>>>>
> >>>>> The 856 field is splitted over 2 lines, causing the ruby library to
> >>>>> ignore
> >>>>> it (I've patched it to overcome this issue) but I want to know if
> >>>>> this kind
> >>>>> of marc is valid ?
> >>>>>
> >>>>> =LDR  00638nam  2200181uu 4500
> >>>>> =001  cla-MldNA01
> >>>>> =008  080101s2008\\\\\\\|||||||||||||||||fre||
> >>>>> =040  \\$aMy Provider
> >>>>> =041  0\$afre
> >>>>> =245  10$aThis Subject
> >>>>> =260  \\$aParis$bJ. Doe$c2008
> >>>>> =490  \\$aSome topic
> >>>>> =650  1\$aNarratif, Autre forme
> >>>>> =655  \7$abook$2lcsh
> >>>>> =752  \\$aA Place on earth
> >>>>> =776  \\$dParis: John Doe and Cie, 1973
> >>>>> =856  \2$qtext/html
> >>>>> =856
> >>>>> \\$uhttp://www.this-link-will-not-be-retrieved-by-ruby-marc-library
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> James L.
> >>>
> >>>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager