Skip to main content
OCLC Support

My Files reports for Bibliographic or Delete WorldCat Holdings collections

Learn about data sync collections reports included in My Files. These include processing results for bibliographic records, local holdings records, WorldCat holdings updates, and local bibliographic data records as well as My Library Records.

 Note: The following reports are currently only produced for Bibliographic or Delete WorldCat Holdings data sync collections.

Report file naming convention

Each report follows the same file naming convention to better identify the original file the report represents as well as ensuring that file names are unique. The standard file name format is:

[File sender’s OCLC symbol]-[OCLC collection symbol].[Collection ID].[Upload sub-directory].D[Date received (YYYYMMDD)].T[Time received (HHMMSSFFF)].[Original filename].[Report name]

 

File name object Description
File sender's OCLC symbol The OCLC account sending the file.
OCLC collection symbol  The OCLC collection symbol.
Collection ID The unique seven-digit number generated when a data sync collection is saved or submitted.
Upload sub-directory Directory where the file was sent (BIB or LHR).
Date received (YYYYMMDD) The date the file was received.
Time received (HHMMSSFFF) The 24 hour time (EST) the file was received.
Original filename The original file name given by the institution.
Report name The report name.

Bibliographic Record Processing reports

Bibliographic Processing Report

The Bibliographic Processing Report encapsulates every system-recognizable bibliographic record received within a file. A bibliographic record is considered recognizable when the file is parsed into individual records at the beginning of processing and the record is assigned a system key, which is used to track the record through processing.

The provided metadata within the Bibliographic Processing Report is per record and gathered based on collection setup, record content, and actions taken on the bibliographic record.

Output location: Metadata > My Files > Downloads > Reports

Example file name: OCWMS-OCWMS.1234567.IN.BIB.D20200505.T092612933.1234567.OCWMS.OriginalFilename.mrc.BibProcessingReport

Report details

The pipe delimited file is divided into the following columns, per record.

 Note: Headings are not provided in this report to promote ease of use across multiple systems/applications.

Column Description
bibKey A unique processing-assigned value per record that helps to accurately target and identify precise records.
Isn The Local System Control Number (LSN) can be used to help you identify records that were not successfully processed.
incomingOcn A value will only be provided when all of the following conditions are met. The bibliographic record was able to be parsed, the collection setup provided one or more potential locations to obtain a value, and a value was found in the designated location.
 

 Note: When more than one location is provided to obtain the OCN, the first value that appears to be a valid OCN from the first provided location is used for processing. If any of these conditions are not met, there will be no value provided for that individual record.

ocn The OCLC Control Number (OCN) is a unique accession number assigned by the OCLC system when a record is added to WorldCat. Used to search for records.
bibAction The resulting bibliographic action.
 
Action Description
create The number of bibliographic records added to WorldCat through the Data Sync platform. 
unresolved The number of bibliographic records that were added to WorldCat but not fully indexed through the Data Sync platform. Library holdings have been attached to these records.
match The number of bibliographic records that could only match to an existing WorldCat record through the Data Sync platform.

Though a match was found in WorldCat, no replace or field transfer actions against the WorldCat record were performed. 
replace The number of bibliographic records that replaced an existing record in WorldCat through the Data Sync platform. A holding set is attempted and the actual holding update can be confirmed in the Holdings Report.
field transfer The number of bibliographic records that had at least one field merged into the Master OCLC record through the Data Sync platform. A holding set is attempted and the actual holding update can be confirmed in the Holdings Report
exclude The number of bibliographic records excluded from processing through the Data Sync platform. A record will be assigned “exclude” because your library requested this setting in the sync collection profile.
data error The number of bibliographic records that encountered a data related issue that did not result in complete processing.
 

 Note: Errors will be provided in the Bibliographic Exception Report. Records will need to be corrected and resubmitted if processing is desired.

process error The number of bibliographic records that encountered a processing related issue that did not result in complete processing.
 

 Note: Errors will be provided in the Bibliographic Exception Report. Records will need to be corrected and resubmitted if processing is desired.

no action The number of bibliographic records that resulted in no match and no further action was made with the record.

Example: A record intended to cancel did not find a match.
others The number of bibliographic records that encountered another error type (not data or processing). Please report these when encountered for further diagnostic support.
Bibliographic Processing Report - Example
Bibliographic Processing Report - Example

Bibliographic Processing Summary Report

