Local Fields: 914 and 915

Owned by Cathy Weng
Last updated: Apr 11, 2024 by Peter Green

Two new local fields have been defined for the Library's on-going OCLC data sync task. The data synchronization task integrates Princeton University Library's holdings in WorldCat to accurately reflect our collections and make them visible to our patrons, other libraries, and other users of the Web. The two new local fields will not affect our current cataloging workflow. Please do not change or remove these 2 fields in the records when you see them.

914 field

The 914 is used for the definitive OCLC number captured from the OCLC reports after the data sync process is completed. It serves as a flag when records with a 914 are done with the data sync process and will be excluded for the next time the job is run. Here is one example of the 914 field in Alma:

914 ##  $$a (OCoLC)on1127965719 $$b OCoLC $$d 20221108 $$e unprocessed

Indicator and Subfield Information

Indicators

Both indicator positions are undefined; each contains a blank (#).

Subfield Codes

  1. $a: Definitive OCLC number with the OCLC prefix. Ex.: (OCoLC)on1296122953
  2. $b: Source of number, reserved for future use. Always OCoLC for DataSync.
  3. $c: Action taken by OCLC. Values:

match – (holding was set, no metadata was added to the OCLC record)
replace – (entire OCLC record was replaced; only occurs on new records or records PUL originally contributed)
field transfer – (certain bibliographic fields are eligible for transfer, see https://help.oclc.org/Metadata_Services/WorldShare_Collection_Manager/Understand_record_processing/Data_sync_processing?sl=en#Transfer_[…]aphic_data for which fields are eligible)

  1. $d: date the record was processed. Format:  yyyymmdd   (Ex: 20221117)
  2. $e: State of the field. It will say 'unprocessed' until a job is run that moves the definitive OCLC number from 914$a to the 035. After that job is run, it will say 'processed'.
  3. $f: Raw OCLC number with no prefix. Ex.: 1296122953

915 field

The 915 field is used for reporting the validation errors identified by OCLC from the data sync job.  Certain validation errors will prevent Princeton records from being accepted by OCLC. Those records need to be fixed and resubmitted for data sync. 915 is indexed and searchable in Alma. The Data Quality Group is charged to fix the records. Once a record is fixed, the 915 fields will be removed. If you encounter a 915 when doing cataloging, there is no need to fix it. Leave the task to the Data Quality Group to work on. Here are some examples of the 915 field in Alma:

915 ##  $$a Validation Error $$b SEVERE $$c 1st $6 in 1st 245 has invalid linking data. $$d 20221108 $$e 1347186166      

915 ##  $$a Validation Error $$b CRITICAL $$c Invalid relationship - when $6 in 245 is present, then 880 must be present. $$d 20221108 $$e 1347186166

Indicator and Subfield Information

Indicators

Both indicator positions are undefined; each contains a blank (#).

Subfield Codes

  1. $a: Type of error. Most, if not all, will say 'Validation error.'
  2. $b: Severity of error. See https://help.oclc.org/Metadata_Services/WorldShare_Collection_Manager/Understand_record_processing/Data_sync_processing?sl=en#Record_va[…]ror_levels for more information. Values:
    1. CRITICAL – The most severe errors; records cannot be loaded. 
    2. SEVERE – Errors that significantly impact effective use of the record; further investigation and probable correction required.
    3. MINOR –  Errors that have no significant impact to effective use of the record. Correction is optional.
  1. $c: Error message. Ex.: 1st $6 in 1st 740 has invalid linking data.
  2. $d: Date the record was processed. Format:  yyyymmdd   (Ex: 20221117)
  3. $e: Staging OCLC number. Use this to find the record in the OCLC Staging database and determine whether the record should be enhanced/corrected and produced  (by clicking "Update holdings") in or deleted (by clicking "Delete holdings") from the WorldCat production database.

See also