Unicorn iLink Catalog Prepared by LadyJane Hickey April 2004 SIRSI BIBLOAD RULES Unicorn iLink Catalog Prepared by LadyJane Hickey April 2004

FIVE BIBLOAD RULES

RULE 1 DESCRIPTION Incoming records will be compared with records already in the system. When a record is new to the system, it will be created. When an incoming record matches a record in the system, it will not load. It will be reported as error.

Rule 1 Description Incoming records will be compared with records already in the system. When a record is new to the system, it will be created. When an incoming record matches a record in the system, it will not load. It will be reported as error.

Rule 1 Usage This rule allows creation of new records This rule does not allow an update/overlay of existing records Could be used anytime duplicate records are anticipated in a bibload

Rule 1 Usage Examples Marcive weekly records Acquisitions records Load Texas records NetLibrary records

RULE 2 DESCRIPTION Incoming records will be compared with records already in the system. When a record is new to the system, it will be created. When an incoming record matches a record existing in the system with a “date cataloged” of NEVER, the existing record will be updated according to other settings in this report. When an incoming record matches an existing record with a date in the “date cataloged” field, it will not load. It will be reported as an error.

Rule 2 Description Incoming records will be compared with records already in the system. When a record is new to the system, it will be created. When an incoming record matches a record existing in the system with a “date cataloged” of NEVER, the existing record will be updated according to other settings in this report. When an incoming record matches an existing record with a date in the “date cataloged” field, it will not load. It will be reported as an error.

Rule 2 Usage This rule is ideal for new OCLC records overlaying Acq. Or Temp records with a date cataloged of NEVER. It is designed to not allow an overlay of a cataloged record, based on the date cataloged Majority of the catalog migrated in 2001 with date cataloged of NEVER, so this rule could be used but would not protect migrated records from unintentional updates. It will allow the creation of new records

Rule 2 Usage Examples Copy Cat Create bibloads OCLC Cat Create bibloads EResource DocAmSo bibload

RULE 3 DESCRIPTION Incoming records will be compared with records already in the system. When an incoming record matches a record existing in the system with a “date cataloged” of NEVER, the existing record will be updated according to other settings in this report. When an incoming record is new to the system or when an incoming record matches an existing record with a date in the “date cataloged” field, it will not be loaded. It will be reported as an error.

Rule 3 Description Incoming records will be compared with records already in the system. When an incoming record matches a record existing in the system with a “date cataloged” of NEVER, the existing record will be updated according to other settings in this report. When an incoming record is new to the system or when an incoming record matches an existing record with a date in the “date cataloged” field, it will not be loaded. It will be reported as an error.

Rule 3 Usage This rule is ideal for new OCLC records overlaying Acq. records or Temp with a date cataloged of NEVER. It is designed to not allow an overlay of a cataloged record, based on the date cataloged Majority of the catalog migrated in 2001 with date cataloged of NEVER, so this rule could be used but would not protect migrated records from unintentional updates. It will not allow the creation of new records.

Rule 3 Usage Examples Copy Cat Bib CatMe edited bibload OCLC CatMe edited bibload OCLC copy cat bibload

RULE 4 DESCRIPTION Incoming records will be compared with records already in the system. Records that are new to the system will be created, and records that match existing records will be updated according to other settings in this report.

Rule 4 Description Incoming records will be compared with records already in the system. Records that are new to the system will be created, and records that match existing records will be updated according to other settings in this report.

Rule 4 Usage The most powerful rule Existing records are overlaid New records are created Could be used for every type of record situation When a record is overlaid, the date cataloged changes. This is important for authority extraction.

Rule 4 Usage Examples Marcive monthly OCLC Eresource bibload OCLC Gov. Doc bibload Marcive Online

RULE 5 DESCRIPTION Incoming records will be compared with records already in the system. When an incoming record matches a record already in the system, the existing record will be updated according to other settings in this report. Records that are new to the system will not be loaded. They will be reported as errors.

Rule 5 Description Incoming records will be compared with records already in the system. When an incoming record matches a record already in the system, the existing record will be updated according to other settings in this report. Records that are new to the system will not be loaded. They will be reported as errors.

Rule 5 Usage Incoming Records will overlay existing records New records will not be created Use only if you’re sure new records are not included in the file

Rule 5 Usage Examples Marcive monthly change bibload Overlay prev. cat. Record bibload

Analysis for Scenarios Do you want to create records? Do you need to prevent duplicate cataloging of a title? Do you need to create and update/overlay records?

Analysis for Scenarios Do you want to update/overlay records? Are you updating/overlaying acquisitions or tmp records? Were those records previously cataloged with a date in the date cataloged field on the SIRSI control tab? Were those records previously cataloged before migration and have NEVER in the date cataloged field on the SIRSI control tab?

Analysis for Scenarios Will title duplication cause an extra expense, such as ordering a title twice? Will changing the date cataloged be a problem? Will not loading a record (i.e. losing the record, sending it to the error file) be a problem?

Scenario Question 1. A new book is being cataloged. OCLC copy cataloging is available. No Acquisitions record exists in the database. Which bibload rule would you use?

Scenario Question 2. A new book is being cataloged. OCLC copy cataloging is available. A short Acquisitions record is available. Which bibload rule would you use?

Scenario Question 3. A serial title is being cataloged. OCLC copy cataloging is available. The OCLC record has our symbol on the record. In SIRSI, the serial title does not have an OCLC number and is much shorter than the current record in OCLC. You decide to bring in the OCLC record and overlay the older migrated title. Which bibload rule would you use?

Scenario Question 4. A government document serial title is being cataloged. You have the item in your hand. OCLC copy cataloging is available. No tmp record exists. Which bibload rule would you use?

Scenario Question 5. A government document serial title is being cataloged. You have the item in your hand. A short record came in over a year ago, but the long record never came. OCLC copy cataloging is available. Which bibload rule would you use?

Scenario Question 6. You cataloged a shelf of new books in OCLC. And downloaded the records in one file. Short acquisitions records are in the catalog. Which bibload rule would you use?

Scenario Question 7. You cataloged a box of microfiche titles for government documents and downloaded the records in one file. Some of these may have short records, but you know at least one does not have a tmp record. Which bibload rule would you use?

Scenario Question 8. You cataloged 10 newly acquired music scores and downloaded the records in one file. Which bibload rule would you use?

Scenario Question 9. The library acquires a large gift collection of music CD-ROMS. As you catalog this collection, you find OCLC copy cataloging for every title. Which bibload rule would you use?

Scenario Question 10. You’re responsible for loading several batches of records for Acquisitions from three different vendors. You don’t want to duplicate an existing record in the catalog. Which bibload rule would you use?

Scenario Question 11. You’re picking up a batch of updated OCLC records from OCLC. These records update OCLC records that contain our symbol. You don’t know what titles are included in the files. Which bibload rule would you use?

Scenario Question 12. You picked up a batch of Marcive change records. You hope they will update/overlay existing records, but in the past you’ve also had problems: the material was in our collection, but never cataloged; the material was removed from the collection; or, we’ve never received the material. Which bibload rule would you use?

Renaming BibLoad Templates

Renaming and Removing I renamed these to pull them together and to tell me the rule number Other renaming possibilities: name them for what they do, such as the Overlay prev. cataloged records Eliminate your templates that are identical

Necessity for Different Templates Different call number scheme: LC, AUTO, SuDoc Adding a copy versus no copy Different selections: With or without multiple occurrences Junktag MeSH

No New Template Rule is the same Adding or not adding copy is the same Other selections are the same Holding code changes