Rarely, an exporter job will run in which no qualifying records are fetched from Sierra (e.g., during times when the library is closed and there were no updates to catalog records the previous day). Recent changes to tasks (JobPlan implementation, etc.) did not take this into account, leading to the error described in issue #46. This adds a check during job initialization and logs an appropriate message if no records were found, bypassing the code path that raised the error.
Also: _initialize_job_plan was a private function that was no longer used but hadn't been removed, so this removes that, as well.
Rarely, an exporter job will run in which no qualifying records are fetched from Sierra (e.g., during times when the library is closed and there were no updates to catalog records the previous day). Recent changes to tasks (JobPlan implementation, etc.) did not take this into account, leading to the error described in issue #46. This adds a check during job initialization and logs an appropriate message if no records were found, bypassing the code path that raised the error.
Also:
_initialize_job_planwas a private function that was no longer used but hadn't been removed, so this removes that, as well.