The Bibliographic Processing Summary Report contains the corresponding statistics for the Bibliographic Processing Report. The visual table provides the quantitative value per each bibliographic action within a file. The numeric values provided in the table sum up to the total number of system-recognizable bibliographic records received within a corresponding file. A bibliographic record is considered recognizable when the file is parsed into individual records at the beginning of processing and the record is assigned a system key, which is used to track the record through processing.

Output location: Metadata > My Files > Downloads > Reports

Example file name: OCWMS-OCWMS.1234567.IN.BIB.D20200505.T092612933.1234567.OCWMS.OriginalFilename.mrc.BibSummaryReport

 Note: This report is currently available via OCLC's file exchange service. In the future, it will only be available via OCLC Usage Statistics.

Report details

The following are captured per symbol, per file.

Column Description
bibAction
Action Description
replace The number of bibliographic records that replaced an existing record in WorldCat through the Data Sync platform. A holding set is attempted and the actual holding update can be confirmed in the Holdings Report.
field transfer The number of bibliographic records that had at least one field merged into the Master OCLC record through the Data Sync platform. A holding set is attempted and the actual holding update can be confirmed in the Holdings Report
match The number of bibliographic records that could only match to an existing WorldCat record through the Data Sync platform.

Though a match was found in WorldCat, no replace or field transfer actions against the WorldCat record were performed. 
create The number of bibliographic records added to WorldCat through the Data Sync platform. 
exclude The number of bibliographic records excluded from processing through the Data Sync platform. A record will be assigned “exclude” because your library requested this setting in the sync collection profile.
no action The number of bibliographic records that resulted in no match and no further action was made with the record.

Example: A record intended to cancel did not find a match.
data error The number of bibliographic records that encountered a data related issue that did not result in complete processing.
 

 Note: Errors will be provided in the Bibliographic Exception Report. Records will need to be corrected and resubmitted if processing is desired.

process error The number of bibliographic records that encountered a processing related issue that did not result in complete processing.
 

 Note: Errors will be provided in the Bibliographic Exception Report. Records will need to be corrected and resubmitted if processing is desired.

unresolved The number of bibliographic records that were added to WorldCat but not fully indexed through the Data Sync platform. Library holdings have been attached to these records.
Count of occurrence within the file The number of times the bibAction occurs within the file.
filename The report file name in which the bibAction occurred. 
Bibliographic Processing Summary Report - Example
Bibliographic Processing Summary Report - Example

Bibliographic Cross Reference Reports

The Bibliographic Processing Cross Reference Report and Bibliographic Processing Unresolved Cross Reference Report replace the two current cross reference reports for data sync collections out of Collection Manager. The Bibliographic Processing Cross Reference Report includes only records that resulted in one of the following bibActions: create, match, replace, or field transfer. The Bibliographic Processing Unresolved Cross Reference Report includes only records that resulted in a bibAction of unresolved.

Output location: Metadata > My Files > Downloads > Reports

Example file name:

Bibliographic Processing Cross Reference Report:
OCWMS-OCWMS.1234567.IN.BIB.D20200505.T092612933.1234567.OCWMS.OriginalFilename.mrc.BibCrossRefReport

Bibliographic Processing Unresolved Cross Reference Report:
OCWMS-OCWMS.1234567.IN.BIB.D20200505.T092612933.1234567.OCWMS.OriginalFilename.mrc.BibUnresolvedCrossRefReport

Report details

Both reports remain tab delimited files divided into the following columns, per record.

 Note: Headings are not provided in this report to promote ease of use across multiple systems/applications.

Column Description
incomingLsn A value will only be provided when all of the following conditions are met. The bibliographic record was able to be parsed, the collection setup provided one or more potential locations to obtain a value, and a value was found in one of the designated locations within the record. When more than one location is provided to obtain the LSN, the first value from the first provided location is used for processing. If any of these conditions are not met, there will be no value provided for the corresponding record.
 

 Note: If there is an error before getting the LSN or an error in determining the LSN, the record’s sequence number will be provided as the incoming LSN. A records sequence number is determined based on the record’s position within the file.

ocn The OCLC Control Number (OCN) is a unique accession number assigned by the OCLC system when a record is added to WorldCat. Used to search for records.
Bibliographic Processing Cross Reference Report - Example
Bibliographic Processing Cross Reference Report - Example
Bibliographic Processing Unresolved Cross Reference Report - Example
Bibliographic Processing Unresolved Cross Reference Report - Example

Bibliographic Exception Report

