Thanks, Terry for the explanation. it's only been 2 records thus far
for me, so not much a problem as of yet to work with correcting them
manually.
best,
heidi
Heidi Frank
Electronic Resources & Special Formats Cataloger
New York University Libraries
Knowledge Access & Resources Management Services
20 Cooper Square, 3rd Floor
New York, NY 10003
212-998-2499 (office)
212-995-4366 (fax)
[log in to unmask]
Skype: hfrank71
On Wed, Mar 13, 2013 at 1:30 PM, Reese, Terry
<[log in to unmask]> wrote:
> When MarcEdit converts data from XML to MARC, it automatically truncates
> fields and records that are too long -- so invalid records due to lengths
> shouldn’t be an issue. That’s been in the application for some time. This
> fix will allow you to more easily identify, through the validator, what is
> causing a processing issue -- specifically, it will identify field errors
> and allow you to remove those records from a source file for later
> processing if necessary.
>
> I’ve kicked around the idea of allowing the Engine to do automatic
> truncation of MARC data as it processes if it runs across fields that are
> too long, but I’ve at this point, avoided that for the most part for a
> variety of reasons.
>
> --TR
>
> *************************************
> Terry Reese, Associate Professor
> Gray Family Chair for
> Innovative Library Services
> 121 Valley Library
> Corvallis, OR 97331
> tel: 541.737.6384
> *************************************
>
> From: Heidi P Frank
> Sent: March 13, 2013 10:15 AM
>
> To: [log in to unmask]
> Subject: Re: [MARCEDIT-L] MarcEdit & Voyager
>
> aah, so this explains things for me too - I had a file of 1424 records
> for archival collections, and 2 of those were "bad" records, where the
> MARC fields got "shifted" within the record. I did find them with the
> MARC validator because those 2 records had a number of invalid MARC
> fields, and am pretty sure it had to do with field lengths over the
> limit.
>
> however, mine were interspersed as well - meaning, only those 2 were
> affected and the ones following were fine.
>
> anyway, Terry, does this mean your fix would keep the MARC fields from
> renumbering in the bad record if one of the fields is over-length, and
> that I'd be able to just delete the field that is too long? my only
> alternative that I could think of is to delete the long fields from
> the original MARCXML files pre-MarcEdit, but am hoping I could somehow
> make it part of my automated tasks.
>
> cheers,
> heidi
>
> Heidi Frank
> Electronic Resources & Special Formats Cataloger
> New York University Libraries
> Knowledge Access & Resources Management Services
> 20 Cooper Square, 3rd Floor
> New York, NY 10003
> 212-998-2499 (office)
> 212-995-4366 (fax)
> [log in to unmask]
> Skype: hfrank71
>
>
> On Wed, Mar 13, 2013 at 12:49 PM, Kathy Martlock <[log in to unmask]> wrote:
>> Terry -- You are more than welcome to hijack any thread you like.
>>
>> Stacy -- It's a one bad record buried in the midst of other records.
>>
>> Kathy
>>
>>
>> On Wed, Mar 13, 2013 at 12:25 PM, Reese, Terry
>> <[log in to unmask]>
>> wrote:
>>>
>>> I hadn’t realized the validator didn’t identify field length errors – but
>>> I guess that makes sense given what it exactly does. I’ve added this
>>> error
>>> check to the next update.
>>>
>>>
>>>
>>> (sorry to hijack this thread for a moment. Unfortunately, I don’t use
>>> voyager so I can’t offer a suggestion)
>>>
>>>
>>>
>>> --TR
>>>
>>>
>>>
>>> From: MarcEdit support in technical and instructional matters
>>> [mailto:[log in to unmask]] On Behalf Of Stacy Pober
>>> Sent: Wednesday, March 13, 2013 9:11 AM
>>> To: [log in to unmask]
>>> Subject: Re: [MARCEDIT-L] MarcEdit & Voyager
>>>
>>>
>>>
>>> I've had that happen to files. Usually, there is one problem record and
>>> whatever error it contain somehow corrupts subsequent records in the
>>> file,
>>> changing their field numbers to invalid/inappropriate ones.
>>>
>>>
>>>
>>> In the files I've worked with, it was pretty straightforward, in that the
>>> problem record corrupted all of the following records. If you can find
>>> the
>>> last good record the problem usually starts after that. A particular
>>> type
>>> of error that would cause this would be a field length over 10,000
>>> characters. Oversize field lengths are not detected by the MarcEric
>>> validation.
>>>
>>>
>>>
>>> If you are having alternate good/bad records, then your problem is
>>> something else.
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Stacy Pober
>>> Information Alchemist
>>> Manhattan College Library
>>> Riverdale, NY 10471
>>> [log in to unmask]
>>>
>>>
>>>
>>> On Wed, Mar 13, 2013 at 9:36 AM, Kathy Martlock <[log in to unmask]> wrote:
>>>
>>> Well, on a second look at this process this a.m. I see that the field
>>> data
>>> comes through fine; however, the field tags are wrong, i.e. the 245 field
>>> is
>>> numbered 501 -- the 100 field is numbered 000, etc..
>>>
>>>
>>>
>>> Does anyone know how to fix this?
>>>
>>>
>>>
>>> Thanks, again.
>>>
>>>
>>>
>>> Kathy
>>>
>>>
>>>
>>> On Tue, Mar 12, 2013 at 5:11 PM, Kathy Martlock <[log in to unmask]> wrote:
>>>
>>> Thank you ... thank you ... I cannot thank you enough ... so simple, yet
>>> effective. Exactly what I wanted.
>>>
>>>
>>>
>>> Kathy
>>>
>>>
>>>
>>> On Tue, Mar 12, 2013 at 4:53 PM, Bornheimer, Bee <[log in to unmask]>
>>> wrote:
>>>
>>> This may be a crazy (and wrong) way to do this, but I just tried this by
>>> copying and pasting the text (minus the heading) in a text file, then
>>> changing the extension to .mrc and letting MarcEdit do its magic.
>>>
>>>
>>>
>>> From: MarcEdit support in technical and instructional matters
>>> [mailto:[log in to unmask]] On Behalf Of Kathy Martlock
>>> Sent: Tuesday, March 12, 2013 1:29 PM
>>> To: [log in to unmask]
>>> Subject: MarcEdit & Voyager
>>>
>>>
>>>
>>> Hi Everyone --
>>>
>>>
>>>
>>> I am rather new at MarcEdit and am just discovering all the features
>>> available. I want to say thanks to all of you for this ListServ - it has
>>> proven to be very helpful.
>>>
>>>
>>>
>>> I have been unable to find help on this and figured it was time to reach
>>> out to the experts.
>>>
>>>
>>>
>>> Here's my mystery :
>>>
>>>
>>>
>>> I am using MarcEdit and Voyager.
>>>
>>>
>>>
>>> I am trying to open the err.imp marc records that do not bulk import
>>> properly.
>>>
>>>
>>>
>>> When I open the report file at err.imp.yyyymmdd.hhmm, I get a very nice
>>> looking web page that shows a heading and what appears to be a tab
>>> delimited
>>> marc record (but I don't think it is). I can get the actual marc record
>>> from the original source file (which is huge and cumbersome) or I can
>>> contact our database administrator and he can send me the marc file(s)
>>> that
>>> have errored/rejected/discarded.
>>>
>>>
>>>
>>> Is there an easier way ... can I somehow capture the marc file from the
>>> web page report? (without being db admin)?
>>>
>>>
>>>
>>> Thanks for any help you can offer,
>>>
>>>
>>>
>>> Kathy Martlock
>>>
>>> Library Specialist III - Cataloging
>>>
>>> Z. Smith Reynolds Library
>>>
>>> Wake Forest University
>>>
>>> ____________________________________________________________
>>>
>>> ________________________________________________________________________
>>>
>>> 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]
>>>
>>> ________________________________________________________________________
>>>
>>> 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]
>>
>>
>> ________________________________________________________________________
>>
>> 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]
>
> ________________________________________________________________________
>
> 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]
________________________________________________________________________
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]
|