Review these guidelines when trying to resolve Marcive file processing errors that arise from importing a file into Sirsi and/or running a Sirsi Load report.
- Save the error log that pops up to a convenient location where you can view it later.
- Read the error message/s, which are preceded by a double asterisk**, to learn about the problem. (How to read an import error log)
- Open your NCSABIB (or NCSAALL) file (in Marcive\Incoming\Year\month\) in the .mrk format (Use MARC Tools\MarcEdit Marc Breaker)
- Keep the NCSABIB (or NCSAALL) .mrk file open. Open a new blank file in a new window (File → New → Open New Window).
- Search for each of the records in the error report in your NCSABIB (or NCSAALL) file (search by 035, Edit, Find, Find All, Jump to page), then copy the records into the new blank .mrk file as you find them.
- Close the original incoming NCSABIB (or NCSAALL) file.
Save the new .mrk file as NCSABIB_### (or NCSAALL_###)_importErrors.
Using the error message in the Sirsi error log as a guide, work in the NCSABIB_importErrors (or NCSAALL_importErrors).mrk file to resolve errors.
Possible Error types:
"**Record encoding scheme incompatible with server characterset"
Check to see that LDR position 9 is blank (remember, when counting positions in MARC fields, start with 0).
If not blank, add a space.
Because you added a character, make sure there are only 23 characters in the field.
- If not, check MARC21 rules to find where there may be an unnecessary extra character.
If position 9 is “a”, change to blank.
**Tag start not in correct position
In this case, your field tag might be too long or improperly encoded. Check the MARC21 rules for that field and review the coding in the field to make sure there are correct or reasonable values in the field.
**"Entry ID not found in format: entry = 065 format = PERSONAL"
There's a new authority tag that needs to be entered into the Sirsi format policy (New authority tags will cause an authority record to error out from the load, while a new bibliographic tag will not cause a bib record to error out from a bib load.) Refer the problem to Lisa and the monographs head.
Other error types
Google the error with quotes.
Ask Lisa to help.
If Lisa can't help, she can ask ILS administrator and/or monographs head.
Review the rest of the field to make sure there aren’t other coding errors
File → Save your NCSABIB_importErrors (or NCSAALL, if appropriate).
File → Compile File into Marc. This option will ask you to name the .mrc file -- give it the same name without a file extension. Save.
Import the NCSABIB_importErrors.mrc (or NCSAALL, if appropriate) file.
Read the error message/s, which are preceded by a double asterisk**, to learn about the problem. (How to read a load error log)
Look for the number of errors by scrolling to the report statistics that tell you how many records were read, replaced, etc.
Does the error say “Flexible key not found?”
Find the oclc number of the record with the error and search it in SIRSI.
If you are unable to find it, search by title.
If find a record, make sure it is the same record as the one in your error report.
If it is the same record, check the title control number tab to make sure it is the same as the 001 in the error report.
If the title control number and 001 don’t match, bring to Lisa’s attention. This may need to be forwarded to monographs.
If the title control number matches, make sure there are no extraneous spaces or characters in the record or error report that may have caused a failure to match.
If you are unable to find the record in SIRSI, it may have been deleted since the extract was done, so you can ignore this record.
If you encounter other errors, forward to Lisa for guidance.