The Bibliographic Exception Report contains unresolved records that were added to WorldCat staging due to containing critical/server validation error(s) and records that did not complete processing due to a process error or data error. All errors for a record will be represented in unique pairs: key to error. This means that a bibliographic record key may be repeated more than once within a report in order to provide the complete set of errors associated with that record.

Output location: Metadata > My Files > Downloads > Reports

Example file name: OCWMS-OCWMS.1234567.IN.BIB.D20200505.T092612933.1234567.OCWMS.OriginalFilename.mrc.BibExceptionReport

Report details

The pipe delimited file is divided into the following columns, per key and error pair.

 Note: Headings are not provided in this report to promote ease of use across multiple systems/applications.

Column Description
bibKey A unique processing-assigned value per record that helps to accurately target and identify precise records.
lsn The Local System Control Number (LSN) can be used to help you identify records that were not successfully processed.
incomingOcn A value will only be provided when all of the following conditions are met. The bibliographic record was able to be parsed, the collection setup provided one or more potential locations to obtain a value, and a value was found in the designated location.
 

 Note: When more than one location is provided to obtain the OCN, the first value that appears to be a valid OCN from the first provided location is used for processing. If any of these conditions are not met, there will be no value provided for that individual record.

ocn The OCLC Control Number (OCN) is a unique accession number assigned by the OCLC system when a record is added to WorldCat. Used to search for records.
errorType
Type Description
Data Error Errors that result from a data issue.
Process Error Errors that result from a system issue.
Validation Error Errors extrapolated by comparing the resulting record with the rules within validation.
validationErrorLevel
Level Description
Critical Critical errors include: no OCLC control number; invalid OCLC control number; invalid OCLC institution symbol.
Minor Minor errors include: invalid indicator values; incorrect encoding level.
Severe Severe errors include: invalid record status value; required field missing; required subfield missing; incorrectly linked fields; presence of more than one non-repeatable field; presence of more than one non-repeatable subfield; invalid characters.
errorMessage Error messages are only provided for the following error types:
  • Validation
  • Data Error
Bibliographic Exception Report - Example
Bibliographic Exception Report - Example

Local Holdings Record Processing reports

See My Files reports for more information.

WorldCat Holdings Processing reports

Holdings Processing Report

The Holdings Processing Report records, per symbol, only the system-recognizable bibliographic records received within a file that attempt a holdings action. A bibliographic record is considered recognizable when the file is parsed into individual records at the beginning of processing and the record is assigned a system key, which is used to track the record through processing. An attempted holdings action includes the attempt to set or to delete a holding.

The provided metadata within the Holdings Processing Report is per record and symbol, gathered based on collection setup, record content, and holdings action requested on the bibliographic record.

Output location: Metadata > My Files > Downloads > Reports

Example file name: OCWMS-OCWMS.1234567.IN.BIB.D20200505.T092612933.1234567.OCWMS.OriginalFilename.mrc.HoldingProcessingReport

Report details

The pipe delimited file is divided into the following columns, per symbol, per record.

 Note: Headings are not provided in this report to promote ease of use across multiple systems/applications.

Column Description
collectionSymbol The OCLC collection symbol.
oclcSymbol The OCLC symbol for the account sending the file.
bibKey A unique processing-assigned value per record that helps to accurately target and identify precise records.
incomingLSN A value will only be provided when all of the following conditions are met.  The bibliographic record was able to be parsed, the collection setup provided one or more potential locations to obtain a value, and a value was found in one of the designated locations within the record.  When more than one location is provided to obtain the LSN, the first value from the first provided location is used for processing.  If any of these conditions are not met, there will be no value provided for the corresponding record.
 

 Note: If there is an error before getting the LSN or an error in determining the LSN, the record’s sequence number will be provided as the incoming LSN.  A records sequence number is determined based on the record’s position within the file.

incoming OCN A value will only be provided when all of the following conditions are met.  The bibliographic record was able to be parsed, the collection setup provided one or more potential locations to obtain a value, and a value was found in the designated location.
 

 Note: When more than one location is provided to obtain the OCN, the first value that appears to be a valid OCN from the first provided location is used for processing.  If any of these conditions are not met, there will be no value provided for that individual record.

