After Alma submitted records to OCLC, OCLC will process the records and generate data sync processing reports, which can be viewed in the /xfer/metacoll/reports folder using FTP service. Details of reports can be found here.
For e-book collection data sync, the Local Holdings Record Processing Exception Summary (Lbd Exception Report) is usually the most useful. which includes the details of errors that OCLC WorldCat data sync couldn't process. Not every submitted file has this Lbd Exception Report.
This report lists each holding's processing status. If a title is marked as "LBD_CREATE", it means the holding is successfully claimed. If a title is marked as "LBD_REJECTED", it means the holding is not successfully claimed. Those rejected titles need to be reviewed manually.
This error occurs if two different records (that match to different OCNs) are sent with the same Local system number and holdings are requested for both records, then Local Bib Data will only be created on one record.
To check which OCN is associated with LSN (local system number, MMS ID), one could go to WCM > Record Manager > Use LBD search
OCLC # is located on the right bottom corner of the result.
Currently, there's no effective way to batch search OCLC's ocn using LSN. We have created a Python Jupyter Notebook to help with batch searching. The script can search LSNs in a TXT file one by one. Users will need to record the LSNs' OCN from the result on the right.
If an OCN found in OCLC does not match with the LSN, or if an OCN cannot be found in OCLC, titles may have "other error." To solve this error: