Currently, the Multi-Year Plan and the Course Admin pages sort courses alphabetically by catalog number, which means that a course like CS 50 is appearing after all the 100, 200, and 300 level courses. We should instead be sorting numerically, as we do on the Courses Table.
There are numberInteger and numberAlphabetical fields on the Course entity that we can use to accomplish this. That should be relatively straightforward to add to the Course admin, but the multi-year plan is using a View that does not include those fields, so I suggest we either:
Add numberInteger and numberAlphabetical to the View (which will need a new migration)
Join the Course repository to the MultiYearPlanView in the service
Currently, the Multi-Year Plan and the Course Admin pages sort courses alphabetically by catalog number, which means that a course like CS 50 is appearing after all the 100, 200, and 300 level courses. We should instead be sorting numerically, as we do on the Courses Table.
There are
numberIntegerandnumberAlphabeticalfields on theCourseentity that we can use to accomplish this. That should be relatively straightforward to add to the Course admin, but the multi-year plan is using a View that does not include those fields, so I suggest we either:numberIntegerandnumberAlphabeticalto the View (which will need a new migration)Courserepository to theMultiYearPlanViewin the serviceThen replace
with
in
CourseInstanceService#getMultiYearPlan.