ocn The OCLC Control Number (OCN) is a unique accession number assigned by the OCLC system when a record is added to WorldCat. Used to search for records.
holdingsAction
Action Description
HOLDING_SET The number of holdings set in WorldCat through the Data Sync platform.
HOLDING_ALREADY_SET The number of holdings sets requested through the Data Sync platform for which WorldCat bibliographic record matches were found but records already had the library's holding attached. No action was taken besides resetting the transaction date.
HOLDING_DELETED The number of holdings deleted when matches are made against WorldCat bibliographic records through the Data Sync platform. A holding already exists for the requesting institution and the request for the holding to be deleted is successful.
HOLDING_ALREADY_DELETED The number of holdings deletes requested through the Data Sync platform for which WorldCat bibliographic record matches were found, but a holding does not already exists for the requesting institution and therefore the request for the holding to be deleted is unsuccessful.
HOLDING_SET_FAILURE The number of holdings sets requested through the Data Sync platform, where the set holding is attempted but is not successful owing to a system problem. No separate error messages provided. Holding set/delete failure is the error and trigger to know that the library may want to process again.
HOLDING_DELETE_FAILURE The number of holdings deletes requested through the Data Sync platform, where the set holding is attempted but is not successful owing to a system problem. No separate error messages provided. Holding set/delete failure is the error and trigger to know that the library may want to process again.
HOLDING_UNKNOWN_RESULT The number of holdings actions requested through the Data Sync platform, where the holdings action does not conform other defined holdings actions categories. No separate error messages provided. Holding set/delete failure is the error and trigger to know that the library may want to process again.
 
Holdings Processing Report - Example
Holdings Processing Report - Example

Holdings Summary Report

The Holdings Summary Report contains the corresponding statistics for the Holdings Report. The visual table provides the quantitative value per institution for each holdings action attempted within a file. The numeric values provided per institution in the table sum up to the total number of attempted holdings actions within the corresponding file. An attempted holdings action includes the attempt to set or the attempt to delete a holding.

Output location: Metadata > My Files > Downloads > Reports

Example file name: OCWMS-OCWMS.1234567.IN.BIB.D20200505.T092612933.1234567.OCWMS.OriginalFilename.mrc.HoldingSummaryReport

 Note: This report is currently available via OCLC's file exchange service. In the future, it will only be available via OCLC Usage Statistics.

Report details

The following are captured per symbol, per file.

Column Description
institutionSymbol The group/collection symbol.
instSymbol The holding institution symbol.
sum of HOLDING_SET The sum of the number of holdings set in WorldCat through the Data Sync platform.
sum of HOLDING_ALREADY_SET The sum of the number of holdings sets requested through the Data Sync platform for which WorldCat bibliographic record matches were found but records already had the library's holding attached. No action was taken besides resetting the transaction date.
sum of HOLDING_DELETED The sum of the number of holdings deleted when matches are made against WorldCat bibliographic records through the Data Sync platform. A holding already exists for the requesting institution and the request for the holding to be deleted is successful.
sum of HOLDING_ALREADY_DELETED The sum of the number of holdings deletes requested through the Data Sync platform for which WorldCat bibliographic record matches were found, but a holding does not already exists for the requesting institution and therefore the request for the holding to be deleted is unsuccessful.
sum of HOLDING_SET_FAILURE The sum of the number of holdings sets requested through the Data Sync platform, where the set holding is attempted but is not successful owing to a system problem. No separate error messages provided. Holding set/delete failure is the error and trigger to know that the library may want to process again.
sum of HOLDING_DELETE_FAILURE The sum of the number of holdings deletes requested through the Data Sync platform, where the set holding is attempted but is not successful owing to a system problem. No separate error messages provided. Holding set/delete failure is the error and trigger to know that the library may want to process again.
sum of HOLDING_UNKNOWN_RESULT The sum of the number of holdings actions requested through the Data Sync platform, where the holdings action does not conform other defined holdings actions categories. No separate error messages provided. Holding set/delete failure is the error and trigger to know that the library may want to process again.
 
filename The report file name in which the holdingsAction occurred. 
Holdings Summary Report - Example
Holdings Summary Report - Example

Local Bibliographic Data Processing reports

LBD Processing Report

The LBD Processing Report records every LBD requested, per symbol and OCN while processing a file. An LBD is requested any time there is holdings set requested on an OCN (i.e., for each set holding request, there is an associated LBD request).

Output location: Metadata > My Files > Downloads > Reports

Example file name: OCWMS-OCWMS.1234567.IN.BIB.D20200505.T092612933.1234567.OCWMS.OriginalFilename.mrc.LbdProcessingReport

Report details

