MARCEDIT-L Archives

February 2014

MARCEDIT-L@LISTSERV.GMU.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Edmunds <[log in to unmask]>
Reply To:
MarcEdit support in technical and instructional matters <[log in to unmask]>
Date:
Thu, 6 Feb 2014 12:56:44 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (22 lines)
All,

Anyone else submitting records to HathiTrust/Google via Zephir? We recently had a record rejected (OCLC # 56437757, for what that's worth) because of a bad Leader. The Zephir diagnostic looks like this:

bad line: <marc:record><marc:leader>01380&amp;#xbf;amưa2200361 a 450̐</marc:leader> yaz_marc_read_xml failed

When we opened the record in MarcEdit, we saw that LDR Position 05 was not a single character, but {BF} (whatever that means). We tried manually changing this string to "c" and re-compiling the record into MARC, but this didn't seem to work. Then we tried overwriting the copy of the record in our catalog with the OCLC version, reconverting it to XML, and resending it to the HathiTrust folks. 

The record was again flagged as having a bad Leader, but this time the diagnostic looks slightly different:

bad line: <marc:record><marc:leader>01750&amp;#xbf;amưa2200433 a 450̐</marc:leader> yaz_marc_read_xml failed

Does anyone have any experience with odd characters somehow making their way into Leaders?

Thanks,

Jeff

________________________________________________________________________

This message comes to you via MARCEDIT-L, a Listserv(R) list for technical and instructional support in MarcEdit.  If you wish to communicate directly with the list owners, write to [log in to unmask] To unsubscribe, send a message "SIGNOFF MARCEDIT-L" to [log in to unmask]

ATOM RSS1 RSS2