UNC-Libraries/Curators-Workbench — Issue #81: Move crosswalk runs to the background (jobs, not builds) 
Author: gregjan
Created: 2011-10-26 14:35:10+00:00
State: open
Labels: crosswalk, performance

Crosswalks currently are triggered whenever the crosswalk definition is saved and might also be trigger under other circumstances. This is because the crosswalk run is currently considered a build. Builds have the disadvantage of locking the workbench while they are running and are designed for short operations. Since crosswalks can potentially be quite long running, they are best moved to background jobs and triggered less frequently.

Jobs will allow workbench UI updates to happen more frequently, providing more active feedback to the user.

The job should be tied in the workbench site for the crosswalk definition, if possible. For instance, if triggered on a crosswalk that is open in the editor, the editor should be the site for job scheduling and in that way edits will be blocked while the job runs.