You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rochester staff are looking into some errors on records that were not converted.
All of the records looked at so far have an C (1E) at the end of an 020 field. It is possible that all 5446 errors reported are of this type but we are still looking at them. The problem is that report does not correctly identify the problem. The logs seem to reference same five tags: 099, 050, 650, 090 and 049, when the problem is the 020.
That said, it would be great if the report can be changed so that it
correctly describes the error (extra field terminator) and correctly
identifies the field where the error exists (020 field).
I will ask Ralph to get some sample records to you.
The text was updated successfully, but these errors were encountered:
JIRA issue created by: rcook
Originally opened: 2012-06-26 09:34 AM
Issue body:
GC Issue http://code.google.com/p/xcoaitoolkit/issues/detail?id=84
Reported by project member [email protected], May 24, 2011
Rochester staff are looking into some errors on records that were not converted.
All of the records looked at so far have an C (1E) at the end of an 020 field. It is possible that all 5446 errors reported are of this type but we are still looking at them. The problem is that report does not correctly identify the problem. The logs seem to reference same five tags: 099, 050, 650, 090 and 049, when the problem is the 020.
That said, it would be great if the report can be changed so that it
correctly describes the error (extra field terminator) and correctly
identifies the field where the error exists (020 field).
I will ask Ralph to get some sample records to you.
The text was updated successfully, but these errors were encountered: