Replicated record not handled in local library

Question

A record which was sent from central library to local library via replication (handled correctly in the replication log files) was not updated in the local library. Why?

Answer

This is caused by a concurrent access on a specific record by a cataloger and by cataloger BATCH-UPD (for the replication). Is a record opened in cataloging module, e.g. for correction and at the same time this record is sent (replicated) from the central library a warning “Record updated by user BATCH-UPD” appears. When this warning is ignored the replication will be refused.

Additional Information

Only relevant for libraries which receive record from a central catalog.

Category: Background processing (500)

Subject: Batch (500)

• Article last edited: 10/8/2013