Adding views support - implementation suggestions.

I think that adding a views support would be of a huge help since queueing jobs is often about bulk/batch node operations/actions and their monitoring. A few issues already come from the limitations of the job_queue logs. I think that this feature could help working that out.

In my case, it would help me to use the great views_bulk_operations.module consistently:

I use VBO_views to help my team administrating the workflow. Thanks to exposed filters in views, the team can choose multiple nodes according to various criterion, and thanks to VBO, they can assign them a new workflow status.

But I have thousands of nodes and operations had caused PHP timeouts. To prevent from such an issue, Kratib has just implemented a Job_queue support in his last 5.x-dev release of his VBO.module.

But a new issue has emerged, which is that once nodes of a certain workflow_status are queued, they still appear in my views. Indeed, as long as the cron hasn't run, the queued nodes keep the same current status and are still available in my VBO_view because its filter criterion remain unchanged.

As a consequence, the nodes are remaining available for the same operations while they shouldn't. This may cause my team to queue twice the same jobs for a single node as for a thousand nodes. Therefore we may loose the potential benefits of this great Job_queue.module which are preventing server overloads.

Remarks:

- the job_queue logs aren't suitable for monitoring the job status of more than a few dozens of nodes.

- #319654: a callback function is probably a first step to this implementation.

- the views support may offer a placeholder for many other features' implementation, such as #304530: Store and display "job status" information in queue or #319650: log execution time, which could be view fields for example. This would lead to a possible (and probably most-wanted) overriding and customizing feature for the Job_queue logs (currently at admin/logs/job_queue).

- the views support may have many other useful outcomes. Supporters of this feature, you could introduce your own examples down there to illustrate the scale of the possible needs and applications.

- I wish I could, but I can't suggest a proper way to implement this feature request. Would it either be fields or filters for views, I wouldn't know what's best. Here again, suggestions or even patches may be welcome to help the developpers/maintainers.

Many thanks and best regards,

Arsène