Add schedule-level data options

[rpruim]

Raymond would really like to see the schedules labeled with academic year.

For chairs importing a past schedule, this academic year will be incorrect, and requiring manual editing of every section to update this is a pain. (And I don't trust all chairs to do it correctly in an external tool like Excel.)

So I'm wondering how hard it would be to collect some schedule-level data. Academic year could go there. We could export that in each row of the CSV, but not require chairs to hand-edit that field for each section. Other things that could go here might be some sort of version comment like "This is just a draft" or "submitted to the dean on such and such a date", etc.

Or perhaps we could have a mechanism to set some values for all sections (department and academic year would likely be the most useful of these, but perhaps something else?). If we did this, we could still list these values at the section level, but you could update the entire schedule in one go. Perhaps this approach would be easier since all the data storage would be the same, we'd just have to run through all the sections to update the data.

[rpruim]

Thinking a bit about what might be set at a schedule level. Here are some ideas:

• creator (who made this schedule)
• notes (textual notes about the schedule)
  • could be further refined with things like version, status, etc. to handle common "notes" types of things in a more systematic way
• academic year
• default values for new course creation
  • prefix
  • department
  • maybe (?) things like delivery mode

We might also like the ability to apply certain processes to the entire schedule:

• set field to a constant value for field in [academic year, department, delivery mode, etc.]

For the latter, one possible interface is something like this:

Set default value of to [ ] for new sections. [ ] Also update all existing section to this value now.