Regarding @ctweney 's earlier comment: 'Please refactor so that Rosters are 1 controller and 1 model line that can be in either "canvas" or "campus" mode.'

Given the nature of the differences, it *may* be prettier to have two AngularJS controllers and/or two Rails controllers (which inherit or mix-in shared code), and/or to have two top-level model classes (which inherit or mix-in shared code).

In either case, we want to avoid the PR's approach of having a "canvasRosterController.js" which also handles NON-Canvas stuff and a "canvas_rosters_controller.rb" which also handles NON-Canvas stuff. Makes it too confusing to figure out where to look.