Skip to main content
OCLC Support

Can Analytics provide a report that tracks or identifies LHR relocations between bibliographic records (Bibs)

Applies to

  • WorldShare Reports
  • WorldShare Record Manager  

Issue

Can Analytics identify when a Local Holdings Record (LHR) has been moved from one bibliographic record (OCN) to another?

Answer

No. Analytics does not provide a report that directly tracks LHR relocations. Analytics is based on periodic snapshots of operational data and reports the current state of records rather than historical changes.

Workarounds 

To identify potential LHR moves:

  1. Export an LHR report containing:

    • LHR Control Number (or another unique LHR identifier)
    • Linked OCN
    • Optional: Last Transaction Date
  2. Create exports from two different points in time.

  3. Compare the exports in Excel, Power BI, or another reporting tool.

If the same LHR identifier is linked to a different OCN in the later export, the LHR has likely been moved.

Example:

LHR Number OCN (Snapshot 1) OCN (Snapshot 2)
123456789 111111111 222222222


The unchanged LHR number and changed OCN indicate a likely relocation.

Alternative Approach

If historical Circulation Item Inventory reports have been saved from the OCLC SFTP server, compare older and newer reports using LHR identifiers or item barcodes to identify OCN changes over time.

Troublshooting : 

No relocations are detected, but a move is suspected
  • Verify that the same LHR identifier (LHR Control Number or barcode) exists in both snapshots.
  • Confirm the snapshots were taken before and after the suspected move occurred.
  • Include the Last Transaction Date in the report to help identify records that were recently updated.
The LHR appears in one report but not the other
  • The LHR may have been created, deleted, or excluded by report filters between snapshot dates.
  • Review report criteria to ensure the same filters were used for both exports.
Multiple records appear to have changed
  • Validate that the comparison is being performed on a unique identifier (LHR Control Number or barcode) rather than title or OCN.
  • Check for duplicate rows or sorting issues in Excel before reviewing the results.
Unsure whether a relocation actually occurred
  • Open the LHR in Record Manager.
  • Note the current linked OCN.
  • Compare it with the OCN recorded in the earlier report snapshot.
  • If the OCN has changed while the LHR identifier remains the same, the LHR was likely relocated.

Verification

To confirm a suspected move:

  1. Open the LHR in Record Manager.
  2. Note the current linked OCN.
  3. Compare it to the OCN recorded in a previous report or export.

If the OCN differs, the LHR has been moved to another bibliographic record.

Additional information

Because Analytics does not retain historical LHR-to-bibliographic record relationships, periodic report exports are required to track changes over time.

Page ID

68663