About Default Import Profiles

When you import bibliographic records using an online collection development tool, you can use the Acquisitions Bibs profile. The profile is set to ignore MARC validation errors because the incoming records are brief and do not require validation. When a duplicate is found, the incoming record is rejected, and the 970 tags from both records are retained in the full bibliographic record.

Copy the Acquisitions Bibs profile for each vendor you use to import records, name each copy of the Acquisitions Bibs profile with the name of the vendor, and make any changes to the settings.

Important:
To ensure that the most recently entered ISBN or UPC is retained, you must add the 020 (ISBN) and 024 (UPC) tags to the profile-defined retention tags. When these tags are retained from an incoming record that is a duplicate of an existing record, and the existing record has multiple ISBNs or UPCs, the most recently added ISBN or UPC is at the top of the list in a purchase order line item.

If you use the Authorities Weekly service to keep your authority records current, use the Authority Update Import profile to import the updated authority records. Innovative sets up this profile specifically for importing updated authority records. This import profile is set to perform duplicate detection using system-defined duplicate detection rules, and if duplicates are found, merge the duplicate records based on which record has a higher ranking in the Authority Record Import Preferred Cataloging Source policy table at the system level.

Important:
The Authority Update Import profile is set to check the Authority Record Import: Preferred Cataloging Source policy table at the system level. To ensure that the updated records from ZMARC files always overlay existing records, delete all entries in the table at the system level. Then, enter the preferred sources in the Preferred Cataloging Source policy table at the branch level so that the branch determines the preferred cataloging source for non-ZMARC imports.

The Enriched EDI Orders profile is set up specifically to import full bibliographic records from your book vendor and create “shelf-ready” item records, including location and collection information (and the call number fields, if your supplier can process this data). It is set to perform MARC validation, authority control, and duplicate detection. If a duplicate is found, the record with the highest encoding level is saved and 949 tags are retained. If you send enriched EDI orders to vendors through acquisitions, copy this profile to reflect the vendor’s name, but leave most of the settings as they are.

The Item Records tab of the Enriched EDI Orders import profile is set to build item records from the data in the 949 tag. If your library and supplier decide to embed the holdings data in a tag other than the 949 tag, you can change the profile to indicate the correct tag.

Note:
When Update items (enriched EDI) is selected, you cannot enter a value in the Circ Status box in the Embedded holdings field/MARC subfield mapping list.

The system matches the content of the 949 tag subfield $e in the incoming bibliographic record to the purchase order line item segment, and the linked on-order item is updated with the full item data from the imported bibliographic record. The updated item is ready to circulate once it is checked in.

However, if there are 949 tags with a purchase order line item segment ID in the 949 tag subfield $e and a volume designation in the 949 tag subfield $v, a final item record will be created even if no matching on-order item is found. The new final item record is linked to the purchase order line item segment in subfield $e. This allows holds that were placed at the bibliographic level for an on-order set to go to the first volume of the set.

Use this profile to import eContent bibliographic records.

Use this profile to import eContent bibliographic records without item records.

The BibsPost PAPI endpoint uses this import profile if the vendor doesn't specify an import profile. The profile is set up to perform MARC validation, authority control, and duplicate detection. During import, Leap attempts to match the incoming 001 tag to an existing bibliographic record ID. If Leap finds a match, it modifies the existing record. If it does not find a match, it creates a new bibliographic record.

This is a general profile for importing bibliographic records. It is set up to perform MARC validation and duplicate detection, and to save records as provisional if any MARC formatting errors or duplicate records are found.

The Polaris Default (with item creation) import profile has the same settings on the Bibliographic Records tab as the Polaris Default import profile, but the Item Records tab is set to create item records from embedded holdings data in 852 tags.