I seem to have missed this in the last patch, but why is there a separate /forceschedulers that's different from /schedulers?  That means two REST resources for the same underlying object (a scheduler), and suggests that if, for example, a nightly scheduler wants to expose a UI, then it would have to invent a new /nightlyschedulers endpoint.

I'd like to find a *very* general way for schedulers to put a description of their UI into the DB (probably as a JSON string), which is then parsed and rendered by the AngularJS code, with the results transmitted back via a JSONAPI call that's routed to the scheduler (for now, locally, assuming the scheduler is running locally)