Managing Large Repair Batches

Use repeatable batches instead of one overwhelming rescue attempt.

Older libraries, or ones that have moved drives a few times over the years, can turn up genuinely large numbers of broken paths, history in particular tends to accumulate a lot of stale entries over time. Facing a workbook with hundreds of rows in one sitting is a good way to lose track of what you’ve actually reviewed.

Instead, work in rounds. Filter or scope a batch down to something reviewable, work through it properly, validate, import, and re-run a Healthcheck to see your progress. Then move on to the next batch. It’s less dramatic than trying to clear everything in one go, but it’s much easier to stay confident in what you’ve actually checked.

This is where understanding Status column helps.

  • Only Not Found rows can be Autofixed
  • Only Autofix, CrossRef and Match rows, and Not Found rows with a new path, are validated
  • Only Validated rows are imported, plus rows marked Delete on the Database worksheet

But there are a couple of key things to remember:

  1. Re-running a /stage:export will replace all rows in the worksheet for the specified repair
  2. Only update the Status on rows you change yourself

There are a few scenarios a batched repair may help:

  • It’s all gone Pete Tong (wrong) – So you have a whole lot of repairs that need sorting
  • Special event – You have a specific event coming up and you need to make sure your most played and those killer playlists are ready to go
  • Time Poor – you just haven’t got enough hours in the day

I’ve made every attempt to make sure VDJTools works for DJs.

Good luck with your repairs make sure you spread the word and visit us on our socials and let us know how you got on.

Healthcheck · History Repair · Folders Repair