Why is it that when I import MARC data using ZLink, the results I get aren what I expected?
[A] The processing of MARC data goes through several stages before it actually appears in the title composition screen, and it is important to understand the order of these operations. Phase I As stated in the File Maintenance reference guide, operations are done in the following order (see further below for post-Phase I release information): 1. MARC field is placed into ABLEä field according to Editing parameter (e.g., Insert); If the MARC field is unavailable, the ABLEä field is used as it is. 2. Any truncation is then performed on field resulting from (1). 3. Any uppercase conversion is performed on above result from (2). 4. Any substitution (of spaces) is performed on above result from (3). This gives (4) as the final result. So, depending upon which data is actually imported and how you have your catalog system mapping table set up, you may get results you didn’t expect. A few examples follow below (for insertion editing, truncating on spaces). Example 1 ABLEä Call field: DEF MARC