Skip to content

Transactional Reporting

OverDrive has no Day-1 functionality for transactional reporting. An interim process is still pending a dedicated meeting — the impacted reports have to be outlined before a workaround can be agreed, so there is no removal timeline yet.

Interim process being finalized

The interim approach for transactional reports is still being finalized. Until it's published here, escalate any transactional-reporting need to Reporting / Analytics.

When this applies

A transactional report is needed during the go-live period and OverDrive cannot yet produce it.

The workaround

  1. When a transactional report is needed, escalate to Reporting / Analytics — an interim source has not yet been agreed. (Reporting / Analytics)

Go-live & cutover notes

Still to be agreed

  • Outline the specific transactional reports impacted by the lack of Day-1 functionality. (Reporting / Analytics)
  • For each impacted report, agree an interim source — a VAST report, the datalake, or a manual pull. (Reporting / Analytics)
  • Define who produces and distributes the interim reports, and on what cadence. (Reporting / Analytics)
  • A dedicated transactional-reporting alignment meeting is still to be scheduled; it has not been held yet. (Reporting / Analytics)