Atlas has handled support requests that are the result of loads being run and courses being entered into the courses table for a semester that has not yet been entered into the Customization Manager's Semesters table. This forces the new courses to associate with the most current course that is available and it overwrites the actual dates and semesters of the courses, causing quite a bit of trouble (enhancement request already exists in UV). As courses aren't updated by new loads (another enhancement that exists in UV) the identification and update of these entries is difficult and must be done manually. These problems would be fixed by updates to the load process, but the problems also wouldn't exist if it weren't difficult to remember that a new semester needs to be entered.

Sometimes future semesters are pre-entered as a batch many years in advance, or during implementation, maybe even by someone who no longer works with Ares, and since it's not a regularly occurring task, nobody was told to follow up years from now and enter more semesters - or even that this is required. It would be nice if there was some sort of alert in the Staff Client that indicated that there were no more semester entries that were beyond X amount of days in the future. So, a site could say, show me an alert if the last semester entry is going to end within the next 90 days, etc. These would have to allow a fairly large amount of days, as course and user loads often contain courses that are many months in the future.