- Product: Voyager
- Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare
Troubleshooting record deletions in Voyager extract for Primo.
The Voyager deleted records files in /rpt are used.
The locations of the Voyager del* directory and files are configured in the PrimoExp-* .ini files.
The delete* files in /rpt are given a timestamp after processing by the extract.
In the deleted records a "deleted" flag is added to the xml:
If your deleted records from Voyager are not being deleted in Primo, examine them in the /rpt directory to see when the last time a delete* file was processed (i.e., timestamped). Also check the extract log files to see if any errors have been logged.
You should periodically check your extract logs on the Voyager server – it’s a recommended Best Practice to make sure your extracts are running without issue and completing properly. The deletes are processed near the end of the extract process, so if you don’t see recently timestamped delete files, it is important to check the logs to make sure you’re seeing the extracts complete fully.
- Why do we have so many record delete files in our /rpt directory?
- Are deleted bibs, mfhds, items archived?
- Article last edited: 04-Dec-2020