PLP Pre-Processing

The purpose of PLP-processing is to ensure that there are no problems in the file–particularly in the System ID and Holdings code fields–before database matching begins.

1. OSMOSIS Global Fixes

The first step in PLP pre-processing is to run the OSMOSIS¹⁾ global fixes on the incoming file. These global fixes correct basic errors in the leader and fixed fields, normalize all primary key fields, correct errors in non-filing indicators, etc.

A complete list of the fixes performed can be found at the top of the following report: OSMOSIS SUMMARY REPORT

If a 'fix' is not desired, it can be turned off by editing the 'plpOsmosisOption.ini' file, located in the 'PLP\Options' folder. Please contact TMQ for assistance in modifying this file.

2. Holdings Code Cleanup

The next step in PLP pre-processing is to dedupe and map the holdings codes in the incoming library file to the field they need to be in during loading to the union catalog. This processing is driven by the options on the Holdings page of the library load profile. For example, the library load profile might map the holdings codes from an 852 $b to the 949 $l used in the union catalog. This step can also be used to add a default holdings code to all records in the library file (useful if the library has only one code and/or does not export holdings records).

3. System Id processing

The last step in PLP-preprocessing is to map the library's System Id from its location in the source file to the field it needs to be in during loading to the union catalog. This processing is driven by the options on the System ID page of the library load profile. The union catalog System Id is typically field 035$a, with an organization code in parens prefixing the number. For example:

 035 $a(DLC)  2009123456 

Note: there is no option to automatically generate a SysId (as there is with holdings codes, for example). This can easily by done, however, by using MARC Global's 'Add Sequential number' option.

About PLP Pre-processing and Self-PLP

PLP-preprocessing should be run on a file even when PLP is not being run. The reason for this is that Self-PLP and PLP share the same code. Thus, the pre-requisites of PLP also become the pre-requisites of Self-PLP. This requirement ensures that Self-PLP will respond to 'match & merge' situations in exactly the same way as PLP, and this in turn permits Self-PLP to be run, automatically and seamlessly, before PLP, to resolve duplicates in the incoming library file.