| • | How are bibliographic data files created with the MARC Order Import Utility wizard? |
| • | How do bibliographic data files display in the MARC Order Import Utility wizard output? |
| • | How can I identify files that were not successfully imported using the MARC Order Import Utility wizard? |
How are bibliographic data files created with the MARC Order Import Utility wizard?
When a record loading report is used, such as the Load Bibs with Order Info report that adds records to the catalog, a backup copy of the records is written in the /Unicorn/Marcordimp/Bibs/Backup directory on the SirsiDynix Symphony server. This backup copy of records is called the bibliographic data backup.
Although the original imported file is no longer available after records have been loaded, the MARC records are stored in one of two directories on the server. Records that were successfully loaded into the catalog are stored in the /Unicorn/Marcordimp/Bibs/Backup directory. Records that failed to load are stored in the /Unicorn/Marcordimp/Bibs/Error directory.
The records that were successfully loaded into the catalog can be copied back into the /Unicorn/Marcordimp/Bibs directory to be available for loading again.
All bibliographic data backup files are saved as part of the daily backup. In the event of a system failure, all of the report-loaded records will be present on the daily bibliographic data backup. The records may easily be reloaded when the system is operational.
The bibliographic data backup files display ont he Loaded Bib Files tab in the MARC Order Import Utility wizard. Bibliographic data backup files use the following naming convention.
[date][library number][session number][n|e]
The first eight digits represent the date of the record load, in YYYYMMDD format. The next four digits represent the library number from the policies. The last one or two digits represent the session number from the given date. The final alphabetic character indicates the file type. The file type may be one of the following.
| • | An n indicates new records that were loaded into the catalog and copied to the bibliographic data backup. |
| • | An e indicates error files that were not loaded. See the FAQ ”How can I identify MARC files that were not successfully imported using the MARC Order Import Utility wizard?” in this topic for more information. |
For example, the following backup file name illustrates the naming convention.
20040118003006n
In the above example, the date is January 18, 2004. The library number from the policies is 0030. The session number shows that this file was the sixth file loaded on that date. The n file extension indicates that new records were loaded into the catalog and copied to the backup file.
How do bibliographic data files display in the MARC Order Import Utility wizard output?
When you choose to display bibliographic data with order information in the MARC Order Import Utility wizard, the MARC record data displays numerically. The header for each record includes the size=, last=, and #tags=, which all contain byte counts used to make sure the record data is accurate. The label ”num=” is equivalent to the MARC tag number. Order information appears for the MARC tag lines 960 and 961 (num=960 and num=961). The indicators in the data are not separated, and immediately precede the text in the data fields. Everything else is a count of data and the position of that data in the MARC record.
How can I identify files that were not successfully imported using the MARC Order Import Utility wizard?
The Bib Error Files tab provides a way to identify MARC files that were not successfully imported using the MARC Order Import Utility wizard. Bibliographic load error files are automatically created when a record loading report, such as the Load Bibs with Order Info report, is used. The original imported file is no longer available after it has been loaded, but the MARC records that produced errors in the log of the report are saved in the /Unicorn/Marcordimp/Bibs/Error directory and can be copied back into the /Unicorn/Marcordimp/Bibs directory to be available for loading again.
All bibliographic load error files use the following naming convention.
[date][library number][session number]e
The first eight digits represent the date of the record load, in YYYYMMDD format. The next four digits represent the library number from the policies. The last one or two digits represent the session number from the given date. The e final alphabetic character indicates error files that were not loaded.
For example, the following error file name illustrates the naming convention.
2004011800306e
In the above example, the date is January 18, 2004. The library number from the policies is 0030. The session number shows that this file was the sixth file loaded on that date. The e file extension indicates that records were not loaded successfully into the catalog because of errors.
Related topics
MARC Order Import Utility Wizard
Load Bibs with Order Info Report
FAQs: Working with Order Files in the MARC Order Import Utility Wizard
© 2006, 2014 SirsiDynix