Comment 5 for bug 1786524

Thinking about this some more as an Evergreen feature there is some reworking to do for a proper 3.6+ patch version. The biggest is the in database logging. The current script assumes no native Evergreen tracking of events and creates a logging table in schema patron_loader to log events such as when a match point can not be found for an account and so on.

Do we want to put a loading log table in the actor schema? That would also allow for field mapper entries for regular reports?