In examining staging and production, the file uploaded to rackspace hasn't been updated since June, and with a dedicated guest not running for delayed_jobs, I'm guessing that ' odc:generate_dataset_csv' may not have run (or perhaps correctly) for a while.
Testing against staging, I can see the data queries look OK, and the html view certainly seems to be showing all the datasets that are current.
I suggest that we turn on config for delayed_job to run from script as well as explicitly adding back the delayed_job container (is there a cost for this?) - either way should give us some means to ensure that the rake job: odc:generate_dataset_csv can be run.
In examining staging and production, the file uploaded to rackspace hasn't been updated since June, and with a dedicated guest not running for delayed_jobs, I'm guessing that ' odc:generate_dataset_csv' may not have run (or perhaps correctly) for a while. Testing against staging, I can see the data queries look OK, and the html view certainly seems to be showing all the datasets that are current. I suggest that we turn on config for delayed_job to run from script as well as explicitly adding back the delayed_job container (is there a cost for this?) - either way should give us some means to ensure that the rake job: odc:generate_dataset_csv can be run.