The pipe delimited file is divided into the following columns, per LBD record.

 Note: Headings are not provided in this report to promote ease of use across multiple systems/applications.

Column Description
collectionSymbol The OCLC collection symbol.
oclcSymbol The OCLC symbol for the account sending the file.
bibKey A unique-processing assigned value per record that helps to accurately target and identify precise records.
owningInstSym (confirmed symbol) The confirmed symbol when making a request.
incomingLSN A value will only be provided when all of the following conditions are met. The bibliographic record was able to be parsed, the collection setup provided one or more potential locations to obtain a value, and a value was found in one of the designated locations within the record. When more than one location is provided to obtain the LSN, the first value from the first provided location is used for processing. If any of these conditions are not met, there will be no value provided for the corresponding record.
 

 Note: If there is an error before getting the LSN or an error in determining the LSN, the record’s sequence number will be provided as the incoming LSN. A records sequence number is determined based on the record’s position within the file.

lsnlnLbd A value will be provided when an LBD record is created or deleted. This value will be the LSN found in the LBD record. When no LSN is provided by the institution in the incoming record, a system LSN is generated and this value will persist to the report and in LBD record when an LBD record is created. If an LBD record is rejected due to the LSN being associated with a different OCN, there will be no value provided in the report since no LBD record could be created. These records will appear on the LBD Error report.
incomingOCN A value will only be provided when all of the following conditions are met. The bibliographic record was able to be parsed, the collection setup provided one or more potential locations to obtain a value, and a value was found in the designated location.
 

 Note: When more than one location is provided to obtain the OCN, the first value that appears to be a valid OCN from the first provided location is used for processing. If any of these conditions are not met, there will be no value provided for that individual record.

ocn The OCLC Control Number (OCN) is a unique accession number assigned by the OCLC system when a record is added to WorldCat. Used to search for records.
lbdNum A value will only be provided when an LBD record is created. The value provided will represent the LBD Number associated with the LBD record.
lbdAction
Action Description
LBD_CREATED The number of LBD records successfully set (without errors?) through the Data Sync platform and associated with an OCN in WorldCat.
LBD_UNRESOLVED The number of LBD records that could not be successfully set through the Data Sync platform. These could be LBD records that contain errors in themselves, or LBD records that are associated with bibliographic records that are unresolved.
LBD_REJECTED The number of LBD records when LBD is intended to be created but is rejected when attempted.
LBD_PROCESSING_ERROR The number of LBD record sets requested through the Data Sync platform, where the set LBD is attempted but is not successful owing to a system problem.
 

 Note: Errors will be provided in the LBD Exception Report. Records will need to be resubmitted if processing is desired.

LBD_OTHERS The number of LBD actions requested through the Data Sync platform, where the LBD action does not conform to other defined LBD actions categories.
 

 Note: Errors will be provided in the LBD Exception Report. Records will need to be resubmitted if processing is desired.

LBD Processing Report - Example
LBD Processing Report - Example

LBD Summary Report

The LBD Summary Report contains the corresponding statistics for the LBD Processing Report. The visual table provides the quantitative value per institution for each LBD request attempted within a file. The numeric values provided per institution in the table sum up to the total number of attempted LBD requests within the corresponding file. An LBD is requested any time there is holdingAction == ‘a’. Ie, for each set holding request, there is an associated LBD request.

Output location: Metadata > My Files > Downloads > Reports

Example file name: OCWMS-OCWMS.1234567.IN.BIB.D20200505.T092612933.1234567.OCWMS.OriginalFilename.mrc.LbdSummaryReport

 Note: This report is currently available via OCLC's file exchange service. In the future, it will only be available via OCLC Usage Statistics.

Report details
The following are captured per symbol, per file.
Column Description
lbdAction
Action Description
LBD_REJECTED The number of LBD records when LBD is intended to be created but is rejected when attempted.
LBD_CREATED The number of LBD records successfully set (without errors?) through the Data Sync platform and associated with an OCN in WorldCat.
LBD_UNRESOLVED The number of LBD records that could not be successfully set through the Data Sync platform. These could be LBD records that contain errors in themselves, or LBD records that are associated with bibliographic records that are unresolved.
LBD_PROCESSING_ERROR The number of LBD record sets requested through the Data Sync platform, where the set LBD is attempted but is not successful owing to a system problem.
 

 Note: Errors will be provided in the LBD Exception Report. Records will need to be resubmitted if processing is desired.

