Terms split across a new year are not correctly imported or represented in the schema (W)

[wildtayne]

When openCloseImport() automatically detects the start/end date of a term here, it appends the entered term year to the day/month supplied in the csv. This is wrong in the case of Winter terms, as they are often split across a new year (start in one year, end in another). This also cannot be correctly represented in the current schema, as each term has exactly one year.

This behavior also results in incorrect section start/end dates here

[afig]

A somewhat related issue with the schema is that there is no constraint for checking whether endDate actually occurs after startDate.

Ideally, we would also make sure that no terms overlap each other, but that seems beyond our current scope. (It would have to be done through a function or trigger.)