Control Number Cleanup	Fields to be Deleted
Incorrect Non-filing Indicators	Global Changes to be Made to MARC Tags
6xx Second Indicators	Copy Notes
Incorrect Representations of Diacritics	Record Notes
Call Number Cleanup	Ticklers
System Workarounds	Excess Spaces Around Subfields
Brief and Provisional Records

  Incorrect Representation of Diacritics

Some libraries have found words in their records that have incorrectly-represented diacritical characters. Example: fran cais (null character which causes a break and incorrect indexing and retrieval)

Source of the problem: either mis-keying, incorrect characters provided by a vendor, deriving records with this problem, or in some cases NOTIS has not support specific characters in its loaders. The problem appears to be more widespread in older records.

Solution: FCLA is developing a program that will correct some of these problems. During test loads of data into ALEPH it will be important to compare any problems with diacritics displays in ALEPH with the source records in NOTIS to determine if the problem was created during data conversion or if the problem existed on NOTIS.

  Call Number Cleanup

For accurate loading and indexing of call numbers on the new system, it is critical that your NOTIS call numbers be correctly identified by Classification Type Code. You might want to create an ARROW report listing call numbers designated as "O" (other class scheme) "Y" (accession-type number) to determine if those call numbers have been correctly classified. Or, you might already be aware of particular collections that require Class. Type Code corrections. !

Call Number Reports:

  Brief and Provisional Records

There are two concerns about brief and provisional records:

1. Some of these records are expected to be replaced by fuller records from batch loads, and it’s important to keep track of the batch loads during the migration process to make sure that any brief records migrated to the new system are correctly overlaid/replaced by loads to the new system.
2. Any records with 9XX fields instead of conventional MARC tags will need to be carefully tracked to make sure that they are correctly loaded into the new system.

  Ticklers

Your 035 "tickler" fields are used for a number of purposes:

1. To identify the source of the record.
2. To match and replace records during batch loads.

Potential problem:
NOTIS loaders have been programmed to make extensive use of ticklers in matching and evaluating records for overlay and replacement. We should pay careful attention to this aspect of the new system to determine if and how this functionality can be recreated.