LBD_OTHERS The number of LBD actions requested through the Data Sync platform, where the LBD action does not conform to other defined LBD actions categories.
 

 Note: Errors will be provided in the LBD Exception Report. Records will need to be resubmitted if processing is desired.

institutionSymbol The group/collection symbol.
instSymbol The holding institution symbol.
count The number of times the lbdAction occurs within the file.
fileName The report file name in which the lbdAction occurred.
LBD Summary Report - Example
LBD Summary Report - Example

LBD Exception Report

The LBD Exception Report contains unresolved LBD records that were added to WorldCat staging due to containing critical/server validation error(s) and LBD records that did not complete processing due to a process error or data error. All errors for an LBD record will be represented in unique pairs: key to error. This means that a bibliographic record key may be repeated more than once within a report in order to provide the complete set of errors associated with that record.

Output location: Metadata > My Files > Downloads > Reports

Example file name: OCWMS-OCWMS.1234567.IN.BIB.D20200505.T092612933.1234567.OCWMS.OriginalFilename.mrc.LbdExceptionReport

Report details

The pipe delimited file is divided into the following columns, per LBD record and error pair.

 Note: Headings are not provided in this report to promote ease of use across multiple systems/applications.

Column Description
oclcSymbol The OCLC symbol for the account sending the file.
bibKey A unique-processing assigned value per record that helps to accurately target and identify precise records.
incomingLSN A value will only be provided when all of the following conditions are met. The bibliographic record was able to be parsed, the collection setup provided one or more potential locations to obtain a value, and a value was found in one of the designated locations within the record. When more than one location is provided to obtain the LSN, the first value from the first provided location is used for processing. If any of these conditions are not met, there will be no value provided for the corresponding record.
 

 Note: If there is an error before getting the LSN or an error in determining the LSN, the record’s sequence number will be provided as the incoming LSN. A records sequence number is determined based on the record’s position within the file.

lsnlnLbd A value will be provided when an LBD record is created or deleted. This value will be the LSN found in the LBD record. When no LSN is provided by the institution in the incoming record, a system LSN is generated and this value will persist to the report and in LBD record when an LBD record is created. If an LBD record is rejected due to the LSN being associated with a different OCN, there will be no value provided in the report since no LBD record could be created. These records will appear on the LBD Error report.
incomingOCN A value will only be provided when all of the following conditions are met. The bibliographic record was able to be parsed, the collection setup provided one or more potential locations to obtain a value, and a value was found in the designated location.
 

 Note: When more than one location is provided to obtain the OCN, the first value that appears to be a valid OCN from the first provided location is used for processing. If any of these conditions are not met, there will be no value provided for that individual record.

ocn The OCLC Control Number (OCN) is a unique accession number assigned by the OCLC system when a record is added to WorldCat. Used to search for records.
lbdNum A value will only be provided when an LBD record is created. The value provided will represent the LBD Number associated with the LBD record.
errorType
Type Description
Data Error Errors that result from a data issue.
Process Error Errors that result from a system issue.
Other Error Used for LBD records. When the LBD record is unresolved due to the associated Bibliographic record's error and not an error within the LBD record. (i.e., Bib is unresolved and therefore the LBD record must also be unresolved regardless of its own validation errors.)
errorLevel
Level Description
Critical Critical errors include: no OCLC control number; invalid OCLC control number; invalid OCLC institution symbol.
Minor Minor errors include: invalid indicator values; incorrect encoding level.
Severe Severe errors include: invalid record status value; required field missing; required subfield missing; incorrectly linked fields; presence of more than one non-repeatable field; presence of more than one non-repeatable subfield; invalid characters.
errorMessage Error messages are only provided for the following error types:
  • Validation
  • Data Error
LBD Exception Report - Example
LBD Exception Report - Example

My Library Records

My Library Records (Own Record Return)

The Own Record return file only includes bibliographic records that resulted in at least one successful holding set/already set action on a WorldCat bibliographic record (either existing or newly created as part of processing). The current WorldCat OCN is inserted in the 035 $a tag of the bibliographic record being returned in the My Library Records file. Currently My Library Records can only be delivered as .mrc files.

Output location: Metadata > My Files > Downloads > Reports

Example file name: OCWMS-OCWMS.1234567.IN.BIB.D20200505.T092612933.1234567.OCWMS.OriginalFilename.mrc.MyLibraryRecords.mrc

 Note: The records returned are not always exact to what was sent due to the transformation and record building processes currently implemented to create the My Library Records files.

 

  • Was this article helpful?